MODS User Guidelines
Version 2.0

Detailed Description of MODS Elements

<titleInfo>

"titleInfo" is a wrapper element that contains all subelements related to title information. Data content is contained in subelements. <titleInfo> is repeated for each type attribute value. If multiple titles are recorded, repeat <titleInfo><title> for each. The language of the title may be indicated if desired using the xml:lang (RFC3066) or lang (3-character ISO 639-2 code) attributes.

Attributes

• type - This attribute is applied when it is necessary to identify what type of title is recorded. For the main title (MARC 21 field 245), no type is indicated. The following values may be used with the type attribute:
  • abbreviated (equivalent to MARC 21 field 210)
  • translated (equivalent to MARC 21 field 242, 246)
  • alternative (equivalent to MARC 21 fields 246, 740)
  • uniform (equivalent to MARC 21 fields 130, 240, 730)
• authority - The name of the authoritative list for a controlled value is recorded here. An authority attribute may be used to indicate that a title is controlled by a record in an authority file (e.g. authority="naf"). A list of authority files is maintained at: www.loc.gov/marc/sourcecode/authorityfile/authorityfilesource.html.
• displayLabel - This attribute is intended to be used when additional text associated with the title is needed for display. It is equivalent to MARC 21 field 246 subfield $i.
• xlink - See the Attributes used throughout the schema for description.
• ID - See the Attributes used throughout the schema for description.
• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

The following subelements are defined for "titleInfo." They are enumerated below.

<titleInfo>
	<title>
	"title" without the <titleInfo> type attribute is roughly equivalent to MARC 21 field 245, except that it does not include the entire title area dictated by AACR2. The statement of responsibility in MARC 21 field 245 is included in the <note> element with type="statement of responsibility," not in <title>. Elements considered part of the title that are separately subfielded in MARC 21 are included here unless they have a separate subelement. For instance, the General Material Designator (MARC 21 field 245 subfield $h) and form (MARC 21 field 245 subfield $k) may be included as part of the title, but a part name or number is included in the subelements below. When there is a subtitle, additional elements should follow the subelement for which it is appropriate (e.g., a part name or number may follow the title or the subtitle depending upon the situation). Dates may be recorded here only if considered part of the title (e.g., a date in a uniform title). (Publication dates are included under <originInfo>.) For parallel titles (i.e., equivalent titles in different languages), use separate <titleInfo><title> elements with type attribute="translated" for each parallel title. For non-collective titles by the same author (i.e. separate titles with no inclusive title for the collection), use separate <titleInfo><title> elements with no type attribute.

<titleInfo>
	<subTitle>
	"subTitle" includes a subtitle when it is desired to include it as a separate element. Alternatively, it may be included as part of a title. It is equivalent to MARC 21 fields 242, 245, 246 subfield $b.

<titleInfo>
	<partNumber>
	"partNumber" is used for a part or section number of a title. This is equivalent to MARC 21 fields 130, 240, 242, 243, 245, 246, 247, 730, 740 subfield $n.

<titleInfo>
	<partName>
	"partName" is used for a part or section name of a title. This is equivalent to MARC 21 fields 130,240, 242, 243, 245, 246, 247, 730, 740 subfield $p.

<titleInfo>
	<nonSort>
	"nonSort" begin and end tags surround the nonfiling text which should not be regarded in sorting. It is equivalent to the new technique in MARC 21 that uses control characters to surround data disregarded for sorting. It is used for the same purpose as the nonfiling indicator value that indicates the number of characters disregarded for sorting. Punctuation may or may not be included within the non-sort value depending upon whether it is part of the sorting or non-sorting data.

Examples

<titleInfo>
	<nonSort>The</nonSort>
	<title>"winter mind"</title>
	<subtitle>William Bonk and American letters</subtitle>
</titleInfo>

<titleInfo>
	<title>Oklahoma [sound recording]</title>
</titleInfo>
<titleInfo>
	<title>Carousel</title>
</titleInfo>
<titleInfo>
	<title>South Pacific</title>
</titleInfo>

<titleInfo xml:lang="en">
	<nonSort>The</nonSort>
	<title>man who would be king</title>
</titleInfo>
<titleInfo xml:lang="fr" type="translated">
	<nonSort>L'</nonSort>
	<title>homme qui voulut être roi</title>
</titleInfo>

<titleInfo>
	<title>Focus on grammar </title>
	<subTitle>basic level</subTitle>
</titleInfo>

<titleInfo>
	<title>Zentralblatt für Bakteriologie, Parasitenkunde, Infektionkrankheiten und Hygiene</title>
	<partNumber>1. Abt. Originale</partNumber>
	<partNumber>Reihe B</partNumber>
	<partName>Hygiene. Krankenhaushygiene. Betriebshygiene, präventive Medizin</partName>
</titleInfo>

