Ingest workflows - smith-special-collections/sc-documentation GitHub Wiki

[NOTE: these workflows need updating.]

Page Table of Contents

Ingesting with IMI spreadsheet

(This is the previous workflow. See revised workflow for batch ingest with IMI here (draft))

compass-ingest-workflow-2018-01-31 Zoomable workflow visualization here

  1. Metadata is created in the metadata repository of record. For archival materials, this is ArchivesSpace. For bibliographic materials, this is Aleph. Metadata should not be created in Compass.

  2. In Compass, staff create an Islandora collection. A collection landing page is automatically created, which staff update in preparation for digital object and metadata ingest.

  3. An IMI metadata spreadsheet is prepared for ingest of metadata and digital objects to Compass. Metadata is copied from ArchivesSpace or Aleph. The spreadsheet is downloaded as a CSV. (Conversely, metadata could be exported from each system, transformed to CSV, then formatted appropriately in the IMI spreadsheet.)

  4. Metadata and objects are ingested into Compass, using the FTP or zip method.

  5. A list of Compass digital object URIs is compiled with their corresponding ArchivesSpace digital object instance identifiers or Aleph identifiers. For archival components, the Compass URI is entered into the File URI field in the file version sub record of the component's digital object instance (Component: Instance: Digital object: File version: File URI). For bibliographic records, the Compass URI is entered in the Electronic location and access field (856 4 ǂu).

Ingesting via API

  1. Metadata is created in the metadata repository of record. For archival materials, this is ArchivesSpace. For bibliographic materials, this is Aleph. Metadata should not be created in Compass.

  2. Archival component metadata, as well as specific archival object metadata (collection title, EAD location, etc.) and the archival component URI, is exported from ArchivesSpace. Bibliographic metadata, as well as the bibliographic record URI, is exported from Aleph as MARC XML.

  3. ArchivesSpace metadata is transformed into XML using a script. Refer to this mapping to see the correlation of archival metadata to Compass MODS.

  4. Dgital objects are ingested into Compass via IMI (with Titles and Identifiers only)

  5. The Compass URIs are compiled and xml metadata is added to Compass records

  6. ArchivesSpace or bibliographic records are updated with the Compass URI.

    • For archival components, the Compass URI is entered into the File URI field in the file version sub record of the component's digital object instance (Component: Instance: Digital object: File version: File URI)
    • For bibliographic records, the Compass URI is entered in the Electronic location and access field (856 4 ǂu)

ArchivesSpace to Compass synced metadata object ingest workflow

Note that the mapping used by the MODS exporter is experimental for collections other than YWCA.

Steps

Establishing a linkage between ASpace digital objects and Compass digital objects can be accomplished in different ways. What's most important is that there are digital object records ASpace that have file versions that point to the Compass object via its URL. This can be accomplished in many ways. For example the digital object records in Aspace could be created by hand and the file version be created by hand, pasting the Compass object URL into the URI field by hand. Or linkages can be established between the digital ASpace object records and the Compass objects via a local ID that is set when using batch creation scripts.

Mint DO local IDs

The local IDs link the LIBPRES files, the Compass objects, and the ASpace archival object records.

Ingest objects into Compass

With stub MODS record containing only Title and DO Local ID

Local ID field should look like this in the MODS:

<identifier type="local">smith_ssc_324_r373_m007</identifier>

Tools

  • IMI or whatever

Create the digital object records in ASpace

(adding the Compass URIs to the digital object records)

Tools

  • digitalobjecturiadd.py

Export MODS records from ASpace

Tools

  • exportASAOtoMODS.py

Ingest the MODS records into Compass

Run mods diff checker to generate list of MODS files to ingest. Then ingest using Islandora CRUD.

Tools

  • check_asis_mods_diff.py
  • Islandora datastream CRUD

Followup synchronizations

Repeat last two steps: export of MODS, and ingest of MODS