Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As an API user, I want to know the Bundle for a given Collection. #452

Closed
jordanpadams opened this issue Mar 26, 2021 · 1 comment
Closed
Assignees
Labels
B12.0 p.must-have requirement the current issue is a requirement

Comments

@jordanpadams
Copy link
Member

jordanpadams commented Mar 26, 2021

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 know the bundle(s) this collection belongs to.

Additional Details

See NASA-PDS/registry#109 and NASA-PDS/registry#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 LIDVID for its parent bundle(s)
Then I expect the API to return the primary bundle (there should be only 1) AND any secondary bundle(s) (could be many) the Collection belongs to

/products/{collection-identifier}/member-of
@jordanpadams jordanpadams added requirement the current issue is a requirement needs:triage labels Mar 26, 2021
@jordanpadams jordanpadams self-assigned this Mar 26, 2021
@jordanpadams jordanpadams changed the title As a user, I want to know the Bundle for a given Collection. As an API user, I want to know the Bundle for a given Collection. Mar 26, 2021
@tloubrieu-jpl
Copy link
Member

Validated in pull request NASA-PDS/registry-api-service#29

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
B12.0 p.must-have requirement the current issue is a requirement
Projects
None yet
Development

No branches or pull requests

3 participants