Page History

...

Installation and testing is similar to any Drupal module. Please see Installing the Islandora Enhancement Modules for details.

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.
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 Islandora API key is the "Islandora Archivematica integration API key" generated on the Archidora admin screen
  - <source_id> should be entered as shown, with the angle brackets
- 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.

On the Archivematica dashboard:

Add the IP address of the storage service to the IP whitelist for the REST API. This will enable transfers to be approved automatically

In Islandora - :

configure Archidora, at admin/islandora/archidora
- 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
Cron must be enabled. You may also need to add a rule to the firewall on the Fedora server to allow access from the Archivematica storage service (e.g. to port 8080)

Note
As a side-effect of using Cron Queues, the submission of objects to Archivematica may not complete during any one invocation of Cron. It is also recommended that cron run at reasonably frequent intervals (e.g. every five minutes), otherwise the expected callbacks may not be triggered often enough.

Versions Compared