...
- No blanket digitization standard is applied to all materials. Each project has unique characteristics and therefore procedures and standards must be tested, discussed, and agreed upon before digitizing.
- Missing Pages: if scanned by Document Services, they will include a page in the pdf with the message that the page was missing in the original.
- OCR will be performed on all typeset items if print quality permits; excluding handwritten text. Handwritten text usually requires manual transcription.
- Image Derivative creation is available as a fee based service only from vendors. Sponsors are welcome to do this on their own.
- File disposition: https://wikis.mit.edu/confluence/spaces/gliffy/viewlargediagram.action?name=File Disposition** RDrive:DSpace Images - the master files will reside in this folder prior to ingestion
- Download locally for faster work ex. Cataloging - download to work locally then only upload the metadata or derivatives
- Never overwrite or replace files on RDrive:DSpace Images
- Exception: When files are damaged or misnamed. Limited number of people who can do this
- Space requirements: DOT needs to approximate their needs for disk space on the R drive and communicate with IT Core. R:\DspaceImages is used as a staging area for files prior to ingest.
- OCA scanned files in Internet Archive will also be loaded into our repository.
- The digital copy is considered one of the “two copies” for the libraries. The disposition of the physical copies is up to the sponsoring library. Blanket decision? The libraries decision? REQUEST DECISION FROM IRLSpace requirements: DOT needs to approximate their needs for disk space on the R drive and communicate with IT Core. R:\DspaceImages is used as a staging area for files prior to ingest. Once a project has been ingested and all issues addressed, DOT determines when the files can be deleted from the staging area. As the amount of digitization projects increase there will be a greater need for more space in our staging area.
Filenaming:
- As we create new collections, it is useful if there is consistency in the filenames assigned to digital objects. This document contains a recommended filenaming schema developed in 2008 for use in the MIT Libraries: https://wikis.mit.edu/confluence/x/-wIrAQEach collection will impose its own restrictions on filenames, but following the requirements outlined in this documents will ensure basic consistency across collections and make later processing of the files much easier. In general, we won't change the file names on born-digital material unless the names violate the Requirements and Best Practices in this document.
...