Northern Illinois University Digital Library

Introduction

Submitted by Matthew Short on Thu, 11/10/2016 - 16:16

This is a set of implementation guidelines of the Metadata Object Description Schema (MODS) for use in describing digital collections at Northern Illinois University. These guidelines are intended to meet minimum requirements for description and interoperability defined by the Digital Library Federation. In the interest of interoperability and shareability, it is important that the same elements, attributes, and values are used consistently from project to project. New projects should adhere closely to this data dictionary, while documenting any divergences. The elements and attributes below are designated as required, required if applicable, or recommended. In many cases, a required element and attribute will also have a required container, which will always be noted at the beginning of the usage guidelines for that element. If an element is not recommended, then it has been omitted from the data dictionary entirely. An element may also be designated as repeatable. The two charts at the beginning of this document attempt to summarize these requirements for ready reference. Each element section below consists of:

  • A list of the element’s attributes and subelements;
  • A summary of usage guidelines and requirements;
  • Element definitions from the MODS User Guidelines;
  • Examples of the element illustrating the application of these guidelines.

Based on MODS Schema version 3.5.

Please direct any questions or corrections to the Metadata Librarian, Matthew Short.

Universal Attributes

Submitted by Matthew Short on Thu, 11/10/2016 - 16:18

lang

This attribute is used to specify the language of a value at the element level. If the language of the element is different from that specified in , then this attribute is required. As specified elsewhere in these guidelines, the value of the lang attribute must be taken from ISO 639-2/b.

script

This attribute is used to specify the script of a value at the element level, and is required anytime a non-roman script is used. The value of the script attribute must be taken from ISO 15924. transliteration This attribute specifies the transliteration technique used at the element level (e.g. ALA/LC Romanization Tables). The value of transliteration is uncontrolled. Non-roman scripts do not need to be transliterated.

xlink:href

Use the xlink attribute when linking to an external resource, like a complementary metadata record. These guidelines recommend using xlink in and only

Title

Submitted by Matthew Short on Thu, 11/10/2016 - 16:30
MODS Element Attributes Subelements
<mods:titleInfo>

@type

@authority

<mods:title>

<mods:subTitle>

<mods:partNumber>

<mods:partName>

<mods:nonSort>

Usage guidelines:

  1. One <mods:titleInfo><mods:title> is always required.
  2. Choice and format of titles are governed by RDA. Other content standards, like CCO, DACS, or DCRM may be used in subsequent <mods:titleInfo> elements. As always, the choice should take into consideration the expectations of users first and the content standard second.
  3. In general, transcribe the title from the resource. If there is no title on the resource, use a title already assigned or found in reference sources.
  4. Do not use “Untitled” or the filename. Title is required and null values are not allowed. If no title can be found, construct a title using RDA.
  5. It is not necessary to have a unique title for every resource.
  6. Do not include punctuation intended to separate parts of the title (eg. a colon after <mods:title>, followed by <mods:subTitle>).
  7. For parallel titles, use separate <mods:titleInfo> elements with @type=“translated” and @lang=’[appropriate iso639-2/b code]
  8. Only include dates if they are considered part of the title.
  9. Multiple <mods:namePart> elements should be used in a single <mods:titleInfo> to describe a single part with many hierarchical levels. Multiple parts should be separated into multiple <mods:titleInfo> elements.
  10. <mods:nonSort> is always required when non-sorting characters are present (e.g. ‘the’, ‘an’)

Elements

<mods:titleInfo>

Required: Y

Repeatable: Y

Definition: A word, phrase, character, or group of characters, normally appearing in a resource, that names it or the work contained in it. <mods:titleInfo> must contain at least one <mods:title> subelement.

Attributes:

type (required if applicable): do not use the type attribute for the primary title, but use it for all subsequent titles. Type accepts the following values:

abbreviated: title as abbreviated for indexing or identification

translated:  cataloger-supplied translation of the title proper

alternative:  varying form of the title if it contributes to the further identification of the item, including parallel titles

uniform:  a preferred title, used when a work has appeared under varying titles

authority (required if applicable): when type=”uniform”, the value is always “naf” for the Library of Congress’ Name Authority File

<mods:title>

Required: Y

Repeatable: N

MARC: 245 $a

Definition: A word, phrase, character, or group of characters that constitutes the chief title of a resource (i.e. the title normally used when citing the resource).

<mods:subTitle>

Required: N

Repeatable: N

MARC: 245 $b

Definition: A word, phrase, character, or group of characters that contains the remainder of the title information after the title proper

<mods:partNumber>

Required: N

Repeatable: N

MARC: 245 $n

Definition: A part or section number of a title (e.g. volume 1, part 3) when that part refers to an intellectual component of the resource

<mods:partName>

Required: N

Repeatable: Y

MARC: 245 $p

Definition: A part or section name of a title (e.g. chapter title, episode name, or audio clip)

<mods:nonSort>

Required: N

Repeatable: N

MARC: 245 second indicator

Definition: Characters, including initial articles, punctuation, and spaces that appear at the beginning of a title that should be ignored for indexing of titles.

Examples

<mods:titleInfo>
  <mods:nonSort>The</mods:nonSort> 
  <mods:title>Olympics</mods:title> 
  <mods:subTitle>a history</mods:subTitle> 
  <mods:partNumber>Part 1</mods:partNumber> 
  <mods:partName>Ancient</mods:partName>
</titleInfo>

<mods:titleInfo type="uniform" authority="naf"> 
  <mods:title>Bible</mods:title> 
  <mods:partName>Exodus</mods:partName> 
