MODS to Dublin Core Metadata Element Set Mapping Version 3
August 1, 2012
This mapping gives equivalencies between the elements in the Metadata Object Description Schema (MODS) and the Dublin Core Metadata Element Set, version 1.1 (unqualified Dublin Core) . Order of elements are according to the Dublin Core Metadata Element Set, version 1.1: Reference Description. The document may be used for converting a MODS record to Dublin Core. For instance, one application is to expose MODS records for OAI harvesting in Dublin Core syntax.
In some cases, multiple MODS elements are equivalent to one Dublin Core element, and all are listed. In these cases, some metadata is lost.
MODS elements are linked to top-level elements in the Outline of Elements and Attributes in MODS.
MODS element |
Dublin Core element |
Notes |
|
| <titleInfo><title> | Title | 1. For multiple MODS titles
use multiple instances of dc:title. 2. MODS allows <titleInfo> subelements to be parsed: <nonSort>, <title>, <subTitle>, <partNumber>, <partName> MODS subelements should be concatenated in Dublin Core, separated by a space or other form of punctuation. |
|
| <name><namePart> | Creator Contributor |
1. MODS puts all names in
a repeated<name> with type of contribution indicated in <role>. It does not make the explicit distinction between creator and contributor in
terms of primary vs. secondary roles. An application may wish to
designate use of Creator or Contributor for all MODS names or use
the role value to determine which DC element is used. 2. MODS allows <name> subelements to be parsed: <namePart>, <displayForm>, <affiliation>, <role>, <description> MODS subelements should be concatenated in Dublin Core, separated by a space or other form of punctuation. |
|
| <subject> |
Subject |
||
| <topic> | |||
| <name> | |||
| <occupation> | |||
| <classification> | |||
| <abstract> | Description | ||
| <note> | |||
| <tableOfContents> | |||
| <originInfo><publisher> | Publisher | ||
| <originInfo><dateIssued> | Date | ||
| <originInfo><dateCreated> | |||
| <originInfo><dateCaptured> | |||
| <originInfo><dateOther> | |||
| <typeOfResource> | Type | 1. Use separate instances of Type for each MODS element value. 2. If converting MODS typeOfResource values to Dublin Core Resource Type values, see conversion details below. If MODS <genre> contains authority="dct", that may be used in dc:type and typeOfResource dropped. |
|
| <genre> | |||
| <physicalDescription> | Format | Use separate instances of Format for each MODS element value. | |
| <internetMediaType> | |||
| <extent> | |||
| <form> | |||
| <identifier> | Identifier | It is suggested that the identifier type be retained and associated with the identifier value. | |
| <location> <url> | |||
| <language><languageTerm> | Language | ||
| <relatedItem> | Relation |
<relatedItem> data
is parsed into subelements in MODS (any MODS element may be used). For example, if giving a reference to a resource
fully described in MODS relatedItem, one could use: <relatedItem><identifier> |
|
| Coverage | |||
| <geographic> | |||
|
|
<temporal> | ||
| <hierarchicalGeographic> | |||
|
|
<cartographics> | ||
| <accessCondition> | Rights | ||
| <recordInfo> | |||
Conversion of MODS typeOfResource values to DC Resource Type vocabulary.
| MODS typeOfResource | DC Type value |
|---|---|
| typeOfResource collection="yes" | Collection (use in addition to specific value below) |
| software and mods:genre="database" | Dataset |
| cartographic material | Image |
| multimedia | InteractiveResource |
| moving image | MovingImage |
| three dimensional object | PhysicalObject |
| software and mods:genre="online system or service" | Service |
| sound recording, sound recording-musical, sound recording-nonmusical |
Sound |
| still image | StillImage |
| software | Software |
| text, notated music | Text |
Questions and comments:
Contact Us (
November 19, 2014
)
Legal | External Link Disclaimer