Annotated Subject Authority Proposal Form for Geographics

     ______ (May Subd Geog)
     ______ (Not Subd Geog)
     ______ (No Decision)  
                
Note: Check or leave as set to "No Decision"

008/39: c [supplied on form]

053: LC class number or span (with qualifier) if needed (SCM H365)

• Note: 053 fields are given only for archaeological sites and extinct cities

151: Proposed new geographic heading: [Distinctive name] [Generic term][geographic qualifier, if needed]
(SCM H690, H810)

• Example: 151 Mendocino, Lake (Calif.)

451: [Variant or alternative names]
(SCM H690)

• On variant names generally use the same qualifier as on the heading
• Rearranged terms, if appropriate (inverted vs. direct order; e.g., 451 Lake Mendocino (Calif.))
• Arrange alphabetically
• Provide justification in 670 fields for variants or alternatives

550 (BT): Broader term: [Type of feature]($z or --)[Country or first order division]
(SCM H690)

• Example: 550 Lakes $z California

551 (BT): Broader island group or mountain range if applicable])

• Make up to three BTs of the first type
• Arrange alphabetically (if more than one)
• Must be established or accompanying proposal must be sent
• Related term references are made only between coextensive feature and park headings
• No narrower terms are traced; Add proposed heading as BT on existing narrower terms

667: Generally used when the 781 field is not appropriate (see 781 field guidelines below)

• Such as when the 151 heading is a celestial body or a geographic entity in a city (cf. SCM H836)
• Supply a 667 field with this note: This heading is not valid for use as a geographic subdivision.

670 (Work cat.) Title of item in hand given in form: Lastname, Forename initials. Title proper, date: $b p. (data found) additional location (data found)

• Include subtitle only if term or variant appears there
• Corporate bodies, conferences, m.e. or title may be abbreviated. (cf.: SCM H200, sec. 9.a)

670 ( Sources found): Additional sources

• Such as to justify heading or UF references
• Repeatable field
• cf.: SCM H202 for substance; H203 for citation style

Examples of citations:

• Reference source: $b p. number (data found)
• Geonet or GNIS, [date searched] $b (approved form, type of feature, coordinates: _____variants:_______ )

Examples of citation to show conflict:

• Web. geog. $b (Coos Bay: 1. Inlet on coast of Coos Co.; 2. City, Coos Co.)
• GNIS, June 16, 1999 $b (McGuire Creek, stream, McCone Co.; also McGuire Creek, Lincoln Co.)

675 (Sources not found): Sources checked with no relevant data on proposed heading or references found

• Field not repeatable
• Multiple sources are listed in repeated $a subfields
• cf: SCM H203, sec. 9.c

680 (Scope Note): Here are entered works on... ( SCM H400)

• A scope note may be needed to clarify geographic extent or usage of heading; most frequently needed for geographic regions

781 (Geographic subdivision): Use only if the 151 heading may be used as a geographic subdivision (If 151 heading contains subdivision, do not apply).

• Supply the geographic subdivision form in one or two successive $z subfields according to SCM H836
  • Example: 781 $z California $z Mendocino, Lake
• If the geographic heading may not be used as a subdivision, supply standard 667 note as indicated above.

952: ..... bib. records to be changed (Optional, LC liaison will search LC database and fill in)

952: (LC pattern or SCM Memo): (SCM H202, sec. 1)

• Not routinely neeeded for standard geographic names
• Possible use: to justify additional or unusual qualifier
• SCM memos may be cited: H1925 for parks; etc.

952: (Comments): Informational notes to SACO Liaison

• Example: "Code as provisional; proposed in English because vernacular form not found; New class # also proposed sent by fax [date]."

953: yz00 [supplied on form]