DCMI Kernel Metadata Task Group J. Kunze
  A. Turner
  California Digital Library
  September 2007 DRAFT

Mapping and Crosswalk: Kernel Metadata to Dublin Core, MARC21, MODS, and VRA Core

Each Kernel element label has a coded synonym (the SYN column below) that consists of the letter 'h' followed by a number, such as h1, h2, h3, etc. The following table, organized by "story", summarizes the rough correspondence between Kernel elements to Dublin Core elements, and approximate crosswalks to Machine-Readable Cataloging (MARC21), Metadata Object Description Schema (MODS), and Visual Resources Association (VRA) Core encoding schemes. For more information, see the Kernel Metadata and Electronic Resource Citations (ERCs) specification.

 

STORY KERNEL LABEL  SYN DUBLIN CORE Mapping DUBLIN CORE RDF/XML Crosswalk MARC21 Crosswalk MODS Crosswalk VRA CORE Crosswalk
erc: * who h1 Creator/Contributor/Publisher <creator>
<contributor>
<publisher>		 1XX
7XX
260		 <name>

<originInfo>
     <publisher>		 <agent>
* what h2 Title <title>
<alternative>
 210
24X		 <titleInfo>
     <title>
          <subtitle>		 <title>
* when h3 Date <date>
<created>
<valid>
<available>
<issued>
<modified>
<dateAccepted>
<dateSubmitted>
 008/07-14
26X subfield $c
245 subfield $f		 <originInfo>
     <dateCreated>

<originInfo>
     <dateOther>

<publicationInfo>
      <dateIssued>		 <date>
* where h4 Identifier (permanent) <identifier> 856
01X
02X		 <location>
     <url>

<identifier>		 <textref>
how h5 (reserved Type restriction) <type> <typeOfResource> <work>
<collection>
<image>
<workType>
about-erc: about-who h11 Subject (personage) <subject> 600
61X		 <subject>
     <name>		 <subject>
about-what h12 Subject    <subject> 650 <subject>
      <topic>		 <subject>
about-when h13 Coverage (temporal) <temporal> 045
650		 <subject>
     <topic>		 <culturalContext>
<date>
<stylePeriod>
about-where h14 Coverage (spatial) <spatial> 651 <temporal> <location>
about-how h15 Description <description>
<tableOfContents>
<abstract>		 520 <abstract>

<tableOfContents>

<note>		 <description>
support-erc support-who h21 (no equivalent) (no equivalent) 852 subfields $a, $b <physicalLocation> <location>
support-what h22 (no equivalent) (no equivalent) (no equivalent) (no equivalent) (no equivalent)
support-when h23 (no equivalent) (no equivalent) (no equivalent) (no equivalent) (no equivalent)
support-where h24 (no equivalent) (no equivalent) (no equivalent) (no equivalent) (no equivalent)
meta-erc meta-who h31 (no equivalent) (no equivalent) 008/39
040		 <recordContentSource> (no equivalent)
meta-what h32 (no equivalent) (no equivalent) 001 <recordIdentifier> (no equivalent)
meta-when h33 (no equivalent) (no equivalent) 008/00-05 <recordCreationDate>

<recordChangeDate>		 (no equivalent)
meta-where h34 (no equivalent) (no equivalent) (no equivalent) (no equivalent) (no equivalent)

 

Where Kernel elements map to Dublin Core (DC) elements, the map is roughly one-to-one, but with a few notable exceptions.

  1. "who" maps to DC Creator, but if no Creator use Publisher, and if no Publisher, use Contributor; "who" resembles what was once considered in DCMI to be an "agent" element
  2. "about-when" maps to the temporal aspect of DC Coverage and "about-where" maps to the spatial aspect of DC Coverage.
  3. The Kernel assumes that most values, especially personal names given in "who", will be given in "sort-friendly" manner, for example, "lastname, firstname" for western names and natural word order for Chinese names.
  4. The Kernel assumes [TEMPER] (Blair, C. and J. Kunze, “Temporal Enumerated Ranges,” August 2007.) format for dates in order to express date ranges, lists, approximate dates, and BC dates (not possible, for example, with [W3CDTF] (, “Date and Time Formats (W3C profile of ISO8601),” .)).