skip navigationThe Library of Congress » Standards » MODS Official Web Site |
Top-level Element: <titleInfo>
GUIDELINES | EXAMPLES | MAPPINGS GUIDELINES FOR USETitles are an extremely important access point for digital library resources and are frequently used in brief record displays to assist end users in deciding whether to investigate a resource further. In supplying a title, consider expectations of end users for naming of resources. Choice and format of titles should be governed by a content standard such as the Anglo-American Cataloging Rules, 2nd edition (AACR2), Cataloguing Cultural Objects (CCO), or Describing Archives: A Content Standard (DACS). Details such as capitalization, choosing among the forms of titles presented on an item, and use of abbreviations should be determined based on the rules in a content standard. One standard should be chosen and used consistently for all records in a set. <titleInfo> is a container element that contains all subelements related to title information. Data content is contained in subelements. Do not include punctuation intended to delineate parts of titles that are separated into subelements of <titleInfo>. If multiple titles are recorded, repeat <titleInfo><title> for each. <titleInfo> is also repeated for each type attribute value. The language of the title may be indicated if desired using the xml:lang or lang attributes. A uniform title may be linked to a name in the record using the nameTileGroup attribute. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer Implementation Guidelines for Shareable MODS Records require the use in all records of at least one <titleInfo> element with one <title> subelement. Other subelements of <titleInfo> are recommended when they apply. Additional <titleInfo> elements should be used to indicate other titles for the resource. When no title appears on the item being described, a title should be supplied. The DLF/Aquifer guidelines recommend against the use of brackets or other punctuation to indicate the title has been supplied rather than appearing on the item; the displayLabel attribute, however, may be used to indicate that the title is supplied. The DLF/Aquifer guidelines recommend the use of authoritative titles and the authority attribute whenever the type attribute is set to "uniform" and/or "abbreviated". Authority codes for "uniform" should be taken from the Name and Title Authority Source Codes; authority codes for "abbreviated" should be taken from the code list for Abbreviated Title Source Codes, both maintained by the Library of Congress. The authority attribute should not be used with titles having a type attribute of "translated" or "alternative" since these title types would not be represented in an authority file. See the <titleInfo> 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: <titleInfo> is the primary descriptive element used for identification and display for many digital objects. Most aggregators index <titleInfo> and will use it in a brief display. The "Title Practices" section in the DLF/NSDL Best Practices for Shareable Metadata discusses the use of titles. The DLF/Aquifer guidelines are more prescriptive than the DLF/NSDL Best Practices, requiring at least one title be present in every record. Element DescriptionAttributesAll attributes except lang, xml:lang, script, and transliteration are only applied to the <titleInfo> element. type Definition
Identifies what type of title is recorded.
Application
The following values may be used with the type attribute:
authority Definition
The controlled list from which the value is taken.
Application
Record the name of the authoritative list used, if applicable, e.g. authority="naf". The Library of Congress maintains a list of authority files for titles: Name and Title Authority Source Codes and Abbreviated Title Source Codes.
authorityURI Definition
A URI uniquely identifying the vocabulary from which the controlled term has been selected, as assigned by the body responsible for the maintenance of the vocabulary.
Application
URIs identifying authorities may or may not be dereferenceable to human- or machine-readable information on the authority file, controlled vocabulary, or thesaurus.
valueURI Definition
A URI uniquely identifying the term or controlled value from a vocabulary, as assigned by the body responsible for the maintenance of the vocabulary.
Application
URIs identifying terms may or may not be dereferenceable to human- or machine-readable records for the term.
usage Definition
Use of the title in the resource description.
Application
This attribute is used with usage="primary" when when there are several titles in a record and for citation purposes one is to be selected. The "primary" title would be used for a citation to the resource.
supplied Definition
An indication that the title information did not come from the resource itself.
Application
This attribute is used as supplied="yes" when the title information has been supplied from an external source, not from the resource.
nameTitleGroup Definition
Provides an explicit link between a uniform title and a name when that is needed.
Application
The same value is assigned to this attribute for the two elements. This attribute is used to link names to uniform titles when the name-uniform title combination is an authority controlled heading.
altRepGroup; xlink; ID; lang; xml:lang; script; transliteration; displayLabel See the Attributes used throughout the schema for description for each. SubelementsThe following subelements are described below:
Subelement: <title>
Guidelines for UseEach element 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). <namePart> subelement includes all parts of a title not covered by the other subelements of <titleInfo>. 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 equal to "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. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer Implementation Guidelines for Shareable MODS Records require at least one <titleInfo><title>. Element DescriptionAttributeslang; xml:lang; script; transliteration See the Attributes used throughout the schema for description for each. SubelementsThere are no subelements for <title>. Subelement: <subtitle>
Guidelines for Use<subTitle> is used when it is desired to include the information as a separate element. Alternatively, the subtitle may be included as part of <title>. When using the <subTitle> element, do not include punctuation at the end of the <title> element intended to delineate the title from the subtitle. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer guidelines recommend the use of this element when a subtitle is present, rather than including the subtitle in the text of the <title> element. Element DescriptionAttributeslang; xml:lang; script; transliteration See the Attributes used throughout the schema for description for each. SubelementsThere are no subelements for <subtitle> Subelement: <partNumber>
Guidelines for UseUse <partNumber> to describe the enumeration-type designation of a section of the object (for example, an episode number or an audio or video clip of a digital item). <partNumber> may follow <title> or <subTitle> as appropriate. When using the <partNumber> element, do not include punctuation at the end of the preceding element intended to delineate the part number from previous parts of the title. Multiple parts of an item should appear in separate MODS records or <relatedItem> elements. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer guidelines recommend the use of this subelement when a part number is present, rather than including the part number in the text of the <title> element. Element DescriptionAttributeslang; xml:lang; script; transliteration See the Attributes used throughout the schema for description for each. SubelementsThere are no subelements for <partNumber> Subelement: <partName>
Guidelines for UseUse <partName> to describe the section or division titles of an object (for example, a chapter title, episode name, or an audio or video clip). Multiple <partName> elements may be used in a single <titleInfo> to describe a single part with multiple hierarchical levels (see the Bible example below). However, multiple parts of an item should appear in separate MODS records or <relatedItem> elements. When using the <partName> element, do not include punctuation at the end of the preceding element intended to delineate the part name from previous parts of the title. Specific DLF/Aquifer GuidelinesThe DLF/Aquifer guidelines recommend the use of this subelement when a part name is present, rather than including the part name in the text of the <title> element. Element DescriptionAttributeslang; xml:lang; script; transliteration See the Attributes used throughout the schema for description for each. SubelementsThere are no subelements for <partName>. Subelement: <nonSort>
Guidelines for Use<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. For instance, "The" as an initial article is input with space following the characters, while other data might not require a space (e.g. "L'"). <nonSort>The </nonSort><title>Trial</title> Specific DLF/Aquifer GuidelinesThe DLF/Aquifer guidelines strongly recommend the use of this element when non-sorting characters are present, rather than including them in the text of the <title> element. Element DescriptionAttributeslang; xml:lang; script; transliteration See the Attributes used throughout the schema for description for each. SubelementsThere are no subelements for <nonSort> EXAMPLES<titleInfo>
<title>Bush Cheney</title>
</titleInfo>
<titleInfo type="alternative" displayLabel="also known as">
<title >Bush-Cheney 2000</title>
</titleInfo>
<titleInfo type="alternative">
<title>George W. Bush for President</title>
</titleInfo>
<titleInfo>
<nonSort>The</nonSort>
<title>"wintermind"</title> <subTitle>William Bonk and American letters</subTitle> </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>
<nonSort>The</nonSort>
<title>Olympics</title> <subTitle>a history</subTitle> <partNumber>Part 1</partNumber> <partName>Ancient</partName> </titleInfo>
<titleInfo type="uniform" authority="naf">
<title>Bible</title>
<partName>O.T.</partName> <partName>Exodus</partName> </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" authority="dnlm">
<title>Annu. rep. notif. dis.</title>
</titleInfo>
<titleInfo lang="rus" script="Latn" transliteration="ALA-LC Romanization Tables">
<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" valueURI="http://id.loc.gov/authorities/n93028706">
<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>
<titleInfo>
<title>Canticum canticorum</title>
</titleInfo>
<titleInfo type="uniform" nameTitleGroup="1">
<title>Motets</title>
<partNumber>(1583)</partNumber>
</titleInfo>
<name type="personal" nameTitleGroup="1" usage="primary">
<namePart>Palestrina, Giovanni Pierluigi da</namePart>
<namePart type="date">1525?-1594</namePart>
</name>
<name type="personal">
<namePart>Picotti, Livio.</namePart>
<role>
<roleTerm authority="marcrelator" type="code">prf</roleTerm>
</role>
</name>
MAPPINGSMARC Mapping (Bibliographic)The <titleInfo> type attribute values are equivalent to the following MARC 21 fields:
The displayLabel attribute = MARC 21 field 246 subfield i. <title> without the <titleInfo> type attribute ≈ MARC 21 field 245. Elements considered part of the title that are separately subfielded in MARC 21 are included in <title> 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 <title>, but a part name or number is included in the subelements below. <subTitle> = MARC 21 fields 242, 245, and 246 subfield b. <partNumber> = MARC 21 fields 130, 240, 242, 243, 245, 246, 247, 730, and 740 subfield n. <partName> = MARC 21 fields 130, 240, 242, 243, 245, 246, 247, 730, and 740 subfield p. See also MARC Mapping to MODS for the <titleInfo> element. Dublin Core MappingThe MODS to Dublin Core Metadata Element Set Mapping recommends mapping the <titleInfo> element and all subelements to the <dc:title> element in simple Dublin Core. Since prescribed punctuation separating elements of the title is not included in MODS records prepared according to these guidelines, they would need to be inserted at the point of transformation. MODS example expressed in Dublin Core: <dc:title>The Olympics: a history. Part 1: Ancient</title>
<dc:title>Bible. O.T. Exodus</title> |
February 18, 2011 |