Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / NASA-PDS/pds-api issues and pull requests

#143 - Update API documentation to have consistent descriptions for the query parameter

Issue - State: closed - Opened by jordanpadams almost 3 years ago - 1 comment
Labels: B12.1, i&t.skip

#141 - Develop github action to create implementation branches for the API

Issue - State: open - Opened by tloubrieu-jpl almost 3 years ago - 3 comments
Labels: enhancement, B12.1, B13.0, icebox, c.search-api, i&t.skip

#140 - Merge unnecessary individual repository

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago - 4 comments
Labels: enhancement, B12.1, i&t.skip

#139 - As a user, I want to see API stable release specifications

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago - 1 comment
Labels: requirement, Epic, B12.1, p.must-have

#137 - As a user, I want to have a detailed description of the API q parameter syntax

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago
Labels: enhancement, B12.1

#136 - Revise the pds-api README so that it gives a perspective on non search api (e.g. doi) from pds

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago - 2 comments
Labels: enhancement, B12.1

#134 - As a user, I want to get a key-value-pair JSON response

Issue - State: closed - Opened by jordanpadams almost 3 years ago - 2 comments
Labels: requirement, B12.1, p.must-have, sprint-backlog

#133 - clarify what `keyword` parameter is for

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago - 1 comment
Labels: enhancement, B12.1

#130 - pds api not able to search using URL parameters

Issue - State: closed - Opened by gxtchen almost 3 years ago - 6 comments
Labels: bug, B12.1, s.low, i&t.issue

#129 - Prep for API v1.0 Release

Issue - State: closed - Opened by jordanpadams almost 3 years ago - 2 comments
Labels: Epic, B12.1, B13.0, theme, proj.registry+api, c.search-api

#126 - Improve products/all endpoint to include all versions of all products

Issue - State: open - Opened by jordanpadams almost 3 years ago
Labels: enhancement, p.should-have, proj.registry+api, icebox, c.search-api

#124 - Changes to API per last tagged release not in SwaggerHub

Issue - State: closed - Opened by jordanpadams almost 3 years ago
Labels: bug, B12.1, s.critical, i&t.skip

#123 - create a super registry+api repository

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago - 2 comments
Labels: B12.1, proj.registry+api, i&t.skip

#122 - analysis of current workflow, ideas for improvment

Issue - State: closed - Opened by tloubrieu-jpl almost 3 years ago - 1 comment
Labels: B12.1, i&t.skip

#112 - As an API client user, I want to consistently and robustly start local servers for development and testing

Issue - State: closed - Opened by nutjob4life about 3 years ago - 10 comments
Labels: enhancement, B12.1, proj.registry+api, i&t.skip

#107 - As an API user, I want to explicitly request the latest version of a product

Issue - State: closed - Opened by jordanpadams about 3 years ago - 1 comment
Labels: requirement, B12.0, p.could-have

#105 - As an API user, I want to know how long a request took to complete

Issue - State: closed - Opened by jordanpadams about 3 years ago - 3 comments
Labels: requirement, B12.0, p.should-have

#104 - Improvements to Keyword Search for Weighting and Suggested Searches

Issue - State: open - Opened by jordanpadams about 5 years ago
Labels: enhancement, Epic, p.should-have, proj.registry+api, icebox, c.search-api

#101 - As a user, I want to receive a JSON response that contains the PDS4 label metadata in JSON format (application/vnd.nasa.pds.pds4+json)

Issue - State: closed - Opened by jordanpadams about 3 years ago - 2 comments
Labels: requirement, Epic, B12.0, B13.0, p.must-have

#99 - As an API user, I want to be able to use the API for free text search

Issue - State: closed - Opened by jordanpadams about 3 years ago - 7 comments
Labels: requirement, Epic, B12.0, p.must-have

#91 - Disable XML and HTML responses from current registry-api-service implementation

Issue - State: closed - Opened by jordanpadams over 3 years ago - 7 comments
Labels: enhancement, B12.0, p.should-have

#88 - As a user,I want to get the list of properties available in summary sorted in alphabetical order

Issue - State: closed - Opened by tloubrieu-jpl over 3 years ago - 3 comments
Labels: duplicate, requirement, p.could-have, proj.registry+api, icebox, c.search-api

#87 - Update Swagger OpenAPI with new `hits` and `took` fields

Issue - State: closed - Opened by jordanpadams over 3 years ago - 2 comments
Labels: B12.0

