LC Digital Repository Development and Support

---

Batch Manifest for Sanborn Maps

---

Table of Contents

Background	Components  ( Batch Manifest File , Attribute File )
Overview	Examples  ( Batch Manifest File , Attribute File )
Assumptions	Other Useful Information
Definition

Background

In 1998 the Sanborn Map Company (Sanborn) will begin digitizing its inventory of U.S. insurance maps and making them available via the World Wide Web. The LC Geography and Map Division and the National Digital Library Program are providing guidance to Sanborn in this endeavour.

In return for this assistance, Sanborn will deliver copies of its digitized maps to the Library of Congress. This will be done after the full inventory of U.S. insurance maps have been digitized; most probably sometime in the year 2008.

Overview

1. Each delivery event by which digitized material is transferred from the Sanborn Map Company to the Library of Congress will include one or more Batch Manifests that identify the contents of the delivery event.
2. All delivery events by which LC receives digitized material will contain a Batch Manifest for each batch included in the event, regardless of the medium used for delivery (e.g., CD/ROM, FTP, floppy disk).
3. The Batch Manifest will contain an entry, or record, for each file in the delivery event that contains digitized content.
4. The Batch Manifest will be the first thing associated with a batch that will be transferred to LC as part of a delivery event.

Assumptions

1. More than one delivery event may be required to transfer the full contents of a given batch of digitized objects from a vendor or other supplier to LC.
2. More than one batch of digitized files may be sent to the Library at a time. Each Batch Manifest encountered during a delivery event signals the start of a new batch and is immediately followed by the digitized files associated with that batch.
3. A batch may contain digitized material of any data type (e.g., sid, gif, tif, jpeg, wav, mpeg, SGML).
4. Information such as Dimensions (dpi) and Chromatic Value are assumed to be carried in the file header.

Definition:  The Batch Manifest identifies the digital files that comprise a digitized batch being delivered to the Library of Congress for quality review and incorporation into the LC digital repository. It also serves as the delivery vehicle for structural metadata attributes that were identified during each file's digitization process.

Components

1. Batch Manifest File:  Contains the list of files in the batch as well as metadata attribute values associated with each file.
2. Attribute File:  Identifies the fields carried in each Batch Manifest File entry and the order in which they occur.

Batch Manifest File:

