HathiTrust Call for US Federal Government Documents Records
November 8, 2013

We are requesting all records to be submitted by *January 31, 2014*.

HathiTrust is issuing a broad call for cataloging records of US federal government publications to be used to compare the holdings of our institutions and understand what portion of the corpus is already in HathiTrust, what portion not in HathiTrust has been digitized by Google or other entities, and what portion remains to be converted to digital format. A full description of the records specifications and requirements for this call is available below. The results of the analysis will be made available at a minimum to those who submit records for analysis, and the records themselves will be available to be used, under appropriate use policies and permissions, by government documents initiatives underway by groups and organizations participating in the call.

Please note that the first part of the analysis we will conduct will involve sending records to Google, to compare with records of materials that Google has already digitized. Any records submitted to Google may be incorporated into a “metadata view” on Google Books (if a record for the item does not already exist; records would not be displayed in their entirety. An example of metadata view is available here: http://tinyurl.com/n7x2xco).

Please see http://www.hathitrust.org/usgovdocs for a list of Frequently Asked Questions and their answers.

Requirements for what to send:

1. Records in all formats (print, electronic, micoform, etc.) identified as, believed to be, or that have a possibility to be, US federal government documents.
2. Records must be submitted as one record per item where more than one distinct item is attached to a record (e.g., for multi-part monographs or serials).
3. MARC21 records must use well-formed UTF-8, be wrapped in MARC XML (http://www.loc.gov/standards/marcxml), and include at a minimum the LDR, 008, and $245|a (or $245|k, when applicable) fields. Records that do not have these fields may be submitted, but should be placed in a separate file named as follows: <MARCOrgCode>-20131002-0300-non_conforming.xml.
4. Records in formats other than MARCXML should be placed in a separate file named as follows: <MARCOrgCode>-20131002-0300-<format>.<appropriate extension>.
5. Files containing the records should be submitted to a single directory designated by a HathiTrust representative who will be in touch after this form is submitted. The format of the filenames should be as follows: <MARCOrgCode>-20131002-0300.xml. If no MARC Organization Code exists, the domain of the URL of the institution should be used as a substitute (e.g., umich for the University of Michigan, which has a URL of http://www.umich.edu).
6. Each file should be no larger than 64 MB in size. Multiple files may be placed into a single zip file.
7. If multiple files are submitted, they should be named with an incremented number at the end, e.g., <MARCOrgCode>-20061002-0300-1.xml, <MARCOrgCode>-20061002-0300-2.xml, etc.

When you are ready to submit records, please fill out the administrative information below describing your records and records submission. Soon after you submit the form, we will be in touch with the location of a shared space for you to upload your records. If you have any questions, please email feedback@issues.hathitrust.org.

Thank you very much!
Sign in to Google to save your progress. Learn more
Institution/Organization contributing records *
Example: University of Michigan
Name of contact for this submission *
Title of contact for this submission *
Email address of contact for this submission *
Institution/Organization URL domain *
Example: for http://www.umich.edu enter umich; for http://www.umd.umich.edu enter umd.umich
MARC Organization Code
Desired. See http://1.usa.gov/KJFuL0. Please enter brief explanation if not available.
Institution primary OCLC symbol
Desired. Example: EYM
Name and version of ILS used to create/store/export records
Desired. Example: Aleph, version 20
MARC location of local system numbers *
Required if available. Please provide an explanation if not available.
Syntax/formatting for local system record numbers
Desired. Example: 9 digits, with leading zeroes
MARC location of (master) OCLC numbers
Desired.
Prefixes for (master) OCLC numbers
Desired. Example: ocn, ocm, (OCoLC), (OCLC).
MARC location of classification number
Desired. Please indicate the locations, if known, for any classification numbers. This could be the SuDoc number, MARC field 086 $a; the  LC number, MARC field 050 $a, $b ; or the Dewey number, MARC field 092 $a. Classification numbers may also be located in the 060, 082, or 09x.
Structure of local classification number in 09X field, if no other classification number is provided
Desired.
MARC location of item barcode or other item identifier *
Required. Please provide an explanation if not able to include. This is important for Google analysis. Each record should include the item barcode or other item identifier (if no identifier is available, please include a pseudo identifier). This and any item-specific information (e.g., enumeration chronology) should be included as separate subfields of a library-specific field, preferably the 955, with the item identifier in a 955|b subfield and enumeration/chronology in a 955|v subfield.
MARC location of item enumeration and chronology *
Required, if available. Should be placed in a field together with the item identifier (see immediately above). Please provide an explanation if available but cannot be included.
Name of file and format of records for any records submitted in a format other than MARCXML
Required, if submitted.
Name of file containing any records that do not meet minimum requirements (listed in #3 of the requirements section).
Required, if submitted
Please enter any additional information here
Submit
Clear form
Never submit passwords through Google Forms.
This form was created inside of University of Michigan. Report Abuse