#84 - [pds-api] Initial Google-like Search

Issue - State: closed - Opened by jordanpadams over 3 years ago - 2 comments
Labels: Epic, B12.0, theme, proj.registry+api

#73 - As a n00b paginator, there might be an off-by-1 error in the `limit` parameter

Issue - State: closed - Opened by nutjob4life over 3 years ago - 4 comments
Labels: bug, B12.0, s.medium

#63 - As an API user, I want to be able to use wildcard search with `like` operator when apply filter queries

Issue - State: closed - Opened by tloubrieu-jpl over 3 years ago - 1 comment
Labels: duplicate, requirement, needs:triage

#58 - As an API user, I want to know the Product(s) that belong to a given Collection.

Issue - State: closed - Opened by jordanpadams over 3 years ago - 1 comment
Labels: duplicate, requirement, B12.0, p.must-have

#55 - As an API user, I want to search for secondary collections that belong to a bundle.

Issue - State: closed - Opened by jordanpadams over 3 years ago - 1 comment
Labels: duplicate, requirement, B12.0, p.should-have

#54 - As an API user, I want to perform a search using wildcards

Issue - State: closed - Opened by jordanpadams over 3 years ago - 15 comments
Labels: requirement, p.must-have

#53 - Add name/description/type from external reference (for target, investigation area, instruments)

Issue - State: open - Opened by tloubrieu-jpl over 3 years ago
Labels: enhancement, p.wont-have, proj.registry+api, icebox, c.search-api

#51 - As a developer, I want a continuous deployment of the API available for testing

Issue - State: closed - Opened by jordanpadams over 3 years ago - 11 comments
Labels: requirement, B12.1, p.must-have, proj.registry+api, c.search-api

#50 - Refine response format conventions and parameter definition per #17

Issue - State: open - Opened by jordanpadams over 3 years ago
Labels: enhancement, Epic, needs:triage, needs:req, proj.registry+api, icebox, c.search-api

#49 - initiate a proposal for the API WG and ENG team

Issue - State: closed - Opened by tloubrieu-jpl over 3 years ago - 2 comments
Labels: enhancement, i&t.skip

#45 - As a user, I want the API to be schema.org compliant

Issue - State: open - Opened by tloubrieu-jpl over 3 years ago - 2 comments
Labels: requirement, Epic, p.should-have, proj.registry+api, icebox, c.search-api

#44 - Implement actual facet result in the response summary

Issue - State: closed - Opened by tloubrieu-jpl over 3 years ago - 2 comments
Labels: duplicate, enhancement, needs:req

#30 - SwaggerHub CodeGen Server adaptation and integration how-tos

Issue - State: closed - Opened by jordanpadams about 4 years ago - 5 comments
Labels: enhancement, wontfix, Epic, B11.1, needs:triage, needs:req, i&t.skip

#29 - Implement EN query passing to DN search UI

Issue - State: open - Opened by jordanpadams about 4 years ago
Labels: proj.registry+api, icebox, c.search-api

#28 - DN Pilot API Project(s)

Issue - State: open - Opened by jordanpadams about 4 years ago - 1 comment
Labels: enhancement, Epic, proj.registry+api, icebox, c.search-api

#27 - Identify nodes and define scope for piloting pds-api-service adaptation

Issue - State: open - Opened by jordanpadams about 4 years ago
Labels: proj.registry+api, icebox, c.search-api

#23 - Implement response format definition in API Service

Issue - State: open - Opened by jordanpadams about 4 years ago
Labels: proj.registry+api, icebox, c.search-api

#22 - Update API Spec with refined response format conventions and field definitions

Issue - State: open - Opened by jordanpadams about 4 years ago
Labels: proj.registry+api, icebox, c.search-api

#21 - Define response formatting for default vs "additional" metadata fields

Issue - State: open - Opened by jordanpadams about 4 years ago
Labels: proj.registry+api, icebox, c.search-api

#18 - Refine format conventions defined by the API WG

Issue - State: closed - Opened by jordanpadams about 4 years ago - 1 comment
Labels: i&t.skip

#16 - Implement EN query of DN API service

Issue - State: open - Opened by jordanpadams about 4 years ago
Labels: proj.registry+api, icebox, c.search-api

#14 - Define initial set of intra-discipline (product-level) search scope

Issue - State: closed - Opened by jordanpadams about 4 years ago - 5 comments
Labels: enhancement, help wanted, Epic, B11.1, i&t.skip