wrlc / archidora

Archivematica integration

SUMMARY

Archivematica Integration Module

REQUIREMENTS

Depends on Islandora.

INSTALLATION

Install as any other Drupal module.

CONFIGURATION

The Archivematica's Storage Service URL, user and user's API key will have to be entered into this modules 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, to be able to pull datastreams.

Archivematica may also be configured to call back to Islandora to delete the high-res "OBJ" datastreams.

Note: As a side-effect of using Cron Queues, the submission of objects to Archivematica may not complete during any one invocation of Cron.

Usage

Drush can be used to send existing collections to Archivematica. If the --children option is set to yes all subcollections and books will be be sent over as well.

drush asca --target=some:pid --children=no

archidora's Issues

Determining workflow directions

According to this site , this Islandora module should allow a workflow where files ingested in Islandora can be retrieved by Archivematica.

Given that our display/access repositories within WRLC generally seem to be more robust than our preservation layer, this is probably the more functional of the two workflow directions in the short term. Especially if the initial priority is to sync/preserve everything in Islandora.

However, it would also be important to explore a way to retrieve or share content between preservation and access (the opposite workflow).

The original repo for this archidora module has not been updated in over 3 years, but I have forked this repo from a member of the Islandora committee who has committed updates and features to archidora much more recently.