Dublin Core/MARC/GILS Crosswalk

November, 1999

Network Development and MARC Standards Office
Library of Congress


I. Introduction.


The following is a crosswalk between the fifteen elements in the Dublin Core Element Set and MARC 21 bibliographic data elements. In addition, it includes a crosswalk from Dublin Core to GILS attributes. The crosswalk may be used in conversion of metadata from another syntax into MARC. For conversion of MARC 21 into Dublin Core, many fields may be mapped into a single Dublin Core element. Such a document will be forthcoming.

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 current thinking of Dublin Core working groups as of this writing. In addition, some qualifiers used in the CORC project are indicated. No identifier (namespace) is given as the initial portion of the element with its qualifier until a set is agreed upon (e.g. Creator.Personal is used in this crosswalk instead of DC.Creator.Personal). As core qualifiers are further standardized within the Dublin Core Metadata Initiative, 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 previous version of this document(April 1997).

Definitions are taken from Dublin Core Metadata Element Set Reference Description, Version 1.1. 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:

Qualified: GILS:

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

MARC 21:

Unqualified:

Qualified:
GILS:

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

MARC 21:

Unqualified:


Qualified: GILS:

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

MARC 21:

Unqualified:

Qualified: Note: Use of some of these qualifiers are dependent upon decisions made by the Dublin Core Metadata Initiative on core qualifiers.

GILS

Description
An account of the content of the resource.

MARC 21:

Unqualified:

Qualified: GILS:

Format
The physical or digital manifestion of the resource.

MARC 21:

Unqualified:

Qualified:

GILS:

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

MARC 21:

Unqualified:

Qualified: GILS:

Language
A language of the intellectual content of the resource.

MARC 21:

Unqualified:

Qualified: GILS:

Publisher
An entity responsible for making the resource available.

MARC 21:

Unqualified:

Qualified: Note: It may be desirable to repeat a qualified publisher in 260$b

GILS:

Relation
A reference to a related resource.

MARC 21:

Unqualified:

Qualified:
Note: Use of some of these qualifiers are dependent upon decisions made by the Dublin Core Metadata Initiative on core qualifiers.

GILS:


Rights
Information about rights held in and over the resource.

MARC 21:

Unqualified:

Qualified: GILS:

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

MARC 21:

Unqualified:

Qualified: GILS:

Subject
The topic of the content of the resource.

MARC 21:

Unqualified:

Qualified: GILS:

Title
The name given to the resource.

MARC 21:

Unqualified:

Qualified: GILS:

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

MARC 21:

Unqualified:

Qualified: See Section III for use to determine Leader/06 (Type of Reecord) values.

GILS

III. Notes.


In addition to the variable length fields listed in the mapping, a MARC 21 record will also include a Leader and field 008 (Fixed-Length Data Elements). Certain character positions in each of these fixed length fields of a USMARC record will need to be coded, although most will generate default values.

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:

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:

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

IV. Changes from the previous version (7 April 1997):


V. Uses for mapping Dublin Core to MARC


A mapping between the elements in the Dublin Core and USMARC fields is necessary so that conversions between various syntaxes can occur accurately. Once Dublin Core style metadata is widely provided, it might interact with MARC records in various ways such as the following:

Enhancement of simple resource description record. A cataloging agency may wish to extract the metadata provided in Dublin Core style (presumably in HTML or SGML) 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. The Library of Congress has worked with a group of SGML experts to create a Document-Type Definition (DTD) for MARC, so that conversions can be made between SGML and MARC in a standardized way. 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 the MARC Home Page

Go to the Library of Congress Home Page


Library of Congress
Library of Congress Help Desk (11/19/99)