</mods:titleInfo>


<mods:titleInfo xml:lang="fr" type="translated">
  <mods:nonSort>L'</mods:nonSort> 
  <mods:title>homme qui voulut être roi</mods:title>
</mods:titleInfo>


<mods:titleInfo lang="rus" script="Latn">
  <mods:title>Geodezja i urzadzenia roline</mods:title>
</mods:titleInfo>

 

Name

Submitted by Matthew Short on Fri, 11/11/2016 - 10:32
MODS Element Attributes Subelements
<mods:name>

@type

@authority

<mods:namePart>

<mods:displayForm>

<mods:affiliation>

<mods:role>

    <mods:roleTerm>

Usage Guidelines

  1. One <mods:name><mods:namePart> with one <mods:role><mods:roleterm type=”text”> is always required.
  2. When choosing an authoritative form of a name, check the Library of Congress Name Authority File. If no authorized form exists, contact the Metadata Librarian.
  3. Always include as many contributors as you can identify.
  4. “Anonymous” may be used if indicated on the source. If the creator is unknown and “anonymous” does not appear on the source, omit <mods:name>. DO NOT use “unknown” or “anonymous” as a generic name value.
  5. Include BOTH the creator of the intellectual content being captured (painter, architect, etc.) AND the name of anyone capturing that content in a new medium (e.g. for an image of a painting, include both the painter and the photographer).
  6. <mods:role> should be repeated for each new role, but multiple <mods:roleTerm> elements may be used in a single <mods:role> wrapper
  7. Values for <mods:roleTerm type=”text”> should be taken from RDA Appendix I or local documentation.
  8. Values for <mods:roleTerm type=”code”> should be taken from the MARC relator code list.
  9. Family and given name should be enclosed in a single <mods:namePart> element, but date and term of address should be enclosed separately, with the appropriate type attribute.
  10. If names are in a hierarchy, include each part in a separate namePart element, from largest to smallest.
  11. Names can also be used as subjects (see below).

Elements

<mods:name>

Required: N

Repeatable: Y

MARC: 1XX, 7XX

Definition: The name of a person, organization, or event (conference, meeting, etc.) associated in some way with the resource. <mods:name> must include at least one <mods:namePart> subelement.

Attributes:

type (required): Type takes the following values:

personal

corporate

conference

authority (required): “naf” or “local”

<mods:namePart>

Required: Y

Repeatable: Y

MARC: 1/7XX $a, $b

Definition: The individual parsed parts that together make up the full name.

Attributes:

type: Type takes the following values:

date

family

given

termsOfAddress

<mods:role>

Required: Y

Repeatable: Y

MARC: 1/7XX $e

Definition: Designates the relationship (role) of the entity recorded in name to the resource describedin the record. <mods:role> is a container element for the role recorded in one or more <mods:roleTerm> subelements.

<mods:roleTerm>

Required: Y

Repeatable: Y

Definition:

Attributes:

type (recommended): type takes the following values:

text

code

authority (recommended): use “marcrelator”

Examples

<mods:name type="personal" authority="naf">
  <mods:namePart>Woolf, Virginia</mods:namePart>
  <mods:namePart type="date">1882-1941</mods:namePart>
  <mods:role>
    <mods:roleTerm type="text">author</mods:roleTerm>
    <mods:roleTerm type="code" authority=”marcrelator”>aut</mods:roleTerm>
  </mods:role>
</mods:name>

<mods:name type="conference" authority=”naf”>
  <mods:namePart>International Workshop on Plasma-Based Ion Implantation (1993 : University of Wisconsin--Madison)</mods:namePart>
</mods:name>

<mods:name type="corporate" authority=”naf”>
  <mods:namePart>United States</mods:namePart>
  <mods:namePart>Court of Appeals (2nd Circuit)</mods:namePart>
</mods:name>

 

Type of Resource

Submitted by Matthew Short on Fri, 11/11/2016 - 12:31
MODS Element Attributes Subelements
<mods:typeOfResource>

@collection

@manuscript

 None

Usage Guidelines

  1. Information recorded in <mods:typeOfResource> refers to the original object. For example, in a record for a digitized photograph, <mods:typeOfResource> would refer to the analog original, not to the digital surrogate. If the object is born-digital, then it would refer to that object.
  2. This element takes only the following values:

text

cartographic

notated music

sound recording

sound recording-musical

sound recording-nonmusical

still image

moving image

three dimensional object

software, multimedia

mixed material

Elements

<mods:typeOfResource>

Required: Y

Repeatable: Y

MARC: Leader/06

Definition: A term that specifies the characteristics and general type of content of the resource.

Attributes:

collection=”yes” (recommended if applicable): used to indicate whether the resource described is a collection. If there are multiple resource types within the collection, use multiple <mod:typeOfResource> elements

manuscript=”yes” (recommended if applicable): use to indicate whether the resource is handwritten or typescript

Genre

Submitted by Matthew Short on Fri, 11/11/2016 - 12:36
MODS Element Attributes Subelements
<mods:genre> @authority None

Usage Guidelines

  1. <mods:genre> refers to the content of the digital resource being described, not to the digital resource itself.
  2. At minimum, use a broad genre term that narrows the scope of the value given in <mods:typeOfResource>. “Photograph,” for example, is a term that can be found in most vocabularies, like LCSH, AAT, and TGM II.
  3. More specific genre terms that suit the needs of a particular project are strongly recommended, but should always be taken from a controlled vocabulary. The most appropriate vocabulary will vary depending on the project, but common choices include:

