# When enough item scans have passed quality control checks 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) by Digital Services. 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.

+

# When enough item scans have passed quality control checks 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) by Digital Services. For instructions on how to prepare batch metadata see here: [[BATCH_Metadata]] 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. <br /><br />Digital Services will note - in the original collection metadata Excel file - which items correspond to this batch. This shall be done via entering the information into a column in the Excel version of the collection metadata. In this fashion, we keep track of which batch we're on. <br /><br />This column and it's cells must be excluded from any subsequent text files that are generated for MODS or Storage purposes.<br /><br />

−

## Digital Services will note - in the original collection metadata Excel file - which items correspond to this batch. This shall be done via entering the information into a column in the Excel version of the collection metadata. In this fashion, we keep track of which batch we're on.

+

# This subset of the collection metadata is then exported from Excel as a tab delimited .txt file and is placed in the appropriate collection metadata folder in s:\Digital Projects\Digital_Coll_Complete by Digital Services.

−

### This column and it's cells must be excluded from any subsequent text files that are generated for MODS or Storage purposes). In this fashion, we keep track of which batch we're on.

+

# The .xlsx version of this metadata subset is placed into S:\Digital Projects\Administrative\collectionInfo\forMDlib\needsRemediation by Digital Services.

−

# 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 by Digital Services.

+

# Metadata Services then applies the same steps as for single batch collections in terms of MODS generation and exporting a .txt files to delivery to Jody for Storage.

−

# The .xlsx version of this metadata subset is placed into S:\Digital Projects\Administrative\collectionInfo\forMDlib\needsRemediation by Digital Services. Metadata Services applies the same steps as for single batch collections.

+

−

==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.

+

:*If there *is* a collnum.2.xlsx or collnum.2.txt, and there is a collnum.xlsx or collnum.txt in the same directory, 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.

−

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.

This PowerPoint, such that it is, has been commented out given that the process it outdated.

+

-->

+

+

[http://intranet.lib.ua.edu/wiki/digcoll/images/d/db/MetadataMovement.DS-MU.pdf Workflow between Digital Services and Metadata Services regarding Excel files/metadata] - This does not cover the creation of MODS files or how Metadata Services delivers tab-delimited metadata for long term Storage.

Revision as of 09:11, 6 August 2013

Diagram of metadata movement for content being digitized in Digital Services effective November 2009: File:Metadata.pdf

When enough item scans have passed quality control checks 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) by Digital Services. For instructions on how to prepare batch metadata see here: BATCH_Metadata 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.

Digital Services will note - in the original collection metadata Excel file - which items correspond to this batch. This shall be done via entering the information into a column in the Excel version of the collection metadata. In this fashion, we keep track of which batch we're on.

This column and it's cells must be excluded from any subsequent text files that are generated for MODS or Storage purposes.

This subset of the collection metadata is then exported from Excel as a tab delimited .txt file and is placed in the appropriate collection metadata folder in s:\Digital Projects\Digital_Coll_Complete by Digital Services.

The .xlsx version of this metadata subset is placed into S:\Digital Projects\Administrative\collectionInfo\forMDlib\needsRemediation by Digital Services.

Metadata Services then applies the same steps as for single batch collections in terms of MODS generation and exporting a .txt files to delivery to Jody for Storage.

If there *is* a collnum.2.xlsx or collnum.2.txt, and there is a collnum.xlsx or collnum.txt in the same directory, 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.