Open kcondon opened 6 years ago
Would this include the ability to "unpublish" datasets that are deaccessioned?
This would be a nice feature to use against suspected spam or pseudo-science datasets; this, and the ability to prevent future publishing, which could be overridden by a superuser?
Just wondering, but is the best alternative to deaccessioned the dataset and publish a new version later? Suggestion from this discussion. https://groups.google.com/g/dataverse-community/c/C6hl_mTx1yM/m/XM75Qy5GAQAJ
@DonRichards yes, that's a completely valid and 100% supported approach.
2024/09/16: ABR review, there is a manual process, but worth investigating for API. @sbarbosadataverse please weigh in.
We need an API endpoint to unpublish datasets in some cases where a user may mistakenly publish their dataset in root when it needs to be reviewed first in by a journal dataverse.
Here are the essential steps by hand that hopefully will become the endpoint:
Tables involved: Dataset Datasetlock Datasetversion Dvobject
To Unpublish a Dataset: