Difference between revisions of "Mapping MODS to OAI DC"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) (→Mapping: added notes) |
Kleinfercher (talk | contribs) m (→Mapping) |
||
| Line 7: | Line 7: | ||
! width="200" |'''[http://www.loc.gov/standards/mods/ MODS] Element''' | ! width="200" |'''[http://www.loc.gov/standards/mods/ MODS] Element''' | ||
! width="200" |'''[http://www.dublincore.org/documents/dces/ Qualified DC]''' | ! width="200" |'''[http://www.dublincore.org/documents/dces/ Qualified DC]''' | ||
!width=" | ! width="500" | '''Comment''' | ||
|- style="height:20px" | |- style="height:20px" | ||
Revision as of 13:29, 21 July 2009
|
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 |