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 16.2.2.5
NAMES FOUND IN A NON-PREFERRED SCRIPT
LC practice/PCC practice: If the name of the place is in a language written in a non-Latin script, transliterate the name according to the ALA-LC romanization table for that language.
If GEOnet contains an approved name that is transliterated using a different standard than the ALA-LC romanization table for that language, use the ALA-LC form of transliteration in the authorized access point. Consider making a variant access point for the BGN approved form.
 
 
 
EXAMPLE
GEOnet
 Alzamay (Approved); Алзамай (Non-Roman Script)
 
151 ##$a Alzamaĭ (Russia)
451 ##$a Alzamay (Russia)
 
 
 
[2017-07]
LC-PCC PS for 16.2.2.5
ALTERNATIVE
LC practice/PCC practice for Alternative: Do not apply.
[2012-10]
LC-PCC PS for 16.2.2.6
DIFFERENT LANGUAGE FORMS OF THE SAME NAME
LC practice/PCC practice: Choose a form of name in English if one is in general use, determining this from reference sources in English.
[2017-03]
LC-PCC PS for 16.2.2.7
CHANGE OF NAME
LC practice/PCC practice: For changes to place names, see Policy Statement 32.1.1.3. When the name of a smaller place remains the same, but the name of the larger place changes, use the current name of the larger place in the qualifier for the smaller place. See Policy Statement 16.4.2 for instructions on recording the variant form using the previous name of the larger place.
[2015-12]
LC-PCC PS for 16.2.2.9.2
PLACES IN A STATE, PROVINCE, TERRITORY, ETC.
Places on Islands
LC practice/PCC practice: Also apply this RDA instruction to places on islands.
 
 
 
EXAMPLE
 
151 ##$a Avalon (Calif.)
 
 
 
[2012-10]
LC-PCC PS for 16.2.2.10.1
PLACES IN ENGLAND, NORTHERN IRELAND, SCOTLAND, AND WALES
Places on Islands
LC practice/PCC practice: Also apply this RDA instruction to places on islands.
 
 
 
EXAMPLE
 
151 ##$a Beaumaris (Wales)
 
 
 
[2013-05]
LC-PCC PS for 16.2.2.12
PLACES IN OTHER JURISDICTIONS
Israel, Jordan, Syria
LC practice/PCC practice: Do not add the name of the country to places that prior to 1967 were in Jordan or Syria and that are currently within the administered territories of Israel.
For Jerusalem, use “Jerusalem.”
[2013-05]
LC-PCC PS for 16.2.2.12
ALTERNATIVE
LC practice/PCC practice for Alternative: Apply the alternative only to places in Malaysia. Defer application to other countries until projects can be developed to change existing records.
[2013-05]
LC-PCC PS for 16.2.2.13
PLACES WITH THE SAME NAME
Conflicts (New Authority Records)
LC practice/PCC practice: Apply either RDA 16.2.2.13 or RDA 11.13.1.6 (type of jurisdiction) to resolve conflicts in preferred names for geographic names and names of governments not already resolved by the additions called for by RDA 16.2.2.9RDA 16.2.2.13. Conflict in place names is not restricted to those already represented in the file against which the searching and cataloging is being done. Instead, if there is no existing conflict in that file, search gazetteers, etc., to determine if two or more places within the same jurisdiction have the same name or if two or more places with the same name would bear the same qualifier for the larger place.
Conflicts (Existing Authority Records)
LC practice/PCC practice: Change the qualifier for the larger place in an existing authority record only to resolve a conflict with a new authority record being established. For instructions on changing the qualifier for the larger place because of a name change, see Policy Statement for 16.4.2.
U.S. Townships
LC practice/PCC practice: If a name of a U.S. township (called “towns” in some states) conflicts with the name of another township within the same state, add the preferred name for the county to each name. Consult GNIS to determine if there is more than one township with the same name in the same state: http://geonames.usgs.gov/pls/gnispublic.
 
 
 
EXAMPLE
 
151 ##$a Spring (Berks County, Pa. : Township)
 
151 ##$a Spring (Centre County, Pa. : Township)
 
 
 
See Policy Statement for 16.4 for further instructions on establishing authorized access points for townships.
Hawaii
If local places in Hawaii conflict, add to each name the authorized access point for the island on which the place is located rather than the authorized access point for the county.
[2014-02]
LC-PCC PS for 16.2.2.14
PLACES WITHIN CITIES, ETC.
LC practice/PCC practice: For places within cities, add the city in parentheses. Use the access point reflecting its current status for the entire period of the place within the city’s existence, including any earlier independent existence it may have had, provided the name remains constant (see RDA 11.3.3.4 and RDA 11.13.1.3). Consider making a variant access point from the name of the place within the city as a subheading of the name of the city. See Descriptive Cataloging Manual Z1 667 for providing notes indicating that the authorized access points for names of city sections, neighborhoods, districts, etc., are not appropriate for use as geographic subdivisions.
 
 
 
