Crosswalk Generator

Dublin Core to MODS

Dublin Core element

MODS element

Notes
Title <titleInfo><title>  
Creator <name><namePart><role><roleTerm type=text">
creator

 

 1. MODS puts all names in a repeated<name> with type of contribution included in <role>. If desired to retain creator or contributor distinction, use <name><namePart><role>creator
2. MODS assumes structured form of name
3. MODS allows distinguishing name as personal, corporate, conference in type attribute. DC does not, so this information is lost.
4. MODS allows <name> subelements to be parsed: <namePart>, <displayForm>, <affiliation>, <role>, <description>. Default DC value to <namePart>.
Subject

<subject><topic>
<classification>

 ††


 

 Data in MODS may be included in a more specific subelement: <topic>, <geographic>, <temporal>, <name>, <titleInfo>, <hierarchicalGeographic>, <coordinates>. DC also uses classification schemes in Subject. These distinctions will be lost when converting from DC to MODS. Default DC value to <topic>.
Description <abstract>
<note>
<tableOfContents>		 Multiple elements in MODS. These distinctions will be lost when converting from DC to MODS. Default DC value to <note>.
Publisher <originInfo><publisher> DC value may include place of publication/issuance. This distinction will be lost when converting from DC to MODS and place may be in MODS publisher.
Contributor <name><namePart> See notes under Creator
Date <originInfo><dateIssued> Multiple elements in MODS. These distinctions will be lost when converting from DC to MODS> Default DC value to <dateOther>.
<originInfo><dateCreated>
<originInfo><dateCaptured>
<originInfo><dateOther>
Type <typeOfResource>
<genre>		 MODS uses high level types in <typeOf Resource> (controlled list); more specific genre terms in <genre> (may or may not be from a controlled list). If DC value is from dc:type list, use <genre> with authority="dct" and supply a MODS enumerated typeOfResource value when possible (see mapping below). If not from dc:type list, default to <genre>.
Format <physicalDescription><internetMediaType> Multiple elements in MODS. Default DC value to <physicalDescription><form>
<physicalDescription><extent>
<physicalDescription><form>
Identifier <identifier>
<location><url>		 MODS makes a distinction between a persistent identifier and a location. A type attribute specifies the identifier type, e.g. <identifier type="uri">; http: URIs also go in <location><url>. Default DC value to <location><url> if it begins "http://"
Source <relatedItem type="original"> + <titleInfo><title> or <location><url> See notes under Relation
Language

<language><languageTerm type="text">
<language><languageTerm type="code">

If DC language data is textual, use type="text". If DC language data is coded, use type="code"

Relation <relatedItem> + <titleInfo><title> or <location><url>
 Data in mods:relatedItem is parsed into subelements (any MODS element may be used). Default DC value to <titleInfo><title> unless it begins "http://", in which case to <location><url>.
Coverage

<subject><temporal>

 Multiple elements in MODS. May result in incorrect mapping, since there is not a way to tell if the coverage is spatial or temporal. Default coverage to <subject><geographic> (although this may result in some errors)

<subject><geographic>

<subject><hierarchicalGeographic>

<subject><cartographics><coordinates>
Rights <accessCondition>  

Conversion of DC Resource Type vocabulary to MODS typeOfResource values

 

DC Type value MODS typeOfResource
Collection (use in addition to specific value below) typeOfResource collection="yes"
Dataset software, multimedia and mods:genre="database"
Image default to still image
InteractiveResource software, multimedia
MovingImage moving image
PhysicalObject three dimensional object
Service software and mods:genre="online system or service"
Sound
 sound recording
StillImage still image
Software software, multimedia
Text text