Difference between revisions of "Workflow:Extraction from the Pure Research Information System and transformation for loading by Archivematica"

From COPTR
Jump to navigation Jump to search
Line 10: Line 10:
 
<!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below  -->
 
<!-- To add an image of your workflow, open the "Upload File" link on the left in a new browser tab and follow on screen instructions, then return to this page and add the name of your uploaded image to the line below - replacing "workflow.png" with the name of your file. Replace the text "Textual description" with a short description of your image. Filenames are case sensitive! If you don't want to add a workflow diagram or other image, delete the line below  -->
  
[[File:workflow.png|Textual description]]<br>
+
<!-- [[File:workflow.png|Textual description]]<br> -->
  
 
<!-- Describe your workflow here with an overview of the different steps or processes involved-->
 
<!-- Describe your workflow here with an overview of the different steps or processes involved-->
Line 20: Line 20:
 
* Initial focus was upon research datasets.  
 
* Initial focus was upon research datasets.  
 
* The work was carried out during the 2016/2017 academic year.
 
* The work was carried out during the 2016/2017 academic year.
* The Ruby gem 'Preservation' was developed for this workflow. The documentation outlines the workflow at https://rubygems.org/gems/preservation.
+
* The Ruby gem 'Preservation' was developed. This workflow is outlined in the accompanying README.
  
  
Line 27: Line 27:
  
 
It worked!
 
It worked!
 +
 +
The pain points were failed transfers, although this was mitigated to some extent by a reporting feature built into the Preservation gem.
  
 
==Further Information==
 
==Further Information==
 
<!-- Provide any further information or links to additional documentation here -->
 
<!-- Provide any further information or links to additional documentation here -->
 +
https://rubygems.org/gems/preservation
  
 
<!-- 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 -->
 
<!-- 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 -->
  
 
<!-- Note that your workflow will be marked with a CC3.0 licence -->
 
<!-- Note that your workflow will be marked with a CC3.0 licence -->

Revision as of 13:48, 28 April 2021

Extraction from the Pure Research Information System and transformation for loading by Archivematica
Status:Experimental
Tools:
Input:Pure ID
Output:A transfer for Archivematica (directory of files and JSON description file)
Organisation:Lancaster University

Workflow Description

Purpose, Context and Content

  • Initial focus was upon research datasets.
  • The work was carried out during the 2016/2017 academic year.
  • The Ruby gem 'Preservation' was developed. This workflow is outlined in the accompanying README.


Evaluation/Review

It worked!

The pain points were failed transfers, although this was mitigated to some extent by a reporting feature built into the Preservation gem.

Further Information

https://rubygems.org/gems/preservation