...

Note
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Section

Column

Table of Contents

maxLevel	1

Column

Excerpt
The following sections present a description of all bibliographic metadata fields of the HBO Bibliographic Metadata application profile of MODS.

...

Code Block

	xml
	xml
title	Example


(...)
<didl:Item>

  <!-- Semantic Type -->
  <didl:Descriptor>
    <didl:Statement mimeType="application/xml">
      <rdf:type rdf:resource="info:eu-repo/semantics/DescriptiveMetadata"/>
    </didl:Statement>
  </didl:Descriptor>

  (...)


  <!-- Content -->
  <didl:Component>
    <didl:Resource mimeType="application/xml">
      (...) <!-- MODS goes here -->
    </didl:Resource>
  </didl:Component>

</didl:Item>
(...)

A MODS record starts with the mods root element. If not declared elsewhere in the XML document, the mods element MUST declare a namespace by setting the xmlns attribute of the mods element to http://www.loc.gov/mods/v3^{Image Removed}. We are using version 3.4. This SHOULD be made explicit by using the version attribute. Referencing the XML schema is optional

Code Block

	xml
	xml
title	Example


(...)
<didl:Resource mimeType="application/xml">

  <mods xmlns="http://www.loc.gov/mods/v3"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-4.xsd"
      version="3.4">
    (...)
  </mods>

</didl:Resource>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<titleInfo>
  <title>Main Title</title>
  <subTitle>Subtitle</title>
</titleInfo>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<abstract xml:lang="en">A short abstract.</abstract>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<genre>info:eu-repo/semantics/BachelorThesis</genre>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<language objectPart="summary">
  <languageTerm type="code" authority="rfc3066">eng</languageTerm>
</language>
<language objectPart="main">
  <languageTerm type="code" authority="rfc3066">nld</languageTerm>
  <languageTerm type="text" lang="nld">Nederlands</languageTerm>
  <languageTerm type="text" lang="eng">Dutch</languageTerm>
</language>
(...)

2. Names of Persons and Organisations

...

Code Block

	xml
	xml
title	Example


(...)
<name>
  <namePart>Name<namePart>
  <role>
    <roleTerm authority="marcrelator">term</roleTerm>
  </role>
  <affiliation>Term</affiliation>
</name>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<name type="personal">
  <namePart type="family">Vries, de<namePart>
  <namePart type="given">J. (Jan)<namePart>
  <role>
    <roleTerm authority="marcrelator">aut</roleTerm>
  </role>
  <affiliation>Lector</affiliation>
</name>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<name ID="nameID_1" type="corporate">
  <namePart>Hogeschool van Amsterdam. Media, Creatie en Informatie. Electronisch Uitgeven</namePart>
  <role>
    <roleTerm authority="marcrelator">pbl</roleTerm>
  </role>
</name>

(...)

<extension>
  <hbo:name xmlns:hbo="info:eu-repo/xmlns/hboMODSextension" ID="nameID_1" type="corporate">
    <hbo:namePart type="organisation">Hogeschool van Amsterdam </hbo:namePart>
    <hbo:namePart type="department">Media, Creatie en Informatie</hbo:namePart>
    <hbo:namePart type="lectorate">Electronisch Uitgeven</hbo:namePart>
  </hbo:name>
</extension>
(...)

Tip
See also: HBO MODS Extension

.

3. Dates

...

