...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