1. File Name:  Consists of a Batch ID followed by a period (.) followed by the file extension MNF.   Example:  cd000004.mnf
2. The Batch ID identifies a set of digitized files being transmitted to the Library of Congress as a group, or batch. It consists of a two (2) character Media Type `followed by a six (6) digit serial number that is right justified and padded with leading zeros. Media Type indicates the means used to transmit the batch. The only media type currently defined is "cd" for CD/ROM. Others will be defined as needed.
3. Fields within Batch Manifest File entries will be of fixed length. Unless otherwise noted, the data in each field will be left justified and right padded with blanks for the full length of the field.
4. All Batch Manifest File data fields are required and must be present in each file entry. When a field does not apply to a given Batch Manifest File entry, it will be set to "hash" (#) marks for the full length of the field.
5. Data Fields: 

   Field	Field Name	Field ID	Length	Format	Default Setting	Req ?
   1	Batch ID	BID	8	Character String	No default; must be filled in.	Yes
   2	Aggregate Name	AGG	8	Character String	sanborn	Yes
   3	Item ID	ITEM	9	Character String	Entry ID (e.g., 01749_010)	Yes
   4	File Name	FN	16	Character String	EntryID_SerialNumber (SerialNumber is one-up count)	Yes
   5	File Extension	FXT	3	Character String ("tif" or "sid")	No default; must be filled in.	Yes
   6	File Size	FSIZE	7	Number (right justified; leading zeros)	n/a (####)	Yes
   7	File Size Unit	FSU	2	KB = Kilobytes   MB = Megabytes   GB = Gigabytes   TB = Terabytes   PB = Petabytes	MB = Megabytes	Yes
   8	Date Created	DATE	8	YYYYMMDD	Current date (e.g., 19981031)	Yes
   9	Creator ID	SUP	11	Character String	edr-sanborn	Yes
   10	Operator ID	OPR	4	Character String		Yes
   11	Equipment ID	EQU	5	Character String	No default; must be filled in.	Yes
   12	Original Content Type	OCT	2	01 = Audio 02 = Text 03 = Motion Visual 04 = Non-motion Visual	Non-motion Visual  (04)	Yes
   13	Digitized Content Use	DCU	2	01 = Archival 02 = Service 03 = Preview	TIF = Archival (01) SID = Service (02)	Yes
   14	Side Digitized	SIDE	1	0 = Front 1 = Back	Front (0)	No
   15	Presentation Sequence Number	PSEQ	3	Character String (right justified; leading blanks)	n/a (###)	No
   16	Page Type	PGT	2	01=Title Page 02=Index 03=Addendum	n/a (##)	No
   17	Printed Page Number	PPN	3	Character String (right justified; leading blanks)	n/a (###)	No
   18	Printed Sheet Number	PSN	6	Character String (right justified; leading blanks)	n/a  (######)	No
   19	Cover	CVR	4	0001=Front-Cover-Outside 0002=Front-Cover-Inside 0003=Back-Cover-Outside 0004=Back-Cover-Inside 0005=Full-Cover-Outside 0006=Full-Cover-Inside 0000=Other	n/a (####)	No
   20	Scanning Orientation	ORI	3	000 = 0 degrees 090 = 90 degrees 180 = 180 degrees 270 = 270 degrees	n/a (###)	No

6. File names for most digitized LC material are currently (Feb. 1998) limited to eight characters.  This is due to Disk Operating System (DOS) constraints during quality review.   By the time the Library receives files containing the digitized Sanborn maps (circa 2008), DOS will no longer be used in the handling of LC digital material and this limitation will no longer apply.

   Consequently, the file names for digitized Sanborn maps will be sixteen (16) characters long.  They will consist of an nine (9) character Entry ID followed by an underscore ( _ ) and a six (6) digit serial number.   The both the Entry ID and the serial number will be right justified and padded with leading zeros.  For example, 01749_010_000321.

7. Scanning Orientation Field:

   000	=	Top of scan is properly oriented.
   090	=	Top of image is 90 degrees clockwise from where it should be.
   180	=	Top of image is 180 degrees clockwise from where it should be.
   270	=	Top of image is 270 degrees clockwise from where it should be.

Attribute File:

1. File Name:  Consists of the Batch ID followed by a period (.) followed by the file extension "att."   Example:  cd004.att
2. The Attribute File contains one record for each field found in Batch Manifest File entries. These records are arranged in the order in which the fields appear in the Batch Manifest File.
3. Fields within the Attribute File record will be of fixed length. Data in the ID and Name fields will be left justified and right padded with blanks for the full length of the field. Data in the third field will be right justified and left padded with leading zeros.
4. Each Attribute File record will contain:

   Attribute File Field Name	Attribute File Field Length
   ID of Data Field in Batch Manifest File Entry	5
   Name of Data Field in Batch Manifest File Entry	25
   Length of Data Field in Batch Manifest File Entry	3

Examples of Attribute File and Batch Manifest File Data

• Attribute File for a batch of digitized Sanborn maps - Example

  BID	Batch ID	008
  AGG	Aggregate Name	008
  ITEM	Item ID	009
  FN	File Name	016
  FXT	File Extension	003
  FSIZE	File Size	007
  FSU	File Size Unit	002
  DATE	Date Created	008
  SUP	Creator ID	011
  OPR	Operator ID	004
  EQU	Equipment ID	005
  OCT	Original Content Type	002
  DCU	Digitized Content Use	002
  SIDE	Side Digitized	001
  PSEQ	Sequence Number	003
  PGT	Page Type	002
  PPN	Printed Page Number	003
  PSN	Printed Sheet Number	006
  CVR	Cover	004
  ORI	Orientation	003

• Batch Manifest File - Sample Entry

  Note:  In this example, blanks for padding are represented by the "dollar" sign and every other field has been underlined for the sake of clarity.

  cd000004sanborn$01749_01001749_010_000321tif0000056MB19981031edr-sanbornjdoe1234504020033##58$XIX$$$##000

  The underlining in this sample is for illustrative purposes only.   Do not include underlining in actual data!

Other Useful Information:

• Digitized Content Use:   Indicates how a the digitized content carried in a file will be used. Digitized content uses defined to date (02/98) include:
  

  Archival	-	File contains the richest, most complete representation of the data content that is available.
  Service	-	File contains data content that will be used to respond to, or service, user requests for data presentation (e.g., display, or printing). Such data content usually is less than archival but greater than preview in its level of completeness and quality.
  Preview	-	File contains data content that will be used to provide a summary presentation of the data. Such data content usually is the smallest, shortest, briefest representation of the data that is available. Data content that is used for preview purposes includes thumbnail images, film clips, and sound bites.

• Original Content Type:   Indicates the general physical nature of the original collection item from which a portion of digitized content was produced. The purpose of the Original Content Type attribute is to facilitate digital object presentation. Original Content Type does not indicate how the digital object was produced (e.g., scanned, encoded), nor does it indicate the genre or subject content of the digital object.

Go to:   Top  ,  Metadata Table List  ,  Structural Metadata Dictionary