EXAMPLE
 
151 ##$a Borgfelde (Hamburg, Germany)
410 1#$a Hamburg (Germany). $b Borgfelde
 
151 ##$a Georgetown (Washington, D.C.)
410 1#$a Washington (D.C.). $b Georgetown
 
151 ##$a Greenwich Village (New York, N.Y.)
410 1#$a New York (N.Y.). $b Greenwich Village
 
151 ##$a Loop (Chicago, Ill.)
410 1#$a Chicago (Ill.). $b Loop
 
151 ##$a Rive gauche (Paris, France)
410 1#$a Paris (France). $b Rive gauche
 
 
 
If the place within the city once had an independent existence but changed its name when it was absorbed into the larger place, create an authorized access point for each name.
 
 
 
EXAMPLE
For resources issued before 1975
151 ##$a Endersbach (Germany)
For resources issued after 1974
151 ##$a Weinstadt-Endersbach (Weinstadt, Germany)
410 1#$a Weinstadt (Germany). $b Weinstadt-Endersbach
 
 
 
If the place within the city once had an independent existence and did not change its name when it was absorbed into the larger place, use the access point reflecting its current status for the entire period of the place. See Policy Statement for 16.4.2 (Choice of larger place) for instructions on making a variant access point using the qualifier for the earlier period.
If the place within the city is within another place within the city, add the name of the city, not the name of the other place within the city.
 
 
 
EXAMPLE
 
151 ##$a Wahn (Cologne, Germany)
not
 
151 ##$a Wahn (Porz, Cologne, Germany)
 
 
 
[2013-12]
LC-PCC PS for 16.4
CONSTRUCTING ACCESS POINTS TO REPRESENT PLACES
LC practice/PCC practice: The following instructions represent LC/PCC practice for the areas below.
Berlin
Use “Berlin, Germany” as the qualifier in authorized access points for corporate bodies.
Great Britain
Follow the British Library’s practice of using “Great Britain” as the conventional name for the government of the United Kingdom.
London
Use “London, England” as the qualifier in authorized access points for corporate bodies located in the City of London or in an inner borough. Also use “London, England” as the qualifier for a corporate body located in an outer borough if the body is commonly associated with London rather than with the name of the particular outer borough. (The inner London boroughs are Camden, Greenwich, Hackney, Hammersmith and Fulham, Islington, Kensington and Chelsea, Lambeth, Lewisham, Southwark, Tower Hamlets, Wandsworth, and the City of Westminster.)
Taiwan
Use “China (Republic : 1949- )” as the authorized access point for the government of this name. Use “Taiwan” for the province of Taiwan only as a location qualifier.
U.S. Townships
For U.S. townships (called “towns” in some states) that encompass one or more local communities and the surrounding territory, apply RDA 16.2.2.8.1 to determine whether the term “township” or “town” should be included as part of the name. If such a term is not included in the name, add the term after the name of the state, etc. in the authorized access point. Generally consider U.S. townships listed in GNIS in the form “Township of” or “Town of” to fall under the first condition in RDA 16.2.2.8.1 and establish them without the first part of the name indicating a type of jurisdiction.
If the jurisdictional term is not part of the preferred name, add it as an addition to the authorized access point. Consider making a variant access point for the form of name that includes the type of jurisdiction.
 
 
 
EXAMPLE
BGN GNIS
 Township of Kintire
 
151 ##$a Kintire (Minn. : Township)
451 ##$a Township of Kintire (Minn.)
 
 
 
 
 
 
EXAMPLE
BGN GNIS
 Town of Milo
 
151 ##$a Milo (Me. : Town)
451##$a Town of Milo (Me.)
 
 
 
If there is more than one township with the same name in the same state, apply Policy Statement for 16.2.2.13.
For U.S. places with the word “town” or “township” in the name that do not encompass multiple local communities, apply RDA 16.2.2.9.2, etc.
 
 
 
EXAMPLE
BGN GNIS
 Godfrey [populated place]
 Village of Godfrey [civil]
 Township of Godrey [civil]
151 ##$a Godfrey (Ill.)
451 ##$a Village of Godfrey (Ill.)
451 ##$a Township of Godfrey (Ill.)
GNIS typically provides both a civil and a populated place listing for the same jurisdictional name
 
 
 