<titleInfo>
	<title>Annual report of notifiable diseases</title>
</titleInfo>
<titleInfo type="abbreviated">
	<title>Annu. rep. notif. dis.</title>
</titleInfo>

<titleInfo lang="rus" script="Latn" transliteration="Code to be determined ">
	<title>Geodezja i urzadzenia roline.</title>
</titleInfo>
<titleInfo type="translated" lang="eng">
	<title>Land surveying and agriculture equipment</title>
</titleInfo>

<titleInfo type="uniform" authority="naf" xlink:href="http://www.loc.gov/sru-lccn/?query=n 93028706">
	<title>Missale Carnotense</title>
</titleInfo>
	[Note: the value of xlink:href is purely illustrative; this link does not currently exist. It assumes establishing a namespace for Library of Congress Control Numbers (LCCN) and initiating a service to retrieve authority records.]

<titleInfo type="alternative" displayLabel="Spine title">
	<title>Science and public affairs</title>
</titleInfo>

<name>

"name" is a wrapper element for names associated with the resource. It is equivalent to the MARC 21 1XX and 7XX fields or Creator and Contributor in Dublin Core. If it is desired to indicate the concept of main entry, the <role> subelement may be used with the value "creator" (e.g. <role>creator</role>. The type of name (personal, corporate, conference) may be indicated, although this is not required.

Attributes

• type - This attribute indicates the type of name. The following values may be used with it:
  • personal
  • corporate
  • conference
• authority - The name of the authoritative list for a controlled value is recorded here. An authority attribute may be used to indicate that a name is controlled by a record in an authority file (e.g., authority="naf"). A list of authorities is maintained at: www.loc.gov/marc/sourcecode/authorityfile/authorityfilesource.html.
• xlink - See the Attributes used throughout the schema for description.
• ID - See the Attributes used throughout the schema for description.
• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

The following subelements are defined for <name>. They are enumerated below.

<name>
	<namePart>
	"namePart" includes each part of the name that is parsed. Parsing is used to indicate a date associated with the name, to parse the parts of a corporate name (MARC 21 fields X10 subfields $a and $b), or to parse parts of a personal name if desired (into family and given name). The latter is not done in MARC 21. Names are expected to be in a structured form (e.g. surname, forename).
	Attribute type - The following values may be used with the type attribute: date family given The attribute date is used to parse dates that are not integral parts of a name. Dates that are part of a name, e.g. dates within a conference name, do not use this attribute to separate the date, since it is an integral part of the name string. The birthdate associated with a personal name, however, is not an integral part of the name but added to distinguish the name from others, so it does include a separate namePart with type="date". This attribute is not used when parsing the components of a corporate name. Note that "family" and "given" are not used in MARC 21.

<name>
	<displayForm>
	"displayForm" is used to indicate the unstructured form of the name. It includes a name as given on the resource. For some applications, contractual agreements require that the form of the name provided on the resource be provided. This data is usually carried in MARC 21 field 245 subfield $c, although the latter may include other information in addition to the display form of the name. If part of an entire statement of responsibility, it may be indicated in a note (with type="statement of responsibility") along with any other text in the statement of responsibility and also repeated here if desired.

<name>
	<affiliation>
	"affiliation" contains the name of an organization, institution, etc. with which the entity recorded in <name> was associated at the time that the resource was created. It may also contain other elements that are part of the affiliation, such as email address, street address, job title, etc.

<name>
	<role>
	"role" is a wrapper element with two subelements that may contain a value in coded or textual form. It is used to indicate the relationship (role) of the entity recorded in name in relation to the resource. <role> is equivalent to a MARC relator code or its textual form.
	Subelements <code> "code" contains the coded form of a relator/role. An authority must be indicated if using a coded form for role.
		Attribute authority - The name of the authoritative list for a controlled value is recorded here. A list of codes for authorities is maintained at: www.loc.gov/marc/sourcecode/relator/relatorsource.html. To indicate the MARC relators list, use authority= "marcrelator."
	<text> "text" contains the textual form of a relator/role. If the textual form is from a controlled list (e.g. the MARC relators list), an authority attribute may be indicated (but is not mandatory).
		Attribute authority - The name of the authoritative list for a controlled value is recorded here. A list of authorities is maintained at: www.loc.gov/marc/sourcecode/relator/relatorsource.html. To indicate the MARC relators list, use authority="marcrelator."

<name>
	<description>
	"description" may be used to give a textual description for a name when necessary, for example, to distinguish from other names. This element does not have a MARC 21 equivalent.

Examples

<name type="personal">
	<namePart>Brown, B. F.</namePart>
	<affiliation>Chemistry Dept., American University</affiliation>
</name>

<name>
	<namePart>Abrams, Michael</namePart>
	<description>American artist, 20th c.</description>
</name>

<name type="personal">
	<namePart>Alterman, Eric</namePart>
	<displayForm>Eric Alterman</displayForm>
	<role>
		<text>creator</text>
	</role>
</name>

<name type="personal">
	<namePart type="given">John</namePart>
	<namePart type="family">Huston</namePart>
	<role authority="marcrelator">
		<code>drt</code>
		<text>director</text>
	</role>
</name>

<name type="personal">
	<namePart type="given">John Paul II, Pope</namePart>
	<namePart type="date">1920-</namePart>
</name>

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

<name type="personal">
	<namePart type="given">Jack</namePart>
	<namePart type="family">May</namePart>
	<namePart>I</namePart>
	<description lang="eng">District Commissioner</description>
	<description lang="fre">Préfet de région</description>
</name>

<name type="corporate">
	<namePart>United States</namePart>
	<namePart>Court of Appeals (2nd Circuit)</namePart>
</name>

<name type="conference">
	<namePart>Paris Peace Conference (1919-1920)</namePart>
</name>

<name type="personal" authority="naf">
	<namePart>Woolf, Virginia</namePart>
	<namePart type="date">1882-1941</namePart>
</name>

<typeOfResource>

"typeOfResource" is generally equivalent to the type of record codes in MARC 21 Leader/06 in that it differentiates the resource being described as to content type. A controlled list of textual values are used. Attributes are used to further indicate whether the resource is a collection (i.e. an aggregation of items, designated in MARC 21 in Leader/07 Bibliographic level) or manuscript in nature (designated in MARC 21 as a separate Leader/06 code that combines the manuscript property with a resource type). This element includes a high-level type that categorizes the material in a general way. More specific typing is done in the <genre> element. The attributes "collection" and "manuscript" are associated with a specific value used in <typeOfResource>. For example, a MODS object which consists of a collection of maps with associated text would be represented by two instances of <typeOfResource>. The first would be "cartographic" with attribute collection="yes," and the second would be "text" (with no attribute).

Attributes

• collection - This attribute is used as collection="yes" when the resource is a collection (falling under the definition of Leader/07 code "c": A made-up multipart group of items that were not originally published, distributed, or produced together.). It may also be applied to electronic resources that are collections in the sense of a made-up multipart group of items.
• manuscript - This attribute is used as manuscript="yes" when the resource is written in handwriting or typescript. MARC 21 Leader/06 values "d", "f" and "t" designate manuscript items (combined with other type of resource information).

Values

The following values may be used with <typeOfResource>:

• text (for "language material"; includes MARC 21 values "a" and "t").
• cartographic (includes MARC 21 values "e" and "f").
• notated music (includes MARC 21 values "c" and "d").
• sound recording (includes MARC 21 values "i" and "j") - This value does not distinguish between non-musical and musical sound recordings. The MODS to MARC mapping suggests that sound recording would be converted to "j" (musical sound recording). If desired, an uncontrolled term such as "nonmusical sound recording" may be used in <genre> to bring out this aspect.
• still image (includes MARC 21 value "k") - Note that value "k" in MARC 21 is defined as "Two-dimensional nonprojectible graphic" so that this is not an exact equivalent. Slides and transparencies are also considered still images in MODS, although in MARC 21 they are coded as code "g" (projected medium).
• moving image (includes MARC 21 value "g") - Note that value "g" in MARC 21 is defined as "Projected medium," so this is not an exact equivalent. It includes motion pictures and videorecordings, as well as television programs, digital video and animated computer graphics, but not slides and transparencies. It does not include moving images that are primarily computer programs, such as computer games or computer-oriented multimedia (these are included in "software, multimedia").
• three dimensional object (includes MARC 21 value "r").
• software, multimedia (includes MARC 21 value "m") - This value is appropriate for any electronic resource without a significant aspect that indicates on of the other <typeOfResource> categories. It includes: software, numeric data, computer-oriented multimedia and online systems and services.
• mixed material (includes MARC 21 value "p") - This value uses the same definitions as value "p" (It indicates that there are significant materials in two or more forms that are usually related by virtue of their having been accumulated by or about a person or body. Mixed material includes archival fonds and manuscript collections of mixed forms of materials, such as text, photographs, and sound recordings.)

Subelements

There are no subelements defined for <typeOfResource>.

Examples

<titleInfo>
	<title>Portals to the world</title>
	<partName>Selected Internet resources</partName>
	<partName>Andorra [electronic resource]</partName>
</titleInfo>
<typeOfResource collection="yes">text</typeOfResource>

<titleInfo>
	<title>Camp Council meeting; speech by Dewey Rodgers</title>
</titleInfo>
<typeOfResource>sound recording</typeOfResource>
<genre authority="marcgt">speech</genre>

<titleInfo>
	<title>[Portrait of Django Reinhardt, Aquarium, New York, N.Y., ca. Nov. 1946] [graphic]</title>
</titleInfo>
<typeOfResource>still image</typeOfResource>

<titleInfo>
	<nonSort>The</nonSort>
	<title>battle-cry of freedom</title>
</titleInfo>
<typeOfResource>notated music</typeOfResource>
<genre>sheet music</genre>

<titleInfo>
	<title> Collection relating to A. E.Housman</title>
</titleInfo>
<typeOfResource manuscript="yes" collection="yes">mixed material</typeOfResource>
<abstract>Correspondence, manuscripts, typescripts, galley and page proofs, newspaper clippings, printed material, monographs, and musical scores pertaining primarily to Richards's biography of A. E. Housman titled Housman, 1896-1936 (1941) </abstract>

<titleInfo><title>Fifty years of Coca-Cola advertising </titleInfo></title>

<typeOfResource>moving image</typeOfResource>

<genre>motion picture</genre>

<titleInfo>
	<title>Cannon ball</title>
</titleInfo>
<typeOfResource>three dimensional object</typeOfResource>

<titleInfo>
	<title>Google</title>
</titleInfo>
<typeOfResource>software, multimedia</typeOfResource>
<genre authority="marcgt">online system or service</genre>
<genre>search engine</genre>

<genre>

"genre" contains a category that characterizes a particular style, form, or content, such as artistic, musical, literary composition, etc. Terms used in this element give more specificity than the broad terms used in <typeOfResource>. The terms may be from a controlled list with a designation of the authoritative list used in the authority attribute, or it may be an uncontrolled term. If no authority is specified, it is assumed that the term is uncontrolled.

Attributes

• authority - The name of the authoritative list for a controlled value is recorded here. Genre terms that appear in various coded elements in MARC 21 are included in the MARC 21 genre terms list at: www.loc.gov/marc/sourcecode/genre/genresource.html, designated as authority="marcgt." Other lists may be used with the designation of the source from the MARC 21 genre source code list at: www.loc.gov/marc/sourcecode/genre/genrelist.html.
• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

There are no subelements defined for <genre>.

Examples

<genre authority="rbgenr">Hymnals–Germany</genre>

<genre authority="marcgt">folktale</genre>

<genre>rock music</genre>

<originInfo>

"originInfo" is a wrapper element that contains all subelements related to publication and origination information. It includes place of origin or publication, publisher/originator, all dates associated with the resource, and issuance information. Data is only input within each subelement.

Attributes

• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

The following subelements are defined for <originInfo>. They are enumerated below.

<originInfo>
	<place>
	"place" is a wrapper element for place <code> and place <text> (if both are included ) to indicate place of publication/origin.
	Subelements <code> "code" is used to express place in a coded form. Attribute: authority - This attribute may be used with the following values: marc - This value is used with the MARC country codes (as used in 008/15-17). A listing of the MARC country codes is online at: www.loc.gov/marc/countries/ iso3166 - This value is used with country codes from ISO 3166. A listing of the ISO 3166 country codes is online at: www.din.de/gremien/nas/nabd/iso3166ma <text> "text" is used to express place in a textual form (may be place of publication as expressed in MARC 21 field 260 subfield $a.

<originInfo>

<publisher> "publisher" includes the name of a publisher/originator or statement about publication/origin. It is equivalent to MARC 21 field 260 subfield $b.

Dates
Note that there is no wrapper element for dates.

<originInfo>

<dateIssued> "dateIssued" is used for the publication or issued date (equivalent to dates in MARC 21 field 260 subfield $c. It may be in textual or structured form. <dateIssued> may be recorded according to the MARC 21 rules for field 008/07-14 with encoding="marc." Attributes encoding - See the Attributes used throughout the schema for description. point - See the Attributes used throughout the schema for description. keyDate - See the Attributes used throughout the schema for description.

<originInfo>

<dateCreated> "dateCreated" contains the date of creation of the resource. It may be in textual or structured form. This type of date is recorded in various places in MARC 21: field 260 subfield $g, for some types of material in field 260 subfield $c, date of original in field 534 subfield $c and date of reproduction in field 533 subfield $d. If creation date is also the origination date as used in MARC 21 field 260 subfield $c, use the <dateIssued> element or repeat both <dateCreated and <dateIssued>. Attributes encoding - See the Attributes used throughout the schema for description. point - See the Attributes used throughout the schema for description. keyDate - See the Attributes used throughout the schema for description.

<originInfo>

<dateCaptured> "dateCaptured" contains the date on which the resource was digitized or a subsequent snapshot was taken. This is particularly useful for Web resources because of their changeability. This could be a date that the resource was captured or could also be the date of creation. Attributes encoding - See the Attributes used throughout the schema for description. point - See the Attributes used throughout the schema for description. keyDate - See the Attributes used throughout the schema for description.

<originInfo>

<dateOther> "dateOther" contains a generic date element that does not fall into another category but is important to record. Attributes encoding - See the Attributes used throughout the schema for description. point - See the Attributes used throughout the schema for description. keyDate - See the Attributes used throughout the schema for description.

<originInfo>

<edition> "edition" contains information relating to the edition or version of the resource. It is equivalent to MARC 21 field 250.

<originInfo>

<issuance> "issuance" designates how the resource is issued. It is equivalent to those values in MARC 21 Leader/07 that designate issuance characteristics. "Collection, which designates an aggregation level is included in the collection attribute in the <typeOfResource> element. <issuance> may be used with the following values: continuing - A resource that is issued over time with no predetermined conclusion. Continuing resources include serials and ongoing integrating resources, i.e. those that are continuously updated. The value is equivalent to codes "b," "i" and "s" in Leader/07. monographic - A resource that is either complete in one part or intended to be completed in a finite number of separate parts. The value is equivalent to codes "a," "c," "d" and "m" in Leader/07.

<originInfo>

<frequency> "frequency" contains a statement of publication frequency in a textual form.

Examples

<originInfo>
	<dateCaptured encoding="iso8601">20010712</dateCaptured>
	<issuance>continuing</issuance>
</originInfo>

<originInfo>
	<place>
		<text>Milan</text>
	</place>
	<publisher>F. Lucca</publisher>
	<place>
		<text>Florence</text>
	</place>
	<publisher>Ducci</publisher>
	<place>
		<text>Chiasso</text>
	</place>
	<publisher>Euterpe Ticinese</publisher>
	<place>
		<text>Naples</text>
	</place>
	<publisher>Girard et C.</publisher>
	<dateIssued>between 1856 and 1862</dateIssued>
	<dateIssued encoding="marc" point="start">1856</dateIssued>
	<dateIssued encoding="marc" point="end">1862</dateIssued>
	<issuance>monographic</issuance>
</originInfo>

<originInfo>
	<place>
		<code authority="marc">nyu</code>
		<text>New York</text>
	</place>
	<publisher>Published for the American Vacuum Society by the American Institute of Physics</publisher>
	<dateIssued>1994</dateIssued>
	<issuance>monographic</issuance>
</originInfo>

<originInfo>
	<dateCreated encoding="iso8601" keyDate="yes">1975-10-08</dateCreated>
</originInfo>

<originInfo>
	<place>
		<code authority="iso3166">usa</code>
		<text>United States</text>
	</place>
	<dateIssued>1975</dateIssued>
</originInfo>

<originInfo>
	<place>
		<code authority="marc">dcu</code>
		<text>[Washington, D.C</text>
	</place>
	<publisher>Library of Congress</publisher>
	<dateIssued>1998-]</dateIssued>
	<dateIssued encoding="marc" point="start">1998</dateIssued>
	<dateIssued encoding="marc" point="end">9999</dateIssued>
	<issuance>monographic</issuance>
</originInfo>

<originInfo>
	<place>
		<code authority="marc">cau</code>
		<text>Menlo Park, CA</text>
	</place>
	<publisher>Center for Computer Assisted Research in the Humanities</publisher>
	<dateIssued>-1988</dateIssued>
	<dateIssued encoding="marc" point="start">1985</dateIssued>
	<dateIssued encoding="marc" point="end">1988</dateIssued>
	<issuance>continuing</issuance>
	<frequency>annual</frequency>
</originInfo>

<originInfo>
	<dateOther point="start">20011008</dateOther>
	<dateOther point="end">20011027</dateOther>
</originInfo>

<language>

"language" contains the language(s) of the resource as a whole. Its content may be textual or may be from a controlled list with the list identified as a value of the authority attribute or may be textual. If no authority is given, it is assumed that the content is textual. (Alternatively, instead of using a textual form, the content may be in coded form with an authority attribute, and an XSLT stylesheet may be used to translate the code into a textual form.) If there is more than one language, <language> is repeated. Language can also be expressed in conjunction with each element in a MODS encoding by means of the xml:lang and/or lang attributes; see section on language for more information. <languageOfCataloging> under <recordInfo> is used to give the language of the metadata in the record as a whole. This element is equivalent to coded data in MARC 008/35-37 (which assumes iso639-2/b) and field 041 (all subfields).

Attribute

• authority - This attribute may contain the following values:
  • iso639-2b - A bibliographic language code from ISO 639-2 (Codes for the representation of names of languages: alpha-3 code). The bibliographic language codes are identical to both NISO Z39.53 and the MARC Code List for Languages.
  • rfc3066 - A language identifier as specified by the Internet Best Current Practice specification RFC3066. This value includes an ISO 639-1 (alpha-2) or ISO 639-2 (alpha-3) language code with optional secondary subtags.

There are no subelements defined for <language>.

Examples

<language authority="iso639-2b">fre</language>
	[An XSLT stylesheet could be applied to transform this code to: ] Language: French

<language>Italian</language>

<language authority="iso639-2b">eng</language>
<language authority="iso639-2b">fre</language>
	[The resource contains both English and French text]

<physicalDescription>

"physicalDescription" is a wrapper element that contains all subelements relating to physical description information of the resource described. Data is only input within each subelement.

Attributes

• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

The following subelements are defined for <physicalDescription>. They are enumerated below.

<physicalDescription>

<form> "form" includes information that specifies the physical form or medium of material for a resource. Either a controlled list of values or free text may be used. Attribute authority - The name of the authoritative list for a controlled value is recorded here. A list of authorities is maintained at: www.loc.gov/marc/sourcecode/form/formsource.html. The MARC 21 form list contains most of the values defined in fields 008/23 (BK, MU, CR, MX) and 008/29 (MP, VM). Use authority="marcform" to indicate its use.

<physicalDescription>

<reformattingQuality> "reformattingQuality" includes an overall assessment of the physical quality of an electronic resource in relation to its intended use. It is roughly equivalent to MARC 21 field 007/13 (ER). The following values may be used: access - The electronic resource is intended to support current electronic access to the original item (i.e., reference use), but is not sufficient to serve as a preservation copy. preservation - The electronic resource was created via reformatting to help preserve the original item. The capture and storage techniques ensure high-quality, long-term protection. replacement - The electronic resource is of high enough quality to serve as a replacement if the original is lost, damaged, or destroyed. If serving more than one purpose, the element may be repeated.

<physicalDescription>

<internetMediaType> "internetMediaType" specifies the identification of the electronic format type, or the data representation of the resource, such as text/html, ASCII, Postscript file, executable application or JPEG image. It is roughly equivalent to MARC 21 field 856 subfield $q. The <internetMediaType> value is generally taken from a controlled list, especially from the Internet Media types (MIME types) (see: www.iana.org/assignments/media-types/index.html for a complete list). The element may also include local x-types.

<physicalDescription>

<extent> "extent" includes information about the extent of a resource. It may be used with electronic resources, e.g. digitized collection of slides, to show how many slides constitute the resource. It is roughly equivalent to MARC 21 fields 300 subfields $a, $b, $c, and $e and 306 subfield $a.

<physicalDescription>

<digitalOrigin> "digitalOrigin" designates whether a digital resource is born digital or reformatted digital. It does not exist in the MARC 21 formats, however, it is beneficial in the description of digital materials. The following values may be used: born digital - A resource was created and is intended to remain in digital form. reformatted digital - A resource was created in a non-digital form and was converted into a digital form.

<physicalDescription>

<note> "note" contains notes relating to the physical description of a resource. It is roughly equivalent to the types of notes that may be contained in MARC 21 fields 340, 351 or general 500 notes concerning physical condition, characteristics, etc. A link may be supplied in lieu of or in addition to the content. Each note should be entered in a separate <note> subelement. A list of note types used by MODS implementors has been compiled. Attributes type - This attribute is not controlled by a list and thus is open-ended. displayLabel - This attribute is intended to be used when additional text associated with the note is necessary for display. xlink - See the Attributes used throughout the schema for description. lang - See the Attributes used throughout the schema for description. xml:lang - See the Attributes used throughout the schema for description. script - See the Attributes used throughout the schema for description. transliteration - See the Attributes used throughout the schema for description.

Examples

<physicalDescription>
	<note type="organization">Fixed-length, nonhierarchical; Month by carrier code and flight number</note>
</physicalDescription>

<physicalDescription>
	<extent>7" x 9"</extent>
	<note displayLabel="Location within resource">Between entry for April 7 and April 19, 1843</note>
</physicalDescription>

<physicalDescription>
	<form authority="marcform">print</form>
	<extent>ill., music ; 26 cm</extent>
	<reformattingQuality>replacement</reformattingQuality>
</physicalDescription>

<physicalDescription>
	<extent>1 sound disc (56 min.) : digital ; 3/4 in.</extent>
</physicalDescription>

<abstract>

"abstract" contains a summary of a resource. It is roughly equivalent to MARC 21 field 520. A link may be supplied in lieu of or in addition to the content.

Attributes

• type - There is no controlled list of abstract types.
• displayLabel - This attribute is intended to be used when additional text associated with the abstract is necessary for display.
• xlink - See the Attributes used throughout the schema for description.
• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

There are no subelements defined for <abstract>.

Examples

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

<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</abstract>

<abstract xml:lang="fr" xlink:href= "http://www.allocine.fr/film/fichefilm_gen_cfilm=808.html"> A la fin du XIXème siècle, Rudyard Kipling, un jeune journaliste installé en Inde, fait la connaissance de Daniel Dravot et de Peachy Carnehan, deux anciens sergents de l'armée britannique à la recherche de la fortune et de la gloire. Après un long et périlleux voyage via l'Afghanistan, ces derniers pénètrent dans une contrée sauvage, le Kafristan, où des villageois sont en guerre contre une ville rivale. Tous deux s'engagent dans la bataille.Au cours des combats, Dravot reçoit une flèche en pleine poitrine, mais continue à lutter. En réalité, la flèche s'est plantée dans la catouchière. Mais aux yeux du peuple, il passe pour un être surnaturel, le dieu Sikander, fils d'Alexandre le Grand. Après ce miracle supposé, Dravot est proclamé roi du Kafristan et bénéficie de la puissance absolue. Mais le pouvoir peut corrompre même le meilleur des hommes.</abstract>

<abstract xlink:href="http://sunsite.berkeley.edu/CurrentCites/2003/cc03.14.3.html" displayLabel="Review">Written in a rather whimsical style, this short article makes a serious statement about the direction in which libraries are evolving. The word 'library' may eventually be dropped from our vocabulary, to be replaced by the 'idea store'. Books are being displaced by computers, multimedia content, playgrounds, thematic displays, and cafes. This is proving extremely propular, given the surge in client population. The library locales mentioned are local, however, the transformation of libraries is universal. </abstract>

<tableOfContents>

"tableOfContents" contains contents notes for a resource. It is roughly equivalent to MARC 21 field 505. A link may be supplied in lieu of or in addition to the content. If a more structured and rich table of contents is needed, use <relatedItem> with type="constituent".

Attributes

• type - There is no controlled list of table of contents types.
• displayLabel - This attribute is intended to be used when additional text associated with the table of contents is necessary for display.
• xlink - See the Attributes used throughout the schema for description.
• lang - See the Attributes used throughout the schema for description.
• xml:lang - See the Attributes used throughout the schema for description.
• script - See the Attributes used throughout the schema for description.
• transliteration - See the Attributes used throughout the schema for description.

Subelements

There are no subelements defined for <tableOfContents>.

Examples

<tableOfContents xlink:href= "http://www.loc.gov/catdir/toc/99176484.html"/> </tableOfContents>

<tableOfContents displayLabel="Chapters included in book">Bluegrass odyssey -- Hills of Tennessee -- Sassafrass -- Muddy river -- Take your shoes off Moses -- Don't let Smokey Mountain smoke get in your eyes -- Farewell party -- Faded love -- Super sonic bluegrass -- Old love letters -- Will the circle be unbroken</tableOfContents>

<tableOfContents type="partial contents">Baptisms, 1816-1872 --Church members, 1816-1831 --History of the Second Presbyterian Church of West Durham</tableOfContents>

<titleInfo>
	<nonSort>The</nonSort>
	<title>September 11 Web archive</title>
</titleInfo>
<tableOfContents>Who made Web sites? – What could people do? – Search the archive – Visit this site – Analysis The September 11 Web Sphere </tableOfContents>

<targetAudience>

"targetAudience" describes the intellectual level of the audience for which the resource is intended. When more than one target audience is recorded, the element is repeated. Either a controlled list of values or free text may be used.

Attributes

• authority - The name of the authoritative list for a controlled value is recorded here. A list of authorities is maintained at: www.loc.gov/marc/sourcecode/target/targetsource.html. The MARC 21 target audience list contains many of the values defined in MARC 21 field 008/22 (BK, CF, MU, VM). Use authority="marctarget" to indicate its use.
  
• lang - See the Attributes used throughout the schema for description.
  
• xml:lang - See the Attributes used throughout the schema for description.
  
• script - See the Attributes used throughout the schema for description.
  
• transliteration - See the Attributes used throughout the schema for description.

Subelements

There are no subelements defined for <targetAudience>.

Examples

<targetAudience authority="marctarget">adult</targetAudience>

<targetAudience>kindergarten</targetAudience>

<targetAudience authority="marctarget">juvenile</targetAudience>
<targetAudience authority="marctarget">adolescent</targetAudience>
	[Resource contains information targeted to both juvenile and adolescent audiences]

<note>

"note" contains any note relating to a resource. It is roughly equivalent to MARC 21 fields 5XX. A link may be supplied in lieu of or in addition to the content. Each note should be entered in a separate element. Notes relating to physical description aspects of a resource should be recorded in the <note> subelement of <physicalDescription>.

Attributes

• type - This attribute is not controlled by a list and thus is open-ended. A list of note types used by MODS implementors has been compiled for interoperability. Some examples of type values are:
  
  • performers (equivalent to MARC 21 field 511)
    
  • venue (equivalent to MARC 21 field 518)
    
  • statementOfResponsibility (equivalent to MARC 21 field 245 subfield $c).
    
  Other types of notes in MARC 21 5XX have separate elements in MODS: <abstract>; <accessCondition>; <tableOfContents>; <targetAudience>.
  
• displayLabel -This attribute is intended to be used when additional text associated with the note is necessary for display.
  
• xlink - See the Attributes used throughout the schema for description.
  
• lang - See the Attributes used throughout the schema for description.
  
• xml:lang - See the Attributes used throughout the schema for description.
  
• script - See the Attributes used throughout the schema for description.
  
• transliteration - See the Attributes used throughout the schema for description.

Subelements

There are no subelements defined for <note>.

Examples

<note type="performers">Anne Baxter (Louise), Maria Perschy (Angela), Gustavo Rojo (Bill), Reginald Gilliam (Mr. Johnson), [Catherine Elliot?] (Aunt Sallie), Ben Tatar (waiter)</note>

<note type="statement of responsibility">written by Burt Kimmelman</note>

<note>Based on a play which originally appeared in France as "Un peu plus tard, un peu plus tôt"</note>

<note type="historical" displayLabel="Historical note:" xlink:href=" http://www.mnhs.org/library/findaids/80881.html">The Faribault State School and Hospital provided care, treatment, training, and a variety of other services to mentally retarded individuals and their families. It was operated by the State of Minnesota from 1879 to 1998 under different administrative structures and with different names. A more detailed history of the Hospital may be found at:</note>

<subject>

"subject" is a wrapper tag that binds together subelements. If the subject is a controlled heading from an authoritative list, use the authority attribute to indicate the authority. If it is not desired to parse the subject subelements, use <subject><topic> and a string. If no authority attribute is present, the data is assumed to be an uncontrolled term. Repeat the subject for each subject string.

Attributes

• authority - The name of the authoritative list for a controlled value is recorded here. An authority attribute may be used to indicate that a subject is controlled by a record in an authority file. A list of authorities is maintained at: www.loc.gov/marc/sourcecode/subject/subjectsource.html. This attribute is equivalent to MARC 21 field 6XX, second indicator value or content of subfield $2. If the subject string is formulated according to the Library of Congress Subject Headings (or LC Name Authority File), the value of the authority attribute is "lcsh." A subject thesaurus that does not include names but has an implied authority for names uses the designation for that thesaurus (i.e., "lcsh" means LCSH plus NAF). Specify authority at the highest level if there are subelements; optionally it may also be specified for a subelement. Authority is not applicable to the subelement <hierarchicalGeographic>.
  • xlink - See the Attributes used throughout the schema for description.
  • ID - See the Attributes used throughout the schema for description.
  • lang - See the Attributes used throughout the schema for description.
  • xml:lang - See the Attributes used throughout the schema for description.
  • script - See the Attributes used throughout the schema for description.
  • transliteration - See the Attributes used throughout the schema for description.

Subelements

The following subelements are defined for <subject>. They are enumerated below.

<subject>

<topic> "topic" is used as the tag for any topical subjects that are not appropriate in the <geographic>, <temporal>, <titleInfo>, or <name> subelements. If there is an uncontrolled term, <topic> is used (since <subject> is a binding element). <topic> is equivalent to MARC 21 fields 650 and 6XX subfields $x and $v (with authority attribute defined) and MARC 21 field 653 with no authority attribute. Note that form subdivisions in LCSH are coded as <topic> because it was felt that the distinction was too difficult to make.

<subject>

<geographic> "geographic" is used for geographic subject terms that are not parsed as hierarchical geographics. If the geographic name is part of a corporate body (i.e., United States. Senate), it is coded as <name>, not <geographic>. <geographic> is equivalent to MARC 21 field 651 and 6XX subfield $z.

<subject>

<temporal> "temporal" is used for chronological subject terms or temporal coverage. It may be expressed as a controlled subject term or as a structured date using the same data definition as MODS dates. <temporal> is equivalent to MARC 21 fields 045 and 6XX subfield $y. Attributes encoding - See the Attributes used throughout the schema for description. point - See the Attributes used throughout the schema for description. keyDate - See the Attributes used throughout the schema for description.

<subject>

<titleInfo> "titleInfo" includes a title used as a subject. All subelements and attributes used under the top-level element <titleInfo> may be used with this subelement. An authority attribute may also be used at this level if desired, in addition to at the highest level (under <subject>). Equivalent to MARC 21 field 630.

<subject>

<name> "name" includes a name used as a subject. All subelements and attributes used under the top-level element <name> may be used. An authority attribute may also be used at this level if desired in addition to at the highest level (under <subject>). Equivalent to MARC 21 fields 600, 610, 611.

<subject>

<hierarchicalGeographic> "hierarchicalGeographic" includes a hierarchical form of place name relating to the resource, which is both readable by humans and parsable by machine