Closed jordanpadams closed 2 years ago
For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
...so that I can <why do you want to do this?>
Notional API Design:
GET /products/{collection-identifier}/members
See https://github.com/NASA-PDS/registry/issues/109 and https://github.com/NASA-PDS/registry/issues/108 for how the registry ingests primary and secondary products.
Given I have a collection LID OR LIDVID When I perform an API query by that LID/LIDVID for its products Then I expect the API to return the primary product(s) AND any secondary product(s) for that collection
This ticket is a duplicate of https://github.com/NASA-PDS/registry-api-service/issues/2
For more information on how to populate this new feature request, see the PDS Wiki on User Story Development:
https://github.com/NASA-PDS/nasa-pds.github.io/wiki/Issue-Tracking#user-story-development
Motivation
...so that I can <why do you want to do this?>
Additional Details
Notional API Design:
See https://github.com/NASA-PDS/registry/issues/109 and https://github.com/NASA-PDS/registry/issues/108 for how the registry ingests primary and secondary products.
Acceptance Criteria
Given I have a collection LID OR LIDVID When I perform an API query by that LID/LIDVID for its products Then I expect the API to return the primary product(s) AND any secondary product(s) for that collection
Sub-tasks