| MARC21 | Description | SCM Memo |
| | | | H 200 |
| 008: 02 | 008/06. Most headings should be authorized to be divided geographically unless they are inherently goegraphic in nature and MARC-tagged as a 151 or they represent extreme concepts. If the new heading should be divided geographically, place an X on the May Subd Geog line. Should you be unable to determine the appropriate response, please leave the field intentionally blank. | | H 194; H 364 |
| | "i" (May Subd Geog) | | |
| | "-" (Not Subd Geog) | | |
| 25: | YZ00 | | Cooperative Cataloging Team code |
| 29: | C | | 008/39 |
| 040: ___ $DLC | NdU $DLC (ex.) | | MARC21 code (formerly NUC symbol) |
| 053: | LC Class number of span with (Qualifier) if needed. Many headings do not require a 053. Repeatable field; Qualifier needed if more than one 053 | | H 196; H 365 |
| 150: | Proposed new topical heading. Indicate the proposed heading in this area. Propsoing a subject heading for inclusion in LCSH must be supported by adquate, appropropriate authority research demonstrating clear preference for the proposed form. | | H 187; H 290-H 360 |
| 151: | Proposed new geographic heading. [distinctive name] [generic term] ([geographic qualifier, if needed]) | | H 690 |
| | - OR - Existing name or subject heading -- New non-free-floating subdivision. Tag for $a subfield | | |
| 450: Cross-ref or Used For-ref (UF) | Variant or alternative terms. Rearranged terms, if appropriate. Arrange alphabetically. Provide authority in 670 fields for variants or alternatives; $a subfield must be a valid heading if there is more than one subfield. | | H 195; H 373 |
| 451: | [alternative or variant names] ([geographic qualifer]). Generally use the same qualifer as on the headings. Arrange alphabetically. Provide authority in 690 fields for vaiants or alternatives. | | H 690 |
| 55_ BT: | Next broader term in hierarchy. Must be established or proposed. Arrange alphabetically | | H 370 |
| 55_ RT: | Related term. Reciprocal must be supplied. Use sparingly. No narrower terms are traced. Add proposed heading as BT on existing narrower terms. | | H 370 |
| 550 BT: | [type of feature, etc.]--[country or first order division] | | H 690 |
| 551 BT: | [Broader island group or mountain range, if applicable]. Make up to three BTs of the first type. Arrange alphabetically. Related term references are made only between co-extensive feature and park headings. No narrower terms are traced. Add proposed heading as BT on existing narrower terms. | | H 690; H 1925 only related terms |
| 670 Work cat.: | Lastname, F. I. Title proper, date: p. (...) (data found) additional location (additional data). Include subtitle if term or variant appears there. Titles, corporate bodies, conferences, etc., may be abbreviated. Provide the title of the item being cataloged which prompted the need for the subject heading. Should the heading itself not be found in the title, indicate where in the item the term concept, name, etc. was found and if possible a sentence or two from the item describing or explaining the heading in question. * | | H 200 sec. 8.a. |
| 670 (Sources found): | Additional sources to justify heading or UF references. Repeatable field. | | H 202 for substance; H 203 for citation style |
| | Reference source: p. (...) (data found). Location may be omitted if the source is alphabetically arranged | | |
| | Phone call to (...), date (data) | | |
| | XYZ Web site, date accessed (data found) | | |
| | LC database, date accessed (titles: data; hdg.: data) | | |
| | Old catalog heading ( ) | | |
| | GEOnet or GNIS, [date searched] (approved form, type of feature, coordinates; variants: Exampels of citation to show conflict: Web. geog. (Coos Bay: 1. Inlet on coast of Coos Co. 2. City, Coos Co.). GNIS, June 16, 1998 (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. Not a repeatable field; multiple sources are listed in repeated $a subfields. | | H 203 sec. 9 |
| 680 Here are entered works on ... | Scope note. Include in this area the text of a note to define or limit the use of a particular heading. A scope note may be needed to clarify geographic extent or usage of heading; most frequently needed for geographic regions | | H 400 |
| 781: $z $z | Subdivision heading linking entry -- geographic subdivision. If 1XX is a 151 supply the 781 field according to SCM H836 (note there is no #a in 781. Geographics used directly have one subfield #z; geographics used indirectly have two subfield z's). | | H 200 sec. 12; H 830 |
| 667: | Note. If 781 is not appropriate for the 151 heading (e.g. a celestial body or a geographic entity in a city; cf. SCM H 836) supply a 667 field with this note: This heading not valid for use as a geographic subdivision. | | H 836 |
| 952: ... bib. records to be changed | LC liaison will search LC database | | |
| LC pattern or SCM Memo: | Cite analogous existing heading to justify form, adjectival qualifier, etc. Cite H memo for rules: H 1334 for buildings; H 1925 for parks; etc. Not routinely needed for standard geographic headings. Possible use: to justify additional or unusual qualifier. | | H 187; H 290-H 360 |
* "It is seldom acceptable to cite only the work cataloged as authority for a new concept, except in case of certain named entities such as obscure archaeological sites, brand name products, computer languages, etc. Although the concept may have been found only in the work being cataloged, other sources appropriate to the subject area in question should be cited to demonstrate that the concept was properly investigated." 
TechServ