MARC to Dublin Core Crosswalk

Development and MARC Standards Office
Library of Congress

Date issued: 2008/04/24

Previous version: http://www.loc.gov/marc/marc2dc-2001.html

Table of Contents

• I. Introduction
• II. MARC to Dublin Core (Unqualified)
• III. MARC to Dublin Core (Qualified)
• IV. Appendix 1--Notes
• V. Appendix 2--Conversion rules for Leader/06 to dc:Type mapping

I. Introduction

The following is a crosswalk between core MARC 21 bibliographic data elements and elements in the Dublin Core Element Set. It may be used in conversion of metadata from MARC into Dublin Core. Since MARC is richer in data than Dublin Core, it differs from the Dublin Core to MARC Crosswalk in that multiple MARC fields are mapped to a Dublin Core element. The Dublin Core to MARC crosswalk maps a Dublin Core element to a single MARC field. In both crosswalks there are different mappings for Dublin Core simple or qualified. Not all possible MARC fields are included in this mapping, but only those considered useful for broad cross-domain resource discovery. Applications may wish to include other MARC elements that are prevalent in their data but are not listed here, or they may not include all that are listed.

MARC 21 fields are listed by field number with specific subfields if applicable. In many cases specific subfields are not provided, since applications may differ in subfields used. Applications may not need control subfields such as $2, $5. Notes concerning implementation are given. Further information about the mapping is given at the end of the document. Definitions of MARC elements may be found at the MARC Bibliographic format site and definitions of Dublin Core elements from the Dublin Core Metadata Element Set Reference Description, Version 1.1 and DCMI Metadata Terms.

Note that it is not expected that round-trip mapping is possible using this crosswalk. Once MARC data is converted to Dublin Core, not enough information is retained to allow for mapping back to MARC accurately. This is inevitable when mapping a complex set of data elements to a simpler set. Where a tag is used in mapping to more than one DC element, a decision may need to be made which Dublin Core element to map it to.

II. MARC to Dublin Core Crosswalk (Unqualified)

• Conventions:
  • 1."$" is used to specify the subfield used. If none is specified, use all subfields.
  • 2. DC element is repeated if multiple MARC fields are used.

III. MARC to Dublin Core Crosswalk (Qualified)

Appendix 1--Notes

DC Refinements and encoding schemes. Some DC refinements or encoding schemes have not been included because they are not generally found or can not be specifically identified in MARC data. Examples include DCMI Point, DCMI Box and Mediator.

Roles. Those roles in the MARC Relators list that indicate that they refine "Contributor" may be used in qualified DC. See: Relator Terms and Dublin Core Elements.

Appendix 2 - Conversion rules for Leader06 - dc:Type mapping

Multiple Type fields may be used; conversions below may result in 2 or 3 Type fields. There are several additional sources of type information in the MARC record; only coded values in Leader/06 and Leaader/07 are detailed in this chart. Field 655 may also be used for more specific type information.

Institutions may want to consider generating additional type values, such as "map" or "cartographic" for codes e or g; "musical notation" for codes c or d, etc.

Go to:

• Dublin Core to MARC Crosswalk
• MARC Home Page
• Library of Congress Home Page