Undoing a deaccession

[paul....@ubc.ca]

Hi,

I realize that deaccessions are meant to be permanent, but that said, is there any way to undo it once it's done?

I suspect that this may involve accessing the postgres database directly.

In a related (but not identical) note, we have this situation: One of of our records requires deaccessioning because of a data file error. If this study is deaccessioned, would creating a new version  once revised data is uploaded allow publication?

ie, Version 1 would be deacessioned, but v2 would show up normally?

Normally, I would just check this myself on our test instance, but we're having (unrelated) issues with it right now.

Note: Dataverse 4.20.

Thanks for your help,

Paul Lesack

University of British Columbia

[Barbosa, Sonia]

Hi Paul, if you go back to the deaccessioned dataset, you should see options to "Edit" the dataset. This will revive the dataset but does require some type of edit, and does create a new version depending on your edits. This revival should allow you to fix the issue with the previous version before you hit publish again.

ᐧ

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/94499109-3a05-4291-805f-3176d4fcf465n%40googlegroups.com.

--

Sonia Barbosa
Manager of Data Curation, The Dataverse Project
Manager of the Murray Research Archive, IQSS
Data Science
Harvard University

All Harvard Dataverse Repository inquiries should be sent to:  sup...@dataverse.harvard.edu

All software inquiries should be sent to: sup...@dataverse.org

Need to deposit data? Visit http://dataverse.harvard.edu

All test dataverses should be created  in our demo environment: https://demo.dataverse.org/

Join our Dataverse Community! https://groups.google.com/forum/#!forum/dataverse-community