-
Notifications
You must be signed in to change notification settings - Fork 3
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
Create / Draft a DOI object capability #2
Comments
Some inputs to start:
|
The pds4 test dataset can found in https://pds.nasa.gov/datastandards/documents/examples/ |
Some details on the use case we want to implement for this sprint (from Jordan's inputs): A) Input test datasets from these PDS4 Collection and Bundle label via URLs
B) Use the latest templates provided in aaaDOI_templateFiles/DOI_IAD2_template_20181025.xml (zip file sent by Ron) C) Defaults – some values you will see in the output are currently “defaults” set in Ron’s config file: aaaConfig_IAD2_IMG_InSight_20191216.xml Ron used to have default configurations for metadata which he did not found in the labels, we should find how we can automatically get them or make them mandatory in the PDS4 label as part of the submission. D) Output: With this inputs we don't need to run Ron's code and this is very straightforward to start the development from scratch and get us going, we can then build off this from here:
|
|
The project is one module: pds-doi-service Submodules are:
|
After the meeting with Ron, I understand that the PDS4 to DOI should work with these different sub-cases:
We can have one reader function for each input type, for example read_pds4_bundle, read_pds4_collection, ... |
closed per c1f77ab |
See detailed design documentation https://github.com/NASA-PDS-Incubator/pds-doi-service/blob/master/docs/design/pds-doi-service-srd.md
This only include this function as a standalone python command based on a pds-data-doi module.
Applicable requirements
🦄 #5
🦄 #15
The text was updated successfully, but these errors were encountered: