skip navigationThe Library of Congress » Standards » MODS Official Web Site |
Top-level Element: <typeOfResource>
GUIDELINES | EXAMPLES | MAPPINGS GUIDELINES FOR USEInformation in <typeOfResource> is about the original item. For example, in the case of a digitized photograph, <typeOfResource> would apply to the analog original; in born-digital materials, it would apply to the original digital format. This element includes a high-level type that categorizes the material in a general way using an enumerated list of values. 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 that 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). Values for <typeOfResource>The following values may be used:
Specific DLF/Aquifer GuidelinesThe Guidelines require the use in all records of at least one <typeOfResource> element using the required enumerated values. See the <typeOfResource> entry in the DLF/Aquifer Summary of MODS Requirements and Recommendations Table for further information on requirements of this element, its attributes, and subelements. Aggregator information: Due to its utility for determining research value (for example, a researcher looking specifically for cartographic material), aggregators may choose to include this field in a brief display to end users, and may also index it to allow limiting or refining by this data. Aggregators may also use this field to determine suitability for harvesting based on their perception of end users' needs. Related information is discussed in the "Types of Resource" and the "Describing Versions and Reproductions" sections of the DLF/NSDL Best Practices for Shareable Metadata. Element DescriptionAttributescollection Definition
A made-up multipart group of items that were not originally published, distributed, or produced together.
Application
This attribute is used as collection="yes" when the resource is a collection. It may also be applied to electronic resources that are collections in the sense of a made-up multipart group of items. If there are multiple resource
types within the collection, these should be enumerated in separate <typeOfResource> elements.
manuscript Definition
A resource that is written in handwriting or typescript.
Application
This attribute is used as manuscript="yes" when a collection contains manuscripts and is considered generally to be manuscript in nature, and for individual manuscripts.
usage Definition
Strength of the form vis-a-vis the resource.
Application
This attribute is used with usage="primary" when the main form of the resource is specified in the element.
altRepGroup; displayLabel See the Attributes used throughout the schema for descriptions of each.
SubelementsThere are no subelements for <typeOfResource>. EXAMPLES<titleInfo>
<nonSort>The</nonSort>
<title>new naval and military map of the United States</title> </titleInfo>
<typeOfResource>cartographic</typeOfResource> <genre>map</genre> <titleInfo>
<title>Camp Council meeting; speech by Dewey Rodgers</title>
</titleInfo>
<typeOfResource>sound recording-nonmusical</typeOfResource> <genre authority="marcgt">speech</genre> <titleInfo>
<title>Glove</title>
</titleInfo>
<physicalDescription> <form authority="gmd">sound recording</form>
</physicalDescription>
<typeOfResource>sound recording-musical</typeOfResource> <titleInfo>
<title>Portrait of Django Reinhardt, Aquarium, New York, N.Y., ca. Nov. 1946</title>
</titleInfo>
<typeOfResource>still image</typeOfResource> <titleInfo displayLabel="Title">
<nonSort>The</nonSort>
<title>battle-cry of freedom</title> </titleInfo>
<typeOfResource displayLabel="Format">notated music</typeOfResource> <genre displayLabel="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 </title>
</titleInfo>
<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> MAPPINGMARC Mapping (Bibliographic)<typeOfResource> = Leader/06 with the following controlled list of textual values:
Attributes are used to further indicate whether the resource is a collection or 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). See also MARC Mapping to MODS for the <typeOfResource>. Dublin Core MappingThe MODS to Dublin Core Metadata Element Set Mapping recommends mapping the <typeOfResource> to <dc:type>. In addition, these guidelines recommend that when mapping the values found in <typeOfResource> to Dublin Core Type values, include both the MODS value and the DC value if they are substantially different. Similarly, the attributes of collection and manuscript should be included as an additional, separate <dc:type> value. MODS examples expressed in Dublin Core: <dc:type>text</dc:type>
<dc:type>still image</dc:type> <dc:type>collection</dc:type> <dc:type>text</dc:type> |
February 18, 2011 |