Annotated SUBJECT AUTHORITY PROPOSAL FORM

008/06: See: SCM H364

     ______ (May Subd Geog)(select if 150 may have geographic orientation, cf. H364, sec. 1)
     ______ (Not Subd Geog)(select if 1XX belongs to one of the types specified in H364, sec. 2)
     ______ (No Decision)  (select if 1XX is 151 geographic heading or other type of heading 
	                    specified in H 364, sec. 3) 

Note: If in doubt, check "No Decision"

008/39: c [supplied on form]

040: $a________$b eng $c DLC (provide institution's MARC 21 identification code in subfield a)

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

• Repeatable field
• Qualifier needed if more than one 053
• Arrange alphabetically by class number.

1XX: Proposed new heading (See: SCM H187; H290-H360) or existing name or subject heading with a new non-free-floating subdivision

4XX: Variant or alternative terms (See: SCM H373)

• Variant forms
• Rearranged terms, if appropriate (inverted vs. direct order)
• Arrange alphabetically
• Provide justification in 670 fields for variants or alternatives
• Note: Heading in subfield $a must be a valid heading if there is more than one subfield

5XX (BT): Next broader term in hierarchy (See: SCM H370)

• Arrange alphabetically (if more than one)
• Must be established or accompanying proposal must be sent
• Note:5XX (NT) Narrower terms are added as BT on existing narrower term.

5XX (RT): Related term (See: SCM H370)

• Use sparingly
• Arrange alphabetically (if more than one)
• Reciprocal (term must be be added to each subject authority record)

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
• FAQ on subject heading proposals is available on the SACO web site

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

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

781 (Geographic subdivision): Use only if the 1XX is a 151 (without subdivision) that may be used as a geographic subdivision.

• Supply the geographic subdivision form in one or two successive $z subfields according to SCM H836
• If the geographic heading may not be used as a subdivision, supply a 667 field instead 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): (cf.: SCM H202, sec. 1)

• Cite analogous existing heading to justify form, adjectival qualifier, etc.
• Cite H memo for rules; H1334 for buildings; H1925 for parks; etc.

952: (Comments): Informational notes to SACO Liaison

• Example: "New class # also proposed sent by fax [date]."

953: yz00 [supplied on form]