Diagram of metadata movement for content being digitized in Digital Services effective November 2009: File:Metadata.pdf
When content is ready for storage:
- put the Excel file into S:\Digital Projects\Administrative\collectionInfo\forMDlib\needsRemediation for Mary,
- export a Unicode tab-delimited text file (use Open Office) and put it with the content for storage
- use a copy of this txt file to generate MODS according to the instructions here: Making MODS
- and upload the MODS to Acumen by following the process outlined here: Uploading_MODS
- then delete the text file
- Retrieve deposited spreadsheet from S:\Digital Projects\Administrative\collectionInfo\forMDlib\needsRemediation, and remediate metadata appropriately
- Save the remediated spreadsheet in S:\Digital Projects\Administrative\collectionInfo\Storage_Excel
- Generate MODS records, according to the instructions here: Making MODS
- Upload these MODS records to Acumen by following the process outlined here: Uploading_MODS
- Deposit the exported Unicode tab-delimited collection-level metadata spreadsheet in S:\Digital Projects\Administrative\collectionInfo\JodyPickup
- Notify Jody it's ready for pickup
Jody: Digital Services
- If initial uploaded content includes text files in the Scans directory (i.e. item-level tab-delimited metadata), move those to S:\Digital Projects\Administrative\collectionInfo\forMDlib\itemMD\
- Notify Mary they're ready for pickup
- Pick up finalized spreadsheets from S:\Digital Projects\Administrative\collectionInfo\JodyPickup and transfer to the deposits directory on libcontent1
- Process for correct deposit into long term storage and linking in LOCKSS Manifests
Metadata Transfer and Remediation for Collections Requiring Multiple Uploads
- Metadata is originally held in a .xlsx file.
- After Digital Services has ensured that the metadata received from the archivists has been formatted to the standard metadata format, this set of metadata is kept on the first worksheet of the workbook. The "original" metadata (i.e. received directly from the Archivists) may exist on a separate tab of the spreadsheet, should the need to refer to it arise.
- When enough item scans have passed quality control checkls to warrant an upload of materials to Storage (i.e. a "batch"), the metadata corresponding to the items to be uploaded is copied out of the original set of metadata and pasted into a new Excel file (.xlsx). The naming convention for this file is collectionNumber.n.xlsx, where "n" is the numerical value of the batch. Ex: u0008_0000001.2.xlsx = the metadata for the second batch of items for collection u0008_0000001.
- This subset of the collection metadata is then exported from Excel as a tab delimited Unicode .txt file and is placed in the appropriate folder in s:\Digital Projects\Digital_Coll_Complete.
- The .xlsx version of this metadata subset is placed into S:\Digital Projects\Administrative\collectionInfo\forMDlib\needsRemediation, and remediated appropriately.
FOR ONGOING or LARGE COLLECTIONS
The following needs remediation: we are using tab-delimited UTF-8 text, not CSV. As each chunk of content is digitized, the tab containing the metadata will be pulled out of the main spreadsheet into a separate Excel file, numbered with the batch number (collnum.1.xlsx, collnum.2.xslx, etc.) and that will be deposited for remediation, and exported for MODS creation and upload for storage. The original reference metadata will contain an extra column for notation of which batch each segment of metadata belongs to. In this fashion, we keep track of which batch we're on.
This means that in Storage_Excel, we will wind up with multiple spreadsheets for each of the large or ongoing collections. This will also be the case in the archive. If there *is* a collnum.2.xlsx or collnum.2.txt, and there is a collnum.xlsx or collnum.txt, we will assume that the latter is the first segment of metadata for the collection. That is to say, it *is* the collnum.1.xlsx or collnum.1.txt file.
Diagram of metadata movement for collections requiring multiple uploads this image shows a potential policy: File:Metadata transfer and remediation.pdf