aat (Art & architecture thesaurus (Getty))

rbgenr (Genre terms)

gmgpc (Thesaurus for graphic materials (LC))

rbbin (Binding terms)

rbpap (Paper terms)

rbpri (Printing & publishing evidence)

rbprov (Provenance evidence)

rbpub (Printing and publishing evidence)

rbtyp (Type evidence)

Elements

<mods:genre>

Required: R

Repeatable: Y

MARC: 008/24-33, 655

Definition: A term or terms that designate a category characterizing a particular style, form, or content, such as artistic, musical, literary composition, etc.

Attributes:

authority (required): Values should be taken from the Subject Category Code Source Codes or the Genre/Form Code and Term Source Codes

Examples

<!--For a digital image of a Civil War era daguerreotype portrait-->

<mods:genre authority="aat">daguerreotypes</mods:genre>
<mods:genre authority="aat">portraits</mods:genre>

<!--For a children's adventure story-->

<mods:genre authority="gsafd">adventure fiction</mods:genre>
<mods:genre authority="lcsh">Children's literature</mods:genre>

 

Origin Info

Submitted by Matthew Short on Fri, 11/11/2016 - 12:48
MODS Element Attributes Subelements
<mods:originInfo>

@type -- <mods:place>

@authority -- <mods:place>

@keyDate -- date

@encoding -- date

@point -- date

@qualifier -- date

@eventType -- <mods:originInfo>

<mods:place>

    <mods:placeterm>

<mods:publisher>

<mods:dateIssued>

<mods:dateCreated>

<mods:copyrightDate>

<mods:dateOther>

<mods:edition>

<mods:issuance>

<mods:frequency>

Usage Guidelines

  1. At least one <mods:originInfo> with one date subelement marked as the key date are required in every record. Even if there is only one date in the record, that date must be marked as the keyDate. For date ranges, the start date should be marked as the keyDate.
  2. This element represents the original form of the resource, not the digitized form of an originally analog resource. Information related to digitization should go in <mods:relatedItem> or <mod:note> (more below).
  3. It is not necessary to include full <mods:originInfo> for every version of a resource known to exist. Only include information about those versions likely to be relevant to an end user.
  4. Rely on RDA for determining the place and publisher of a resource. This element may also be used for production, manufacture, or distribution.
  5. Omit <mods:place> element if no information is known about the originating place of a resource. DO NOT use “unknown.”
  6. For coded <mods:placeTerm> values, the MARC Code List for Countries is preferred, but ISO3166 may also be used. Indicate your choice in the authority attribute.
  7. If multiple date elements apply, but would contain identical information, use only one of the relevant date elements.
  8. If a date range is being indicated, always use the point attribute. If a single date is being indicated, never use the point attribute.
  9. When a date is uncertain, indicate this in a qualifier attribute. When only the decade or century are known, enter a date range for the entire decade or century and mark the date as questionable. DO NOT use “ca.”
  10. Information related to the digitization process, such as <mods:dateCaptured> or <mods:dateValid> should be omitted in the descriptive record.
  11. Places can also be subjects (more below).

Elements

<mods:originInfo>

Required: Y

Repeatable: Y

Definition: Information about the origin of the resource, including place of origin or publication, publisher/originator, and dates associated with the resource.

Attributes:

eventType (required): Takes the following values:

production

publication

distribution

manufacture

<mods:place>

Required: R

Repeatable: Y

Definition: Name of a place associated with the issuing, publication, release, distribution, manufacture, production, or origin of a resource. Place is a wrapper for <mods:placeTerm>

<mods:placeTerm>

Required: Y

Repeatable: Y

MARC: 264 $a

Definition: Used to express place in a textual or coded form.

Attributes:

type (required): Takes the following values:

text

code

authority (recommended if applicable): Used to indicate the controlled list from which the code is taken. Authority takes the following values:

marccountry

iso3166

<mods:publisher>

Required: N

Repeatable: Y

MARC: 264 $b

Definition: The name of the entity that published, printed, distributed, released, issued, or produced the resource.

<mods:dateIssued>: publication or issued date (260 $c, 008/07-14)

<mods:dateCreated>: date of creation of the resource (260 $c, $g, 534 $c, 533 $d)

<mods:copyrightDate>: date on which a resource is copyrighted (260 $c)

<mods:dateOther>: generic date element that does not fall into another category but is important to the record

Required: Y

Repeatable: Y

MARC: 264 $c, 008/07-14

Attributes for date elements:                       

encoding (required): Dates should always be recorded in a structured form using W3CDTF. If W3CDTF cannot be used for some reason (e.g. the exact year is unknown), ISO8601 may be used instead.

point (required if applicable): always use for date ranges, but never for single dates

keyDate=”yes” (required): the date considered to be the most important for end user access, typically the date of creation or issuance.

qualifier (recommended if applicable): qualifier takes the following values:

inferred

questionable

<mods:edition>

Required: R

Repeatable: N

MARC: 250

Definition: Information identifying the version of the resource.

<mods:issuance>

Required: N

Repeatable: N

MARC: Leader/07

Definition: A term that designates how the resource is issued. <mods:issuance> takes the following values:

monographic

single unit

multipart monographic

continuing

serial

integrating resource

<mods:frequency>

Required: N

Repeatable: N

MARC: 008/18, 310

Definition: A statement of publication frequency in textual form.

Examples

