Closed jordanpadams closed 3 years ago
@jordanpadams @jimmie @ramesh-maddegoda I need test data for /products/{lidvid}/bundles, can you help me download and load it to the docker image? thanks.
@gxtchen I am thinking it is probably best if you use data we are not using for our test cases? Here are some test bundles/collections we have grabbed for testing: https://pds.nasa.gov/data/pds4/test-data/registry/
@rchenatjpl also put together a custom bundle for testing purposes here: https://pds.nasa.gov/data/pds4/test-data/custom-datasets/
Those paths map to pds-int:/data/pds4/test-data/
if you want to use the data from there.
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.
Note: This logic is a little funkier for secondary bundles:
Acceptance Criteria
Given I have a product LID OR LIDVID When I perform an API query by that LIDVID for its grandparent bundle(s) Then I expect the API to returns the primary bundle (there should be only 1) AND any secondary bundle(s) (could be many) the product belongs to
Sub-tasks