...
It was developed in a partnership between Artefactual Systems and Discovery Garden, sponsored by the University of Saskatchewan Library.
About Archivematica
Archivematica is a free and open-source digital preservation system that is designed to maintain standards-based, long-term access to collections of digital objects. It uses a micro-services design pattern to provide an integrated suite of software tools that allows users to process digital objects from ingest to access in compliance with the ISO-OAIS functional model. Users monitor and control the micro-services via a web-based dashboard. Archivematica uses METS, PREMIS (events, agents, rights and restrictions), Dublin Core, the Library of Congress BagIt specification and other best practice standards and practices to provide trustworthy, authentic, reliable, and interoperable archival packages (AIPs) for storage in your preferred repository.
...
You may read more about Archivematica here.
About Archidora
You may read more about Archidora on this presentation from Justin Simpson, Artefactual at the iCamp BC - February 16 - 18, 2015
Download
Islandora module:https://github.com/discoverygardenIslandora-Labs/archidora
You may also download the alpha Archivematica: Archivematica 1.4 .0 release from Artefactual. They have tested it against an Islandora instance set up in their office, using the islandora-labs/islandora_vagrant git repoand Storage Service 0.7 or later is required; download from http://www.archivematica.org.
This integration is currently (as of 1.4/0.7 release) considered a beta feature.
Installation
Installation and testing is similar to any Drupal module. Please see Installing the Islandora Enhancement Modules for details.
Configuration
The In the Archivematica Storage Space:
- Create a Space with access protocol FEDORA via SWORD2; and create a Location within that Space (purpose = FEDORA deposits). The Fedora URL, username and password will need to be entered here. See Archivematica documentation for more details.
In Islandora - configure Archidora's Storage Service URL, user and user's API key will have to be entered into this module's admin screen, at admin/islandora/archidora
, and a Deposit Location selected. An API token should also be generated to allow Archivematica to call back to Islandora.In Fedora, the domain name of the server will have to be configured properly as well as a user created for Archivematica. The user created in Fedora will have to be entered in Archivematica's configuration to be able to authenticate with Fedora, so to be able to pull datastreams.
- Archivematica Storage Service Base URL - normally http://archivematica-url:8000
- Deposit Location - will be configured automatically once storage service URL is entered
- Archivematica User - Archivematica dashboard user to be used for Islandora integration (not storage service)
- Archivematica API Key - API key for the Archivematica dashboard user listed above
- EM-IRI Solr field - used for constructing Sword API call (default is "RELS_EXT_edit_media_uri_ms")
- AIP max age - new objects will not be added to a deposit after the specified time has elapsed
- AIP max size - new objects will not be added to a deposit after the specified size has been reached. Note that this is really the transfer size; the AIP could be larger due to normalized objects
- Cron time - the amount of time for which the queue of items will be allowed to process, at each cron invocation. Setting a higher time is recommended if compound objects are being ingested (especially manually), otherwise the relationships may not be included in the METS file sent to Archivematica
Archivematica may also be configured to call back to Islandora to delete the high-res "OBJ" datastreams. This is done in the Storage Service - Administration | Service callbacks
- URI: http://islandora-base-url/islandora/object/<source_id>/archidora/{Islandora API}/delete
- where the API key is the "Islandora Archivematica integration API key" listed/generated on the Archidora admin screen
- Event: post-store
- Method: post
- Expected status: 200
Note: the OBJ datastreams are not deleted automatically, but rather are listed at the collection level (or compound object level) on the Manage | Archivematica tab. They can be deleted individually or in bulk.
Cron must be enabled.
Note |
---|
As a side-effect of using Cron Queues, the submission of objects to Archivematica may not complete during any one invocation of Cron. |
Collection-level configuration:
Check off "Don't Archive Children" to stop objects from being sent to Archivematica for a particular collection.