Difference between revisions of "Workflow:Workflow for preserving research data using Archivematica, Fedora, Hydra and PURE"

From COPTR
Jump to navigation Jump to search
(Created page with "Upload file (Toolbox on left) and add a workflow image here or remove Category:COW Workflows ==Workflow description== <!-- Describe your workflow he...")
 
Line 6: Line 6:
  
 
This workflow uses Archivematica, Fedora, Hydra and PURE to preserve and provide access to academic research data. The workflow includes a high level of automation.
 
This workflow uses Archivematica, Fedora, Hydra and PURE to preserve and provide access to academic research data. The workflow includes a high level of automation.
 +
 +
The workflow was created as part of the [Filling the Digital Preservation Gap project|https://www.york.ac.uk/borthwick/projects/archivematica/] and is heavily based on an implementation plan included in the Phase 2 project report
  
 
==Purpose, context and content==
 
==Purpose, context and content==
 
<!-- Describe what your workflow is for, what the organisational context of the workflow is, and what content it is designed to work with -->
 
<!-- Describe what your workflow is for, what the organisational context of the workflow is, and what content it is designed to work with -->
  
The purpose of this workflow is to preserve and disseminate research data in an automated fashion. Research data is a valuable asset produced by academic institutions and should be retained so that findings can be validated. Some of this data may have longer term re-use potential, particularly where it can not be replicated  
+
The purpose of this workflow is to preserve and disseminate research data in an automated fashion. Research data is a valuable asset produced by academic institutions and should be retained so that findings can be validated. Some of this data may have longer term re-use potential, particularly where it can not be replicated. At the University of York our Research Data Management policy states that research data should be retained for ten years from date of last access. This means that even for datasets that are only occasionally accessed, the retention period may be much longer than ten years.
  
 
==Evaluation/Review==
 
==Evaluation/Review==
 
<!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate -->
 
<!-- How effective was the workflow? Was it replaced with a better workflow? Did it work well with some content but not others? What is the current status of the workflow? Does it relate to another workflow already described on the wiki? Link, explain and elaborate -->
  
 +
This workflow has been created as a proof of concept at the University of York. It is due to move into production in May 2017.
  
 
<!-- 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 -->
 
<!-- 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 -->

Revision as of 14:18, 3 March 2017

Upload file (Toolbox on left) and add a workflow image here or remove

Workflow description

This workflow uses Archivematica, Fedora, Hydra and PURE to preserve and provide access to academic research data. The workflow includes a high level of automation.

The workflow was created as part of the [Filling the Digital Preservation Gap project|https://www.york.ac.uk/borthwick/projects/archivematica/] and is heavily based on an implementation plan included in the Phase 2 project report

Purpose, context and content

The purpose of this workflow is to preserve and disseminate research data in an automated fashion. Research data is a valuable asset produced by academic institutions and should be retained so that findings can be validated. Some of this data may have longer term re-use potential, particularly where it can not be replicated. At the University of York our Research Data Management policy states that research data should be retained for ten years from date of last access. This means that even for datasets that are only occasionally accessed, the retention period may be much longer than ten years.

Evaluation/Review

This workflow has been created as a proof of concept at the University of York. It is due to move into production in May 2017.