Difference between revisions of "Research data management"
Jump to navigation
Jump to search
(→Automated DIP generation: intro) |
|||
| Line 12: | Line 12: | ||
=Automated DIP generation= | =Automated DIP generation= | ||
| + | |||
| + | The tasks related to this phase of development are: | ||
| + | |||
| + | * change workflow so that the ‘upload DIP’ choice can be preconfigured. | ||
| + | * update AIP reingest workflow to allow uncompressed AIPs to be reingested. | ||
| + | * enhance the callback functionality in the Storage Service, to notify third party apps when a DIP is ready to be used. | ||
| + | |||
| + | |||
| + | These developments are necessary for research data management to meet use cases when research data is stored without the expectation that it will be re-used, but then subsequently a need for re-use arises and/or is approved by the creator of the data. | ||
=METS parsing= | =METS parsing= | ||
Revision as of 10:46, 30 August 2015
Main Page > Documentation > Requirements > Research data management
About
This page describes requirements for enhancements to Archivematica to better handle research data management. It is funded by Jisc, through University of York and University of Hull.
See also
- Dataset preservation
- Dataverse
- Digital Archiving blog written by archivists at University of York
Automated DIP generation
The tasks related to this phase of development are:
- change workflow so that the ‘upload DIP’ choice can be preconfigured.
- update AIP reingest workflow to allow uncompressed AIPs to be reingested.
- enhance the callback functionality in the Storage Service, to notify third party apps when a DIP is ready to be used.
These developments are necessary for research data management to meet use cases when research data is stored without the expectation that it will be re-used, but then subsequently a need for re-use arises and/or is approved by the creator of the data.