NTL / MARC VARIABLE FIELD MAPPINGS

The National Transportation Library has created this crosswalk from NTL’s extended Dublin Core metadata to MARC to make NTL data more accessible to other libraries and information sources.

Note: Whenever possible, NTL field names are used in the underlined headings. If a heading is in square brackets, it does not have a corresponding field name. Items in bold are NTL field names.

001 - NTL record ID

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: NTL record ID number
  • EXAMPLE:
    001 # # $a []

003 - [Control number identifier]

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: [Control number identifier]
  • EXAMPLE:
    003 # # $a 3878779798

020 - ISBN

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: contents of ISBN field
  • EXAMPLE:
    020 # # $a 3878779798

022 - ISSN

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: contents of ISSN field
  • EXAMPLE:
    022 # # $a 0090-001X

035 - OCLC number

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: (OCoLC) contents of OCLC number field
  • EXAMPLE:
    035 # # $a (OCoLC)7374506

043 - Geographical coverage

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: contents of code in the Geographical coverage field
    Each location should be assigned its own Subfield a
  • EXAMPLE:
    043 # # $a n-us-md

088 - Use for Contract number(s), Report number(s), TRIS accession number, and NTIS number

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Contents of Contract number(s), Report number(s), TRIS accession number and NTIS number fields
    Each number should be assigned its own Subfield a
  • EXAMPLE:
    088 # # $a DOT-HS-810-762

100, 110, & 111 fields

IMPORTANT NOTE: There can be only one 100, 110, or 111 field in each record. If the item’s Resource type is “Proceedings”, the data in the Conference title field should be placed in a 111 field. Otherwise, the first personal creator listed should be the default entry in the 100 field. If there are no personal creators, a 110 field should be created for the first corporate creator listed in the record. All other personal and corporate creators/contributors should be assigned separate 700 and 710 fields, as appropriate

100 - Personal creator

  • Indicator 1: 1
  • Indicator 2: #
  • Subfield a: personal name
  • Subfield c: titles and other words associated with the name
    Separated from the rest of the name by [comma][space]
  • Subfield q: fuller form of name
    Name should be inserted in parentheses
  • Subfield d: dates associated with the name
    Separated from title by [space][comma]
  • EXAMPLES:
    100 1 # $a McGuire, John P. $q (John Patrick), $d1937-
    100 1 # $a Huntley, M. Stephen, $c Jr.

110 - Corporate creator

NOTE: This field is for the first corporate creator listed only. All other corporate creators should be assigned separate 710 fields

  • Indicator 1:
       1 - jurisdiction name (if name starts with United States[period])
       2 - name in direct order
  • Indicator 2: #
  • Subfield a: first part of Corporate creator name (break at [period])
  • Subfield b: subordinate unit (remainder of Corporate creator name)
    Separated from the rest of the name by [period][space]

    There may be multiple subordinate units (break at [period]); each should have it’s own subfield b
  • EXAMPLES:
    110 1 # $a United States. $bNational Highway Traffic Safety Administration
    110 2 # $a University of Michigan. $b Highway Safety Research Institute. $b Policy Analysis Division

111 - Conference Title

NOTE: This field is only used if the Resource type is “Proceedings”. If the Resource type is “In proceedings”, all conference title information should be placed in a 711 field.

  • Indicator 1: 2
  • Indicator 2: #
  • Subfield a: first part of conference name
  • Subfield c: location of conference
  • Subfield d: date of conference
  • Subfield e : subordinate unit (remainder of conference name)
  • Subfield n: conference number
  • EXAMPLE:
    111 2 # $a International High-Occupancy Vehicle (HOV) Systems Conference $n (11th : $d 2002 : $c Seattle, Wash.)

245 - Title

  • Indicator 1:
       0 - use if there is no author entered in either the Personal or Corporate creator fields
       1 - use at all other times
  • Indicator 2: number of non-filing characters present at the beginning of the title (0-9)
    Note: the space following A, An, and The is counted.
  • Subfield a: main title
  • Subfield h: [electronic resource]
  • Subfield b: subtitle
    Separated from the title by [space][colon][space]
  • Subfield n: number of a section of a work, such as “Volume 2”
    Separated from title by [space][period]
  • Subfield p: name of a section of work
    Separated from the number of the section by [comma][space]
  • Subfield c : all creators’ names un-inverted (e.g. “Smith, John” changed to “John Smith”)
    This includes all entries in the Personal creator(s) field.
    If there are no personal creator(s), include all entries in the Corporate creator(s) field here instead.
    Exception: If there are more than three Personal creator(s), only the first one is listed followed by the phrase “et al.”
    Separated from the rest of the title by [space][slash][space]
  • EXAMPLES:
    245 1 3 $a An evaluation of a community service sanction for DWI $h[electronic resource] : $b the Baton Rouge community service work program. $n Volume 2, $p Community action programs / $c National Highway Traffic Safety Administration
    245 1 0 $a Use of intermediaries in DWI deterrence $h[electronic resource]. $n Volume 1, $p Phase 2 report : $b development of intermediary programs / $c William A. Cozzens

