Digital Reserves Image Scanning

Receiving Books from Access Services

1. Access Services determines books needing to be scanned.
2. Access Services updates the shared spreadsheets with identified books.
3. Access Services delivers books to a shelf on D-Level, Widener Library.

Batching Books together to Imaging Labs

1. Imaging Services will assemble the books into batches based on owning repository, page count, disbind-allowed and moves batches into proper production stream.
   1. If the books should not been disbound, they will be delivered to our high-volume digital scanning studio (D20).
   2. If the books are allowed to be disbound, they will be sent to the Collection Care for disbinding, when the books are returned to IS, they will be sent to our High-speed sheet-fed scanner.
2. Imaging Service will create tickets in our Aeon order tracking system to track the production status.

 
Note: the images from bound and sheet-fed workstations are slightly different.

• A book scanned as bound at one of our scanning workstations
• A book scanned at high-speed sheet-fed scanner

Image Scanning and Quality Control

• Our labs will treat the Digital Reserves batches as high priority
• The images will be saved as 300 dpi color TIFF
• The image filename will be [MMSID]_####.tif or [MMSID]_V###_####.tif (if the book is one of the volumes in a series).
• The staff in the labs will go through a quality control process.
  • Checking for completeness
  • Checking the image quality
• After QC, scanning labs staff will notify the processing and depositing unit for the scanning completion

Image Processing and Uploading

1. Processing and uploading unit staff will run a script to:
   1. generate ALTO files from the TIFF images (the MMSID will be used to retrieve language code(s) from the cataloging system);
   2. generate medium quality  (quality: 92) full-size JPEG files from the TIFF images;
   3. generate meta file metadata-[MMSID].xml for ALMA-D uploading;
   4. the metadata XML file, ALTO and JPEG files for the books will be saved at a staging area on the Imaging Services file server.
2. Processing and uploading staff move the files (XML, ALTO, and JPEG) from staging area to a NextCloud local directory.
3. A tracking file for the day will be saved in a NextCloud local directory. The file contains the MMSID, the date the items added into the cloud, and the estimated date the item to be loaded into ALMA.
4. The NextCloud local directores will be synchronized with the server.

Imaging Services Contact Information

Imaging Services Office: imaging@fas.harvard.edu

Bill Comstock: comstock@fas.harvard.edu

Mingtao Zhao: mzhao@fas.harvard.edu
Hilary Kline: kline@fas.harvard.edu
Kai Fay: kfay@fas.harvard.edu