Migration Specialist

The MS writes scripts to prepare images for ingestion into the Oxford Common File Layout used by the Library Digital Repository (LDR) and prepare IIIF manifests. The MS remediates supplied metadata by replacing strings for place names in elements equivalent to dcterms:spatial with Getty Thesaurus of Geographical Names (TGN) codes, ISO 8601- or Extended Date/Time Format (EDTF) -compliant values in elements equivalent to dcterms:date and dcterms:temporal, and strings for language names in elements equivalent to dcterms:language with ISO 639-3 codes. Supplied metadata will be accompanied by mappings to the Europeana Data Model (EDM). The MS is responsible for inputting the supplied metadata into OCHRE and to supply the OCHRE Data Service with mappings to EDM.

The Digitization Unit (DU) of the Preservation Department creates a folder to store project documentation and creates a spreadsheet to serve as the project inventory. ("Project" here is used in the sense of "collection", treating each digital collection as a separate project.) This inventory will help to manage the entire project and should include one row per digital object. Because every step in this process depends on the inventory, it needs to be completed before any further work begins. In cases where that is impossible, the inventory should be produced in batches that are each as large as possible.

DU staff create a digital identifier (e.g., gms-0931, pres2019-0023₀₀₀₁) to track each digital object. This identifier is used for directory and file naming during the scanning process. DU staff add the digital identifier to the first column in the spreadsheet. Subsequent columns will include other identifying information.

DU staff create digital master files for each object and perform quality control. Files may be corrected or re-scanned if necessary. After quality control, the DU deposits the files and inventory in pickup areas (typically one for the files and one for the inventory), and alerts the MS that new objects are available for pickup.

The MS writes scripts to verify that files have been named according to specs, that they are well-formed and valid, and that all files produced conform to content specifications. These scripts should produce error logs that can be sent to DU staff to guide re-work.

The Project Coordinator (PC) is responsible for providing the metadata, which the MS may need to remediate as indicated in the Outline above.

Once the inventory, files, and metadata have been provided, the MS mints ARK identifiers (e.g., ark:61001/b2jt29x3v493) for each digital object to an internal database by writing SQL to INSERT new rows for each digital object. The MS adds the ARK to an ARK column of the spreadsheet inventory and adds it to the metadata. This will link the metadata to the files.

In the case of image files, the MS creates a tab-delimited file associating the ARK identifier with its IIIF address, e.g.,

b29b1tv7xn73 [TAB] https://iiif-server.lib.uchicago.edu/ark:61001/b29b1tv7xn73/00000001/

etc., and gives this file to the supervisor. In the case of audio or audio-visual files, the link will be to the address of the audio or audio-visual data in the Panopto viewer, e.g.

b24f7f568t5m [TAB] https://uchicago.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=ce89829d-04db-4d17-9bc6-afd301332ad0

Once files have been verified, MS ingests these files into OCFL using the ARK identifier from the inventory as the guide to the layout.

MS adds remediated metadata and any other corresponding file (e.g., OCR) for each digital file to OCFL. This completes the digital archiving process.

Based on full digital object packet in OCFL, including master image files and finalized metadata records, MS writes scripts to produce IIIF manifests. Metadata included in IIIF Manifests should match a spec supplied by the DLDC. Manifests should be uploaded to the manifest server.

Supervisor will update the ARK resolver with the ARK/IIIF corresondence using the tab-delimited file. This makes the ARK identifier actionable, in the sense that clicking on it will take the user to a URL that does something.

It the supplied metadata has come from the Library catalog, supervisor alerts Cataloging staff that objects are available via IIIF. Cataloging staff add actionable ARK identifiers (e.g., https://n2t.net/ark:61001/b2jt29x3v493) to the MARC record. Once these records have been updated in the catalog, the cataloging records will take the user to the appropriate file as displayed in the IIIF viewer. Image files will be available at URLs like https://iiif-collection.lib.uchicago.edu/object/ark:/61001/b2d05353d58m.json. The image server will pull images directly from OCFL.

The MS will input the remediated metadata into OCHRE and use the EDM mapping files to publish linked data for Node.