246 - Alternate title

  • Indicator 1: 3
  • Indicator 2: #
  • Subfields - same as 245 subfields (except subfields h & c are not used)
  • EXAMPLE:
    246 3 # $a Experimental field test of proposed anti-dart-out training programs. $n Volume 3, $p Program staff training materials and videotape/film An evaluation of a community service sanction for DWI

260 - Publication information & Copyright

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: place of publication
    From publisher information
  • Subfield b: Corporate publisher(s) or Personal publisher(s)
    Separated from place of publication by [space][colon][space]
    If there are multiple publishers, separate them by [space][colon][space] and a subfield b
  • Subfield c: dates of publication and/or copyright
    From Publication date field - year only
    Separated from the publisher name by [comma][space]
    If the Probable date box is checked, put square brackets around the date
    If a there is a date stored in the Copyright date field, insert it using the following format: [comma][space]c[date]
  • EXAMPLES:
    260 # # $a Washington, D.C. : $b United States. National Highway Traffic Safety Administration, $c 2006, c2005
    260 # # $a Washington, D.C. : $b United States. Dept. of Transportation, $c [1967]

300 - Physical description

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: extent (e.g. number of pages, total playing time, etc.)
  • Subfield b : other physical details (e.g. illustrations)
    Separated from the earlier data [space][colon][space]
  • EXAMPLE:
    300 # # $a iv, 7 p. : $b col. ill.

310 - [Current publication frequency]

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Frequently updated
    Only use for documents with Fixed Field bibliographic level “i”
  • EXAMPLE:
    310 # # $a Frequently updated

500 - Edition

NOTE: Each Edition listed should be assigned its own 500 field

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Place each Edition statement in quotation marks (“ “)
  • EXAMPLE:
    500 # # $a “Final report”

500 - [Date viewed note]

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Title and description based on contents viewed [date]
    Pull [date] information from Date Captured field and put them in direct order (Month Day, Year)
  • EXAMPLE:
    500 # # $a Title and description based on contents viewed May 16, 2007

500 - Personal contributor(s)

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Contributor: [contents of Personal contributor(s) field, un-inverted]
    If there is more than one personal contributor, change “Contributor” to “Contributors” and put a comma between the names
  • EXAMPLE:
    500 # # $a Contributors: Marvin Levy, J. Neil Russell

500 - Corporate creator(s)

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Performing organization: [contents of Corporate creator(s) field]
    Only use if there are Personal Creators in the record
    Remove the periods between the main section of the name and any subordinate units
    If there is more than one Corporate Creator, change “organization” to “organizations” and put a comma between the names
  • EXAMPLE:
    500 # # $a Performing organization: Anacapa Sciences, inc.

500 - Corporate contributor(s)

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Sponsoring agency: [contents of Corporate contributor(s) field]
    Remove the periods between the main section of the name and any subordinate units
    If there is more than one personal contributor, change “agency” to “agencies” and put a comma between the names
  • EXAMPLE:
    500 # # $a Sponsoring agencies: United States National Highway Traffic Safety Administration, United States Federal Highway Administration

500 - Contracting officer

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Contracting officer: [contents of Contracting officer field, un-inverted]
    If there is more than one contracting officer, change “officer” to “officers”
  • EXAMPLE:
    500 # # $a Contracting officer: John C. Fegan

500 - Notes

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: contents of the Notes field
    Each note should be assigned its own Subfield a
  • EXAMPLE:
    500 # # $a Report originally published February 2006, this edition is an October 2007 reprint

513 - Period covered

  • Indicator 1: #
  • Indicator 2: #
  • Subfield b: contents of Period covered field
  • EXAMPLE:
    513 # $b January 2003 - December 2004

520 - Abstract

  • Indicator 1: 3
  • Indicator 2: #
  • Subfield a: contents of Abstract field
  • EXAMPLE:
    520 3 # $a This report (Volume 3 of three volumes) provides detailed descriptions of additional program materials suggested for use with the recommended version of a child pedestrian safety program. This volume contains additional materials and videotape/film scripts which have been recommended for use in the program. Training programs for the program coordinators and instructors are included, in addition to a program introductory videotape/film and videotape/film training vignettes for use in personnel training. /Abstract from report summary page/

538 - [Mode of access]

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Mode of access: World Wide Web
  • EXAMPLE:
    538 # # $a Mode of access: World Wide Web

540 - Copyright Information

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: Copyright: [contents of Copyright field]
  • EXAMPLE:
    540 # # $a Copyright: Copyright © 2005, Commonwealth of Virginia. All rights reserved.

650 - Use for TRT Terms

NOTE: Each term listed should be assigned its own 650 field

  • Indicator 1: #
  • Indicator 2: 7
  • Subfield a: contents of the TRT term(s)
  • Subfield 2: Transportation Research Thesaurus
  • EXAMPLE:
    650 # # $a Asphalt pavements $2 Transportation Research Thesaurus

