| skip navigationThe Library of Congress » Standards » MADS Official Web Site |
Top Level Core Element: <authority>
Guidelines for UseAt least one <authority> element is mandatory. This element is repeatable to allow for multiple authoritative forms for the same entity in different languages and scripts. There must be at least one subelement under <authority>. Element DescriptionAttributesgeographicSubdivision Definition
Defines whether a concept can append a geographic facet, such as the name of a
country or other jurisdiction, region, or geographic feature.
Application
The following values may be used:
lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThe following subelements are described below: More than one of these subelements may be combined within the <authority> element to control an authoritative heading that consists of multiple parts. Examples include name/title headings and subject strings with various components (e.g., <topic> and <geographic>). MARC MappingMapping to MARC 21 Authority fields is shown at the individual subelement levels, below. If the geographicSubdivision attribute is used, the appropriate value in the MARC Authority 008/06 (Direct or indirect geographic subdivision) is used as follows:
See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority>: <name>
Guidelines for Use<name> is a container element that contains the subelements with the value of the authoritative name. If <name> is used, at least one occurrence of the subelement <namePart> must be included. The Library of Congress maintains a list of authority files, Name and Title Authority Source Codes, that can be used for the authority attribute of this element. This subelement is optional and repeatable. Element DescriptionAttributestype Definition
Optionally, indicates the type of name that is recorded.
Application
The following values may be used with type:
authority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThe following subelements are described below: MARC Mapping<authority><name type="personal"> = MARC 21 Authority field 100 <authority><name type="family"> = MARC 21 Authority field 100 (1st Indicator=3) <authority><name type="corporate"> = MARC 21 Authority field 110 <authority><name type="conference"> = MARC 21 Authority field 111 See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority><name>: <namePart>
Guidelines for UseThe content of an authoritative name is always contained in one or more <namePart> subelements. Parsing of names into parts can be used to indicate a date associated with the name, to parse the parts of a corporate name, or to parse parts of a personal name if desired. MADS allows for either breaking up parts of the name (given and family, for example) in different <namePart> elements or enclosing the entire name in one element. Use of the former method affords more control in sorting and display. Either method is acceptable. Name elements should appear in the same order as in their authorized form (the authority cited in the <name> authority attribute). If no authority is used for personal names, last name or family name should appear first, followed by a comma, followed by first or given names. At least one occurrence of this subelement is mandatory if the <name> element is used. This subelement is repeatable. Element DescriptionAttributestype Definition
Identifies which part of the name is recorded in the <namePart>.
Application
When breaking a <name> element into constituent <namePart>
elements, the type attribute should be used whenever
applicable. The following values may be used with the type attribute:
lang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <namePart>. MARC Mapping<authority><name type="personal"><namePart> = MARC 21 Authority field 100 subfieilds a and q <authority><name type="personal"><namePart type="date"> = MARC 21 Authority field 100 subfield d <authority><name type="personal"><namePart type="termsOfAddress"> = MARC 21 Authority field 100 subfields b and c <authority><name type="corporate"><namePart> = MARC 21 Authority field 110 subfields a, b, c, d, and n <authority><name type="conference"><namePart> = MARC 21 Authority field 111 sufields a, c, d, e, n, and q See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority><name>: <description>
Guidelines for UseUsed for additional descriptive information about the name entity. This subelement is optional and repeatable. Element DescriptionAttributeslang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <description>. MARC MappingThere is no MARC 21 Authority equivalent for <description>. Subelement of <authority>: <titleInfo>
Guidelines for Use<titleInfo> is a container element that contains all subelements related to the authoritative form of a title. The data content is contained in the relevant subelements. Although in most cases, at least one of the subelements will appear if the <titleInfo> element is used, there are instances where <titleInfo> may be used without subelements, for instance when the valueURI or xlink attribute is used. Do not include punctuation that is intended to delineate parts of titles that are separated into the different subelements of <titleInfo>. There is no type attribute because only uniform titles are applicable. The language of the title may be indicated if desired using the xml:lang or lang attributes. The Library of Congress maintains a list of authority files, Name and Title Authority Source Codes, that may be used for the authority attribute. This subelement is optional and repeatable. Element DescriptionAttributesdisplayLabel Definition
Provides additional text associated with the title if needed for display purposes.
Application
Include the text preferred and capitalization, but do not include delimiters such as colons.
authority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThe following subelements are described below: MARC Mapping<authority><titleInfo> includes titles found in MARC Authority fields 100, 110, 111, or 130. See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority><titleInfo>: <title>
Guidelines for UseUse for the uniform title of the resource. Dates may be recorded here only if considered part of the uniform title. This element is optional and repeatable. Element DescriptionAttributeslang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <title>. MARC Mapping<authority><titleInfo><title> = MARC 21 Authority fields 100, 110, 111, and 130 with various title subfields See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority><titleInfo>: <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. This element is optional and repeatable. Element DescriptionAttributeslang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <subTitle>. MARC MappingThere is no MARC 21 Authority format equivalent for <subTitle>. Subelement of <authority><titleInfo>: <partNumber>
Guidelines for UseUse <partNumber> to describe the enumeration-type designation of a section of a title entity (for example, a volume number or an episode number of an 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. This element is optional and repeatable. Element DescriptionAttributeslang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <partNumber>. MARC Mapping<authority><titleInfo><partNumber> = MARC 21 Authority fields 100, 110, 111, and 130 subfield n See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority><titleInfo>: <partName>
Guidelines for UseUse <partName> to describe the section or division titles of an object (for example, a volume title, a chapter title, or episode name of an item). Multiple <partName> elements may be used in a single <titleInfo> to describe a single part with multiple hierarchical levels. 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. This element is optional and repeatable. Element DescriptionAttributeslang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <partName>. MARC Mapping<authority><titleInfo><partName> = MARC 21 Authority fields 100, 110, 111, and 130 subfield p See also MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority><titleInfo>: <nonSort>
Guidelines for Use<nonSort> begin and end tags surround the nonfiling text which should not be regarded in 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'"):
This element is optional and repeatable. Element DescriptionAttributeslang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <nonSort>. MARC MappingIt is equivalent to the technique in MARC 21 that uses control characters to surround data disregarded for sorting. It is used for the same purpose as the MARC nonfiling indicator value that indicates the number of initial characters disregarded for sorting. Subelement of <authority>: <topic>
Guidelines for UseThe Library of Congress maintains a list of Subject Heading and Term Source Codes that can be used for the authority attribute of this element. Element DescriptionAttributesauthority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <topic>. MARC Mapping<authority><topic> = MARC 21 Authority field 150 subfields a and b, and fields 100, 110, 111, 130, 148, 150, 151, 155, 180, 181, or 185 subfield x. See MARC 21 Authority Format Mapping to MADS Schema Subelement of <authority>: <temporal>
Guidelines for UseThe date may be in textual or structured form. If it is structured, the encoding attribute specifies the encoding scheme. No good standard for encoding BCE dates in a structured form currently exists; until such time as these recommendations emerge, BCE dates may be represented in textual forms. When a date is uncertain or cataloger-supplied, indicate this through the use of the qualifier attribute rather than inserting characters such as "ca.", brackets, or a question mark as part of the date string. When only a decade is known, enter a date range for the entire decade and mark the date as questionable. When only a century is known, enter a date range for the entire century and mark the date as questionable. Mark one and only one date as a key date using keyDate="yes" attribute. Library of Congress maintains a list of Subject Heading and Term Source Codes, that may be used with the authority attribute of this element. Element DescriptionAttributesencoding, point, qualifier, keyDate, authority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <temporal>. MARC Mapping<authority><temporal> = MARC 21 Authority field 148 subfield a and fields 100, 110, 111, 130, 148, 150, 151, 155, 180, 181, or 185 subfield y See MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority>: <genre>
Guidelines for UseThe Library of Congress maintains a list of Genre/Form Code and Term Source Codes that can be used for the authority attribute of this element. This element is optional and repeatable. Element DescriptionAttributesauthority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <genre>. MARC Mapping<authority><genre> = MARC 21 Authority filed 155 subfield a and fields 100, 110, 111, 130, 148, 150, 151, 155, 180, 181, 182 or 185 subfield v See MARC 21 Authority Format Mapping to MADS Schema Subelement of <authority>: <geographic>
Guidelines for UseIf the geographic name is part of an organizational entity (e.g., United States. Senate; British Columbia. Fish and Wildlife Branch; or a corporate body), it is included in the <name> subelement. If the geographic name is in a hierarchical form use the <hierarchicalGeographic> element. The Library of Congress maintains a list of authority files, Name and Title Authority Source Codes, that can be used for the authority attribute of this element. This element is optional and repeatable. Element DescriptionAttributesauthority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <geographic>. MARC Mapping<authority><geographic> = MARC 21 Authority fields 151 subfield a or 181 subfield z <authority><geographic authority="xxx"> = MARC 21 Authority fields 100, 110, 111, 130, 148, 150, 151, 155, 180, 182, or 185 subfield z See MARC 21 Authority Format Mapping to MADS Schema. Subelement of <authority>: <hierarchicalGeographic>
Guidelines for Use<hierarchicalGeographic> is a container element for the specific hierarchical parts of a geographic entity. If a hierarchical description is not warranted or desirable, use the <geographic> element instead. In general, to designate the subelement, use the term most commonly used in the original language or its translation for the geographic entity. First order political divisions may have different terms depending on the country. For instance, first order political divisions in the U.S. are states; in Canada are provinces; in United Kingdom, England, Scotland, and Wales are countries and the next order division (e.g. Yorkshire) is county. The Library of Congress maintains a list of authority files, Name and Title Authority Source Codes, that can be used for the authority attribute of this element. This element is optional and repeatable. Element DescriptionAttributesauthority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThe following subelements are defined for <hierarchicalGeographic>. There are no attributes for these subelements.
Subelement AttributesAll <hierarchicalGeographic> sublements have the attributes: lang, xml:lang, script, transliteration See Attributes Used Throughout the MADS Schema for a description of each of these attributes. MARC MappingThere is no MARC 21 Authority format equivalent for <hierarchicalGeographic>, but it would establish the value used in field 662 or 752 in the MARC Bibliographic format. Subelement of <authority>: <occupation>
Guidelines for UseThe Library of Congress maintains a list of Occupation Term Source Codes, that can be used with the authority attribute of this element. Element DescriptionAttributesauthority, authorityURI, valueURI, lang, xml:lang, script, transliteration, ID, xlink See Attributes Used Throughout the MADS Schema for a description of each of these attributes. SubelementsThere are no subelements for <occupation>. MARC MappingThere is no MARC 21 Authority format equivalent for <occupation>, but it establishes the value used in the 656 field in the MARC Bibliographic format. EXAMPLES
Name - Personal <authority>
<name type="personal" authority="naf" >
<namePart>Farrukhzād, Furūgh</namePart>
</name>
</authority>
<authority>
<name type="personal" authority="naf" >
<namePart>Juana Inés de la Cruz</namePart>
<namePart type="termsOfAddress">Sister</namePart>
<namePart type="date">1651-1695</namePart>
</name>
</authority>
Name - Corporate <authority>
<name type="corporate" authority="naf" >
<namePart>Eastman Kodak Company</namePart>
<namePart>Laboratory and Research Products Division</namePart>
</name>
</authority>
Name - Conference <authority>
<name type="conference" authority="naf" >
<namePart>Jacobsen-McGill Arctic Research Expedition (1959-1962).</namePart>
</name>
</authority>
Name/Title <authority>
<name type="personal" authority="naf">
<namePart>Bach, Johann Christian</namePart>
<namePart type="date">1735-1782</namepart>
</name>
<titleInfo authority="naf">
<title>Bach, Johann Christian, Symphonies, E♭ major</title>
<partNumber>W. C 19b, E♭ major</partNumber>
</titleInfo>
</authority>
Title <authority>
<titleInfo authority="naf" >
<title>Silver Surfer (Comic strip)</title>
</titleInfo>
</authority>
<authority>
<titleInfo authority="naf" >
<title>Iraq War, 2003 Web Archive</title>
</titleInfo>
</authority>
Topic <authority>
<topic authority="lcsh">Fibonnaci numbers</topic>
</authority>
<authority>
<topic authority="lcsh">Chapultepec, Battle of, Mexico City, Mexico, 1847</topic>
</authority>
<authority>
<topic authority="lcsh">Blue-ringed octopuses</topic>
</authority>
<authority>
<topic authority="lcsh">World War, 1939-1945</topic>
<topic>Campaigns</topic>
<temporal>Iraq</topic>
</authority>
<authority>
<topic authority="lctgm">Abandoned vehicles</topic>
</authority>
Temporal <authority>
<topic authority="lctgm">Tuberculosis</topic>
<temporal>1880-1900</topic>
</authority>
Genre <authority>
<genre authority="lcgft">Aerial photographs</genre>
</authority>
<authority>
<genre authority="gmgpc">Caricatures</genre>
</authority>
Geographic <authority>
<geographic authority="lcsh">Neckar River (Germany)</geographic>
</authority>
Hierarchical Geographic <authority>
<hierarchicalGeographic authority="tgn" >
<country>United States</country>
<state>California</statee>
<county>Los Angeles (County)</county>
<city>Los Angeles</city>
<citySection>Little Tokyo</citySection>
</hierarchicalGeographic>
</authority>
<authority>
<state>District of Columbia</state>
<city>Washington</city>
<citySection>Northwest</citySection>
</authority>
Occupation <authority>
<occupation authority="onet" >Nanosystems Engineers</occupation>
</authority>
Last Updated: April 26, 2012 |
|
April 26, 2012 |