Deaccessioning a dataset

[Courtney Mumma]

Hi Dataverse Community,

One of our Texas Data Repository liaisons has questions about deaccessioning that seem beyond the limits of the available documentation. For context, we are a multi-institutional implementation of the Dataverse OSS. 

There is a TDR committee working on deaccessioning in the context of data retention explorations and they want to know what exactly happens when a user selects the Deaccession Dataset Button. What happens on the backend of these datasets? They understand that there is a tombstone created, but is there still a copy stored somewhere? Does this just do dataset files, or everything associated with the dataset?

Also, is this outcome the same if a user deaccessions their own dataset, or an admin deaccessions it for them (there are TDR liaison admins for each institution). Do admins have more options or is the final effect of clicking the Deaccession Dataset Button the same for everyone?

See - https://guides.dataverse.org/en/latest/user/dataset-management.html#dataset-deaccession 

Thanks,

Courtney

[Sherry Lake]

Hi Courtney,

Deaccessioning happens the same way for both admin or curator, there are no additional options for admins. Deaccessioning creates a tombstone page, but admins and dataset curators (of that dataset) can see the previous versions (metadata and files). All the "deaccessioned" metadata and files are still in the Dataverse database, the dataset is "tagged" in the database as "DEACCESSIONED" (the  "public" version shows a tombstone page).

Also note, any deaccessioned dataset can be re-published - see the version tab in this dataset: https://doi.org/10.18130/V3/ATJOZW 

Admins can "delete" (destroy API endpoint) datasets, then all the metadata and files are removed from the Dataverse database (all versions).

You can also deaccession selected versions, or all versions of a datasets.

Discussion on deaccessioning from Dec 2023:

https://groups.google.com/g/dataverse-community/c/MgkprLAlkfg/m/5SqgamBsAwAJ

--

Sherry Lake

UVA Datavesrse http://dataverse.lib.virginia.edu

--
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 visit https://groups.google.com/d/msgid/dataverse-community/CAKx6Rmsyzj49HjLZ6N7J3_6NLn%2BGzRTDc0am%2B-81B77n-H%2B8TA%40mail.gmail.com.

[James Myers]

FWIW: There are also retention periods these days that can make individual files unavailable. As with deaccession, with retention periods, the files still exist and would have to be manually deleted from storage if that’s desired/required.

 

-- Jim

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/CADL9p-UqHFzZYTUmtVJTACy9-9vEobSUbn44QZ83XNtu2PRDOw%40mail.gmail.com.

[Philip Durbin]

There are a couple feature requests for deleting the files themselves when datasets are deaccessioned: https://github.com/IQSS/dataverse/issues/8037 and https://github.com/IQSS/dataverse/issues/8942

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/LV8P220MB1978C50DAB23179F0223D5BCBF4A2%40LV8P220MB1978.NAMP220.PROD.OUTLOOK.COM.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin