Add Bookmark

Please click in the document at the location of desired bookmark.

Find URL

Please click in the document at the location for the desired URL.

Warning

Content displayed is Filtered. Hits in filtered content are not currently visible in the document as displayed. To view all hits, select the Full view from the View Text menu.

LC-PCC PS for 11.13.1.1
GENERAL GUIDELINES ON CONSTRUCTING AUTHORIZED ACCESS POINTS TO REPRESENT CORPORATE BODIES
Use of Existing Authority Records in the LC/NACO Authority File
LC practice/PCC practice: Consult the PCC Post RDA Test Guidelines for up-to-date instructions on the issues related to RDA and AACR2 authority records and their use in bibliographic records.
Conflicts
LC practice/PCC practice: When two or more bodies have the same name, make an addition to each name. Determine that a conflict exists when the preferred name or authorized access point for one body is the same as the preferred name or authorized access point for another body. "Conflict" is restricted to names already created or being created in the catalog. If a variant name conflicts with a form used in the authorized access point for another body, apply the provisions for resolving conflicts only to the variant name. Ignore the conflict that is only between names used as variants.
 
 
 
EXAMPLE
 
110 2#$a Arlington Development Center (Arlington, Tex.)
Independent nongovernment body
 
110 2#$a Arlington Development Center (Arlington, S.D.)
Government body belonging to the city of Arlington
 
110 2#$a Arlington Development Center (Infodata, Inc.)
Subordinate nongovernment body
 
110 2#$a Arlington Development Center (S.D.)
Government body belonging to the state of South Dakota
 
 
 
For corporate bodies that have resumed an earlier name, see Policy Statement 32.1.1.3.
Prosecuting Attorneys of Jurisdictions
LC practice/PCC practice: Construct an authorized access point for a prosecuting attorney of a jurisdiction according to the following guidelines:
1.
Use the authorized access point for the appropriate jurisdiction as the first element in the access point.
2.
Add the conventional name for the office, e.g., "Attorney," "District Attorney."
3.
Add the name of the particular area served, in parentheses, in a conventionalized form.
Note: In the states of the United States, prosecuting attorneys are agents of the states as a whole; they are not agents of a particular county as publications might suggest.
 
 
 
EXAMPLE
 
110 1#$a United States. $b Attorney (District of Columbia)
110 1#$a United States. $b Attorney (Illinois : Northern District)
110 1#$a New Mexico. $b District Attorney (2nd Judicial District)
110 1#$a Wisconsin. $b District Attorney (Milwaukee County)
 
 
 
[2015-12]
LC-PCC PS for 11.13.1.2
TYPE OF CORPORATE BODY
LC practice/PCC practice: Add the designation in English.
Existing Authority Records
LC practice/PCC practice: Update existing access points not formulated according to these guidelines only when needing to resolve a conflict.
Initialisms and Acronyms
LC practice/PCC practice: If the name chosen for the authorized access point for a corporate body is an initialism or acronym written in all capital letters (with or without periods between them), add a Type of corporate body qualifier to the name. Alternatively, a spelled out form of the name may be used as an Other designation addition (see 11.7.1.6) if such an addition better identifies the corporate body.
 
 
 
EXAMPLE
 
110 2#$a CAST (Group)
410 2#$a C.A.S.T. (Group)
 
111 2#$a CAV (Conference)
 
110 2#$a AAA (Association Art Action)
 
 
 
Ships
LC practice/PCC Practice: When establishing an authorized access point for a ship, add an appropriate designation in English if the name alone does not convey the idea of a corporate body. For powered vessels, the appropriate designation is "(Ship)." If there is more than one powered vessel with the same name, add a more specific term to each to resolve the conflict.
 
 
 
EXAMPLE
 
110 2#$a Ulua (Ship)
Unique name; qualifier added to clarify the meaning
 
110 2#$a Franklin (Aircraft carrier)
110 2#$a Franklin (Steamship)
Two ships of the same name but each of a different type
 
110 2#$a Lexington (Aircraft carrier : CV6)
110 2#$a Lexington (Aircraft carrier : CVA(N) 65)
Two aircraft carriers with the same name
 
 
 
For sailing vessels, the appropriate designation is the type of rigging. Because the term "ship" as applied to sailing vessels refers to a particular rigging, that term is not always appropriate. If there is more than one sailing vessel with the same name and the same rigging, add another addition (e.g., dates of existence, date launched, date ceased, port) to resolve the conflict. If the particular rigging is unknown, use "(Sailing vessel)."
 
 
 
EXAMPLE
 
110 2#$a Rachel Ann (Sloop)
 
