Dublin Core/MARC/GILS Crosswalk

Network Development and MARC Standards Office
Library of Congress

I. Introduction.

In the Dublin Core to MARC mapping, two mappings are provided, one for unqualified Dublin Core elements and the other for qualified. Qualifiers used are generally based on the qualifiers approved by the Dublin Core Metadata Initiative and documented in Dublin Core Qualifiers There are some qualifiers given (for Contributor, Creator, and Publisher) that have not been approved by the Dublin Core Metadata Initiative; as these are further standardized, this crosswalk will be adjusted.

MARC 21 fields are listed with field number, then two indicator values with field name/subfield name in parentheses. If both the field and subfield have the same name, the subfield name is not included. A blank (H'20') is indicated in this document by "#". The label is a shortened form of the element name. GILS attribute names for each Dublin Core element are also given. Note that the GILS mapping has not been revised since the April 1997 version of this document.

Definitions are taken from Dublin Core Metadata Element Set, Version 1.1: Reference Description. For further information about Dublin Core elements, including application notes (given in Comment), refer to that document. All Dublin Core elements are optional and repeatable. In this document elements are listed in alphabetical order by Dublin Core identifier (i.e. label).

II. Dublin Core to MARC and GILS Crosswalk.

Contributor
An entity responsible for making contributions to the content of the resource.

MARC 21:

Unqualified:

• 720 ##$a (Added Entry--Uncontrolled Name/Name) with $e=collaborator (or other term used as value of role qualifier)
  

• Personal: 700 1#$a (Added Entry--Personal Name) with $e=collaborator
  
• Corporate: 710 2#$a (Added Entry--Corporate Name) with $e=collaborator
  
• Conference: 711 2#$a (Added Entry--Conference Name) with $e=collaborator
  
• Role: 720 ##$e (Added Entry--Uncontrolled Name/Relator term
• Role (Personal): 700 1#$e (Added Entry--Personal Name/Relator term)
• Role (Corporate):
710 2$e (Added Entry--Corporate Name/Relator term)

• Contributor

Coverage
The extent or scope of the content of the resource.

MARC 21:

Unqualified:

• 500$a (General note)
  

• Spatial: 522 ##$a (Geographic Coverage Note)
  
• Temporal: 513 ##$b (Type of Report and Period Covered Note/Period covered)

• Supplemental Information
  
• Spatial: Bounding Coordinates
  
• Temporal: Time Period Textual

Creator
An entity primarily responsible for making the content of the resource.

MARC 21:

Unqualified:

• 720 ##$a (Added Entry--Uncontrolled Name/Name) with $e=author

• Personal: 700 1#$a (Added Entry--Personal Name) with $e=author
  
• Corporate: 710 2#$a (Added Entry--Corporate Name) with $e=author
  
• Conference: 711 2#$a (Added Entry--Conference Name) with $e=author
  
• Role: 720 ##$e (Added Entry--Uncontrolled Name/Relator term
• Role (Personal): 700 1#$e (Added Entry--Personal Name/Relator term)
• Role (Corporate):
710 2$e (Added Entry--Corporate Name/Relator term)

• Originator

Date
A date associated with an event in the life cycle of the resource.

MARC 21:

Unqualified:

• 260 ##$c (Date of publication, distribution, etc.)
  

• Available: 307 ##$a (Hours, Etc.)
• Created: 260 ##$g (Date of manufacture)
• Issued: 260 ##$c (Date of publication, distribution, etc.)
• Modified: 583 ##$d with $a=modified
• Valid: 518 ##$a (Date/Time and Place of an Event Note). Text may be generated in $3 to include qualifier name.
• Scheme=ISO 8601: date may also be generated in 008/07-10; see below under Notes. If ISO 8601, use basic form that does not include hyphens in 008.

GILS:

• Date of Publication

Description
An account of the content of the resource.

MARC 21:

Unqualified:

• 520 ##$a (Summary, etc. note)

• Description.Abstract: 520 ##$a (Summary, etc. note)
• Description.TableofContents: 505 0#$a (Formatted Contents Note)

• Abstract

Format
The physical or digital manifestion of the resource.

MARC 21:

