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 know the specific date these data were made publicly accessible.
π Additional Details
The year should match publicationYear
This information is used by ADS for statistics purposes
Currently, this needs to be input by a user because it ties to the release calendar, which cannot be specified in the label. New requirement proposal created to potentially archive this information.
Acceptance Criteria
Given a request to release a DOI for a product for the first time When I perform the operation to attempt to release a DOI Then I expect to be required to input a release date (YYYY-MM or YYYY-MM-DD), and that metadata is included in the DOI metadata as:
Checked for duplicates
Yes - I've already checked
π§βπ¬ User Persona(s)
Node Operator
πͺ Motivation
...so that I can know the specific date these data were made publicly accessible.
π Additional Details
publicationYear
Acceptance Criteria
Given a request to release a DOI for a product for the first time
When I perform the operation to attempt to release a DOI
Then I expect to be required to input a release date (YYYY-MM or YYYY-MM-DD), and that metadata is included in the DOI metadata as:
or in JSON:
βοΈ Engineering Details
No response
The text was updated successfully, but these errors were encountered: