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 ensure sufficient licensing information is included in the DOI metadata and I know how I am allowed to use PDS data.
Additional Details
Licensing should be CC0
Example TBD from SBN
Acceptance Criteria
AC1: New DOI
Given a data set requiring a new DOI When I perform the steps to create a DOI Then I expect CC0 licensing info to included in the DOI metadata submitted to DataCite
AC2: Update existing DOI
Given an existing DOI that was created prior to this ticket creation When I perform a query for the DOI Then I expect CC0 licensing info has been updated and included in the DOI metadata
Engineering Details
UPDATE FROM SMD AS OF 11/18/2021
PDS data should be licensed under CC0 unless otherwise specified.
The text was updated successfully, but these errors were encountered:
deferring until later date. not super critical at this time.
jordanpadams
changed the title
As a user, I would like to include licensing information with all PDS DOIs
As a DOI user, I would like to know the licensing information PDS data
Jun 3, 2022
Motivation
...so that I can ensure sufficient licensing information is included in the DOI metadata and I know how I am allowed to use PDS data.
Additional Details
Licensing should be CC0
Example TBD from SBN
Acceptance Criteria
AC1: New DOI
Given a data set requiring a new DOI
When I perform the steps to create a DOI
Then I expect CC0 licensing info to included in the DOI metadata submitted to DataCite
AC2: Update existing DOI
Given an existing DOI that was created prior to this ticket creation
When I perform a query for the DOI
Then I expect CC0 licensing info has been updated and included in the DOI metadata
Engineering Details
UPDATE FROM SMD AS OF 11/18/2021
PDS data should be licensed under CC0 unless otherwise specified.
The text was updated successfully, but these errors were encountered: