Skip to content
Branch: master
Find file History
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
..
Failed to load latest commit information.
README.txt
aspace_batch_dao.py
aspace_ead_to_tab.xsl
fits-to-json.xsl

README.txt

Boston College ArchivesSpace Batch DAO Process

Object: To automatically generate description in ArchivesSpace for digitized archival materials, and to re-use that description to ingest files into the Digital Libraries repository (currently DigiTool).

Steps:
1. When material is selected for digitization, it is identified in ArchivesSpace by the addition of a Component Unique Identifier at the level of digitization (usually but not always the File level). The format of the Compnent Unique Identifier is as follows: the collection identifier reformatted as LLYYYY_NNN_ followed by the unique database ID number of the object in question (which is present in the ASpace URL when you are viewing the object as "tree::archival_object_NNNN - we are only interested in the number at the end of the URL, and it may consist of any number of digits). As an example, a properly formatted Component Unique Identifier may look like this: MS2013_043_54063.

2. Once all objects selected for digitization within a given collection have been marked with CUIs, export the EAD for the entire collection with only the "include <dao> tags" option checked.

3. Transform the collection EAD into a tab-delimited file using aspace_ead_to_tab.xsl. Send a copy of this file to the digitizer, so that the CUIs can be used to generate filenames in the digitization process.

4. When the digitization is complete, the Digital Preservation Librarian runs FITS over the resulting files. Run the fits-to-json XSL over the FITS file, to create a .json file of technical metadata.

5. Run aspace_batch_dao.py from the command line with the following usage: "aspace_batch_dao.py tab_file.txt fits-file.json" where tab_file.txt is the output of aspace_ead_to_tab.xsl, and fits-file.json is the output of step 4. This will call on the ArchivesSpace API to create a Digital Object and Digital Object Components for each object and the image files that represent it. If there are errors, the object metadata in ArchivesSpace or various aspects of the python script may need editing.

6. After running aspace_batch_dao.py, there will now be a file titled "ids_for_manifest.txt'. This file can be used as input for the aspace-iiif gem to generate manifests for Mirador ingest.
You can’t perform that action at this time.