Unqualified:

• 856 ##$q (Electronic Location and Access/Electronic format type)
  

• Extent: 300 ##$a (Physical Description)
  Note that "Extent" has been defined by the Format WG as "the size or duration of a resource"
• Medium: 340 ##$a (Physical Medium)
• Medium (Scheme=IMT): 856 ##$q (Electronic Location and Access/Electronic Format Type)

GILS:

• Available Linkage Type

Identifier
An unambiguous reference to the resource within a given context.

MARC 21:

Unqualified:

• 024 8#$a (Other Standard Identifier/Standard number or code)
  

• Scheme=URI: 856 40$u (Electronic Location and Access/Uniform Resource Locator)
• Scheme=ISBN: 020 ##$a (International Standard Book Number)
  
• Scheme=ISSN: 022 ##$a (International Standard Serial Number)
  
• Scheme=(other): 024 8#$a (Other Standard Identifier/Standard number or code) with $2=scheme value
  

• Available Linkage

Language
A language of the intellectual content of the resource.

MARC 21:

Unqualified:

• 546 ##$a (Language note)
  

• Scheme=ISO 639-2: 041$a (Language code)
• Scheme=RFC 1766: 546 ##$a (Language note) with $b=RFC 1766

• Language of Resource (note that GILS assumes use of Z39.53)

Publisher
An entity responsible for making the resource available.

MARC 21:

Unqualified:

• 260 ##$b (Publication, Distribution, etc. (Imprint)/Name of publisher, distributor, etc.)

• Personal: 700 1#$a (Added Entry--Personal Name) with $e=publisher
  
• Corporate: 710 2#$a (Added Entry--Corporate Name) with $e=publisher
  
• Conference: 711 2#$a (Added Entry--Conference Name) with $e=publisher
  

GILS:

• Distributor

Relation
A reference to a related resource.

MARC 21:

Unqualified:

• 787 0#$n (Nonspecific Relationship Entry/Note)
  

• Scheme=URI: 787 0#$o (Nonspecific Relationship Entry/Other identifier)
• HasFormat: 776 0#$n (Additional Physical Form Entry/Note)
• HasFormat: (Scheme=URI): 776 0#$o (Additional Physical Form Entry/Other identifier)
• IsFormatOf: 776 0#$n (Additional Physical Form Entry/Note)
• IsFormatOf: (Scheme=URI): 776 0#$o (Additional Physical Form Entry/Other identifier)
• IsPartOf: 773 0#$n (Host Item Entry/Note)
• IsPartOf (Scheme=URI): 773 0#$o (Host Item Entry/Other identifier)
• HasPart: 774 0#$n (Constituent Unit Entry/Note)
• HasPart (Scheme=URI): 774 0#$o (Constituent Unit Entry/Other identifier)
• IsVersionOf: 775 0#$n (Other Edition Entry/Note)
• IsVersionOf (Scheme=URI): 775 0#$o (Other Edition Entry/Other identifier)
• HasVersion: 775 0#$n (Other Edition Entry/Note)
• HasVersion (Scheme=URI): 775 0#$o (Other Edition Entry/Other identifier)
• IsBasedOn: 786 0#$n (Data Source Entry/Note)
• IsBasedOn (Scheme=URI): 786 0#$o (Data Source Entry/Other identifier)
• IsReferencedBy: 510 0#$a (Citation/References Note/Name of source)
• Requires: 538 ##$a (System Details Note)
• Replaces: 780 00$t (Preceding entry)
• IsReplacedBy: 785 00$t (Succeeding entry)

GILS:

• Cross Reference Relationship
  
• If scheme=URL: Cross Reference Linkage

Rights
Information about rights held in and over the resource.

MARC 21:

Unqualified:

• 540 ##$a (Terms Governing Use and Reproduction Note)
  

• Scheme=URL: 856 42$u (Electronic Location and Access/Uniform Resource Locator) with $3=Rights

• Use Constraints

Source
A reference to a resource from which the present resource is derived.

MARC 21:

Unqualified:

• 786 0#$n (Data Source Entry/Note)
  

• Scheme=URI: 786 0#$o (Data Source Entry/Other identifier)

