Child pages
  • ContentDM to Aquifer MODS
Skip to end of metadata
Go to start of metadata

Guide to converting ContentDM metadata to Aquifer MODS

Following is a table that could be used to map the default ContentDM export format to MODS that adhere to the Digital Library Federation/Aquifer Implementation Guidelines for Shareable MODS Records. The mapping could be used to create an XSLT to do the conversion. The MODS metadata could then be made available via a static OAI repository.

One approach that we have thought about is to use the "CONTENTdm default" mapping as a base, and then use the position of the unmapped fields to signal which source field data is represented. This approach assumes that this export always exports empty tags when no data is present in a field, assuring, say, the 2nd "unmapped" element in the output always comes from the same custom field.

ContentDM element

MODS element

Notes

format

do not map

This appears to be a local filename that would not be useful in a shared environment.

identifier

<identifier @type="local">xxxx</identifier>

 

alternative

<titleInfo @type="alternative><title>xxxx</title></titleInfo>

 

creator

<name><namePart>xxx</namePart><role><roleTerm type="text">creator</roleTerm></role></name>

Since we cannot assume that a name is a personal name, we recommend leaving out the "type" attribute.

contributor

<name><namePart>xxx</namePart><role><roleTerm type="text">contributor</roleTerm></role></name>

 

language

<language><languageTerm type="text">xxx</languageTerm></language>

 

publisher

<originInfo><publisher>xxx</publisher></originInfo>

 

title

<titleInfo><title>xxxx</title></titleInfo>


coverage

<note>xxx</note>

This element could contain either geographic or temporal information, so it could not be reliably mapped to either date or subject

date

<originInfo><dateCreated keyDate="yes">xxxx</dateCreated></originInfor>

One and only one keyDate attribute is required by the Aquifer guidelines. If multiple <date> elements are present in a ContentDM record, the first date should be given the keyDate attribute

type

<note>xxx</note>

This is closest to <typeOfResource>, but values in this element are restricted. Therefore, we recommend mapping to <note>

medium

<physicalDescription><form>xxx</form></physicalDescription>

 

description

<note>xxxx</note>


extent

<physicalDescription><extent>xxxx</extent></physicalDescription>

 

contributor

<name><namePart>xxx</namePart></name>

ContentDM allows multiple names in the same name element. These should be broken out into separate <name> elements, if possible.

subject

<subject><topic>xxxx</topic></subject>

Some ContentDM example documents carry multiple subjects in a single element. Conversion programs should attempt to break multiple subjects into multiple MODS elements.

rights

<accessCondition type="useAndReproduction">xxx</accessCondition>

 

relation

do not map

Unclear about what this element means

audience

<targetAudience>xxx</targetAudience>

Use the authority attribute, if applicable

cdmid

<identifier type="ContentDM_id">xxx</identifier>


cdmaccess

no mapping


cdmcreated

no mapping


cdmmodified

no mapping


thumbnailURL

<location><url access="preview">....</url></location>

 

viewerURL

no mapping


structure

no mapping


  • No labels