Washington, D.C.
Use “District of Columbia” as the authorized access point for the government of this name.
[2014-02]
LC-PCC PS for 16.4.1
AUTHORIZED ACCESS POINTS FOR THE PLACE
LC practice/PCC practice: The following instructions represent LC/PCC practice for the categories below.
Ambiguous Entities
For city sections, collective settlements, communes, conservation districts, jurisdictions, ancient places other than cities, park districts, recreation districts, sanitation districts, utility districts, and water districts, consult Descriptive Cataloging Manual, Z1.
Military Installations
Treat military installations (forts, bases, camps, airfields, and Coast Guard stations but not shipyards) as local places.
Add as a qualifier the country, state, province, etc., that would have been added to a city or town in the same place, even if the installation is located outside the country that controls it.
 
 
 
EXAMPLE
source
 Fort Hood, Texas
authorized access point
151 ##$a Fort Hood (Tex.)
source
 March Air Force Base, Calif.
authorized access point
151 ##$a March Air Force Base (Calif.)
source
 Yokosuka Naval Base
authorized access point
151 ##$a Yokosuka Naval Base (Japan)
 
 
 
Indian Tribes in the United States
Tribes recognized by the U.S. government are independent, autonomous political entities with inherent powers of self-government; they possess sovereignty and are equal to national governments. There are over 500 recognized tribes within the continental United States. Nearly all federally recognized tribes have jurisdiction over some delimited area of land, a geographic place, although land and area vary with each tribe.
Consult the official list created and maintained by the Department of the Interior, Bureau of Indian Affairs to determine the preferred name for the tribe. The list of federally recognized tribes, entitled: Indian Entities Recognized and Eligible to Receive Services from the United States Bureau of Indian Affairs is available online at the Bureau's website at http://www.bia.gov/DocumentLibrary/index.htm. It may also be accessed through the Federal Register website. This source may be cited as “BIA Indian Entities.” If a name for a tribal entity is not found in the BIA list, conduct additional research and/or construct the authorized access point from information on the resource being cataloged.
 
 
 
EXAMPLE
 
151 ##$a San Carlos Apache Tribe of the San Carlos Reservation, Arizona
670 ##$a BIA Indian Entities, 2005, Dec. 14, 2005 $b (San Carlos Apache tribe of the San Carlos Reservation, Arizona)
 
 
 
Some tribes have federally-approved names that sound as if the name were for a populated place rather than a tribe. Confusion may result when there actually is a populated place of that name. In such cases, the tribe and the populated place are separate entities.
 
 
 
EXAMPLE
 
151 ##$a Native Village of Nunapitchuk
Tribe
 
151 ##$a Nunapitchuk (Alaska)
Populated place
 
 
 
[2017-01]
LC-PCC PS for 16.4.2
VARIANT ACCESS POINT FOR THE PLACE
Choice of Larger Place
LC practice/PCC practice: When adding the name of a larger place as a qualifier, use the current name of the larger place (see RDA 16.2.2.9-RDA 16.2.2.12), and apply Appendix B.11, as applicable. If the smaller place existed when the larger place had an earlier name, and the name in the resource pertains to the earlier period, consider recording a variant access point from the form that shows the earlier name of the larger place if the qualifier is appropriate for the smaller place.
 
 
 
EXAMPLE
 
151 ##$a Minsk (Belarus)
451 ##$w nne $a Minsk (Byelorussian S.S.R.)
Variant access point that was previously used as authorized form. Byelorussian S.S.R. became Belarus
 
151 ##$a Torit (South Sudan)
451 ##$w nne $a Torit (Sudan)
Variant access point that was previously used as authorized form. Torit became part of the new country South Sudan
 
151 ##$a Charles Town (W. Va.)
451 ##$a Charles Town (Va.)
Variant access point that was not previously used as authorized form
 
151 ##$a Ballard (Seattle, Wash.)
451 ##$a Ballard (Wash.)
Variant access point that was not previously used as authorized form. The city Ballard became a city section of Seattle
 
 
 
Military Installations
LC practice/PCC practice: Construct variant access points from the name as a subheading of the country that controls it and as a subheading of the military branch to which it belongs.
 
 
 
EXAMPLE
 
151 ##$a Fort Hood (Tex.)
410 1#$a United States. $b Fort Hood
410 1#$a United States. $b Army. $b Fort Hood
 
151 ##$a March Air Force Base (Calif.)
410 1#$a United States. $b March Air Force Base
410 1#$a United States. $b Air Force. $b March Air Force Base
 
151 ##$a Yokosuka Naval Base (Japan)
410 1#$a United States. $b Yokosuka Naval Base
410 1#$a United States. $b Navy. $b Yokosuka Naval Base
 
 
 
[2015-12]