Preparing Collections on the S Drive for Online Delivery and Storage
Things to do before marking a folder as "Ready" or "Store"
The collection number u0003_0000001 will be used as an example.
Check Subfolders of Collection Level Folder
The Collection Level folder contains subfolders and their content must adhere to certain specifications prior to the collection being considered "Ready" (to go online via the Metadata Unit) or "Store" (to go directly into storage).
- This folder must exist.
- Must contain:
Make sure to refer to the Collection_Information page regarding acceptable types of content, etc.
- u0003_0000001.log.txt - include a text version of the log file with every batch; previous versions of the log will be overwritten by the newest version.
- May also contain:
- Thumbs Icon - .png extension.
- and other relevant documents saved as plain .txt (ANSI or UTF-8 without BOM preferred). If possible please incorporate any additional data into the log.txt file.
For example, audio collections often have significant item-level notes that we want to retain. These plain text files can be saved with a ".notes.txt" extension - i.e. "u0008_0000001_0000001.notes.txt".
- If multiple Digital Collections spawn from the same Analog Collection, there can be more than one Collection Information XML file as follows:
- This folder must exist.
- If going to Metadata Unit, must contain:
The Metadata Unit will convert this to a tab-delimited.txt file after adding subject headings, etc. and uploading the content. Will get converted to UTF-8 later.
If metadata for a set of scans being transported to Storage needs to be segmented out, instructions for doing so can be viewed here. The work of parsing out the metadata can be assisted by script; see: Parsing_Metadata.
- If going directly to Storage, must contain:
This is tab-delimited text export of the original spreadsheet. The prior .xlsx spreadsheet should be moved to S:\Digital Projects\Administrative\collectionInfo\Storage_Excel. Will get converted to UTF-8 later.
If this is a large or ongoing collection, the tab-delimited text export should contain ONLY the metadata for the items currently being transported to storage. The text file itself should have a period and then a number to indicate which portion of the complete metadata this is. The first tab-delimited export would be named, for example, u0003_0000001.1.txt, and would contain the first 500 entries, for example. The second tab-delimited export, for items 501-1000, would be named u0003_0000001.2.txt, and so forth. Thus, only by collecting all these tab-delimited exports do we have a complete set of descriptive metadata for the collection items.
If this is an ongoing collection, the Excel version of the metadata for the items currently being transported to storage must go in the Metadata Unit's remediation queue.
- May also contain (whether going to Metadata Unit or Storage):
All must use ANSI or UTF-8 without BOM encoding.
Additionally, if you (are comfortable with) XML, please open the EAD file and look for this line (should be the 4th one down): <eadid countrycode="US" mainagencycode="US-US-ALM"></eadid> If the collection number is not there (what we name the file: u0003_0000580) then please enter it, so that line looks like this: <eadid countrycode="US" mainagencycode="US-US-ALM">u0003_0000580</eadid> This way the file self-references, and can be found by this number during searches, if we index it properly. Also, if something gets misnamed somewhere, this will help to sort out the problem. - J Deridder, 082409
- This folder must exist.
Note: we may break Scans folders into chunks for manageability, for more information click here.
- Must only contain:
- scans (tiffs/wavs) of non-compound objects and compound objects (inside respective subfolders)
All other files types will not be retained. Temporary files and thumbs.db files do not have to be deleted since they will be removed upon transfer to Storage.
- This folder must exist only if transcripts exist.
- Must only contain one or more of the following types of files:
- u0003_0000001_0000001.tif, u0003_0000002_0001.tif, etc. - corresponding to non-compound and compound objects (inside respective subfolders).
- u0003_0000001_0000001.txt, u0003_0000002_0001.txt, etc. - plain .txt files corresponding to non-compound and compound objects (inside respective subfolders).
- u0003_0000001_0000001.ocr.txt, u0003_0000002_0001.ocr.txt, etc. - plain .txt files of OCRed tiffs corresponding to non-compound and compound objects (inside respective subfolders).
If cleaned up .txt files exist, remove the corresponding .ocr.txt file.
Perform Quality Control on Scans
Run Quality Control Scripts
Use the following PERL scripts from S:\Digital Projects\Administrative\scripts\qc
- filenames.pl - Checks for correct filenaming.
- numfiles.pl - Outputs the number or scans per object in a folder.
Always run numfiles.pl AFTER filenames.pl is run and all naming errors corrected in order to ensure an accurate report from numfiles.pl.
Spot check all .xml, .txt, and .xlsx files
- Check all such files for proper filenames and extensions.
- Open all such files and look for anomalies and inconsistencies, misspellings, and missing data, etc.
- make sure fields such as Funder(s), Funding Information, Repository Collection, Digital Collection, Digital Publisher, etc. are filled out.
- ideally, no additional fields such as "Notes" are in the Metadata file. "Notes" as such should be deleted or moved to the appropriate row in the log.txt file.
- make sure the Format column in the Metadata file has not been altered to the Time format as it sometimes is:
If a tab delimited metadata file is opened via Excel (especially by right clicking the file and choosing to open in Excel), the format column if like: 3 p., 4 p., etc. Will get interpreted as 3:00 PM, 4:00 PM, etc. If then resaved as .txt, times will have been saved instead of page #s. The way around this is to have Excel open first, choose Open. open your text file and while you are being interrogated by Excel about how to import, set the Format column as "Text".
Check all Folder names
- Make sure folders are named correctly and that there are no superfluous word concatenations to object level folders, etc.
Match Data across documents and folders
This table attempts to show how data in one of our documents/folders should match with data in another document/folder.
Corresponding data must properly match/equate prior to marking "Scans" folders - and especially collection level folders - as "Ready" or "Store".
|TrackingFileNames||Admin XML||Metadata||Archivist Queue (\"Selection.xlsx\")||TrackingFiles||Finding Aid||Scans folder|
|Collection Number||[first 14 characters of Filename]||Collection Number|
|physical location||Manuscript_Number [Is this true?]||Manuscript Number; Physical Location||MSS #|
|primary analog format||Genre [since there can be multiple genres in the metadata, this will correspond, in average, to the TrackingFileNames Primary Analog Format]||Genre/type|
|source collection||Analog_Collection_Name||Repository Collection||Name of Analog Collection||Title|
|Description||Digital_Collection_Description||Blurb||Abstract; or Scope and Contents [limited to digitized portion]|
|Digital_Collection_Name||Digital Collection||Project Name|
|Type_Of_Content||Type(s) [since there can be multiple Types in the Metadata, this will correspond, in average, to the Admin XML Type_of_Content]||Genre/type|
|Finding_Aid_Link||Link to finding aid|
|Total Scans (Scans + Transcript Scans)||[use PERL script or folder search to retrieve number of Total Scans (tifs or wavs)]|
|[count total objects in Metadata sheet]||Total Objects||[use PERL script or folder search to retrieve number of objects (singletons + compound object subfolders)]|
From a digital preservation/delivery perspective, it's not as important to match information to the Archivist Queue spreadsheet, though it would be ideal if possible. Also, it isn't always feasible to match the number of actual scans vs. what is notated in the TrackingFiles, although that is also ideal.