690 - Use for NTL Classification and Subject keyword(s)

NOTE: Each term listed should be assigned its own 690 field

  • Indicator 1: #
  • Indicator 2: #
  • Subfield a: contents of the TRT term(s), and Subject keyword(s) fields
    Include only the first level of the NTL Classification here
  • Subfield x: second level of the NTL Classification
  • EXAMPLES:
    690 # # $a Household survey
    690 # # $a Marine/waterways transportation $x Marine safety

700 - Use for remaining Personal Creator(s), and all Personal Contributor(s) or Contracting Officer

NOTE: Each person should be assigned a separate 700 field

  • Indicator 1: 1
  • Indicator 2: #
  • Subfield a: personal name
  • Subfield c: titles and other words associated with the name
    Separated from the rest of the name by [comma][space]
  • Subfield q: fuller form of name
    Name should be inserted in parentheses
  • Subfield d: dates associated with the name
    Separated from title by [space][comma]
  • EXAMPLE:
    700 1 # $a Solomon, M. G. $q (Mark Geoffrey)

710 - Use for remaining Corporate Creator(s) and any Corporate Contributor(s)

NOTE: Each Corporate creator/contributor should be assigned a separate 710 field

  • Indicator 1:
       1 - jurisdiction name
       2 - name in direct order
  • Indicator 2: #
  • Subfield a: first part of corporate name
  • Subfield b: subordinate unit (remainder of corporate name)
    Separated from the rest of the name by [period][space]
    There may be multiple subordinate units; each should have it’s own subfield b
  • EXAMPLE:
    110 2 # $a University of Arkansas, Fayetteville. $b Dept. of Industrial Engineering

711 - Conference Title

NOTE: This field is only used if the Resource type is “In proceedings”. If the Resource type is “Proceedings”, all conference title information should be placed in a 111 field.

  • Indicator 1: 2
  • Indicator 2: #
  • Subfield a: first part of conference name
  • Subfield c: location of conference
  • Subfield d: date of conference
  • Subfield e: subordinate unit (remainder of conference name)
  • Subfield n: conference number
  • EXAMPLE:
    711 2 # $a International High-Occupancy Vehicle (HOV) Systems Conference $n (11th : $d 2002 : $c Seattle, Wash.)

77x fields

NOTE: The indicators and subfields are all the same for all 77x fields. Individual field titles are listed below.

773 - Use for Journal and Is Part Of
774 - Contains

775 - Is version of

  • Indicator 1: 0
  • Indicator 2: #
  • Subfield t: Journal title
  • Subfield g: Vol. Volume[comma][space]no. Issue[space][open parentheses]PublishedDateMonth PublishedDateDay [comma] PublishedDateYear[close parentheses][comma]Page numbers (from Physical Description field)
    E.g.: Vol. 25, no. 5 (May 15, 1996), p. 99-120
  • Subfield w: (OCoLC)OCLC number
  • Subfield x: ISSN
  • Subfield z: ISBN
  • EXAMPLE:
    773 0 # $t National geographic $g Vol. 1, no. 1 (Dec. 1959), p. 35-37 $w (OCoLC)6451257 $x 0027-9358

780 - Use for Preceding Entry

  • Indicator 1: 0
  • Indicator 2: 0
  • Subfield t: Preceding entry title
  • Subfield w: Record control number
    Use NTL control number identifier and Record ID
  • EXAMPLE:
    780 0 0 $t National survey of drinking and driving attitudes and behavior : 1999

785 - Use for Succeeding Title

  • Indicator 1: 0
  • Indicator 2: 0
  • Subfield t: Succeeding entry title
  • Subfield w: Record control number
    Use NTL control number identifier and Record ID
  • EXAMPLE:
    780 0 0 $t National survey of drinking and driving attitudes and behavior : 2001

787 - Use for Is Format Of, Requires, and References

  • Indicator 1: 0
  • Indicator 2: #
  • Subfield t: title
  • Subfield g: field name
  • Subfield w: Record control number
    Use NTL control number identifier and Record ID
  • EXAMPLE:
    787 0 # $t National geographic $g References

856 - Use for Primary URL, Alternate URLs, and Digital Object Identifier

NOTE: Each URL should be assigned a separate 856 field

  • Indicator 1: 4
  • Indicator 2:
       0 - use for the Primary URL field
       1 - use for any URLs in the Alternate URL(s) field or any URLs in the Digital Object Identifier field
  • Subfield u: URL
  • Subfield q: Information pulled from the Format field
    Use the following codes for each format:
    • DOC: application/msword
    • HTML: text/html
    • PDF: application/pdf
    • XLS: application/vnd.ms-excel
  • EXAMPLE:
    856 4 0 $u http://ntl.bts.gov/lib/26000/26700/26710/1437-NHTSAs_Pedestrian_Safety_Program-09-04.pdf $q application/pdf