Difference between revisions of "Workflow:Extraction from the Pure Research Information System and transformation for loading by Archivematica"
Jump to navigation
Jump to search
Aalbinclark (talk | contribs) |
Aalbinclark (talk | contribs) |
||
| Line 18: | Line 18: | ||
==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 --> | ||
| − | + | * 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. |
| − | |||
| − | 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== | ||
Revision as of 13:50, 28 April 2021
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