<mods:originInfo eventType="publication">
  <mods:place>
    <mods:placeTerm type="text">New York</mods:placeTerm> 
  </mods:place> 
  <mods:publisher>MacMillan</mods:publisher>
  <mods:copyrightDate encoding="w3cdtf" keyDate="yes" qualifier="inferred">1922</mods:copyrightDate>
  <mods:edition>2nd ed.</mods:edition>
</mods:originInfo>

<mods:originInfo eventType="publication">
  <mods:place>
    <mods:placeTerm type="code" authority="marccountry">dcu</mods:placeTerm>
    <mods:placeTerm type="text">Washington, DC</mods:placeTerm>
  </mods:place>
  <mods:publisher>Library of Congress, Cataloging Distribution Service, in collaboration with Follett Software Company</mods:publisher>
  <mods:dateIssued encoding="w3cdtf" keyDate="yes" >2003</mods:dateIssued>
  <mods:edition>7th ed.</mods:edition>
  <mods:issuance>monographic</mods:issuance>
</mods:originInfo>

<mods:originInfo eventType="publication">
  <mods:dateCreated encoding="w3cdtf" keyDate="yes" qualifier="approximate" point="start">1857</mods:dateCreated> 
  <mods:dateCreated encoding="w3cdtf" qualifier="approximate" point="end">1860</mods:dateCreated>
</mods:originInfo>

 

Language

Submitted by Matthew Short on Fri, 11/11/2016 - 13:11
MODS Element Attributes Subelements
<mods:language>

@type -- <mods:languageTerm>

@authority -- <mods:languageTerm>

<mods:languageTerm>

<mods:scriptTerm>

Usage Guidelines

  1. At least one <mods:language><mods:languageTerm> element is required for all resources in which language is primary (e.g. textual resources and video/audio resources with spoken-word components).
  2. At minimum, there should be one pair of <mods:languageTerm> elements: one element in text and one in code.
  3. Coded values should be taken from ISO639-2b, which is identical to the MARC Code List for Languages.
  4. When the text of a resource is in a non-Latin script, ALWAYS code for the script using ISO15924. This is especially important for South East Asian materials.

Elements

<mods:language>

Required: Y

Repeatable: Y

Definition: A designation of the language in which the content of a resource is expressed. <mods:language> is a wrapper for one or more <languageTerm> elements.

<mods:languageTerm>

Required: Y

Repeatable: Y

Definition: Contains the textual or coded form for the language of the content of the resource.

Attributes:

type (required): this attributes takes the following values:

text

code

authority (required if applicable): this attribute is required when type=”code,” taking the value “iso639-2b”

<mods:scriptTerm>

Required: Y

Repeatable: N

Definition: Contains the script(s) of the resource

Attributes:

type (required): this attributes takes the following values:

text

code

authority (required if applicable): this attribute is required when type=”code,” taking values from ISO15924.

Examples

<mods:language>
  <mods:languageTerm type="text">French</mods:languageTerm>
  <mods:languageTerm type="code" authority="iso639-2b">fre</mods:languageTerm>
</language>

<!-- This resource is a Persian/English dictionary -->
<mods:language> 
  <mods:languageTerm type="code" authority="iso639-2b">per</mods:languageTerm>
  <mods:scriptTerm type="code" authority="iso15924">Arab</mods:scriptTerm>
</mods:language>

<mods:language> 
  <mods:languageTerm type="code" authority="iso639-2b">eng</mods:languageTerm>
  <mods:scriptTerm type="code" authority="iso15924">Latn</mods:scriptTerm>
</mods:language>

 

Physical Description

Submitted by Matthew Short on Fri, 11/11/2016 - 13:28
MODS Element Attributes Subelements
<mods:physicalDescription>

@type -- <mods:form>, <mods:note>

@authority -- <mods:form>

@unit -- <mods:extent>

<mods:form>

<mods:reformattingQuality>

<mods:internetMediaType>

<mods:extent>

<mods:digitalOrigin>

<mods:note>

Usage Guidelines

  1. At least one <physicalDescription> element, with one <digitalOrigin> and one <internetMediaType> are always required.        
  2. It is not necessary to include a full physical description of every version of a resource known to exist. Usually, it is sufficient to include one description of the digital form and one description of the analog form, if it varies significantly from the digital form.
  3. <reformattingQuality> takes only: access, preservation, and replacement.
  4. <internetMediaType> must take values from the MIME Media Types list, expressed in the format type/subtype format. Use multiple iterations of <internetMediaType> for resources that comprise multiple file types.
  5. Use RDA when determining the extent of a resource.
  6. Include RDA media, content, and carrier types in a series of <form> elements.
  7. <digitalOrigin> takes the following values:

born digital

reformatted digital

digitized microfilm

digitized other analog

  1. If a resource incorporates pre-existing analog content with new digital content, the <digitalOrigin> should be “born digital.”

Elements

<physicalDescription>

Required: Y

Repeatable: N

Definition: Describes the physical attributes of the information resource. <physicalDescription> is a wrapper element that contains all subelements relating to the physical description of the resource being described.

<form>

Required: R

Repeatable: N

Definition: A designation of a particular physical presentation of a resource, including the physical form or medium of material for a resource.

Attributes:

type: this attribute takes the following values:

content

media

carrier

authority (required if applicable): takes values from Genre/Form and Term Source Codes.

<reformattingQuality>

Required: N

Repeatable: N

MARC: 007/13

Definition: Indicates an overall assessment of the physical quality of an electronic resource in relation to its intended use.

<internetMediaType>

Required: Y

Repeatable: Y

MARC: 856 $q

