DCM Z1: 2. Group
1 - Name Authority Group (Appendix
1: Ambiguous Entities) DCM Z1: 2. Group
1 - Name Authority Group (Appendix
1: Ambiguous Entities)
Authorized access points always established according to descriptive cataloging guidelines (RDA and the LC-PCC PSs); authority record always resides in the name authority file.
NOTE: MARC coding in the examples reflects the provisions of MARC 21 Format for Authority Data (except spaces added before and after subfield codes) and not any individual system.
Establish the authorized access point according to descriptive cataloging rules and procedures. If an authorized access point in this category is needed in subject cataloging, those involved in descriptive cataloging establish it, and the authority record is added to the name authority file.
Establish the authorized access points for an airport according to the provisions for any other corporate body (see RDA chapter 11).
110 2# $a San Francisco International Airport
110 2# $a Logan International Airport (Boston, Mass.)
110 2# $a Jan Smuts Airport (Johannesburg, South Africa)
110 2# $a Greater Cincinnati International Airport
110 2# $a Davis Airport (Montgomery County, Md.)
110 2# $a Davis Airport (Luzerne County, Pa.)
2.3. Arboretums, botanical gardens, herbariums, public aquariums, zoological gardens, etc.
These Group 1 entities are tagged as corporate names (110) and established according to chapter 11 of RDA. For other gardens, parks, etc., see Group 2.
110 2# $a State Arboretum of Utah
110 2# $a Missouri Botanical Garden
110 2# $a National Zoological Park (U.S.)
110 2# $a Hayden Planetarium
110 2# $a Miami Seaquarium
2.4. Cemeteries, concentration camps, country clubs
After July 1996, cemeteries, concentration camps, and country clubs are treated only as Group 1 entities. Establish them in accordance with the general principles for corporate name authorized access points (see RDA chapter 11). For cemeteries that are archaeological sites, see Group 2.
110 2# $a Arlington National Cemetery (Arlington, Va.)
110 2# $a Riverside Cemetery (Jackson, Tenn.)
110 2# $a Cmentarz Ewangelicko-Augsburski w Warszawie (Warsaw, Poland)
110 2# $a Auschwitz (Concentration camp)
110 2# $a Campo 62 di Bergamo (Concentration camp)
110 2# $a Riomar Country Club
110 2# $a Manteno Young Women's Country Club
City sections, including city districts and neighborhoods, are treated only as Group 1 entities. Establish them in accordance with the general principles for geographic names (see RDA chapter 16).
151 ## $a Georgetown (Washington, D.C.)
151 ## $a Greenwich Village (New York, N.Y.)
151 ## $a Loop (Chicago, Ill.)
151 ## $a Rive gauche (Paris, France)
2.6. Collective settlements, conservation districts, communes, sanitation districts, forest districts, etc.
Collective settlements, conservation districts, communes, sanitation districts, forest districts, etc., are treated as Group 1 entities. Establish them in accordance with the general principles for geographic names (see RDA chapter 16).
151 ## $a Erez (Israel)
151 ## $a Santa Cruz County Sanitation District (Calif.)
151 ## $a Englewood Water District (Fla.)
151 ## $a Chicago Park District (Ill.)
If a name is for an event that is formally convened, directed toward a common goal, capable of being reconvened, and has a formal name, location, date, and duration that can be determined in advance of the date, establish the name according to the provisions of RDA chapter 11.
111 2# $a Ridge Folklife Festival
111 2# $a Palio di Siena (Festival) $d (2003 : $c Siena, Italy)
111 2# $a Miss America Pageant
111 2# $a World Cup (Soccer)
111 2# $a Tour de France (Race)
111 2# $a Biennale di Venezia
111 2# $a Biennale di Venezia $n (55th : $d 2013 : $c Venice, Italy)
111 2# $a World Jamboree of Boy Scouts
111 2# $a National Folk Media Festival $d (1988 : $c Nairobi, Kenya)
2.8. Forests, parks, preserves, etc.
When a forest, park, preserve, etc. (commonly a unit of the United States National Park Service or the United States Forest Service), is needed as a descriptive authorized access point on a bibliographic record because the forest, park, preserve, etc., has some responsibility for the intellectual content of the item, establish it in accordance with the general principles for corporate name authorized access points and qualify the name with "(Agency)." When this is not the case, continue to treat these as Group 2 entities and establish as a subject authority record as directed in SHM 1925.
110 2# $a Chugach National Forest (Agency : U.S.)
[Needed as a descriptive access point—Group 1.]
151 ## $a Chugach National Forest (Alaska)
[No intellectual content responsibility—Group 2.]
In 2006 the former Policy and Standards Division determined that names of Indian tribes recognized by the U.S. government as legal entities should be tagged 151 (Geographic name) in name authority records rather than 110 (Corporate name), as they were previously tagged. In April 2015, it was determined that all Canadian First Nation entity names should also be tagged 151 to align with the instructions for U.S. tribal entities.
This change in status of headings for tribal entities to 151 (Geographic name) enabled these headings to be used as jurisdictions when needed in cataloging. When a heading of this type is used in a bibliographic record to represent a government (110), the MARC 21 indicator is set to "1" to reflect that the entity is acting as a jurisdiction. These headings may also be used as geographic subdivisions, subdivided directly. Access points for populated places (PPLs) on reservations are established as geographic names according to RDA instructions and should also be established as place names tagged 151 when these are different from the tribal entity.
Example of populated place name (complete name authority record fields not provided):
151 ## $a San Carlos (Ariz.)
. . .
670 ## $a GNIS,July 29,2002 $b (San Carlos, Gila County, Arizona, populated place; 33°20'43"N, 110°27'09"W)
When the reservation as a geographic area, not the tribal entity, is the subject of an item being cataloged, the guidelines in the SHM will continue to be applied, and these place names will continue to be established as subject headings tagged 151.
Example of subject heading:
010 ## $a sh90004101
151 ## $a San Carlos Indian Reservation (Ariz.)
550 ## $w g $a Indian reservations $z Arizona
670 ## $a Work cat.: Brown, J.G. Geology and ground-water resources of the San Carlos Indian Reservation ... Arizona, 1990: $b t.p. (San Carlos Indian Reservation, Gila, Graham, and Pinal counties, Arizona)
670 ## $a Rand McNally
781 #0 $z Arizona $z San Carlos Indian Reservation
If an authorized access point is needed for an entity in the category of a named building/museum, judge whether or not the entity is a museum. If it is a museum, treat it as a Group 1 entity and establish it accordingly; if not, treat it as a Group 2 entity and have it established as a subject authority record as directed in the guidelines for Group 2 entities in 3.1.
110 2# $a Albrecht-Dürer Haus
[museum—Group 1]
110 2# $a Simson African Hall (California Academy of Sciences)
[building—Group 2]
2.11. Plans, programs, and projects
Treat plans, programs, and projects as corporate bodies whether or not they have a staff. Do not consider that authorized access points for entities with these words in their name need the addition of a qualifier that conveys the idea of a corporate body.
Establish railroads in accord with the general principles for corporate name authorized access points. During the period 1984-1985, railroad access points were established according to the conventions of the former Subject Cataloging Division. Generally, a railroad authorized access point represented by an RDA name authority record should be accepted unless the item being cataloged shows another form and the item is the railroad's own publication. In such cases re-evaluate the existing authorized access points. At one time, railroads were represented by two separate access points, one for the company, which was tagged as a corporate access point, and another for the line, which was tagged as a topical subject heading. To locate all existing bibliographic records for a railroad when a name authority record for it needs to be created or coded for RDA, search for the name both as a corporate body and as a topical subject heading.
2.13. Fictitious characters, legendary characters, etc. (Individual)
Establish headings for individual fictitious and legendary characters in accord with the general principles for personal name authorized access points (see RDA chapter 9). Previous to 2013, these headings were established in the subject authority file according to subject cataloging files. Consult the LC-PCC PS 9.0 and SHM 1610 for further information.
100 1# $a Holmes, Sherlock
[individual character—Group 1]
100 0# $a Alcestis, $c Queen, consort of Admetus, King of Pherae
[individual character—Group 1]
100 1# $a Mouse, Mickey $c (Fictitious character)
[individual character—Group 1]
Headings for named groups of fictitious characters (e.g., Hardy Boys, Teenage Mutant Ninja Turtles) continue to be established in the subject authority file.
150 ## $a Addams family (Fictitious characters)
[group of characters—Group 2]
150 ## $a Care Bears (Fictitious characters)
[group of characters—Group 2]
See also:
1. Introduction
(Appendix 1 - Ambiguous Entities)
3.
Group 2 - Subject Authority Group (Appendix
1 - Ambiguous Entities)
For more information on DCM Z1 Instructions, select: