Summary of Issue: Dataset owners may request to retract the datasets that they published. The reason of the retraction can be various, such as the data is not available anymore, or the data is not valid.
As administrator, you can unpublish the dataset so that the dataset is retracted, but you also need to provide tombstone page for the retracted dataset to serve as the new landing page of the dataset. The tombstone page needs to include a statement to specify the reason that leads to the retraction and removal of the dataset. Currently a dataset that is substituted by a new version is not considered to be a dataset retraction. If you publish a new version of the dataset and link it to the old version, researchers can be made aware of it.
Summary of Fix/Changes: Created a tombstone page for retracted datasets and a workflow for the dataset owner request to unpublish a dataset and provide the reason, and for the administrator to change publications from published to unpublished, select the reason for retraction, and change the resource url of the DOI. (See JIRA task for link to further documentation).
Summary of Testing: Testing done by PURR staff on their dev environment. This will be tested again on PURR production hub by PURR staff.
Hotfix needed? This will be pulled to PURR prod as part of testing and targeted for next CMS release (2.2.27)
NOTE: This update contains a migration that adds a new column (unpublished_reason) to the publication_versions table.
dbenham
commented
1 year ago
NOTE: This update contains a migration that adds a new column (unpublished_reason) to the publication_versions table.