![]() ![]() An organization code prefix, preferably 2 characters only.ġ.1.5.1.1.1. Each file name should have 4 components:ġ.1.5.1.1. This is a central organizing principle for the project project staff should review all incoming master files and edit file names whenever necessary files should be named carefully and in accordance with the following recommendations:ġ.1.5.1. File Name: file names given to master images will be preserved by all derivatives. Black and white prints with color tones (for example, a sepia tone) worth preserving: 24 bit RGB.ġ.1.5. Most black and white prints: 8 bit grayscale.ġ.1.3.2. Recommended: If the input resolution recommended above is not available using your scanner software, use the nearest available resolutionġ.1.3.1. If the input resolution recommended above is not an integer divisor of the maximum resolution, use the nearest resolution that is an integer divisor.ġ.1.2.5.5. Recommended: input resolution number should be an integer divisor of the maximum resolution of the scanner being used. Do not create an input resolution that differs from the scan resolution that is, do not "scale" the image at the scanner for printing.ġ.1.2.5.4. Required: in no case should interpolated resolution be used.ġ.1.2.5.3. Required: minimum resolution is 300 ppi, unless an organization arranges a smaller minimum.ġ.1.2.5.2. Images larger than 12 inches in the long dimension: scan at 300 ppi.ġ.1.2.5.1. Images between 7 and 12 inches in the long dimension: scan at 400 ppi.ġ.1.2.4. Images between 2 and 7 inches in the long dimension: scan at 600 ppi.ġ.1.2.3. Images less than 2 inches in the long dimension: scan at 800 ppi.ġ.1.2.2. Scan Resolution (this refers to the actual resolution at which the scanner scans): recommendations :ġ.1.2.1. Analog camera (scan from negative).ġ.1.2. Formats too large for a flatbed scanner:ġ.1.1.2.2. Anything more ambitious was outside the scope of our efforts.ġ. We publish these specifications without citations, annotations or explanations/justifications for our decisions primarily as an indicator of our project's direction rather than to give direction to other projects. Given the marginal importance of these specifications in the project, they were written on-the-fly and a bibliography of sources was not practical to maintain, let alone annotations for specific passages and assertions. In all cases, whether guided by these specifications or by instruction sheets based on these specifications, the recommendations of these specifications were only loosely followed. Thus this was written as a working document, a practical document, not as a theoretical document or work of scholarship.Īs the digitization work for this project was "distributed" - that is, project planners designed this project so that many different people in many different places would create digital objects for the project - the specifications were not intended to be read by all digitizers in fact, the specifications were most often used to draft "how to" sheets custom-written to meet specific needs. ![]() This was necessary due to the distributed nature of the digitization process and the need to follow standards and best practices. These specifications were written to guide the digitization of all media types for the Olympic Peninsula Community Museum Project. Copy for University of Washington Archive Media Type 4: Three Dimensional Objects (and generally anything digitized using a digital camera)Īreas of description in these specifications. Media Type 3: Slides (and other positive transparencies)Ĥ. Introduction: brief explanation of these specificationsģ. ![]() Areas of Description in these Specifications Prepared by Theodore Gerontakos for the Olympic Peninsula Community Museum Project SPECIFICATIONS FOR DIGITIZATION Version 3 (third and final draft, twelfth revision) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |