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

Develop initial requirements and design for DOI Service #1

Closed
jordanpadams opened this issue Mar 28, 2020 · 1 comment
Closed

Develop initial requirements and design for DOI Service #1

jordanpadams opened this issue Mar 28, 2020 · 1 comment
Labels

Comments

@jordanpadams
Copy link
Member

This web service should meet the following use cases:

  1. Generate DOI Object from PDS4 Label
    a. A user posts a bundle bundle/collection/product PDS4 label to the service.
    b. The service translates the metadata from the PDS4 label into the DOI/IAD Record Object
    c. The service return the IAD record object

Example Record Objects: DOI_bundle.xml.txt, DOI_collection_data.xml.txt

  1. User Submits DOI Object
    a. A user posts a DOI/IAD Record object
    b. The service verifies validity of the object
    c. The service posts the object to the Tracking Service
    i. Alternatively, the service could post the object to a file staging area or just include in email
    c. The service notifies Operator of DOI submission
    i. Alternatively, the service could send an email to Operator for manual vetting and submission.

  2. Operator Reserves DOI Object
    a. The authenticated Operator submits a DOI object to the service for reserve DOI
    b. The service validates the DOI object
    c. The service submit the DOI object to the IAD Service and verifies return values
    d. The service posts Reserved DOI information to Tracking Service and forwards response to Operator

  3. Operator Release DOI Object
    a. The authenticated Operator submits a DOI object to the service for release DOI
    b. The service validates the DOI object
    c. The service submit the DOI object to the IAD Service and verifies return values
    d. The service posts Released/Published DOI information to Tracking Service and forwards response to Operator

Other things to think about:

  • Ability to query DOIs - should probably be done by Tracking Service, but for workaround, could probably use DataCite
  • Accumulating volumes - allow for some easy way to version accumulating volumes
  • Best effort DOIs - e.g. "LROC RDR data" - give them the latest DOI for that data
  • Figure out how to track DOIs at a LID-level

More details on the IAD API and Schema: https://www.osti.gov/iad2/docs#record-model-fields

jordanpadams added a commit that referenced this issue Mar 28, 2020
@jordanpadams
Copy link
Member Author

See 742e5b0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant