Cornell University Library
MARC to Dublin Core Crosswalk
April 10, 2002
Last updated: September 19, 2002
Dublin Core Mapping Group
Cornell University Library
Table of Contents
I. General Notes on Dublin Core
II. MARC to Dublin Core Crosswalk
III. Notes on Initial Articles
|
DC Element |
Recommendation, notes |
|
Title |
Qualified Title: Qualified titles are mandatory and NOT repeatable. Explanation: a. If a title is not present, use the filename for the title b. Alternative is an acceptable qualifier, however, translated and uniform are not necessary b. The recommendation to not allow titles to repeat is based on how we perceive qualified titles to be used in local systems. For example, with Canadian governmental titles in English and French, it is expected that the CUL would retain one title, English. Unqualified Title: Unqualified titles are mandatory and repeatable |
|
Creator |
Treat these separately (Creator, Contributor, Publisher rather than just Contributor) but index them together. |
|
Subject |
Interpret more broadly; i.e., include MARC tags 651, 650 $z, 650 $y. |
|
Description |
Potentially useful qualifiers include ToC, abstract, and version, if incoming data allows making these decisions. |
|
Contributor |
See Creator. |
|
Publisher |
See Creator. |
|
Date |
Use ISO 8601 |
|
Type |
Qualify, picking from "List of MARC Sources". Example in XML: <type type="gsafd">value</type> |
|
Format |
1. Use qualifiers if applicable to resource 2. Extent, in particular, should be recorded using the “extent” qualifier 3. If value not on list of formats in approved lists, make element unqualified -- this would likely be a file format name that is not on the IMT or other list. |
|
Identifier |
1. Mandatory 2. Prefer unique string, i.e., string that establishes a 1 to 1 relationship between the record and the resource. (See also: “holdings” proposal.) |
|
Source |
1. Do not use. 2. For digitized versions of analog, use relation.isFormatOf. 3. Evaluate incoming DC data to make mapping decisions. 4. If present in data, index with relation. |
|
Language |
Qualify, per DC-Lib recommendations. Prefer ISO 639-2. If possible, convert incoming data. |
|
Relation |
1. Use qualifiers if possible. 2. For both qualified and unqualified relation, do not index with title. 3. For digitized versions of analog, use relation.isFormatOf. |
|
Coverage |
Interpret more narrowly; i.e., include 034 using controlled data values; preserve its usefulness by limiting its possible contents. |
|
Rights |
1. Use for rights information about the resource described, not the metadata record. 2. Use a URI if available, pointing to external rights document (?). |
II. MARC to Dublin Core Crosswalk
|
DC Element |
MARC Fields |
Implementation notes |
|
Title |
245 130, 210, 240, 242, 246, 730, 740 |
|
|
Creator |
100, 110, 111 |
|
|
Subject |
050 080 082 090 600, 610, 611, 630, 650, 651, 653, 690 |
|
|
Description |
255 500-599, EXCEPT 506, 510, 530, 540 |
i.e., include 522, 546, 538 |
|
Contributor |
700, 710, 711, 720 |
|
|
Publisher |
260$b |
Exclude 260$a |
|
Date |
008/07-10 008/11-14 260$c 260$g 533$d |
|
|
Type |
Leader06, Leader07 |
We need a crosswalk to map Leader 06/07 to natural language terms. |
|
655 |
i.e., all occurrences of 655, not just those w/subfield $2=dct |
|
|
Format |
856$q 300$a 533$e 340$a |
Decided against 776$h |
|
Identifier |
856$u |
|
|
Source |
|
CUL deprecates source. |
|
Language |
008/35-37 |
|
|
041, except $h |
Multiple codes need to be parsed by threes. |
|
|
Relation |
440, 490 510 530 760 773$n$o$t 774$n$o$t 775 776$n$o$t 780$n$o$t 785$n$o$t 786$n$o$t 800,810,811,830, 899 |
|
|
Coverage |
034$d-g 043$a$c |
Analyze incoming 043 data for other subfields. |
|
Rights |
506, 540 |
|
Recommendation: Decide on a project-by-project basis based on the particular needs of the project.
Explanation:
Retain initial article when...
a. The formal title is necessary or essential
b. The initial article is a distinguishing feature
c. The initial article has significant values- as with a particular language
Do not retain initial article when...
a. The purpose is resource discovery
b. The sorting order will be adversely affected
c. The display list will be adversely affected
d. A more complete record is readily attainable elsewhere