Definition: An identification of the electronic format type, or the data representation of the resource.

<extent>

Required: R

Repeatable: Y

MARC: 300 $a, $b, $c, $e, 306 $a

Definition: A statement of the number and specific material of the units of the resource that express physical extent.

<digitalOrigin>

Required: Y

Repeatable: N

MARC: 007/11

Definition: The method by which a resource achieved digital form.

<note>

Required: R

Repeatable: Y

MARC: 340, 351, 500

Definition: General textual information about the physical description of a resource.

Examples

<!-- For a digitized photograph -->

<mods:physicalDescription>
  <mods:form authority="smd">photoprint</mods:form>
  <mods:form authority="marcform">electronic</mods:form>
  <mods:form authority="rdacontent" type="content">still image</mods:form>
  <mods:form authority="rdamedia" type="media">computer</mods:form>
  <mods:form authority="rdacarrier" type="carrier">online resource</mods:form>
  <mods:internetMediaType>image/jpeg</mods:internetMediaType>
  <mods:extent>1 photograph</mods:extent>
  <mods:digitalOrigin>reformatted digital</mods:digitalOrigin>
</mods:physicalDescription>

<!-- For a diary that has been imaged and for which a text transcription has been made-->

<mods:physicalDescription>
  <mods:form authority="marcform">electronic</mods:form>
  <mods:form authority="marcform">print</mods:form>
  <mods:internetMediaType>image/jpeg</mods:internetMediaType>
  <mods:internetMediaType>text/xml</mods:internetMediaType>
  <mods:extent>177 pages</mods:extent>
  <mods:digitalOrigin>reformatted digital</mods:digitalOrigin>
</mods:physicalDescription>

<!-- For a learning web site -->

<mods:physicalDescription>
  <mods:form authority="marcform">electronic</mods:form>
  <mods:internetMediaType>image/jpeg</mods:internetMediaType>
  <mods:internetMediaType>text/html</mods:internetMediaType>
  <mods:extent>5 digital files</mods:extent>
  <mods:digitalOrigin>born digital</mods:digitalOrigin>
</mods:physicalDescription>

 

Abstract

Submitted by Matthew Short on Fri, 11/11/2016 - 13:33
MODS Element Attributes Subelements
<mods:abstract> None None

Usage Guidelines

  1. Omit this element if a title adequately describes the content of the resource.
  2. However, this element is always required in collection-level records, and should be used to provide an overview of the scope, history, and provenance of the collection.

Elements

<mods:abstract>

Required: R

Repeatable: Y

MARC: 520

Definition: A summary of the content of the resource.

Examples

<mods:abstract displayLabel="Content description">Broadside advertising a funeral ceremony assassinated president Abraham Lincoln, held in Elgin, Illinois, on April 19, 1865. It details the route of the procession, the order of local official participants in the procession, and the order of service for the ceremony to be held in the Academy Hall.</mods:abstract>

<mods:abstract>Describes the results of an ongoing evaluation of State activity relating to improvement of criminal records. Activities reviewed include upgrading of accuracy and completeness of records, automation, implementation of positive identification procedures and procedures for responding to firearm background check inquiries. The report describes the nature of activities initiated, time until completion, and impact on availability of records. Characteristics of individual states are represented in some areas. The document was prepared by Queues Enforth Development under BJS award 95-RU-RX-K002. 2/00 NCJ 179768.</mods:abstract>

 

Table of Contents

Submitted by Matthew Short on Fri, 11/11/2016 - 14:40
MODS Element Attributes Subelements
<mods:tableOfContents> None None

Usage Guidelines

  1. If a more structured description is required, use <mods:relatedItem> with type=”constituent” instead.
  2. <mods:tableOfContents> may also be used as an empty element with an xlink:href attribute, allowing you to link to an external table of contents.
  3. DO NOT use structured content notes.

Elements

<mods:tableOfContents>

Required: R

Repeatable: N

MARC: 505

Definition: A description of the contents of a resource.

Examples

<mods:tableOfContents displayLabel="Partial Contents">Honey Boy – Hiawatha Song – Her Boy in Blue</mods:tableOfContents>

<mods:tableOfContents xlink:href="http://www.ojp.usdoj.gov/bjs/toc/cchrie98.htm"/>

 

Note

Submitted by Matthew Short on Fri, 11/11/2016 - 14:40
MODS Element Attributes Subelements
<mods:note> @type None

Usage Guidelines

  1. This element should be used sparingly. If a more specific MODS element would be more appropriate, always use the more specific element.
  2. Consult this list of common note terms from the Library of Congress. If you require an additional type, please contact the Metadata Librarian.
  3. The following types of notes are most common:
Type Label MARC
bibliography Bibliography 504
credits Credits 508
exhibitions Exhibition History 585
provenance Provenance 541, 561
statementOfResponsibility Responsibility 245 $c
titleSource Title Source 500

Elements

<mods:note>

Required: N

Repeatable: Y

MARC: 5XX, 245 $c

Definition: General textual information relating to a resource.

Attributes:

type (required): see above

displayLabel (optional): see above

Examples

<mods:note type=“credits”>Digital file includes a piano score composed and performed by Philip Carli.</mods:note>

<mods:note>Based on the play "I am a camera" by John Van Druten, and "Berlin stories" by Christopher Isherwood.</mods:note>

 

Subject

Submitted by Matthew Short on Fri, 11/11/2016 - 15:26
MODS Element Attributes Subelements
<mods:subject>

@authority

@authorityURI

@valueURI

@usage

