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 a developer, I want to include supplemental file data sizes in the registry #112

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

Comments

@jordanpadams
Copy link
Member

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 accurately describe the data volume for a particular data sets / bundle

Additional Details

Acceptance Criteria

Given I have registered a product containing a File_Area_*_Supplemental
When I perform a query for that product
Then I expect the ops:Data_File_Info/ops:file_size to include the file sizes for both the File_Area object and Supplemental object

@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
Copy link
Member Author

jordanpadams commented Mar 26, 2021

Looks like the default functionality for the Registry captures this story. Screenshot from kibana discover portal below for https://pds-imaging.jpl.nasa.gov/data/nsyt/insight_cameras/data/sol/0000/mipl/edr/idc/D000M0000_596535424EDR_F0000_0106M5.xml, which contains a supplemental file area

Screen Shot 2021-03-26 at 9 19 21 AM

@jordanpadams jordanpadams transferred this issue from nasa-pds-engineering-node/pds-registry-app Oct 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p.must-have requirement the current issue is a requirement
Projects
None yet
Development

No branches or pull requests

1 participant