DSpace to MODS mappings

Mandatory velden

UBU-format / DSpace

MODS

Remarks for MODS

Example of XML

M

title

titleInfo>title
titleInfo>subTitle

<titleInfo>
<title>The provisions of the Corpus Juris on community fraud</title>
<subTitle>a Belgian and Dutch perspective</subTitle>
</titleInfo>

M

contributor.author

name>namePart
name>role>roleTerm=aut

Indien type.content=patent:
name>namePart
name>role>roleTerm=pth

Many possibilities with use of subelement Role

<name type="personal" ID="n1">
<namePart type="given">Michael G</namePart>
<namePart type*="family">Faure{*}</namePart>
<role>
<roleTerm authority="marcrelator" type="code">aut</roleTerm>
</role>
<affiliation>Universiteit Maastricht. METRO</affiliation>
</name>

creator.congress

name>namePart
name>role>roleTerm=orm

roleTerm authority="marcrelator" type="code">orm</roleTerm

<name type="conference">
  <namePart>International Workshop on Plasma-Based Ion Implantation 1993 : University of Wisconsin--Madison)*</namePart>
<role><roleTerm authority="marcrelator" type= "code">orm{*}</roleTerm></role>
  </name>

M

creator.corporation

name>namePart
name>role>roleTerm=aut

roleTerm authority="marcrelator" type="code">aut</roleTerm

<name type="corporate">
  <namePart>Applied Science and Technology (ASTeX), Inc</namePart>
<role><roleTerm authority="marcrelator" type="code">aut</roleTerm> 
</name>

contributor.digitizer

name>namePart
name>role>roleTerm=oth

roleTerm authority="marcrelator" type="code">oth</roleTerm

<name type="corporate">
  <namePart>Universiteitsbibliotheek Utrecht</namePart>
<role><roleTerm authority="marcrelator" type="code">oth</roleTerm> 
</name>

contributor.advisor

name>namePart
name>role>roleTerm=ths

<name type="personal">
<namePart type="family">Wortmann</namePart>
<namePart type="given">J.C.</namePart>
<role>
<!-- promotor ->
<roleTerm authority="marcrelator" type="code">ths</roleTerm>
</role>

subject.discipline

classification

<classification>Farmacie</classification>

subject.keywords

subject>topic

<subject>
<topic>grooming</topic>
<topic>hypertension</topic>
</subject>

description.abstract

abstract

<abstract xml:lang="nl">
Voorliggend rapport beschrijft de doelen, de gevolgde aanpak en de
resultaten van de conferentie. Daarna wordende aanbevelingen van de
Commissie Hersenen en Leren gegeven voor een mogelijk vervolgtraject
</abstract>

description.note

note

<note>Deze publicatie heb ik reeds eerder ingediend met de status van "ter perse". Hij is uiteindelijk pas in 2004 verschenen, maar ik heb pas onlangs een exemplaar van het tijdschrift ontvangen</note>

M

publisher

originInfo>publisher

<originInfo>
<publisher>
Netherlands Organization for Scientific Research (NWO)</publisher>
<dateIssued encoding="iso8601">2005</dateIssued>
</originInfo>

M

date.created

originInfo>dateIssued

<originInfo>
<dateCreated encoding="iso8601">1997</dateCreated>
</originInfo>

date.valid

originInfo>dateValid

<originInfo>
<dateValid encoding="iso8601">1997</dateValid>
</originInfo>

date.available

recordInfo.recordCreationDate

Not to be used with OAI-response!

M

date.issued

originInfo>dateIssued

Use only when date.created is not available

<originInfo>
<dateIssued encoding="iso8601">1997</dateIssued>
</originInfo>

M

type.content

genre

Much better

<genre>info:eu-repo/semantics/article</genre>

M

type.physical

typeOfResource
Indien type.physical afwezig: standaard op text zetten

Much better

<typeOfResource>text</typeOfResource>

format.extent

format.extent

Not to be used with OAI-response!

identifier.isbn

identifier type="isbn"
Indien "chapter":
relatedItem> identifier type="isbn"

<identifier type="uri">URN:ISBN:90-5278-327-6</identifier>

relation.ispartofissn

identifier type="issn"

<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>

identifier.uri

identifier.uri

Not in metadata-section of DIDL

identifier.urljumpoff

location.url?

Not in metadata-section of DIDL

language.iso

language>languageTerm

