The official AIP Backup & Restore Documentation is avaliable at: AIP Backup and Restore. This page is just for discussion around the existing feature and how to make it better. |
This page serves as a Discussion page for the AIP Backup and Restore feature, first released in DSpace 1.7.0.
Below you'll find more information pertaining to decisions made when developing this feature, etc.
Feel free to add your own notes!
The majority of the code changes are in two main areas:
PackageIngester
interface - Now ingests 'java.io.File' objects instead of InputStreams (to better support recursive imports of Communities/Collections)PackageDisseminator
interface - Now exports 'java.io.File' objects instead of OutputStreams (to better support recursive exports of Communities/Collections)DSpaceAIPDisseminator
- Disseminates/Exports AIP(s)DSpaceAIPIngester
- Ingests exported AIP(s)\AbstractMETSDisseminator
, AbstractMETSIngester
, and METSManifest
classesAIPDIMCrosswalk
- Crosswalks DIM metadata for AIPsAIPTechMDCrosswalk
- Crosswalks METS TechMD sections for AIPsMODSDisseminationCrosswalk
and XSLTDisseminationCrosswalk
to support creating "Site" AIPsFor a full list of code changes (including patches) see: AipCoreAPIChanges |
Because of the changes to the |
The below special cases need further testing, especially when performing a "Restore" or "Replace". Mostly, these are just notes for Tim (and other developers), to ensure that all these various "edge" cases can be restored properly (or perhaps not restored properly, if the decision is made that it needs not be restored).
As each special case is implemented, we can check off the item in the below list. Special cases which have been fully tested & implemented are marked with a . Feel free to add more special cases to this listing, if we missed anything.
Anything not marked with a either is not working or has not yet been fully tested! If you test it and it works, let us know, so we can check it off the list!
Special Cases
Special Cases
Special Cases
As part of the CurationTaskProposal (led by Richard Rodgers & MIT), a new Curation Framework is in the works. This Curation Framework will have a Command Line interface initially. However, the goal for 1.7, is to also have Administrative UI tools which are able to kick off various "curation tools". Among these curation tools will be the ability to export/import AIPs via the Admin UI.
Some very basic ingestion speed tests were performed on a set of 26 AIPs (which represented a Community containing a Collection containing 24 Items). These tests found that, by default, the parsing/ingest settings are currently not optimized for speed.
Here are the basic (non-scientific) results
-o validate=true
flag) (but using external Schemas): took about 1 minute, 12 seconds to ingest all 26 AIPsmets.xsd.*
settings in dspace.cfg
. See AIP Backup and Restore#AIP Configurations To Improve Ingestion Speed while Validating in the official AIP Backup and Restore documentation.Please add your own potential use cases or discussion topics
Questions or comments – either add them inline above, or contact Tim Donohue