A batch is simply a portion of a collection that goes through the upload process bundled together. This page contains or links to information related to the batching process and what differentiates it from a whole-collection upload.

A batch is simply a portion of a collection that goes through the upload process bundled together. This page contains or links to information related to the batching process and what differentiates it from a whole-collection upload.

−

==When to make a batch==

+

==Creating a Batch==

−

A new batch is created when you decide to upload content from an ongoing collection. This almost always happens when you've broken off and numbered a new [[Scans folder]], but it is possible to upload several Scans folders at once. Whatever the case, the content from a particular collection which is uploaded together is a batch, and this content should be ''no more than 300 items or 4000 captures.''

+

===What is a batch?===

−

==Documentation for a batch==

+

A new batch is created when you decide to upload content from an ongoing collection. This almost always happens when you've broken off and numbered a new [[Scans folder]], but it is possible to upload several Scans folders at once. Whatever the case, the content from a particular collection which is uploaded together is a batch, and this content should be ''no more than 300 items or 4000 captures.''

===Dual role of the metadata spreadsheet===

===Dual role of the metadata spreadsheet===

−

As of January 2013, tracking data is incorporated into the metadata spreadsheet during the capture process. For the purposes of this explanation, metadata refers to the data which goes online, while tracking data is the internal, administrative data we capture for our unit. Those columns are found at the end of the spreadsheet (after the Staff Notes and Batch columns).

+

As of January 2013, tracking data is incorporated into the metadata spreadsheet during the capture process. For the purposes of this explanation, ''metadata'' refers to the data which goes online, while ''tracking data'' is the internal, administrative information we capture for our unit. Those columns are found at the end of the spreadsheet, and they should be removed before handing off the spreadsheet to the metadata unit.

−

===Isolating the batch within the metadata spreadsheet===

+

===Isolating a batch within the metadata spreadsheet===

* As you tracking your captures in the metadata spreadsheet, make sure to note in the Batch column that the item is part of the current batch.

* As you tracking your captures in the metadata spreadsheet, make sure to note in the Batch column that the item is part of the current batch.

Line 17:

Line 17:

* When you are ready to upload a batch, sort the spreadsheet by the Batch column; this will bring all of the lines of metadata for that batch together

* When you are ready to upload a batch, sort the spreadsheet by the Batch column; this will bring all of the lines of metadata for that batch together

−

===Creating batch documentation===

+

==Batch Documentation==

−

* ''Batch metadata spreadsheet''

+

===Batch Spreadsheet===

−

** Copy the batch metadata to another sheet, and also the spreadsheet headers

+

* Used by: the Metadata Unit

−

*** Do not copy the tracking data

+

* Used for: remediating metadata that has already gone online

−

** Save that sheet as a new, separate file, so that you don't alter the original collection metadata

** With a batch (unless it's the first), the collection info xml is already online, so you don't have to wait 24 hours for Acumen to index the items before you can run moveContent

+

** With a batch (unless it's the first), the collection info xml is already online, so you don't have to wait for Acumen to index the items before you can run moveContent

* Storage

* Storage

** You will not need the collection info xml file when you move the collection from the share drive to storage. In fact, the moveContent script will tell you to delete it...unless it is a new, improved version

** You will not need the collection info xml file when you move the collection from the share drive to storage. In fact, the moveContent script will tell you to delete it...unless it is a new, improved version

* Documentation

* Documentation

** Unless you're working on the last batch of a collection, do not move the collection from in progress to completed on the Selection spreadsheet

** Unless you're working on the last batch of a collection, do not move the collection from in progress to completed on the Selection spreadsheet

Revision as of 17:15, 8 January 2013

A batch is simply a portion of a collection that goes through the upload process bundled together. This page contains or links to information related to the batching process and what differentiates it from a whole-collection upload.

Creating a Batch

What is a batch?

A new batch is created when you decide to upload content from an ongoing collection. This almost always happens when you've broken off and numbered a new Scans folder, but it is possible to upload several Scans folders at once. Whatever the case, the content from a particular collection which is uploaded together is a batch, and this content should be no more than 300 items or 4000 captures.

Dual role of the metadata spreadsheet

As of January 2013, tracking data is incorporated into the metadata spreadsheet during the capture process. For the purposes of this explanation, metadata refers to the data which goes online, while tracking data is the internal, administrative information we capture for our unit. Those columns are found at the end of the spreadsheet, and they should be removed before handing off the spreadsheet to the metadata unit.

Isolating a batch within the metadata spreadsheet

As you tracking your captures in the metadata spreadsheet, make sure to note in the Batch column that the item is part of the current batch.

Note which items have been skipped by labeling them 'skipped' in the Batch column

When you are ready to upload a batch, sort the spreadsheet by the Batch column; this will bring all of the lines of metadata for that batch together

Batch Documentation

Batch Spreadsheet

Used by: the Metadata Unit

Used for: remediating metadata that has already gone online

To create a batch spreadsheet...

Select just the rows that belong to the batch, plus the header row

Deselect the tracking data, leaving the metadata

Save the selection as a new, separate file: a Microsoft Excel document (.xlsx)

Naming format: collectionnumber.batchnumber.m0number.xlsx

Example: u0003_0000193.2.m01.xlsx

Save this file to Administrative\Pipeline\collectionInfo\forMDlib\needsRemediation

With a batch (unless it's the first), the collection info xml is already online, so you don't have to wait for Acumen to index the items before you can run moveContent

Storage

You will not need the collection info xml file when you move the collection from the share drive to storage. In fact, the moveContent script will tell you to delete it...unless it is a new, improved version

Documentation

Unless you're working on the last batch of a collection, do not move the collection from in progress to completed on the Selection spreadsheet