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:
- 720 ##$a (Added Entry--Uncontrolled Name/Name) with $e=collaborator (or other term
used as value of role qualifier)
Qualified:
- Contributor.Personal: 700 1#$a (Added Entry--Personal Name) with $e=collaborator
- Contributor.Corporate: 710 2#$a (Added Entry--Corporate Name) with $e=collaborator
- Contributor.Conference: 711 2#$a (Added Entry--Conference Name) with
$e=collaborator
- Contributor.Role: 720 ##$e (Added Entry--Uncontrolled Name/Relator term)
GILS:
Coverage
The extent or scope of the content of the resource.
MARC 21:
Unqualified:
Qualified:
- Coverage.Spatial: 522 ##$a (Geographic Coverage Note)
- Coverage.Temporal: 513 ##$b (Type of Report and Period Covered Note/Period
covered)
GILS:
- Supplemental Information
- Coverage.Spatial: Bounding Coordinates
- Coverage.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
Qualified:- Creator.Personal: 700 1#$a (Added Entry--Personal Name) with
$e=author
- Creator.Corporate: 710 2#$a (Added Entry--Corporate Name) with $e=author
- Creator.Conference: 711 2#$a (Added Entry--Conference Name) with $e=author
- Creator.Role: 720 ##$e (Added Entry--Uncontrolled Name/Relator term)
GILS:
Date
A date associated with an event in the life cycle of the resource.
MARC 21:
Unqualified:
- 260 ##$c (Date of publication, distribution, etc.)
Qualified:
- Date.Accepted: 518 ##$a (Date/Time and Place of an Event Note).
Text may be generated in $3 to include qualifier name (e.g. 518 ##$a Date.Accepted: 19 April
1999)
- Date.Acquired: 541 ##$d (Immediate Source of Acquisition Note/Date of acquisition)
- Date.Available: 307 ##$a (Hours, Etc.)
- Date.Created: 260 ##$g (Date of manufacture)
- Date.DataGathered: 567 ##$a (Methodology note)
- Date.Issued: 260 ##$c (Date of publication, distribution, etc.)
- Date.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.
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:
- 520 ##$a (Summary, etc. note)
Qualified:
- Description.Abstract: 520 ##$a (Summary, etc. note)
- Description.Audience: 521 ##$a (Target Audience)
- Description.Award: 586 ##$a (Awards Note)
- Description.Contents: 505 0#$a (Formatted Contents Note)
- Description.Notes: 500 ##$a (General note)
GILS:
Format
The physical or digital manifestion of the resource.
MARC 21:
Unqualified:
- 856 ##$q (Electronic Location and Access/Electronic format type)
Qualified:
- Format.Extent: 300 ##$a (Physical Description)
Note that "Extent" has been defined by the Format WG as "the size or duration of a
resource"
- Format.Media: 340 ##$a (Physical Medium)
- Format.Media (Scheme=DCF1): 340 ##$a (Physical Medium)
- Format.Media (Scheme=IMT): 856 ##$q (Electronic Location and Access/Electronic Format
Type)
GILS:
Identifier
An unambiguous reference to the resource within a given context.
MARC 21:
Unqualified:
- 024 8#$a (Other Standard Identifier/Standard number or code)
Qualified:
- Scheme=ISBN: 020 ##$a (International Standard Book Number)
- Scheme=ISSN: 022 ##$a (International Standard Serial Number)
- Scheme=URL: 856 40$u (Electronic Location and Access/Uniform Resource Locator)
- Scheme=URN: 856 #0$g (Electronic Location and Access/Uniform Resource Name)
- Scheme=(other): 024 8#$a (Other Standard Identifier/Standard number or code) with
$2=scheme value
GILS:
Language
A language of the intellectual content of the resource.
MARC 21:
Unqualified:
Qualified:
- Scheme=ISO 639-2/B: 041$a (Language code)
- Scheme=RFC 1766: 546 ##$a (Language note) with $b=RFC 1766
- Scheme=MARC21-lang: 041$a (Language code).
Language may also be generated in 008/35-37; see below under Notes.
GILS:
- 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.) with
$e=publisher
Qualified:
- Publisher.Personal: 700 1#$a (Added Entry--Personal Name) with $e=publisher
- Publisher.Corporate: 710 2#$a (Added Entry--Corporate Name) with $e=publisher
- Publisher.Conference: 711 2#$a (Added Entry--Conference Name) with $e=publisher
- Publisher.Role: 720 ##$e (Added Entry--Uncontrolled Name/Relator term) with
$e=publisher
- Publisher.Place: 260 ##$a (Publication, Distribution, Etc./Place of publication, distribution,
etc.)
Note: It may be desirable to repeat a qualified publisher in 260$b
GILS:
Relation
A reference to a related resource.
MARC 21:
Unqualified:
- 787 0#$n (Nonspecific Relationship Entry/Note)
Qualified:
- Scheme=URI: 787 0#$o (Nonspecific Relationship Entry/Other identifier)
- Relation.OtherFormat: 776 0#$n (Additional Physical Form Entry/Note)
- Relation.OtherFormat: (Scheme=URI): 776 0#$o (Additional Physical Form Entry/Other
identifier)
- Relation.IsPartOf: 773 0#$n (Host Item Entry/Note)
- Relation.IsPartOf (Scheme=URI): 773 0#$o (Host Item Entry/Other identifier)
- Relation.HasPart: 774 0#$n (Constituent Unit Entry/Note)
- Relation.HasPart (Scheme=URI): 774 0#$o (Constituent Unit Entry/Other identifier)
- Relation.OtherVersion: 775 0#$n (Other Edition Entry/Note)
- Relation.OtherVersion (Scheme=URI): 775 0#$o (Other Edition Entry/Other identifier)
- Relation.IsBasedOn: 786 0#$n (Data Source Entry/Note)
- Relation.IsBasedOn (Scheme=URI): 786 0#$o (Data Source Entry/Other identifier)
- Relation.IsReferencedBy: 510 0#$a (Citation/References Note/Name of source)
- Relation.Requires: 538 ##$a (System Details Note)
- Relation.IsPartofSeries: 490 1#$a (Series statement)
- Relation.IsPartofSeries (Scheme=ISSN): 490 1#$x (Series statement/International Standard
Serial Number)
- Relation.PrecedingVersion: 780 00$t (Preceding entry)
- Relation.SucceedingVersion: 785 00$t (Succeeding entry)
Note: Use of some of these qualifiers are dependent upon decisions made by the Dublin Core
Metadata Initiative on core qualifiers.
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)
Qualified:
- Scheme=URL: 856 42$u (Electronic Location and Access/Uniform Resource Locator)
with $3=Rights
GILS:
Source
A reference to a resource from which the present resource is derived.
MARC 21:
Unqualified:
- 786 0#$n (Data Source Entry/Note)
Qualified:
- Scheme=URL: 786 0#$o (Data Source Entry/Other identifier)
GILS:
Subject
The topic of the content of the resource.
MARC 21:
Unqualified:
- 653 ##$a (Index Term--Uncontrolled)
Qualified:
- Subject.Geographic: 651 #7$a (Subject Added Entry--Geographic Name) with $2=local
(or other scheme as specified)
- Subject.PersonalName: 600 17$a (Subject Added Entry--Personal Name) with $2=local (or
other scheme as specified)
- Subject.CorporateName: 610 27$a (Subject Added Entry--Corporate Name) with $2=local
(or other scheme as specified)
- Subject.ConferenceName: 611 27 (Subject Added Entry--Conference Name) with $2=local
(or other scheme as specified)
- Scheme=LCSH: 650 #0$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=(other): 650 #7$a with $2=code from MARC Code List for Relators, Sources,
Description Conventions
GILS:
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)
Qualified:- Title.Alternative: 246 33$a (Varying Form of Title/Title proper)
- Title.Release: 250 ##$a (Edition Statement)
Note: Use of this qualifier is dependent upon decisions made by the Dublin Core Metadata
Initiative on core qualifiers.
- Title.Translated: 242 00$a (Translation of Title/Title)
- Title.Uniform: 130 0#$a (Main Entry--Uniform Title)
GILS:
Type
The nature or genre of the content of the resource.
MARC 21:
Unqualified:
- 655 #7$a (Index Term--Genre/Form) with $2=local
Qualified:
- Type.Note: 516 ##$a (Type of Computer File or Data Note)
- Scheme=DCT1: 655 #7$a (Index Term--Genre/Form) with $2=DCT1
- Scheme=(other): 655 #7$a (Index Term--Genre/Form) with $2=code from MARC Code List
for Relators, Sources, Description Conventions
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:
- 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=Z39.53, ISO 639-2/B or MARC21-lang.
- 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. Changes from the previous version (7 April 1997):
- Qualifiers:some recommended qualifiers from Dublin Core working
groups and some qualifiers from CORC project added and mapped to MARC.
- Elements reordered alphabetically.
- Introduction rewritten.
- Definitions changed according to DC 1.1. Comments not included.
- "USMARC" changed to "MARC 21".
- MARC 21 indicator values added.
- Identifier: Unqualified changed from 856$u to 024$a
- Coverage: Type=Spatial changed from 255$c to 522$a
- Table included in Notes to indicate setting of Leader/06 value.
- Additional character positions in Leader included.
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)