Page History

...

It was developed in a partnership between Artefactual Systemsand  and Discovery Garden, sponsored by the University of Saskatchewan Library.

...

You may read more about Archivematica here.

About Archidora

...

• Presentation by Justin Simpson, Artefactual at the iCamp BC - February 16 - 18, 2015
• Archidora: Integrating Archivematica and Islandora, Code4Lib Journal, January 2018

Download

Islandora module: https://github.com/Islandora-Labs/archidora

...

This integration is currently (as of 1.6/0.10 release) considered a beta feature. Support for Archivematica and/or the Storage Service running on secure servers (https) will likely require Storage Service 0.11 or later.

Installation

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

...

• 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.
• Make sure the Pipeline is configured with the correct credentials (with API username and API key matching the appropriate dashboard user)

...

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. Note also that the callback does not currently work on objects whose access are is restricted by a XACML policy.

...

• Add the IP address of the storage service to the IP whitelist for the REST API. This is needed to allow transfers to be approved automatically.

Storage Service - gunicorn settings

• The default SS gunicorn worker class (gevent) is incompatible with Python's multiprocessing package, which is required for the Sword API. To resolve this:

1. Add the line `env SS_GUNICORN_WORKER_CLASS=sync` to the AM SS service config file at /etc/init/archivematica-storage-service.conf.

2. Reload the config and restart the SS service:

    $ sudo initctl reload-configuration
    $ sudo service archivematica-storage-service restart

3. Check the SS logs and expect the last Using worker line to be Using worker: sync and NOT Using worker: gevent:

    $ sudo vi /var/log/upstart/archivematica-storage-service.log

Archivematica automation tools:

• It is recommended that automation tools be used to regularly clean up the Archivematica dashboard (transfers and ingests). With too many transfers/ingests remaining on the dashboard, response time becomes very slow. A script is available to hide completed transfers and ingests. If a transfer/SIP is rejected or fails, it will remain on the dashboard, but otherwise (even if there are other errors) it will be hidden.
• This script is part of Artefactual Systems' automation-tools repository (transfers/amclient.py). Crontab can be used to invoke it regularly.
  

  sudo python amclient.py close-completed-transfers --am-user-name <username> <archivematica-api-key>

  sudo python amclient.py close-completed-ingests --am-user-name <username> <archivematica-api-key>

  where archivematica-api-key is the API key for the dashboard user.

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)

...