Dates are specified according to [ISO-8601|http://www.w3.org/TR/NOTE-datetime] using the RECOMMENDED notation {{YYYY-\ using the RECOMMENDED notation YYYY-[MM-\[DD\]\]}}. In this notation, only the year is a REQUIRED part. A month MUST be specified when the day is present. It is RECOMMENDED to specify both year, month and day.

All dates are placed under the originInfo top-level element.

...

Code Block

	xml
	xml
title	Example


(...)
<originInfo>
  <dateIssued encoding="iso8601">2011-03-23</dateIssued>
</originInfo>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<originInfo>
  <dateCreated encoding="iso8601">2010-12-07</dateCreated>
</originInfo>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<originInfo>
  <dateOther type="embargo" encoding="iso8601">2011-05-17</dateOther>
</originInfo>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<originInfo>
  <dateOther type="approved" encoding="iso8601">2011-02-28</dateIssued>
</originInfo>
(...)

4. Keywords, Classifications and Target Audiences

...

Code Block

	xml
	xml
title	Example


(...)
<subject xml:lang="nl">
  <topic>metadata</topic>
  <topic>digitale brievenbus</topic>
</subject>
<subject xml:lang="en">
  <topic>keyword</topic>
</subject>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<classification authorityURI="info:eu-repo/classification/Nbc" displayLabel="Informatica">54</classification>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<targetAudience authority="marctarget">general</targetAudience>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<subject>
  <geographic>Netherlands</geographic>
</subject>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<subject>
  <temporal encoding="iso8601">1985-05</temporal>
</subject>
(...)

5. Related bibliographic material

...

Code Block

	xml
	xml
title	Example


(...)
<relatedItem type="host">
  <identifier type="uri">URN:ISSN:0304-3940</identifier>
  <titleInfo>
    <title>Neuroscience Letter</title>
  </titleInfo>
  <originInfo>
   <place>Amsterdam</place>
   <publisher>Elsevier</publisher>
  </originInfo>
  <part>
    <detail type="volume">
      <number>77</number>
    </detail>
    <detail type="issue">
      <number>1</number>
    </detail>
    <extent unit="page">
      <start>71</start>
      <end>75>
    </extend>
  </part>
</relatedItem>
(...)

6. Bilbliographic Identifiers

...

Code Block

	xml
	xml
title	Example


(...)
<name type="personal" ID="n1">
  <namePart type="family">Vries, de</namePart>
  <namePart type="given">J. (Jan)</namePart>
  <role>
    <roleTerm authority="marcrelator" type="code">aut</roleTerm>
  </role>
</name>
(...)
<extension>
  <dai:daiList 
    xmlns:dai="info:eu-repo/dai"
    xsi:schemaLocation="info:eu-repo/dai
    http://www.surfgroepen.nl/sites/oai/metadata/Shared%20Documents/dai-extension.xsd">
    <dai:identifier IDref="n1" authority="someAuthority">123456789</identifier>
  </dai:daiList>
</extension>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<identifier type="someType">1234567890</identifier>
(...)

...

Code Block

	xml
	xml
title	Example


(...)
<location>http://thirdparty.org/resource</location>
(...)

7. Copyright

MODS provides no native mechanism to publish copyright statements for described material. For this, an extension has been defined that is used in the NARCIS infrastructure. This extension will also be use in this specification.

Code Block

	xml
	xml
title	Example


(...)
<extension>
	<wmp:rights
		xmlns:wmp=http://www.surfgroepen.nl/werkgroepmetadataplus
		xmlns:dc="http://purl.org/dc/elements/1.1/"
		xsi:schemaLocation="http://www.surfgroepen.nl/werkgroepmetadataplus rights.xsd">
		<dc:description>
			© 2010 Hogeschool van Amsterdam
			This work is licensed under a Creative Commons
			Attribution-Noncommercial-No Derivative Works 3.0 Unported License.
		</dc:description>
		<dc:rights>http://creativecommons.org/licenses/by-nc-nd/3.0/</dc:rights>
	</wmp:rights>
</extension>
(...)

Tip
See also the Use of MODS#UseofMODS-CopyrightMODS#Copyright for the associated schema.

Child pages

Versions Compared

Old Version 8

New Version Current

Key

2. Names of Persons and Organisations

3. Dates

4. Keywords, Classifications and Target Audiences

5. Related bibliographic material

6. Bilbliographic Identifiers

7. Copyright

Child pages

Page History

Versions Compared

Old Version 8

New Version Current

Key

2. Names of Persons and Organisations

3. Dates

4. Keywords, Classifications and Target Audiences

5. Related bibliographic material

6. Bilbliographic Identifiers

7. Copyright