<language>
<languageTerm authority="rfc3066" type="code">en</languageTerm>
</language>

M

relation.ispartofseries

relatedItem type="host">titleInfo>title

<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>

M

relation.ispartofmonograph

relatedItem type="host">titleInfo>title

<relatedItem type="host">
<titleInfo>
<title>Das Corpus Juris als Grundlage eines europaeischen Strafrechts : Europaeisches Kolloquium, Trier, 4.-6. Maerz 1999 </title>
</titleInfo>

M

ispartofvolume

relatedItem>part>detail type="volume">number

<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>

M

ispartofissue

relatedItem>part>detail type="issue">number

<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>

ispartofstartpage

relatedItem>part>extent unit="page">start

<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>

ispartofendpage

relatedItem>part>extent unit="page">end

<relatedItem type="host">
<identifier type="uri">URN:ISSN:0304-3940</identifier>
<titleInfo>
<title>Neuroscience Letter</title>
</titleInfo>
<part>
<detail type="volume">
<number>77</number>
</detail>
<detail type="issue">
<number>1</number>
</detail>
<extent unit="page">
<start>71</start>
<end>75</end>
</extent>
</part>
</relatedItem>

coverage.spatial

subject>geographic

- <<subject authority="lcsh">
  <geographic>{*}Campbell County (Wyo.)*</geographic></ subject>

coverage.temporal

subject>temporal

<subject><temporal>1980-2000 </temporal></subject>

rights.accessrights

accessCondition

Not in metadata-section of DIDL

rights.placeofpublication

originInfo>place>placeTerm

<originInfo>
<place>
<placeTerm>Freiburg im Breisgau</placeTerm>
</place>

audience

targetAudience

<targetAudience>students></ targetAudience>

edition

originInfo>edition

<originInfo><edition>2e herz. Versie></edition>
</originInfo>

UBU types

New MODS-types

Old DARE-types

Annotation

annotation

Annotation

Article
Article / Letter to editor
Article - letter to the editor
Article in monograph or in proceedings
Book editorial

article

Article / Letter to editor


Article in monograph or in proceedings
Book editorial

Bachelor thesis

bachelorThesis

Bachelor thesis

book
Book (monograph)
Book-monograph-editorial book

book

Book (monograph)

Part of book or chapter of book
Part of book - chapter
Part of book / Chapter

bookPart

Part of book or chapter of book

Book review

bookReview

Book review

Pamphlet

conferencePaper

Contribution for newspaper or weekly magazine
Newspaper article

contributionToPeriodical

Contribution for newspaper or weekly magazine
Newspaper article

Doctoral thesis
Dissertation

doctoralThesis

Doctoral thesis

Conference lecture
Educational material
Inaugural lecture
Working material

lecture

Conference lecture
Educational material
Inaugural lecture
Working material

Master thesis

masterThesis

Master thesis

Patent

patent

Patent

Preprint

preprint

Preprint

Commission report or memorandum
Conference report
External research report
Internal report
Statistical report

report

Commission report or memorandum
Conference report
External research report
Internal report
Statistical report

Student thesis

studentThesis

Student thesis

Technical documentation

technicalDocumentation

Technical documentation

Research paper

workingPaper

Research paper

DC field

Title

Repeatable

Comments

contributor

author

Yes

title

No

title

alternative

Yes

date

issued

No

publisher

No

identifier

citation

No

relation

is part of series

Yes

identifier

Yes

any identification numbers or codes associated with it

type

Class / type of content

No

type

type of content

Yes

language

ISO

No

subject

keywords

Yes

description

abstract

No

description

sponsors

No

description

other

No

DC field

Repeatable

Comments

contributor

author

Y

contributor

editor

Y

contributor

promotor

Y

contributor

coverage

court

coverage

researchinstiture

coverage

spatial

creator

faculty

Y

creator

metisid

Y

creator

Do not use; only for harvested metadata.

date

accessioned

date

available

date

created

date

issued

date

metis

description

abstract

description

sponsorship

Y

description

format

extent

Y

format

mimetype

identifier

annotationnr

identifier

metisid

identifier

uri

language

Y

provenance

metis

publisher

place

publisher

relation

references

rights

source

booktitle

source

bundletitle

source

contribution

source

epage

source

issue

source

journaltitle

source

pag

source

series

source

spage

source

uri

Do not use; only for harvested metadata.

source

volume

source

Do not use; only for harvested metadata.

subject