<mods:topic>

<mods:geographic>

<mods:geographicCode>

<mods:temporal>

<mods:genre>

<mods:titleInfo>

<mods:name>

Usage Guidelines

  1. Use Library of Congress Subject Headings, which should be indicated by @authority=lcsh in <mods:subject>. Other controlled vocabularies, including local vocabularies, may be used at the discretion of the project manager and defined in the project’s data dictionary.
  2. Authority is specified at the <mods:subject> level, except in the case of <mods:geographic>, <mods:temporal>, <mods:titleInfo>, or <mods:name>.
  3. Always parse subject values into subelements. DO NOT place precoordinated subject headings into a single <mods:subject><mods:topic>string.
  4. If end users are more likely to be interested in the form or genre of the item, use <mods:genre>. If the object is about a particular form or genre, or if the form/genre is part of a precoordinated subject heading, use <mods:subject><mods:genre>.
  5. If specifying subjects from different authorities, use separate <mods:subject> elements for each.
  6. Dates in <mods:temporal> should be formatted according to W3CDTF, which should, in turn, be indicated in the encoding attribute. For more details about how to input dates, see the Date section above.
  7. If a geographic name is part of a corporate body (e.g. United States, Senate), it is coded as <mods:name>, not <mods:geographic>.
  8. All subelements of <mods:titleInfo>, <mods:name>, and <mods:genre> may be used.
  9. <mods:hierarchicalGeographic> and <mods:cartographics> are not in use at this time.

Elements

<mods:subject>

Required: Y

Repeatable: Y

Definition: A term or phrase representing the primary topic(s) on which a work is focused.

Attributes:

authority (required): this attributes accepts only two values, unless otherwise specified in the project’s data dictionary:

lcsh

local

<mods:topic>

Required: N

Repeatable: Y

MARC: 650, 653, 6XX $x and $v

Definition: Include here all terms that would not be more appropriate in <mods:geographic>, <mods:temporal>, <mods:titleInfo>, <mods:name>, or <mods:genre>.

<mods:geographic>

Required: N

Repeatable: Y

MARC: 651, 6XX $z

<mods:​geographicCode>

Required: N

Repeatable: Y

MARC: 043

Definition: A geographic area code associated with a resource.

Attributes:

authority (required): takes the following values:

marcgac

marccountry

iso3166

<mods:temporal>

Required: N

Repeatable: Y

MARC: 045, 6XX $y

Definition: Used for chronological subject terms or temporal coverage.

Attributes:

encoding (required): takes only “w3cdtf”

point (required if applicable): takes only “start” or “end”

<mods:titleInfo> Refer to the Title section of these guidelines

<mods:name> Refer to the Name section of these guidelines.

<mods:genre> Refer to the Genre section of these guidelines.

Examples

<!-- With parsed and repeated <mods:subject> values, with LCSH specified as the authority at the <mod:subject> level -->

<mod:subject authority="lcsh"> 
  <mod:topic>Railroads</mod:topic> 
  <mod:geographic>West (U.S.)</mod:geographic> 
  <mod:genre>Maps</mod:genre> 
</mod:subject>

<!-- Topical: With <topic> grouped with other <subject> subelements that use same authority, with LCSH and local specified separately as authority at the <subject> level -->

<mod:subject authority="lcsh"> 
  <mod:topic>Funeral rites and ceremonies</mod:topic> 
  <mod:geographic>Louisiana</mod:geographic> 
  <mod:geographic>New Orleans</mod:geographic>
</mod:subject> 

<mod:subject authority="local"> 
  <mod:topic>Jazz funerals</mod:topic>
</mod:subject> 

<!-- Temporal: With the encoding attribute used to indicate a single date in time -->

<mod:subject>
  <mod:temporal encoding="w3cdtf">1975-05-15</mod:temporal>
</mod:subject>

<!-- Temporal: With the encoding and point attributes used to indicate a date range -->

<mod:subject>
  <mod:temporal encoding="w3cdtf" point="start">2001-09-11</mod:temporal> 
  <mod:temporal encoding="w3cdtf" point="end">2003-03-19</mod:temporal>
</mod:subject>

<!-- Title: With name and topical subelement -->

<mod:subject authority="lcsh">
  <mod:name type="personal" authority="naf">
    <mod:namePart>Woolf, Virginia</mod:namePart>
    <mod:namePart type=”date”>1882-1941</mod:namePart> 
  </mod:name> 
  <mod:titleInfo> 
    <mod:title>Three Guineas</mod:title> 
  </mod:titleInfo>
  <mod:topic>Criticism and interpretation</mod:topic>
</mod:subject>

<!-- Genre --> 

<mod:subject authority=”lcsh”>
  <mod:name type=”personal” authority=”naf”>
    <mod:namePart>Edmondston, Catherine Devereux</mod:namePart>
    <mod:namePart type=”date”>1823-1875</mod:namePart> 
  </mod:name> 
  <mod:genre>Diaries</mod:genre>
</mod:subject>

 

Related Item

Submitted by Matthew Short on Fri, 11/11/2016 - 15:50
MODS Element Attributes Subelements
<mods:relatedItem> @type All MODS elements

Usage Guidelines

  1. One <mods:relatedItem type=”host”>, with a title and link, is required in every record to identify the collection.
  2. Any MODS element may be used as a subelement of <mods:relatedItem>, except nested <mods:relatedItem> elements.
  3. <mods:relatedItem> may be used:
    • If you need to point to a record for a related item, using xlink and an empty element.
    • If you need to provide contextual information, such as a description of a series or version.
    • If you need to provide specific and detailed information about constituent parts, like the tracks on a CD.
  4. The analog version of a digital surrogate should be described in the main record.
  5. <mods:tableOfContents> is preferred over <mods:relatedItem>, unless more information is needed about constituent parts.

