AIP Backup & Restore Sunita Barve NCRA, Pune

AIP The latest version of DSpace 1.7.0, supports backup and restore of all its contents as a set of AIP files. It is possible to include all Communities, Collections, Items, Groups and People from the software. This feature allows to export entire hierarchy (ie bitstreams, metadata and relationships between Communities/Collections/Items) into a relatively standard format such as METS. This backup can be re-imported or restored into same DSpace installation or different DSpace installation.

AIP AIP is different compared to the traditional backup system. In traditional backup it is required to backup and restore Dspace's database and files (also known as the “assetstore”) separately. The new AIP Backup & Restore option try to help to resolve many of the complexities of a traditional backup and restore.

AIP While using backing up and restoring option of AIP, it is necessary to also backup local DSpace configurations and customizations. It is a package describing one archival object in Dspace. The archival object may be a single Item, Collection, Community or Site. When AIP command is run it creates a ZIP file containing a METS manifest and all related content bitstreams.

AIP Exporting just a single AIP : To export a single AIP use the following command /home/dspace/bin/dspace packager -d -t AIP -e -i 1849/220 aip220.zip The above command will export the object of the given handle i.e. 1849/220 into an AIP file named “aip220.zip”. This will not include any child objects for Communities or Collections.

AIP To export an hierarchy only use -a with the above command. This will take care of exporting all child objects in 1849/220.

AIP Exporting Entire Site using AIP: To export an entire DSpace site run the following command /home/dspace/bin/dspace packager -d -a -t AIP -e -i 1849/0

Ingesting AIP Like export, AIP allows to perform two types of ingestion one by single AIP and other by Hierarchical AIP. To ingest a single AIP and create a new DSpace object under a parent object, following command can be used /home/dspace/bin/dspace packager -s -t AIP -e -p 1849/220 aip220.zip

AIP The above command will ingest single object in the DSpace repository. To ingest an AIP hierarchy from a directory of AIPs, use the -a package parameter. To ingest entire site use the following command /home/dspace/bin/dspace packager -s -a -t AIP -e -p 1849/0 aipentire.zip

Restoring AIPs Restoring is slightly different than just submitting. While using restore command, we make every attempt to restore the object as it used to be. AIP currently supports restoring at three levels such as Default Restore Mode (-r) this option attempt to restore object and make all changes, Restore, Keep Existing Mode (-r -k) allow to restore object but if existing object is found it will not be restored, Force Replace Mode (-r -f) this option overwrite any existing objects in Dspace.

Restoring AIP To restore single AIP here is the command /home/dspace/bin/dspace packager -r -t AIP -e aip220.zip To restore hierarchy of AIPs use /home/dspace/bin/dspace packager -r -a -t AIP -e aip220.zip

Restoring AIP To restore an entire site from a set of AIPs, install a completely fresh DSpace with a completely empty fully- functional DSpace installation. Create initial administrator user in order to perform the restore command and once that is done run the following command /home/dspace/bin/dspace packager -r -a -f -t AIP -e -i 1849/0 aipentire.zip When you restore large amount of content to your Dspace, the internal database counts may get out of sync hence as a best practice run the following commands /home/dspace/etc/postgres/update-sequences.sql

Export To export data from dspace and here is command to export collection as a whole. dspace export -t COLLECTION -i /2 -d /home/dspace/IRExport -n 1 In the above example collection ID is /2 and it is exported into destination directory /home/dspace/IRExport and from item number 1.

Import dspace import -a -c /2 -e -s /home/dspace/IRExport -m /home/dspace/import.map Here it is necessary to know the collection ID where items/bitstreams will be imported as well as who is importing/allowed to import the records and source directory from where all records should be imported and one has to specify the itemmapper file name that could be anything which will only list item details such as /1, /2, /3 etc.