Difference between revisions of "Mapping MODS to OAI DC"
Kleinfercher (talk | contribs) |
Kleinfercher (talk | contribs) m (→Comment) |
||
| Line 81: | Line 81: | ||
==Comment== | ==Comment== | ||
* If we provide export of ViRR metadata in oai_dc and/ or marc21 it must be clear | * If we provide export of ViRR metadata on the user interface in oai_dc and/ or marc21 it must be clear that the export in this format only contains bibliographic metadata. For exporting structural metadata one has to use [[ViRR_and_METS| mets]] export | ||
==General Information== | ==General Information== | ||
Revision as of 07:29, 22 July 2009
|
The following specifies the mapping of MODS metadata, which are part of the escidoc metadata record for ViRR items to Dublin Core metadata. This transformation will be exploited for the OAI-PMH interface of the ViRR solution.
This mapping basically reflects the mapping recommended by the Library of Congress.
Mapping[edit]
| MODS Element | Dublin Core Metadata Element | 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. |
| order | -- | Add to title (???) |
| subject | Subject | |
| 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 | |
| originInfo.edition | -- | |
| originInfo.place.placeTerm | -- | Add to Publisher (???) |
| typeOfResource | Type | Use separate instances of Type for each MODS element value. |
| genre | Type | |
| physicalDescription | Format | Use separate instances of Format for each MODS element value. |
| internetMediaType | Format | |
| extent | Format | |
| form | Format | |
| recordInfo.recordIdentifier | Identifier | |
| identifier | Identifier | It is suggested that the identifier type be retained and associated with the identifier value. |
| location.URL | Identifier | |
| location.physicalLocation | Description | With prefix "Location:" (???) |
| 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 | |
| copyInformation | Rights |
Other LoC Formats[edit]
We can also provide ViRR metadata in MARC21 format, as there is a transformation already provided (mods2marc21).
Comment[edit]
- If we provide export of ViRR metadata on the user interface in oai_dc and/ or marc21 it must be clear that the export in this format only contains bibliographic metadata. For exporting structural metadata one has to use mets export
General Information[edit]
- Metadata Object Description Schema (MODS)
- Dublin Core Metadata Elements V1.1
- Mapping from Library of Congress
- MODS in CoLab
- If we can do it without escidoc specific mapping parts we can also use the xsl provided by the LoC. (Differences are colored)