Elements

<mods:relatedItem>

Required: N

Repeatable: Y

MARC: 7XX, 490, 8XX, 510

Definition: Information that identifies other resources related to the one being described.

Attributes:

type (required): This attribute describes the relationship between the related item and the parent MODS record. It accepts the following values:

host

constituent

series

isReferencedBy

xlink:href (recommended if applicable): Used to link to external resources, taking a URL

display label (optional)

Examples

<!-- Linking -->

<mods:relatedItem displayLabel="Preceding Title" type="preceding" xlink:href="http://hdl.loc.gov/umich.dli.moa/AGE3371"/>

<mods:relatedItem xlink:href="info:lccn/85000002" />

<!-- Context -->

<mods:relatedItem displayLabel="Appears in" type="host">
  <mods:titleInfo>
    <mods:title>Post-Fordism</mods:title>
    <mods:subTitle>a reader</mods:subTitle>
   </mods:titleInfo>
  <mods:name type="personal" authority="naf"> 
    <mods:namePart type="given">Ash</mods:namePart>
    <mods:namePart type="family">Amin</mods:namePart> 
    <mods:role>
      <mods:roleTerm type="text">editor</mods:roleTerm>
     </mods:role> 
  </mods:name>
  <mods:originInfo>
    <mods:dateIssued>1994</mods:dateIssued> 
    <mods:publisher>Blackwell Publishers</mods:publisher> 
    <mods:place>
      <mods:placeTerm type="text">Oxford</mods:placeTerm> 
    </mods:place>
  </mods:originInfo>
  <mods:part>
    <mods:extent unit="page">
      <mods:start>23</mods:start>
      <mods:end>45</mods:end> 
    </mods:extent> 
  </mods:part>
</mods:relatedItem>

<!-- Constituent parts -->

<mods:relatedItem type="constituent" ID="DMD_disc01_tr001">
  <mods:titleInfo type="uniform" authority="naf">
    <mods:title>Chaconne von Vitali</mods:title> 
  </mods:titleInfo> 
  <mods:titleInfo>
    <mods:title>Chaconne</mods:title> 
  </mods:titleInfo> 
  <mods:name type="personal" authority="naf"> 
    <mods:namePart>Vitali, Tomaso Antonio</mods:namePart>
     <mods:namePart type="date">1663-1745</mods:namePart>
     <mods:role>
       <mods:roleTerm authority="marcrelator" type="text">composer</mods:roleTerm>
     </mods:role>
  </mods:name> 
  <mods:name type="personal" authority="naf"> 
    <mods:namePart>Blatt, Josef</mods:namePart>
    <mods:role>
      <mods:roleTerm authority="marcrelator" type="text">performer</mods:roleTerm> 
    </mods:role>
  </mods:name> 
  <mods:physicalDescription>
    <mods:extent>9:55</mods:extent> 
  </mods:physicalDescription> 
  <mods:note type="Standard Restriction">This item is unavailable due to copyright restrictions.</mods:note> 
  <mods:note type="performers">Nathan Milstein, violin ; Josef Blatt, piano.</mods:note> 
  <mods:note type="statement of responsibility">Tomaso Vitali</mods:note>
  <mods:note>Originally for violin and continuo; arr. for violin and piano.</mods:note>
  <mods:note>Attributed to Tomaso Vitali, but most likely not by him.</mods:note> 
  <mods:subject authority="lcsh"> 
    <mods:topic>Chaconnes (Violin and piano), Arranged.</mods:topic> 
  </mods:subject>
</mods:relatedItem>

 

Identifier

Submitted by Matthew Short on Fri, 11/11/2016 - 15:54
MODS Element Attributes Subelements
<mods:identifer> @type None

Usage Guidelines

  1. Every MODS records should include at least one <mods:identifier><mods:type> element.
  2. For digital objects, the identifier is the Fedora PID.
  3. For analog resources, the <mods:identifier> is typically the ISBN or ISSN. However, in some cases a local control number, like a classification number or an accession number, may be assigned instead.
  4. It is not necessary to assign an identifier to an analog resource, but it is recommended.

Elements

<mdos:identifier>

Required: Y

Repeatable: Y

MARC: 010, 020, 022, 024, 856

Definition: Contains a unique standard number or code that distinctively identifies a resource.

Attributes:

type (required): The values for this attribute are not controlled, but common examples include:

pid

isbn

issn

lccn

local

Examples

<mods:identifier type="pid">niu-lincoln:30924</mods:identifier>

<mods:identifier type="lccn">00694010</mods:identifier>

 

Location

Submitted by Matthew Short on Fri, 11/11/2016 - 16:01
MODS Element Attributes Subelements
<mods:location>

@type -- <mods:physicalLocation>

@authority -- <mods:physicalLocation>

@access -- <mods:url>

@usage -- <mods:url>

<mods:physicalLocation>

<mods:url>

<mods:holdingSimple>

<mods:copyInformation>

<mods:subLocation>

<mods:shelfLocator>