110 2#$a Annawan (Brig : 1841-1859)
510 2#$w b $a Annawan (Bark)
Vessel built as a brig in 1841; altered to a bark in 1859
 
110 2#$a Ohio (Bark : 1830-1888)
Vessel built at Baltimore in 1830; lost in Arctic Ocean in 1888
 
110 2#$a Discovery (Ship : Launched 1789)
Merchant ship launched Dec. 19, 1789
 
110 2#$a Centurion (Ship : London, England)
Resource in hand refers to the vessel as being of London
 
110 2#$a Maria (Ship : Active 1799)
Resource in hand is a ship’s receipt dated 1799
 
110 2#$a Columbus (Ship : 1809-1858)
Vessel built in 1809; sold and broken up in 1858
 
110 2#$a Columbus (Ship : 1820-1851)
510 2#$w b $a Columbus (Bark : 1851-1858)
Vessel built in 1820; converted to bark in 1851
 
110 2# $a Columbus (Bark : 1851-1858)
510 2#$w a $a Columbus (Ship : 1820-1851)
Vessel converted to bark in 1851; lost at sea in 1858
 
110 2#$a Columbus (Bark : 1836-1839)
Vessel built in 1836; lost 1839
 
 
 
[2015-01]
LC-PCC PS for 11.13.1.3
PLACE ASSOCIATED WITH CORPORATE BODY
Change in Place
LC practice/PCC practice: When the geographic name changes or the corporate body moves from one locale to another, revise an existing authorized access point to reflect the changed situation.
 
 
 
EXAMPLE
 
110 2#$a Midlands Museum (Zimbabwe)
410 2#$a Midlands Museum (Southern Rhodesia)
Founded in 1972; name of the government changed in 1980
 
110 2#$a Fourth Presbyterian Church (Bethesda, Md.)
410 2#$a Fourth Presbyterian Church (Washington, D.C.)
Founded in 1828 in Washington, D.C.; moved to Bethesda, Md., in 1957
 
 
 
Conflicts
Consult Policy Statement 11.13.1.1 for additional information on conflicts.
Consult Policy Statement 16.2.2.4 for additional information on formulating the names of certain types of jurisdictions.
[2017-03]
LC-PCC PS for 11.13.1.6
TYPE OF JURISDICTION
LC practice/PCC practice: This Policy Statement represents a long-standing practice in the U.S. context, not a principled approach to constructing authorized access points for jurisdictions.
When a sovereign entity and another place of the same name that is not a sovereign entity exist at the same time, do not add a type of jurisdiction to the name of the sovereign entity.
 
 
 
EXAMPLE
 
151 ##$a Italy (Tex.)
151 ##$a Italy
 
 
 
However, use "Washington (State)" as the authorized access point for the state of Washington.
When a succession of jurisdictions would be created under the same name, use one unqualified authorized access point.
 
 
 
EXAMPLE
 
151 ##$a North Carolina
not151 ##$a North Carolina (Colony)
and151 ##$a North Carolina (State)
 
 
 
 
 
 
EXAMPLE
 
151 ##$a Texas
not151 ##$a Texas (Republic)
and151 ##$a Texas (State)
 
 
 
 
 
 
EXAMPLE
 
151 ##$a Hawaii
not151 ##$a Hawaii (Kingdom)
and151 ##$a Hawaii (Republic)
and151 ##$a Hawaii (State)
 
 
 
 
 
 
EXAMPLE
 
151 ##$a India
not151 ##$a India (Dominion)
and151 ##$a India (Republic)
 
 
 
However, when the geographic name added to a name of a jurisdiction to reflect its current status is not appropriate for the earlier entity, use two authorized access points and make additions to each.
 
 
 
EXAMPLE
 
151 ##$a Brabant (Belgium)
151 ##$a Brabant (Duchy)
 
151 ##$a Tuscany (Italy)
151 ##$a Tuscany (Grand Duchy)
 
151 ##$a Venice (Italy)
151 ##$a Venice (Republic : To 1797)
151 ##$a Venice (Republic : 1848-1849)
 
151 ##$a Aragon (Spain)
151 ##$a Aragon (Kingdom)
 
 
 
If an entity that has been treated as an independent state (country) retains the same name when it is absorbed into an existing state (country) or if a part of an existing country becomes an independent state and retains the same name, create an authorized access point for the new entity and retain the authorized access point for the former entity.
 
 
 
EXAMPLE
existing authorized access point
151 ##$a Hong Kong
Reverted to China on July 1, 1997
authorized access point for the new entity
151 ##$a Hong Kong (China)
 
 
 
 
 
 
EXAMPLE
existing authorized access point
151 ##$a Eritrea (Ethiopia)
Declared independence on May 24, 1993
authorized access point for the new entity
151 ##$a Eritrea
 
 
 
