Skip Navigation Links The Library of Congress >> Cataloging >> PCC Home
NACO: Program for Cooperative Cataloging
  NACO Home >>
Find in

Frequently Asked Questions on Establishing Geographic Names for NACO

For geographic names used as jusrisdictions see the FAO on Corporate Names
  1. When establishing geographic names can we use the apostrophe and quotation marks to represent degrees, minutes, and seconds when supplying the coordinates in the 670s?
  2. Why is it when a large jurisdiction changes its name a see-also is made from the old form of name to the current form but when adding that new jurisdiction's name to a smaller jurisdiction a see reference is made ...?
  3. Why are geographic names for some countries not changed even though the new name is in common usage?
  4. Are PCC catalogers required to search GEOnet or GNIS in order to establish a geographic name?
  5. Do all geographic names used as qualifiers for corporate headings need to be established?
  6. What is the underlying principle of whether a geographic name is established through NACO or through SACO?
  7. When should catalogers add a 667 note to an NAR to show subject usage, such as when there is a earlier/later linear jurisdictional change?
  1. When establishing geographic names can we use the apostrophe and quotation marks to represent minutes and seconds when supplying the coordinates in the 670s? What about the degree symbol --can we use that?

    No to both. LCRI 1.0E lists degrees, minutes, and seconds as exceptions to the use of conventional diacritical marks. Degrees are represented by the superscript zero, minutes by the miagkii znak and seconds by the tvërdyi znak. This instruction applies to usage in bibliographic description but LC and PCC practice is to apply this convention to bibliographic and authority records. Note that recent extensions to the ALA character set has been approved for use in MARC 21 formatted records; however, LC has not implemented its use.

  2. Why is it when a large jurisdiction (e.g., country or state) changes its name a see-also (earlier/later) is made from the old form of name to the current form but when adding that new jurisdiction's name to a smaller jurisdiction (e.g., state or city) within that country a see reference is made (4XX)?
    Example 1: Example 2: Example 3:
    151 $a Southern Rhodesia 151 $a Salisbury (Zimbabwe) 151 $a Salisbury (Zimbabwe)
    551 $wb$a Zimbabwe 451 $wnne$a Salisbury (Southern Rhodesia) 551 $wb$a Harare (Zimbabwe)

    (Note: complete reference structure not given in these examples)

    In example 1 the jurisdiction changed names thus an earlier/later see-also reference is made on the NAR. In example 2 the smaller jurisdiction (city, state, etc.) has not changed its name, what has changed is the cataloger's addition to the name; therefore, one cannot apply AACR2 23.4B but instead LCRI 23.4B is applied. In other words, the name of the city had not changed at the time the larger jurisdiction changed names; thus, the earlier form of the heading is converted into a see reference (note that it is coded "nne" in the subfield $w to denote an earlier AACR2 form of name). In example 3 the see-also (earlier/later) reference is made because the name of the smaller jurisdiction has now changed.

  3. Why are geographic names for some countries not changed even though the new name is in common usage (e.g., Myanmar vs. Burma)?
    The Library or Congress does not change a country's name unless the new name is recognized by the United States Board on Geographic Names (BGN) (cf. LCRI 23.2).
  4. Are PCC catalogers required to search GEOnet or the Geographic Names Information System GNIS in order to establish a geographic name?
    Yes, note that according to LCRI 23.2 place names in the U.S. must be based on the form found in GNIS or a recent edition of the Rand McNally Commercial Atlas & Marketing Guide (the latter only if access to the web is not an option). For most foreign place names the LCRI states that these may be established using the item being cataloged with consideration of the form found in the GEOnet Names Server (GNS) or an appropriate gazetteer if access to the web is not an option.

    Note: LCRI 23.2 stipulates exceptions to the above statement for place names in Australia, New Zealand, Canada and Great Britain.

    Note also: The Web Resources for SACO Proposals page has a large number of links to electronic geographic names sources, including official gazetteers for Australia, N.Z., and Canada, that may be used for establishing geographic names for NACO.

  5. Do all geographic names used as qualifiers for corporate headings need to be established?
    Yes. (Cf. LCRI24.4C "Non-conflicts" paragraph1c and 2c).
  6. What is the underlying principle of whether a geographic name is established through NACO or through SACO?
    A geographic name heading (151) may be established in either the subject or the name authority file; however, it is only the geographic heading established in the name authority file that is also eligible for use as a jurisdiction or government heading (110). Therefore, jurisdictional status is the primary difference between geographic name and subject headings. Geographic subject headings are typically geographic features, regions, and collective names for groups of jurisdictions that do not also function as national governments (cf. SCM H690 and the Alphabetic list of ambiguous entities SCM H405)
  7. When should cataloger's add the 667 note to the NARs to show subject usage, such as when there is a earlier/later linear jurisdictional change?
    According to DCM Z1, 667 pages "Upon creating an earlier/later heading for a geographic name, catalogers must notify CPSO to add a 667 subject usage note to the earlier name and adjust the appropriate 008 fields". Coop has created a form to facilitate this notification at: http://www.loc.gov/catdir/pcc/naco/nar667form.html Note that for jurisdictional mergers or splits a 667 subject usage note is not required, see SCM H710.
Top of Page Top of Page
  NACO Home >>
Find in
  The Library of Congress >> Cataloging >> PCC Home
  January 3, 2008
Contact Us