Workflow:Deaccessioning data - Revision history

Valentijn at 13:41, 5 October 2023

2023-10-05T13:41:08Z

Valentijn at 11:41, 5 October 2023

2023-10-05T11:41:36Z

172.104.134.96: Procedure to remove datasets but retaining the PID

2023-10-05T11:39:44Z

Procedure to remove datasets but retaining the PID

New page

{{Infobox COW
|status=Production
|tools=DataCite
|input=Datasets for which there is reason to remove them from the collection.
|output=A tombstone page (or similar) to ensure the resolving of the PID of the dataset, leading to information that the dataset was removed.
|organisation=SEADDA community of archaeologists and digital specialists
|organisationurl=https://www.seadda.eu/
}}
==Workflow Description==



[[File:workflow.png|Textual description]]<br>



Datasets may need to be deaccessioned or deleted, depending on institutional policy, when:
* Errors are discovered in a published dataset that renders it unusable for research.
* If the content is unlawful or the dataset is fraudulent from a scientific point of view.
* If one or more of the authors or rights holders did not give permission for publication.
* If personal data appears to have been deposited without a legal ground such as permission of research subjects.
* If the content consists of personal data, and a research subject rightfully objects to the preservation of a digital object with an appeal to the GDPR (e.g. right to be forgotten; or revocation of informed consent).
* If there is a legally binding maximum preservation period for the content.

If there is sufficient ground to decide to deaccession a dataset, the deaccessioning is done by a Data Manager who will conduct an appraisal of the request.

In all cases where access to a published dataset is terminated, a notice will be added to the landing page of the Persistent Identifier (PID) associated with the dataset to indicate that the dataset is no longer available: this is called a 'tombstone page'. This is done to ensure that anyone that has citations to resources that have subsequently been removed are retained, and furthermore that the provenance of the deaccession or removal is recorded within all associated metadata.

==Purpose, Context and Content==


Within the SEADDA consortium, workflows for dealing with deaccessioning of datasets were examined from three long standing digital repositories for archaeological data: the Archaeology Data Station of Data Archiving and Networked Services (DANS), the Swedish National Data Service (SND), and the Archaeology Data Service (ADS).

==Evaluation/Review==


==Further Information==

https://docs.google.com/document/d/1mAL20vvhZnYkZuc_60awac5wc-kiaBzYZ_AJahS_nkM/edit?usp=sharing


[[Special:Contributions/172.104.134.96|172.104.134.96]] 11:39, 5 October 2023 (UTC)

@@ Line 37: / Line 37: @@
 ==Further Information==
 <!-- Provide any further information or links to additional documentation here -->
-https://docs.google.com/document/d/1mAL20vvhZnYkZuc_60awac5wc-kiaBzYZ_AJahS_nkM/edit?usp=sharing
+https://doi.org/10.11141/ia.67.3
 <!-- Add four tildes below ("~~~~") to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow -->

@@ Line 40: / Line 40: @@
 <!-- Add four tildes below ("~~~~") to create an automatic signature, including your wiki username. Ensure your user page (click on your username to create it) includes an up to date contact email address so that people can contact you if they want to discuss your workflow -->
 [[Special:Contributions/172.104.134.96|172.104.134.96]] 11:39, 5 October 2023 (UTC)
 <!-- Note that your workflow will be marked with a CC3.0 licence -->