When the name of a state, province, or territory of Australia, Canada, or the United States conflicts with the name of a place within the same larger jurisdiction, add the type of jurisdiction to the larger geographic entity.
 
 
 
EXAMPLE
 
151 ##$a New York (N.Y.)
 
151 ##$a New York (State)
not151 ##$a New York
 
 
 
When the name of a state, province, or territory of Australia, Canada, or the United States conflicts with the name of a place in another jurisdiction, qualify only the place in another jurisdiction.
 
 
 
EXAMPLE
 
151 ##$a Alberta (Va.)
 
151 ##$a Alberta
not151 ##$a Alberta (Province)
 
 
 
 
 
 
EXAMPLE
 
151 ##$a Victoria (Tex.)
 
151 ##$a Victoria
not151 ##$a Victoria (State)
 
 
 
 
 
 
EXAMPLE
 
151 ##$a Virginia (Minn.)
 
151 ##$a Virginia
not151 ##$a Virginia (State)
 
 
 
Make an addition to the authorized access point for a jurisdiction that does not conflict with the authorized access point for another jurisdiction when
1.
the authorized access point for the jurisdiction is the same as the name of a geographic area but the territory governed by the jurisdiction varies significantly from the geographic area;
 
 
 
EXAMPLE
 
151 ##$a West Indies (Federation)
The authorized access point for Federation of the West Indies, which consisted only of some of the British possessions in the Caribbean
 
151 ##$a Pacific Islands (Trust Territory)
The authorized access point for Trust Territory of the Pacific Islands, which consists of the Caroline, Marshall, and Mariana Islands
 
 
 
2.
the authorized access point for the jurisdiction is the same as the name of a geographic area but the name of the jurisdiction has ceased.
 
 
 
EXAMPLE
 
151 ##$a New Guinea (Territory)
The authorized access point for Territory of New Guinea, which ceased in 1942
 
 
 
[2014-08]
LC-PCC PS for 11.13.1.8
NUMBER, DATE, AND LOCATION OF A CONFERENCE, ETC.
Authority Records for Ongoing Conferences
LC practice/PCC practice: For ongoing conferences, separate authority records may be created for the collective conference (typically made when cataloging a serial), an individual instance of an ongoing conference (typically made when cataloging a monograph), or both. These records may coexist in the LC/NACO authority file. A record for the collective conference should always be made to connect the earlier and later names of the collective conference.
[2013-05]
LC-PCC PS for 11.13.1.8.1
AUTHORIZED ACCESS POINT FOR A SINGLE INSTANCE OF A CONFERENCE, ETC.
Individual Instance of an Ongoing Conference
LC practice/PCC practice: When creating an authority record for an individual instance of an ongoing conference, the additions for number, date, and location of a conference, etc. are given in the authorized access point. Variant access points may be given for variant names of the individual conference, such as acronyms for a spelled-out form. Generally do not connect an individual instance of an ongoing conference to the earlier or later instance of the conference using a 5XX field, or to an authority record for the collective conference.
 
 
 
EXAMPLE
 
111 2#$a ILCLI International Workshop on Cognitive Science $n (10th : $d 2010 : $c San Sebastián, Spain)
411 2#$a International Workshop on Cognitive Science $n (10th : $d 2010 : $c San Sebastián, Spain)
411 2#$a IWCogSc-10 (Workshop) $n (10th : $d 2010 : $c San Sebastián, Spain)
 
 
 
[2016-03]
LC-PCC PS for 11.13.1.8.1
FIRST EXCEPTION
LC practice/PCC practice: When adding the name of an institution instead of a local place name as the location of a conference, record the preferred name for the institution, minus any additions used in the institution’s authorized access point (see RDA 11.5).
[2013-05]
LC-PCC PS for 11.13.1.8.2
AUTHORIZED ACCESS POINT FOR A SERIES OF CONFERENCES, ETC.
Collective Treatment of an Ongoing Conference
LC practice/PCC practice: Connect authority records for earlier and later names of the collective conference using 5XX fields. Include a 667 field shown in the example below when there are authority records for both collective and individual instances of an ongoing conference. Variant access points may be given for variant names of the collective conference.
 
 
 
EXAMPLE
 
111 2#$a ILCLI International Workshop on Cognitive Science
411 2#$a International Workshop on Cognitive Science
411 2#$a Institute for Logic, Cognition, Language, and Information International Workshop on Cognitive Science
411 2#$a IWCogSc (Workshop)
511 2#$w a $a International Colloquium on Cognitive Science
667 ##$a See also related access points for individual instances of this conference which include specific information about the number, date, or place of the individual conference.
 
 
 
[2015-09]