• Sources of Data

Subject
The topic of the content of the resource.

MARC 21:

Unqualified:

• 653 ##$a (Index Term--Uncontrolled)

• Scheme=LCSH: 650 #0$a (Subject added entry--Topical term)
  
• Scheme=MeSH: 650 #2$a (Subject added entry--Topical term)
  
• Scheme=LCC: 050 ##$a (Library of Congress Call Number/Classification number)
  
• Scheme=DDC: 082 ##$a (Dewey Decimal Call Number/Classification number)
  
• Scheme=UDC: 080 ##$a (Universal Decimal Classification Number)
  
• Scheme=(other): 650 #7$a with $2=code from MARC Code List for Relators, Sources, Description Conventions
  

• Uncontrolled Term

Title
The name given to the resource.

MARC 21:

Unqualified:

• 245 00$a (Title Statement/Title proper)
• If repeated, all titles after the first: 246 33$a (Varying Form of Title/Title proper)
  

• Alternative: 246 33$a (Varying Form of Title/Title proper)

• Title

Type
The nature or genre of the content of the resource.

MARC 21:

Unqualified:

• 655 #7$a (Index Term--Genre/Form) with $2=local
  

• Scheme=DCMI Type: 655 #7$a (Index Term--Genre/Form) with $2=dct
• Scheme=(other): 655 #7$a (Index Term--Genre/Form) with $2=code from MARC Code List for Relators, Sources, Description Conventions

GILS

• Medium

III. Notes.

Leader: a fixed field comprising the first 24 character positions (00-23) of each record that provides information for the processing of the record. The following positions should be generated:

• Character Position 06: Type of record
  Leader/06 value should be set according to value in Type as follows (these values are from Dublin Core List of Resource Types (DC Type Vocabulary):

  Type value	Leader/06 value
  collection	p
  dataset	m
  event	r
  image	k
  interactive resource	m
  service	m
  software	m
  sound	i
  text	a

  If no type is indicated, use value "a". If two type values are indicated, and one of these is "collection" use the other value for setting Leader/06. If more than two, use "m".

• Character Position 07: Bibliographic level
  • If Type value is collection, use value "c" (Collection)
  • All others, use value "m" (Monograph).
• Character Position 08: Type of control
  • Use value "#" (blank: no specific type of control).
• Character Position 09: Character coding scheme
  • Use value "#" (blank: MARC-8).
• Character Position 17: Encoding level
  • Use value "3" (Abbreviated level) or other value as appropriate to application
• Character Position 18: Descriptive cataloging form
  • Use value "u" (Unknown) to indicate that the descriptive cataloging form is unknown.

008 Fixed Length Data Elements: Forty character positions (00-39) containing positionally-defined data elements that provide coded information about the record as a whole or about special bibliographic aspects of the item being cataloged. For records originating as Dublin Core, the following character positions are used:

• Character positions 00-05: Date the MARC 21 record was created or converted (generate by date record entered system; formatted as YYMMDD)
• Character positions 07-10: Date of Publication (YYYY portion from Date if present). Qualified DC: Date.Issued in ISO 8601 (only YYYY portion).
• Character positions 35-37: Language. May be generated from data in Language if scheme=ISO 639-2.
• Other character positions can default to fill characters (ASCII 7C)

042$a Authentication Code: Use "dc" (identifies that MARC 21 record is derived from Dublin Core style record).

IV. Uses for mapping Dublin Core to MARC

Enhancement of simple resource description record. A cataloging agency may wish to extract the metadata provided in Dublin Core style (presumably in HTML or XML) and convert the data elements to MARC fields, resulting in a skeletal record. That record might then be enhanced as needed to add additional information generally provided in the particular catalog. Some projects convert data and use as basic record for reporting to national bibliography.

Searching across syntaxes and databases. Libraries have large systems with valuable information in metadata records in MARC format. Over the past few years with the expansion of electronic resource over the Internet, other syntaxes have also been considered for providing metadata. It will be important for systems to be able to search metadata in different syntaxes and databases and have commonality in the definition and use of elements.

Go to:

• MARC Home Page
• Library of Congress Home Page