You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
...so that I can update the metadata associated with a reserved (aka draft) or released (aka findable`) DOI.
Additional Details
Per the info from Ron, can only update a DOI in a draft or registered state.
if the DOI is `findable`:
`hide` DOI to move the DOI from `findable` to `registered` states
update DOI
Acceptance Criteria
Given a DOI in draft state When I perform an update of the DOI metadata, and a follow-on query to verify the results Then I expect to see the DOI metadata has been updated. Check with url http://{apihost}/(apiport)/PDS_APIs/pds_doi_api/0.2/doi?identifier={lidvid}
Given a DOI in registered state When I perform an update of the DOI metadata, and a follow-on query to verify the results Then I expect to see the DOI metadata has been updated, check with url http://{apihost}/(apiport)/PDS_APIs/pds_doi_api/0.2/doi?identifier={lidvid}
Given a DOI in findable state When I perform an update of the DOI metadata, and a follow-on query to verify the results Then I expect to see the DOI metadata has been updated. Check with url http://{apihost}/(apiport)/PDS_APIs/pds_doi_api/0.2/doi?identifier={lidvid} and https://api.test.datacite.org/dois/id/{doi}
Given a DOI that does not exist When I perform an attempted update of that DOI metadata Then I expect to receive an error message that DOI does not exist
(moving this AC to separate issue)
The text was updated successfully, but these errors were encountered:
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 update the metadata associated with a reserved (aka
draft) or released (aka
findable`) DOI.Additional Details
Per the info from Ron, can only update a DOI in a
draft
orregistered
state.Acceptance Criteria
Given a DOI in
draft
stateWhen I perform an update of the DOI metadata, and a follow-on query to verify the results
Then I expect to see the DOI metadata has been updated. Check with url http://{apihost}/(apiport)/PDS_APIs/pds_doi_api/0.2/doi?identifier={lidvid}
Given a DOI in
registered
stateWhen I perform an update of the DOI metadata, and a follow-on query to verify the results
Then I expect to see the DOI metadata has been updated, check with url http://{apihost}/(apiport)/PDS_APIs/pds_doi_api/0.2/doi?identifier={lidvid}
Given a DOI in
findable
stateWhen I perform an update of the DOI metadata, and a follow-on query to verify the results
Then I expect to see the DOI metadata has been updated. Check with url http://{apihost}/(apiport)/PDS_APIs/pds_doi_api/0.2/doi?identifier={lidvid} and https://api.test.datacite.org/dois/id/{doi}
Given a DOI that does not existWhen I perform an attempted update of that DOI metadataThen I expect to receive an error message that DOI does not exist(moving this AC to separate issue)
The text was updated successfully, but these errors were encountered: