Difference between revisions of "Mapping MODS to OAI DC"

From MPDLMediaWiki
Jump to navigation Jump to search
m (added link)
(→‎Mapping: added notes)
Line 6: Line 6:
|- bgcolor="#ccccff"
|- bgcolor="#ccccff"
! width="200" |'''[http://www.loc.gov/standards/mods/ MODS] Element'''  
! width="200" |'''[http://www.loc.gov/standards/mods/ MODS] Element'''  
! width="400" |'''[http://www.dublincore.org/documents/dces/ Qualified DC]'''  
! width="200" |'''[http://www.dublincore.org/documents/dces/ Qualified DC]'''  
!width="400"|'''Comment'''   
!width="400"|'''Comment'''   
|- style="height:20px"  
|- style="height:20px"  


|titleInfo.title ||  Title ||
|titleInfo.title ||  Title || For multiple MODS titles use multiple instances of dc:title. <br/>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  ||
|name.namePart || Creator || 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 ||
|subject|| Subject || Use separate instances of Type for each MODS element value.
|-
|-
|subject.topic|| Subject ||
|subject.topic|| Subject ||
Line 42: Line 42:
|genre|| Type ||
|genre|| Type ||
|-
|-
|physicalDescription|| Format ||
|physicalDescription|| Format || Use separate instances of Format for each MODS element value.
|-
|-
|internetMediaType|| Format ||
|internetMediaType|| Format ||
Line 50: Line 50:
|form|| Format ||
|form|| Format ||
|-
|-
|identifier|| Identifier ||
|identifier|| Identifier || It is suggested that the identifier type be retained and associated with the identifier value.
|-
|-
|location.URL|| Identifier ||
|location.URL|| Identifier ||
Line 56: Line 56:
|language||  Language ||
|language||  Language ||
|-
|-
|relatedItem|| Relation ||
|relatedItem|| Relation || If type="constituent", a full description may be given under relatedItem and conversion may result in an incomprehensible value. Alternatively, an application may wish to map only some elements under <relatedItem>, e.g., <titleInfo> and <identifier> or <location> if a full MODS description is given. <br/>
For example, if giving a reference to a resource fully described in MODS relatedItem, one could use: <relatedItem><identifier>
and/or title of a resource: <relatedItem><titleInfo><title>
|-
|-
|accessCondition||  Rights ||
|accessCondition||  Rights ||

Revision as of 13:28, 21 July 2009

Virr Medium Multivolume 31 Static.gif Virtueller Raum Reichsrecht

Overview
Functionalities
Support
Copyright and Disclaimer
Scope

Metadata:
Application Profile · Content Models
Metadata Display · ViRR Metadata
Action Matrix

Transformations:
virr 2 mets · mab 2 mods
mods 2 oai dc · mods 2 marc21

Specification

Intern:
Meetings · GUI · Miscellaneous
Development · Planning · Feedback
Related Projects:
Judicial Journals · Late Scholasticism
Digitization Lifecycle

edit


Mapping[edit]

MODS Element Qualified DC Comment
titleInfo.title Title For multiple MODS titles use multiple instances of dc:title.
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 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 Use separate instances of Type for each MODS element value.
subject.topic Subject
subject.name Subject
classification Subject
abstract Description
note Description
tableOfContents Description
originInfo.publisher Publisher
originInfo.dateIssued Date
originInfo.dateCreated Date
originInfo.dateCaptured Date
originInfo.dateOther Date
typeOfResource Type
genre Type
physicalDescription Format Use separate instances of Format for each MODS element value.
internetMediaType Format
extent Format
form Format
identifier Identifier It is suggested that the identifier type be retained and associated with the identifier value.
location.URL Identifier
language Language
relatedItem Relation If type="constituent", a full description may be given under relatedItem and conversion may result in an incomprehensible value. Alternatively, an application may wish to map only some elements under <relatedItem>, e.g., <titleInfo> and <identifier> or <location> if a full MODS description is given.

For example, if giving a reference to a resource fully described in MODS relatedItem, one could use: <relatedItem><identifier> and/or title of a resource: <relatedItem><titleInfo><title>

accessCondition Rights

Example Data[edit]

General Information[edit]