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
While checking deposits in the Harvard Dataverse Repository, I occasionally have to deaccession multiple datasets that don't contain data (they often contain only research articles) while I learn more from the depositor about their intentions and data availability.
Deaccessioning reduces the chance that deposits will appear when people are looking for data and gives the depositors a chance to create new dataset versions with data. (If the depositor can't add data or doesn't reply, I later delete the published deposit.)
When I need to deaccession multiple datasets, I have to do so by visiting each dataset page. It would be a lot faster to be able to deaccession multiple datasets at once using the GUI. It's already possible using the Dataverse API.
The text was updated successfully, but these errors were encountered:
jggautier
changed the title
As a data curator, I'd like to be able to deaccession multiple datasets at once
As a data curator, I'd like to be able to use the GUI to deaccession multiple datasets
Apr 3, 2024
While checking deposits in the Harvard Dataverse Repository, I occasionally have to deaccession multiple datasets that don't contain data (they often contain only research articles) while I learn more from the depositor about their intentions and data availability.
Deaccessioning reduces the chance that deposits will appear when people are looking for data and gives the depositors a chance to create new dataset versions with data. (If the depositor can't add data or doesn't reply, I later delete the published deposit.)
When I need to deaccession multiple datasets, I have to do so by visiting each dataset page. It would be a lot faster to be able to deaccession multiple datasets at once using the GUI. It's already possible using the Dataverse API.
The text was updated successfully, but these errors were encountered: