Overview of the Feature Request
Tell Dataverse not to use the "Available" dateType in the DataCite/Datacite export that it creates.
What kind of user is the feature intended for?
API User, Superuser, and Sysadmin
What inspired the request?
Following a review of part of the NIH GREI Metadata Recommendations (#470), we've found that how we've told Dataverse to determine the date to include in the date property where the dateType is "Available" is different than what's recommended in the NIH GREI Metadata Recommendations at https://doi.org/10.5281/zenodo.16953588.
We're also deprioritizing figuring out what to tell Dataverse to include in the the "Available" dateType because we're not aware of any cases where others are using this information, such as by designing systems, to help people find data based on when the files are or were available, and because the challenges are complex.
Until we can tackle this, we should tell Dataverse not to use the "Available" dateType in the DataCite/Datacite export that it creates.
What existing behavior do you want changed?
Currently, the DataCite/Datacite export uses "Available" to indicate when the user published the dataset's first version in the Dataverse repository.
<date
dateType="Available">YYYY-MM-DD
</date>We should tell Dataverse not to use the "Available" dateType.
Any open or closed issues related to this feature request?
Overview of the Feature Request
Tell Dataverse not to use the "Available"
dateTypein the DataCite/Datacite export that it creates.What kind of user is the feature intended for?
API User, Superuser, and Sysadmin
What inspired the request?
Following a review of part of the NIH GREI Metadata Recommendations (#470), we've found that how we've told Dataverse to determine the date to include in the
dateproperty where thedateTypeis "Available" is different than what's recommended in the NIH GREI Metadata Recommendations at https://doi.org/10.5281/zenodo.16953588.We're also deprioritizing figuring out what to tell Dataverse to include in the the "Available"
dateTypebecause we're not aware of any cases where others are using this information, such as by designing systems, to help people find data based on when the files are or were available, and because the challenges are complex.Until we can tackle this, we should tell Dataverse not to use the "Available"
dateTypein the DataCite/Datacite export that it creates.What existing behavior do you want changed?
Currently, the DataCite/Datacite export uses "Available" to indicate when the user published the dataset's first version in the Dataverse repository.
We should tell Dataverse not to use the "Available" dateType.
Any open or closed issues related to this feature request?
dateTypeby following same logic used for determiningpublicationYear#12361