ddc

subject

lcc

subject

lcsh

subject

mesh

subject

metis

subject

Uncontrolled index term.

title

alternative

title

type

class

type

metis

type

DC field

MODS element

Comments

Title

<titleInfo><title>

Creator

<name><namePart><role 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><uri>

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>

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>

Rights

<accessCondition>

DC field

Title

MODS field

Comments

contributor

author

<name><namePart><role type="text">creator

title

<titleInfo><title>

title

alternative

<titleInfo><title>

Type alternative

date

issued

<originInfo><dateIssued>

publisher

<originInfo><publisher>

identifier

citation

Used for theses

relation

is part of series

<relatedItem>

identifier

<identifier>

type

Class / type of content

<genre>

type

type of content

<genre>

language

ISO

<language>

subject

keywords

<subject>

description

abstract

<abstract>

description

sponsors

<note>

description

other

<note>

DC field

Title

MODS field

Comments (from Leiden and when noted from Utrecht)

contributor

author

<name><namePart>*<role type="text">creator*

contributor

editor

<name><namePart>*<role type="text">editor*

contributor

promotor

<name><namePart>*<role type="text">promotor*

contributor

<name><namePart>

coverage

court

<subject><hierarchicalGeographic>

coverage

researchinstiture

<subject><hierarchicalGeographic>

coverage

spatial

<subject><geographic>

creator

faculty

<name type="text">corporate

creator

metisid

<name type="text">enumerated

Utrecht: is this the DAI? We use that as suffix for contributor.author

creator

<name><description>

date

accessioned

<originInfo><dateCaptured>

(means 'addition to repositorium' -> date in DSPACE

date

available

<originInfo><dateOther type="text">available

date

created

<originInfo><dateCreated>

date

issued

<originInfo><dateIssued>

date

metis

<originInfo><dateOther type="text">metis

description

abstract

<abstract>

description

sponsorship

<note>

description

<note>

format

extent

<physicalDescription><extent>

format

mimetype

<physicalDescription><internetMediaType>

identifier

annotationnr

<identifier type="text">annotationnr

identifier

metisid

<identifier type="text">metisid

identifier

uri

<location><uri>

language

<language>

publisher

place

<originInfo><place>

publisher

<originInfo>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0407c31e-28ff-4b64-a34f-04cfce822f6a"><ac:plain-text-body><![CDATA[

relation

references

[Title of a book][][Place of publication]:[] [publisher]; [ ][year of issue].

Utrecht: We don't use relation.references

]]></ac:plain-text-body></ac:structured-macro>

rights

<accessCondition>

source

booktitle

<relatedItem><titleinfo><title>

Utrecht: We use our own defined field relation.ispartofmonograph

source

bundletitle

<relatedItem><type>bundle</type><titleinfo><title>

Utrecht: We use our own defined field relation.ispartofseries

source

contribution

<relatedItem><type>contributing</type><titleinfo><title>

Utrecht: We don't use a field for this (yet)

source

epage

<relatedItem><part><extent><end>

Utrecht: We use our own defined field relation.ispartofendpage

source

issue

<relatedItem><type>issue</type><titleinfo><title>

Utrecht: We use our own defined field relation.ispartofissue

source

journaltitle

<relatedItem><type>host</type><titleinfo><title>

Utrecht: We use our own defined field relation.ispartofseries

source

pag

<relatedItem><part><extent><total>

Utrecht: We don't use a field for this (yet)

source

series

<relatedItem><type>series</type><titleinfo><title>

Utrecht: We use our own defined field relation.ispartofmonograph

source

spage

<relatedItem><part><extent><start>

Utrecht: We use our own defined field relation.ispartofstartpage

source

uri

<location><url>

Utrecht: We don't think this is part of MODS

source

volume

<relatedItem><type>bundle</type><identifier>

Utrecht: We use our own defined field relation.ispartofvolume

source

<relatedItem><note>

Utrecht: We use our own defined field description.note

subject

ddc

<classification>*<authority>ddc*

subject

lcc

<classification>*<authority>lcc*

subject

lcsh

<subject><authority>lcsh

subject

mesh

<subject><authority>mesh

subject

<subject><name>

title

alternative

<titleInfo><type>alternative<title>

title

<titleInfo><title>

type

class

KNAW
Utrecht: We don't think this is part of MODS

type

metis

Utrecht: We don't use a part field, but make a mapping to dc:type with import

type