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

+

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 ''500-1000 captures, optimally 600-850.''

* Used for: telling MakeJpegs which files to process through Tesseract

−

−

To create a batch OCR list, see [[OCR List | these instructions]]

===Note on naming files made from older spreadsheets===

===Note on naming files made from older spreadsheets===

Latest revision as of 08:38, 8 January 2016

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 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 500-1000 captures, optimally 600-850.

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.

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