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 user, I want to acquire a DOI for a PDS4 product that has been registered and is publicly accessible #42

Closed
jordanpadams opened this issue May 4, 2021 · 3 comments
Labels
B12.0 p.must-have requirement the current issue is a requirement

Comments

@jordanpadams
Copy link
Member

jordanpadams commented May 4, 2021

Motivation

...so that I can get a DOI for a PDS4 product after it has already been publicly released.

The PDS Policy describes that the PDS "should" acquire DOIs prior to peer review. However, some scenarios will call for DOIs after the fact (e.g. DOIs for already existing User Guides or other documentation where a DOI was not foreseen as being needed prior to peer review).

Additional Details

Acceptance Criteria

Given an PDS4 product that has been registered, a landing page exists, and the data is available publicly online
When I perform a request to get a new DOI
Then I expect to be prompted to "release a new DOI"
Then I expect to be prompted to input the expected metadata to release a DOI
Then I expect to submit the required metadata to the DOI service (https://pds-imaging.jpl.nasa.gov/data/nsyt/insight_cameras/bundle_7.0.xml)
Then I expect to receive a notification as to the status of the request
Then I expect a DOI to be displayed, or information on how I will receive that DOI
Then I expect the information I entered to be saved in a draft state until it is released

Given an PDS4 product that has not been registered, a landing page does not exist, or the data is not publicly accessible
When I perform a request to get a DOI
Then I expect to be prompted to "release a new DOI"
Then I expect to be prompted to input the expected metadata to release a DOI (https://pds-gamma.jpl.nasa.gov/data/pds4/test-data/registry/doi/bundle_doi_test.xml)
Then I expect to submit the required metadata to the DOI service
Then I expect to receive a prompt that the DOI request has failed do to the lack of landing page / public accessibility of the data.
Then I expect the information I entered to be saved in a draft state until it is released

Engineering Details

Related Requirements

🦄 NASA-PDS/doi-service#7

@jordanpadams jordanpadams added the requirement the current issue is a requirement label May 4, 2021
@jordanpadams jordanpadams self-assigned this May 4, 2021
@jordanpadams jordanpadams removed their assignment May 4, 2021
c-suh pushed a commit that referenced this issue May 26, 2021
- Remove navigation buttons for Release and Reserve
- Add navigation buttons for Home, Search, and FAQ
- Add new page for Home
- Add new page for FAQ
- Add new page for Create DOI
- Display error/warning messages on page from which raised

Addresses #44
Addresses #34
Possibly addresses #41
Possibly addresses #42
tloubrieu-jpl pushed a commit that referenced this issue Jun 2, 2021
* Rework userflow for DOI UI

- Remove navigation buttons for Release and Reserve
- Add navigation buttons for Home, Search, and FAQ
- Add new page for Home
- Add new page for FAQ
- Add new page for Create DOI
- Display error/warning messages on page from which raised

Addresses #44
Addresses #34
Possibly addresses #41
Possibly addresses #42

* Correct button text and API calls

- Revert to appropriate actions, i.e. 'draft' and 'reserve' only
- Edit button text to say 'Submit for Review' instead of 'Release

Additional changes:
- Display DOI of newly reserved item in success message
- Add margin to bottom of page

Resolves #47
Continues #44
@jordanpadams
Copy link
Member Author

@gxtchen
Copy link

gxtchen commented Oct 18, 2021

@tloubrieu-jpl @jordanpadams I need access to the doi service and doi ui in pds-gamma.

@jordanpadams
Copy link
Member Author

@gxtchen login information provided via secure email

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

2 participants