Usage Guidelines

  1. The MODS record must include one <mods:location><mods:url> with usage=”primary display” or usage=”object in context”. This element may not be repeated. Best practice is to link to a page that includes BOTH the resource and the metadata display.
  2. This element is used to record the URL of the object in the digital collection, but it may also be used to record holding information for the analog resource.
  3. When recording the physical location of an analog resource, include a text instance (type=”text”) and a coded instance (type=”code”). The coded instance must include the OCLC organization code, which will typically be “JNA.”
  4. If the record describes a multi-part resource, like a set, choose one primary entry point.
  5. This element is NOT used to indicate the physical location of files.

Elements

<mods:location>

Required: Y

Repeatable: Y

Definition: identifies the institution or repository holding the resource, or a remote location in the form of a URL where it is available. <mods:location> is a wrapper for <mods:physicalLocation>, <mods:url>, and <mods:holdingSimple>.

<mods:physicalLocation>

Required: N

Repeatable: Y

MARC: 852 $a

Definition: the institution or repository that holds the resource or where it is available

<mods:url>

Required: Y

Repeatable: N

Definition: the Uniform Resource Location of the resource.

Attributes:

primary display (required)

access (recommended): this attributes takes the following values:

raw object

object in context

<mods:holdingSimple>

Required: N

Repeatable: N

Definition: General information about what the institution identified in <mods:physicalLocation> holds of the resource and its specific location

<mods:copyInformation>

Required: N

Repeatable: N

Definition: Information about a specific tangible instance of a bibliographic resource or set which comprises one or more pieces via indication of sublocation and/or locator.

<mods:subLocation>

Required: N

Repeatable: N

MARC: 852 $b

Definition: Department, division or section of an institution holding a copy of the resource.

<mods:shelfLocator>

Required: N

Repeatable: N

MARC: 852 $h

Definition: Shelfmark or other shelving designation that indicates the location identifier for a copy.

Examples

<mods:location> 
  <mods:url usage="primary display" access="object in context"> http://lincoln-dev.lib.niu.edu/fedora/repository/niu-lincoln%3A30922</mods:url>
</mods:location>

<mods:location>
  <mods:physicalLocation type="text">Founders Memorial Library. Donn V. Hart South East Asian Collection. 
  </mods:physicalLocation>
  <mods:physicalLocation type="code" authority="marcorg">JNA</mods:physicalLocation>
  <mods:holdingSimple>
    <mods:copyInformation>
      <mods:subLocation>fmlspx</mods:subLocation>
      <mods:shelfLocator>PL3957.H684 1825</mods:shelfLocator>
    </mods:copyInformation>
  </mods:holdingSimple>
  <mods:url usage="primary display" access="object in context">http://sea.lib.niu.edu/fedora/repository/SEAImages:houghcollection/-/An%20English%20and%20Burman%20vocabulary</mods:url>
</mods:location>

 

Access Condition

Submitted by Matthew Short on Fri, 11/11/2016 - 16:04
MODS Element Attributes Subelements
<mods:accessCondition>

@type

 None

Usage Guidelines

  1. Every MODS record must include one <mods:accessCondition> element with the attribute type=”useAndReproduction.”

​Elements

<mods:accessCondition>

Required: Y

Repeatable: N

MARC: 506 (restrictions), 540 (use)

Definition: information about restrictions imposed on access to a resource

Attributes:

type (required): This attribute takes the following values:

use and reproduction

restriction on access

Record Info

Submitted by Matthew Short on Fri, 11/11/2016 - 16:09
MODS Element Attributes Subelements
<mods:recordInfo>

@authority -- <mods:recordContentSource>, <mods:languageTerm>

@type -- <mods:languageTerm>

<mods:recordIdentifier>

<mods:recordContentSource>

<mods:recordOrigin>

<mods:languageOfCataloging>

<mods:languageTerm>

Usage Guidelines

  1. Every MODS record requires one <mods:languageTerm authority="iso639-2b" type="code">eng</mods:languageTerm>.
  2. The source of the record is always our OCLC organization identifier: <mods:recordContentSource authority=”oclcorg”>JNA</mods:recordContentSource>
  3. Use the URL that points to the MODS record in the Fedora repository for <mods:recordIdentifier>.

Elements

<mods:recordInfo>

Required: Y

Repeatable: N

Definition: Information about the metadata record. <mods:recordInfo> is a wrapper for <mods:recordIdentifier>, <mods:recordContentSource>, and <mods:languageOfCataloging>.

<mods:recordIdentifier>

Required: Y

Repeatable: N

MARC: 001

Definition: Contains the system control number assigned by the organization creating, using, or distributing the record.

<mods:recordContentSource>

Required: Y

Repeatable: N

MARC: 040

Definition: The code or name of the organization that either created or modified the original record.

Attributes:

authority (required): Always “oclcorg”

<mods:recordOrigin>

Required: R

Repeatable: N

Definition: Shows the origin or provenance of the MODS record.

<mods:languageOfCataloging>

Required: Y

Repeatable: N

MARC: 040 $b

Definition: The language of the text of the cataloging in the MODS record.

<mods:languageTerm>

Required: Y

Repeatable: N

Definition: Contains the language(s) of the metadata record.

Attributes:

authority (required): Always “iso639-2b”

type (required): Always “code”

Examples

<mods:recordInfo>
  <mods:recordContentSource>JNA</mods:recordContentSource>
  <mods:recordIdentifier>http://prairiefire.lib.niu.edu/fedora/repository/niu-prairie%3A1631/MODS/MODS </mods:recordIdentifier>
  <mods:languageOfCataloging>
    <mods:languageTerm authority="iso639-2b" type="code">eng</mods:languageTerm>
  </mods:languageOfCataloging>
</mods:recordInfo>