Name Authorities: General Field Specific Guidelines

043 - Geographic Area Code

Include in records for geographic names, which are tagged 151, and reside in the LC NACO file.

1XX and 4XX

Include commas in a series of words except before an ampersand (but also include a comma before an ampersand if such a comma is found in actual usage), in order to maintain consistency with pre-existing authorized access points, headings, and references. Include a comma before the final "and" in a series of words. When updating an existing authority record, add commas according to this practice only to records that were created by GPO. Such records will have DGPO in field 040ǂa.

4XX – See From Tracing

Although the inclusion of variant access points (4XX see from tracings) became optional with the implementation of RDA (6.2, 9.2, 11.2), GPO includes these whenever these are readily available. Include variant access points that users are likely to search for. However, do not make a variant of a variant. LCRI 26.3 is still appropriate: "Generally, trace a reference from variant forms of entry that apply to the name chosen for the heading. However, do not trace a reference that would normalize to the same form as the heading on the same record or to the same form as a heading on another record. For variant forms of a name, generally, trace only one reference from each variant, normally, constructing it in the form in which it would be constructed if chosen as the heading." LCRI 26.1: "In general, construct a reference in the same form in which it would be constructed if chosen as the heading."

"All elements of hierarchy used in references must also be established ... References made through the parent body must use the established form of the parent body!" (NACO Training for OCLC Libraries, rev. May 2001. Program for Cooperative Cataloging, Library of Congress)

 

For more explanations, see:

• "FAQ on Establishing Corporate Names for NACO" on the NACO Web site: "Why can't a cross-reference for a subordinate body ..."
• LCRI 26.1, 26.3
• DCM Z1: Introduction, Name Authority Records (NARs) (Note: In Cataloger's Desktop, this subsection of the Introduction does not appear in the left-hand vertical table of contents pane. It can be accessed, however, once the Introduction is opened.)

For a former authorized access point: See the "FAQ on creating Personal Name Authority Records (NARs) for NACO" on the NACO Web site: Questions 12-13. Make a see reference for the old valid form of heading, with ǂw nnea, unless the reference itself is a valid RDA variant access point, in which case use ǂw nne. In case of doubt, use ǂw nnea. Take into account the rules of NACO normalization.

5XX – See Also From Tracings

Consult and follow LC-PCC PS 32.1 and 32.1.1.3. For earlier/later relationships, follow this sentence of the LC Practice: "Make sequential references to connect immediately adjacent bodies only, thus creating a chain leading from one authorized access point to another." When creating a new authority record, or adding a 5XX field to an existing record, use subfield ǂi in conjunction with ǂw code "r" for relationship designators, rather than using the earlier/later values in subfield ǂw. However, pre-existing 5XX references in AACR2 format (i.e., ǂw values without ǂi) do not need to be changed to RDA when updating or recoding the record. They are acceptable under PCC standards.

670 – Source Data Found

Consult and follow DCM Z1: Field 670, unless instructed differently below. Also consult the NACO Participants' Manual, Section I. New Authority Records, 670 Field. Always include at least one 670 field. Generally, the first 670 field cites the resource for which the authorized access point is being established. Include, at a minimum, the 670 for this resource.

A 670 field must be used to support information used as part of an access point in 1XX and 4XX. For more information on whether to use a 670 field or a ǂv in another field, see the section: Name Authorities, RDA, General Policies: Source of Information: 670 vs. ǂv in the 046 and 3XX optional fields.

ǂa - Citing the source of the information found

When citing an agency or corporate body Web site, etc. do not use pronouns or the possessive form in the ǂa. Instead, prefer to use the name itself, followed by the date viewed, without the phrase "viewed" or "viewed on." Since Web sites are usually uncataloged, it is not necessary to use the same form of the name that appears in the 1XX field as you would when citing an authorized access point for a work. Instead, you may use the form of the name that appears prominently on the Web site.

ǂb - Citing the location of the information found

Include in ǂb the specific location(s) of the information found. Use the list of examples and follow the instructions in the NACO Participants' Manual: New Authority Records, 670 - Sources found, Citing location of data found. Use your own location term when needed.

In past practice, when the title was taken from the cover, caption, or any source, the location may have been given as "title page" or "t.p." We now cite the specific location. Do not change the location in older records.

Near the bottom of the DCM Z1 section on the 670 field, is a section headed “LC database.” GPO will usually cite the OCLC database, instead. In addition, GPO will substitute the RDA term “access point" for “heading” when citing OCLC.

678 - Biographical or Historical Data

Include if information is readily available and does not require significant time to construct.

Remember to use the appropriate code for the first indicator

• 0 - Biographical sketch
• 1 - Administrative history

781 - Subdivision Linking Entry-Geographic Subdivision

Include in records for geographic names, which are tagged 151, and reside in the LC NACO file.