Skip to main content
An official website of the United States Government Here’s how you know
Official websites use .gov A .gov website belongs to an official Government organization in the United States.
Secure .gov websites use HTTPS A lock or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
  • GPO
    • U.S. Government Publishing Office
    • govinfo
    • U.S. Government Bookstore
    • Ben's Guide to the U.S. Government
GPO
  • Contact Us
  • Login
FDLP
  • Depository Tools
    • Federal Depository Library Directory
    • askGPO
    • FDLP Data Manager (FDM)
    • Claims
    • Depository Selection Information Management System (DSIMS)
    • Print Distribution Dashboard
    • Item Lister
    • List of Classes
    • Reporting Publications
    • GovInfo
    • FDLP eXchange
    • PURL Usage Reporting Tool
    • Shipping Lists
    • WEBTech Notes
    • UNION-L
    • LSCM GitHub Repositories
    • FDLP Resource Guides
    • Ben's Guide to the U.S. Government
  • Requirements & Guidance
    • Regulations
    • Guidance
    • Instructions
    • Collections & Databases
    • Promotion
    • FDLP eXchange Tips
  • Preservation
    • Preservation at GPO
    • Trusted Digital Repository Audit and Certification
  • About The FDLP
    • Superintendent of Documents
    • Depository Library Council
    • Join the FDLP
    • FDLP Academy
    • LSCM Digital Imaging Efforts
    • FDLP Training
    • Events and Conferences
    • FDLP Events Calendar
    • Projects
    • Collaborations with GPO
    • File Repository
    • Mission & History
    • Digital FDLP Implementation
    • Notable Numbers
    • The National Collection
  • Cataloging & Classification
    • GPO Cataloging Guidelines
    • Superintendent of Documents Classification Guidelines
    • Cataloging Record Distribution Program
    • Cataloging & Indexing
    • Catalog of U.S. Government Publications
    • Sources of GPO Cataloging Records
    • GPO Statement on Outdated and Offensive Language
  1. Home
  2. GPO Cataloging Guidelines
  3. Name Authorities: Policy Overview

Name Authorities: Policy Overview

  • Last Updated: March 18, 2025
  • Published: November 10, 2021

Sources

Use the Name Authorities sections of the Cataloging Guidelines in conjunction with the following sources for name authority guidance.

Primary sources:

  • RDA and associated LC-PCC PSs (GPO follows all LC-PCC PSs)
  • DCM Z1
  • MARC 21 Format for Authority Data
  • LC Guidelines Supplement to the MARC 21 Format for Authority Data
  • NACO Participants’ Manual

Additional sources:

  • NACO home page (includes: Documentation & Updates, Cataloging FAQs, and Training)
  • NACO Normalization
  • PCC NACO Training
  • PCC Post-RDA Test Guidelines
  • Frequently Asked Questions: Program for Cooperative Cataloging and RDA (PCC-RDA-FAQ Update 20130401)
  • Constant data records (internal GPO documentation, available to the public by request)
  • AACR2 and associated LCRIs (GPO followed all LCRIs)
  • Carroll's Federal Directory, Carroll's Federal Regional Directory (all paper issues for current and previous year retained; one issue for each past year retained permanently)
  • Congressional Directory (issues available via Internet; all paper issues retained permanently)
  • The United States Government Manual (issues available via Internet; all tangible, e.g., paper, issues retained permanently)

General Policies

GPO catalogers utilize name and series authority records from the Library of Congress Name Authority File (LC NAF). GPO has a local collection of authority records in its ILS, which are essentially the same as their counterparts in the LC NAF. Except for cataloger codes and other minor proprietary information, GPO currently includes no additional information in its local versions of authority records.

GPO participates in NACO (the Name Authority Cooperative Program) by creating and updating name authority records (NARs) and series authority records (SARs) in the LC NAF, via OCLC, as outlined below. Per NACO guidelines, new authority records are created according to the instructions in RDA. Updates are made to existing records in accordance with the PCC Post RDA Test Guidelines.

GPO considers the type of resource being cataloged when determining whether to create an authority record for an access point. Resources are categorized as either “Higher Priority” or “Lower Priority.” These categories are defined in Bibliographic Cataloging: Overview, Cataloging Priorities.

  • If authority work is required, and no copy of the resource is in hand or viewable online, request a surrogate from a library in order to complete the authority work.
  • Establish access points specifically requested via askGPO, obtaining surrogates as needed.
  • Exceptions to the guidelines for lower priority resources may be made on a case-by-case basis, in consultation with a supervisor, if the cataloger judges an otherwise unrequired access point to be necessary.

GPO bibliographic records may be produced prior to the completion of NACO work. While NACO work is pending, the associated bibliographic record(s) can be produced at full level with unauthorized (i.e., uncontrolled) access points. The following conditions apply:

  • NACO work needs to be drafted and saved to GPO’s online authority save file before the associated bibliographic record(s) can be produced.
    • Exception: If a NAR is needed because there is a conflict in the authority file, the NAR must be completed before the bibliographic record(s) can be produced.
  • When the completed authority record has been added to the LC authority file, the associated bibliographic record(s) can be authenticated if all PCC requirements are met.

All guidance below is GPO practice.

Working with Existing Authority Records

  • Update an existing authority record, regardless of the priority of the resource being cataloged, when needed to:
    • Conform to the PCC Post RDA Test Guidelines.
      • For more information, see Non-RDA Authority Records, below.
    • Add a variant name found in the resource being cataloged.
    • Correct an erroneous access point.
    • Correct transcription and other errors, if:
      • The authority record was created by GPO 

        and/or

      • The record is being used to support an authorized access point in a GPO bibliographic record
  • See additional guidance for Personal Names, Corporate/Conference Names, and Works and Expressions below.

Non-RDA Authority Records

Background information about NACO’s transition to RDA can be found in the Word document Frequently Asked Questions: Program for Cooperative Cataloging and RDA (PCC-RDA-FAQ Update 20130401). Especially note: 5.1, 5.6, and 5.7.

Current NACO practice for using and updating non-RDA authority records is in the PCC Post RDA Test Guidelines. The guidance applied most frequently by GPO is summarized here for convenience, but it is not a substitute for the PCC documentation.

  • Re-code non-RDA authority records to RDA (using the instructions in Name Authorities: General Procedures, How to Recode an Existing NAR from AACR2 to RDA) in the following situations:
    • The authority record is needed for a PCC RDA bibliographic record, and either of the following is true:
      • The authority record contains a 667 field stating “THIS 1XX FIELD CANNOT BE USED UNDER RDA UNTIL THIS RECORD HAS BEEN REVIEWED AND/OR UPDATED.”
      • The authority record lacks the 667 note above, but its authorized access point does not qualify as “RDA acceptable.”
        • This is most common when working with a personal name that includes Jr., III, or the like. If such a term is missing from the person’s authorized access point, the NAR is not “RDA acceptable.” For more information, see RDA 9.2.2.9.5 and 9.19.1.1.
    • The authority record is being updated for another reason. This includes adding variant names, adding other identifying characteristics, fixing a typo, etc.
      • Exception: When a record is being updated only to change a 5XX field, in response to changing a 1XX in another record, evaluation and recoding of the record with the 5XX is not required.
  • Aside from the situations covered above, do not take the encouraged action wherever the phrase “strongly encouraged” appears in the PCC Post RDA Test Guidelines.

Hybrid Authority Records

It is possible for a NAR to be a hybrid, i.e., contain mixed RDA and AACR2 elements. For example:

  • An existing NAR coded as RDA may contain variants (4XX) formulated according to AACR2 and related bodies (5XX) that have AACR2-coded NARs.
  • An original NAR coded as RDA may contain an “RDA acceptable” AACR2 authorized access point in a 5XX field.

However, NACO disallows a hybrid authorized access point (1XX), so every component of the 1XX in an RDA-coded record must be RDA compliant.

A common situation will occur with the creation of a new RDA NAR for a subordinate body that resides within a long-standing government agency.

  • When the NAR for a parent body was established according to AACR2, and that parent body is needed as part of the authorized access point (1XX) for a subordinate body in an RDA record:
    • Re-code the NAR for the parent body as RDA. See #4 in the PCC Post-RDA Test Guidelines.
  • When the NAR for a parent body was established according to AACR2, and that parent body is needed as part of a variant access point (4XX) for a subordinate body in an RDA record, evaluate whether the parent body’s authorized access point appears to be RDA acceptable.
    • If RDA acceptable, the parent body’s authorized access point can be used in the new NAR’s variant as-is.
    • If not RDA acceptable, the parent body’s NAR must be re-coded to RDA before its authorized access point can be used in the new NAR’s variant.

Example:

In order to create the following NAR (no2013009922):

008/10 = z

040 ##  DGPO ǂb eng ǂe rda ǂc DGPO

110 1#  United States. ǂb National Guard Bureau. ǂb Family Program Office

The record for the base NAR (n 50064765) needed to be recoded from AACR2:

008/10 = c

040 ##  DLC ǂb eng ǂc DLC ǂd DLC ǂd DGPO ǂd DLC ǂd ViNSC ǂd Uk ǂd IEN

110 1#  United States. ǂb National Guard Bureau

to RDA:

008/10 = z

040 ##  DLC ǂb eng ǂe rda ǂc DLC ǂd DLC ǂd DGPO ǂd DLC ǂd ViNSC ǂd Uk ǂd IEN ǂd DGPO

110 1#  United States. ǂb National Guard Bureau

Note that even though the 110 in the base NAR remained the same, the record needed to be recoded per #4 in the PCC Post-RDA Test Guidelines.

Personal Names

Updating Existing Personal NARs

  • In addition to the situations covered in Working with Existing Authority Records above, update an existing NAR, regardless of the priority of the resource being cataloged, when needed to:

    • Help users identify the person. Such an update is important when it is discovered that a person is involved in very different fields of activity.
      • If readily available information does not confirm whether an existing NAR represents the person from the work cat, attempt to contact the person or their institution for clarification. Make two email attempts, two weeks apart. Also attempt to call if a phone number is available. If no response is received within a week of the phone call or second email, create a new NAR.

    Example:

    n 85306066

    100 10  Posey, Carl A., ǂd 1933-2018

    373 ##  United States. National Oceanic and Atmospheric Administration ǂa National Optical Astronomy Observatories (U.S.) ǂ2 naf

    670 ##  His Bushmaster fall, c1991: ǂb CIP t.p. (Carl Posey)

    670 ##  The big book of weirdos, c1995: ǂb CIP t.p. (Carl A. Posey; editor for Time-Life Books)

    670 ##  Cunningham Turch Funeral Home website, Apr. 21, 2023: ǂb obituaries > search: carl posey > result: Carl A. Posey (Carl A. Posey; February 2018: Carl Alfred Posey, Jr., author and former Public Affairs Officer for NOAA and National Optical Astronomy Observatories, Dies at 84; Carl A. Posey, Jr., a prolific author of fiction and nonfiction books and a regular contributor to Air & Space magazine, died at home on February 9. By the time of his death he had authored eight published novels, a score of non-fiction books, and dozens of magazine articles, most of them about science and aviation)

    This NAR originally indicated the person was affiliated with fiction and comic strips. When searching the OCLC bibliographic file, the GPO cataloger found this authorized access point in a bib record for a NOAA publication. Rather than assuming the access point was assigned incorrectly, the cataloger located the person’s obituary and discovered he was indeed responsible for both the fiction and non-fiction works. The NAR was updated to make the connection apparent for future catalog users.

Creating New Personal NARs

Whether an authority record is created for a personal name depends upon the type of resource being cataloged. Resources are categorized as either “higher priority” or “lower priority.”

  • All personal name access points (MARC 100, 600, and 700) must be authorized in bibliographic records for higher priority resources.
  • Personal name access points (MARC 100, 600, and 700) may be unauthorized in bibliographic records for lower priority resources, under certain conditions. See below for more specific guidance.

Whether a NAR is created at the comprehensive or brief level depends upon the cataloger’s research.

  • Create a brief name authority record if warranted according to the guidance in Brief Personal NARs. Otherwise, create a comprehensive authority record.

Personal Names in Higher Priority Resources

  • Create a NAR if none exists, following the guidance for Comprehensive Personal NARs or Brief Personal NARs, as appropriate. 

Personal Names in Lower Priority Resources

Personal name access points (MARC 100, 600, and 700) may be unauthorized in bibliographic records for lower priority resources, under certain conditions. Such records cannot be authenticated for PCC.

  • See the Decision Tree for Personal Names to determine whether an unauthorized access point is allowable.
    • If a NAR must be created, follow the guidance for Comprehensive Personal NARs or Brief Personal NARs, as appropriate.
    • Catalogers who are fully independent for personal names can choose to establish a name that is not otherwise required under this policy.
  • When drafting an unauthorized access point:
    • Utilize the form of name and distinguishing information found in the work being cataloged.
      • If the work cat does not provide sufficient information to make the unauthorized access point unique when compared to the LC NAF, a NAR will need to be created.
    • Follow all RDA and NACO rules for access point formulation.
      • See RDA 9.19.1 and 9.2.
    • If additions are needed to make the unauthorized access point unique, follow GPO’s order of preference for constructing the access point.

Comprehensive Personal NARs

  • When a personal NAR is needed, create a comprehensive name authority record. For detailed guidance, see Name Authorities: General Procedures, Research in OCLC, Personal Names and Name Authorities: Personal Names.
    • Exception: Create a brief name authority record if warranted according to the guidance in Brief Personal NARs.
Constructing the Access Point
  • If, after constructing an authorized access point according to the LC-PCC PS for 9.19.1.1 and 9.19.1.3, additions are needed to make the access point unique, follow GPO’s order of preference for qualifiers. This order should be applied to information that is readily available:
    • Fuller form of name
      • If a fuller form of name is not readily available, it is cataloger’s judgment whether to contact a person to obtain this information or use the next available qualifier.
      • e.g., ǂa Alexander, Donald W. ǂq (Donald William)
    • Profession or occupation
      • Prefer the singular form of an LCSH term.
      • e.g., ǂa Alexander, Donald W. ǂc (Government librarian)
    • Other term of rank, etc.
      • e.g., ǂa Alexander, Donald W., ǂc Ph. D.
    • Associated institution
      • Begin the qualifier with “Of the” and use a grammatically correct form of the institution name. It is cataloger’s judgment whether to base the institution name on the authorized access point for the corporate body; if using the access point, modify punctuation as needed for clarity.
      • e.g., ǂa Alexander, Donald W. ǂc (Of the United States Government Publishing Office)

Brief Personal NARs

  • A brief name authority record is warranted under either or both of the following conditions:
    • The work cat pre-dates 1995, and no more recent works by or about the person can be found in ten minutes of research.
    • Ten minutes of research on a person does not yield any of the preferred qualifiers listed for comprehensive NARs above.
    • Research includes searching the OCLC bibliographic file. For details, see Name Authorities: General Procedures, Research in OCLC, Personal Names.
  • To create a brief name authority record, only two MARC fields are required: 
  1.  670 field citing the work cataloged
    • If other citations are readily available and helpful, they can be included as additional 670 fields.
  2. 100 field for the authorized access point:
    • Use a period of activity to make the access point unique:
      • ǂd active [pub date of work cat]
        • e.g., ǂa Alexander, Donald W., ǂd active 1962
      • Exception: If the publication date of the work cat is within 10 years of the publication date in a conflicting NAR’s 670 field, use a work title instead:
        • ǂc (Author of [work cat])
          • e.g., ǂa Alexander, Donald W. ǂc (Author of Great lakes trade routes)

Corporate/Conference Names

The guidance in this section applies to both federal and non-federal corporate bodies, including conferences.

  • To determine whether a non-federal corporate body warrants an access point in a bibliographic record, see Bibliographic Cataloging: General Policies, Non-Federal Corporate Bodies.

Updating Existing Corporate NARs

  • Update an existing NAR, regardless of the priority of the resource being cataloged, in accordance with Working with Existing Authority Records, above.
  • When updating existing NARs for corporate bodies, add references (4XX and 5XX) and 670 citations to the authority record as needed.
    • Optional fields such as 046, 368, 37X, etc., may be added if the information is readily available, helpful, and can quickly be added. Otherwise, do not add any optional fields.

Creating New Corporate NARs

Whether an authority record is created for a corporate body depends upon the type of resource being cataloged. Resources are categorized as either “higher priority” or “lower priority.”

  • All corporate body access points (MARC 11X, 61X, and 71X) must be authorized in bibliographic records for higher priority resources.
  • Corporate body access points (MARC 11X, 61X, and 71X) may be unauthorized or partially authorized in bibliographic records for lower priority resources. See below for more specific guidance.

Corporate Names in Higher Priority Resources

  • Create a NAR if none exists. 

Corporate Names in Lower Priority Resources

Corporate body access points (MARC 11X, 61X, and 71X) may be unauthorized or partially authorized in bibliographic records for lower priority resources. Such records cannot be authenticated for PCC.

  • If a corporate body is not found in the LC name authority file (LC NAF), search the CGP for an access point that represents the body.
    • When an access point is found in the CGP, use it in the bibliographic record.

Example:

Unauthorized access point (hypothetical example)

Found in work cat:

Publishing & Cataloging Associates

Found in CGP (not in LC NAF):

Publishing and Cataloging Associates

Unauthorized access point used in bibliographic record for work cat:

Publishing and Cataloging Associates

  • If no access point for the body is found in the CGP, create an unauthorized or partially authorized access point to use in the non-PCC bibliographic record.
    • Utilize the form of name found in the work being cataloged.
    • Follow all RDA and NACO rules for access point formulation.
      • See RDA 11.13.1 and 11.2.
      • Ensure that the access point created does not conflict with any 1XX in the LC name authority file.
    • For corporate bodies entered subordinately:
      • Form a partially authorized access point when possible, beginning with the authorized access point for the parent body from the LC name authority file.
      • When a partially authorized access point is not possible, look for the parent body in the CGP. If an unauthorized access point for the parent body exists in the CGP, use it to begin the unauthorized access point for the subordinate body.

Example:

Unauthorized access point (hypothetical example)

Found in work cat:

Expert Metadata, a consulting firm in Washington, D.C.

Unauthorized access point used in bibliographic record for work cat:

Expert Metadata (Firm)

Example:

Partially authorized access point (hypothetical example)

Found in work cat:

Cataloging Policy and Documentation Committee, U.S. Government Publishing Office

no2015002503 exists for the parent body:

United States. ǂb Government Publishing Office

Partially authorized access point used in bibliographic record for work cat:

United States. ǂb Government Publishing Office. ǂb Cataloging Policy and Documentation Committee

Catalogers who are fully independent for corporate names can choose to establish a name that is not required under this policy.

Conferences

  • Follow the guidance for corporate names, above.
    • When cataloging a lower priority resource for an individual instance of a conference and there is no matching NAR, use an unauthorized or partially authorized access point.

Example:

Partially authorized access point (hypothetical example)

Found in lower-priority work cat:

NASA/DOD Controls-Structures Interaction Technology

Proceedings of a conference held in San Diego, California, January 29-February 2, 1989

This publication is a compilation of the papers presented at the third NASA/DOD CSI Technology Conference

n 88035156 exists for the ongoing conference:

NASA/DOD CSI Technology Conference

Partially authorized access point used in bibliographic record for work cat:

NASA/DOD CSI Technology Conference ǂn (3rd : ǂd 1989 : ǂc San Diego, Calif.)

Programs and Projects

See RDA 11.0 and Glossary: Corporate body.

GPO provides authorized access points in bibliographic records, and creates and updates authority records for programs and projects, unless these are mere abstract ideas that appear only in a title or within the text of a publication. In other words, the program or project must have some intrinsic existence of its own, apart from a reference in a publication. Note: Studies are corporate bodies. Here are two examples of programs/projects that GPO would establish as corporate bodies:

Example:

110 2#  WaterSMART (Program)

670 ##  WaterSMART, 2012: ǂb PDF t.p (U.S. Department of the Interior's WaterSMART(Sustain and Manage America's Resources for Tomorrow) Initiative; WaterSMART Initiative) p.2 (DOI Water SMART Program)

670 ##  WaterSMART (Program) Web site, viewed Apr. 9, 2013 ǂb (U.S. Department of the Interior, Bureau of Reclamation, WaterSMART (Sustain and Manage America's Resources for Tomorrow))

Example:

110 2#  Measuring Broadband America (Program : U.S.)

670 ##  Measuring Broadband America, 2012: ǂb Background and overview (Federal Communication Commission's Measuring Broadband America program, an ongoing, rigorous, nationwide performance study of residential broadband performance in the United States)

Here is an example of a "program" that GPO would not establish as a corporate body:

Example:

245  A history of the Unemployment Compensation Program.

The "Unemployment Compensation Program" would not be established; it is used loosely in this title, as a concept.

Corporate Names for Parks, Forests, Preserves, etc.

DCM Z1: Appendix 1, Section 2.8: Forests, Parks, Preserves, etc., explains that a park, forest, etc. can have two separate authority records, one in the Names file, and one in the Subjects file. Establish corporate names for the administrative aspect of these entities, when functioning as a creator (such as an author), issuing body, sponsoring body, publisher, etc. of a publication (or when functioning as any of the relationship designators in RDA Appendix I.2). For the authorized access point, use the form in the following example: 110 2 Everglades National Park (Agency : U.S.).

For more specific instructions, see: Name Authorities: Corporate Names and Name Authorities: AACR2, Corporate Bodies.

Works and Expressions

If a work or expression (previously called uniform titles) that must be established, such as a series, law, or treaty, is not in the LC/NACO authority file, it is established following the instructions in DCM Z1, and RDA/LC-PCC PSs. GPO authorizes all titles for series, laws, and treaties in the authority file, and creates and update authority records for these as needed.

Authority records for certain other titles (such as monographs, serials, computer programs or applications) may be created and contributed to the LC/NACO authority file per LC's DCM Z1 instructions only if cross-references need to be made. This is usually the case with private and public laws and treaties involving three or more countries. Often the official name of the public law appears on a publication in several manifestations (e.g. the official name, the name of the law in a citation, and the public law number).

If there are no cross references, an authority record is not created. Titles for works and expressions are included in bibliographic records, if required, even though they have not been established (See RDA 6.27.1.9).

Per RDA chapter 6, unique authorized access points are required for publications published simultaneously with different titles (6.2.2.4), in different languages (6.2.2.4, 6.27.3), or that are translations (6.27.3). However, LC/NACO authority records are not created for them by GPO.

Consider a publication a translation rather than a version in a different language if it contains explicit translation statements, e.g., 500 "Translated by ..." or 500 "Translation of ...."; Prior to RDA, some time before 2002, the Library of Congress requested that GPO not establish uniform titles for translations of individual journal articles. Therefore, GPO will not establish unique authorized access points for translations of individual journal articles.

Multipart (Collective) Titles

New authority records are created and existing records are updated for use in bibliographic records only if a multipart collective title is to be recorded in the series statement of a record per GPO policy. Variant forms found in publications cataloged are added to authority records.

Series

Series titles and series numbering are always confirmed in OCLC's authority file.

For all publications that are not individual issues of serials or articles from serials, new series authority records are created and updated. Series statements are recorded in the 490 field and traced in the 830 or 810 series added entry field. Variant series statements appearing in resources are always confirmed in, and added if necessary, to the authority record. If following specific CONSER or BIBCO guidance, only the 830 field need be entered, if the series statement appears on the resource in its authorized form.

If publications are either individual issues of serials or articles from serials, series authority records are not created for these.

Instead, the serial's title and designation in which an individual article or group of articles appears is recorded in a note.

Example:

500 ##  "Journal of elementary education, volume 50, number 1."

The title of the individual article or the title given to a group of individual articles is recorded in the title and statement of responsibility area of the record. Hypothetical example:

Example:

100 1#  Smith, Jane

245 10  Effective instruction / ǂc Jane Smith.

500 ##  "Journal of elementary education, volume 50, number 3."

If the individual issue of a serial has its own individual title, the individual title is recorded in the title area of the cataloging record. The serials title and numbering are recorded in a note. See hypothetical example below.

Example:

245 00  Los Angeles and the future of secondary education.

500 ##  "Journal of elementary education, volume 52, number 11."

If the individual issue does not have its own title, the title and issue numbering are recorded in the title and statement of responsibility area. See hypothetical example below:

Example:

245 04  The journal of elementary education, ǂn Volume 52, Number 11.

Series-Like Phrases

In the past, GPO established series-like phrases, but no longer establishes them regularly. Authority records are created only for series-like phrases that are frequently confused with one or more series and are inadvertently, but frequently, recorded as series. Notes giving instructions on usage are added to multipart and series authority records.

Example:

130 #0  NPS D

667 ##  Document

667 ##  Give as a quoted note, including the number, if present, e.g., "NPS D-6"; not a report no., but designates a geographic area covered by the publication, do not enter in fields used to record report numbers.

Series-like phrases that qualify to be recorded are confirmed for full-level records. Authority records are created only if required for the reasons indicated above.

For more specific instructions, see: Name Authorities: Works & Expressions: General.

Places (Jurisdictional Geographic Names)

New jurisdictional geographic name authority records are created in the LC/NACO authority file. These include countries, states, provinces, counties, cities, and towns, as well as water, sanitation, utility, conservation, soil, recreation, park, and ranger districts. Active military installations, city sections, and U.S. Indian tribes as legal entities are also geographic names that GPO establishes and updates. For more details, consult: LC-PCC PS 16.4.1, and: DCM Z1: Appendix 1: Ambiguous Entities.

Existing name authority records for geographic entities are updated as needed. Cross-references and variant forms are added as they are discovered. For all work on geographic NARs, whether creating a new record or updating an existing one, RDA chapter 16 is followed, along with its corresponding LC-PCC PSs. If appropriate, you may apply RDA chapter 11 elements and their corresponding MARC 046 and 3XX fields, which record various attributes of corporate bodies. Include MARC fields 043 and 781 in geographic NARs. In addition, one of the following two sources is always consulted and cited (See SHM (Subject Headings Manual) H 203 for citation method):

  • Geographic Names Information System (GNIS) for domestic (U.S.) names
  • GEOnet Names Server for foreign (non-U.S.) names

The following sources may additionally be consulted as needed:

  • Columbia Gazetteer of the World, 1998
  • National Geographic's Atlas of North America
  • Rand McNally ... Commercial Atlas & Marketing Guide
  • Rand McNally's The New International Atlas
  • The Times Atlas of the World
  • Merriam-Webster's Geographical Dictionary, 3rd edition

Works in which a geographic name is found are recorded in the 670 field, while those in which the name is not found are recorded in the 675 field. New jurisdictional geographic heading authority records are created in the LC/NACO authority file, whether needed in the bibliographic record as a subject or as a name. Below are some examples.

Title of resource cataloged: Flood insurance study. ǂp Town of Milan, New Hampshire, Coos County.

Example:

650 #0  Flood insurance ǂz New Hampshire ǂz Milan (Town)

Because "Milan (Town)" is needed as a geographic subdivision of a topical subject, the geographic name authority record is established: 151 Milan (N.H. : Town)

A corporate body authority record is needed.

Example:

151 ##  Door County (Wis.)

(The above record may be created so that the following record may be created.)

110 1#  Door County (Wis.). ǂb Soil and Water Conservation Department

Occasionally, a jurisdictional name may be needed as a qualifier in another authority record:

Example:

245 10  Alaska Native Village Corporation : ǂb report (to accompany S. 924).

610 20  Newtok Native Corporation (Newtok, Alaska)

In order to establish the corporate name: 110 2 Newtok Native Corporation (Newtok, Alaska), the following jurisdictional name is established: 151 Newtok (Alaska)

The resource cataloged may contain a statement on the title page: "prepared in cooperation with the city of Hopkinsville, Kentucky." The following record is created:

Example:

151 ##  Hopkinsville (Ky.)

However, this same authorized access point may appear in the bibliographic record as follows:

710 1#  Hopkinsville (Ky.)

This added entry will control (authorize) in OCLC, even though it is tagged differently than the authority record. This is true of all geographic names in the LC/NACO (Names) file. It is not true of geographic names that are subjects in the LC/SACO (Subjects) file. See: DCM Z1: Appendix 1: 1.2.a: "Note that when entities tagged 151 in the authority file are used as access points in bibliographic records (110, 710, and 810), the first indicator is set to the value 1."

Another example of this is below.

Example:

151 ##  Gary Sanitary District (Ind.) (in the authority record)

710 1#  Gary Sanitary District (Ind.) (in the bibliographic record)

For more details and documentation about using geographic names as corporate bodies, coded X10, see: MARC 21 Format for Bibliographic Data--X10.

For clarification on the treatment of ambiguous geographic entities, see DCM Z1: Appendix 1.

For additional information, also see:

  • LC-PCC PS 16.4.1, which deals with ambiguous entities such as Indian Tribes.
  • AACR2: chapter 23, 24.3E1, 24.6
  • LCRI: 23.1, 24.1A

For more specific instructions, see: Name Authorities: Places.
 

Cataloging Guidelines:

  • GPO Cataloging Guidelines: Introduction
    • Cataloging/Metadata Policy-making Process
      • Cataloging Policy and Documentation Committee (CPDC)
      • GPO Cataloging Guidelines Review and Revision Processes
    • GPO Cataloging Guidelines: Organization and Structure
      • Examples
    • List of Standards
      • Bibliographic
      • Classification
      • Other Metadata Schemes
    • Other
      • Cooperative Associations
      • Questions
  • Bibliographic Cataloging: Overview
    • Sources
    • Authoritative Status of the Catalog of U.S. Government Publications
      • GPO Records in OCLC and Record Maintenance
    • Scope of Cataloging
    • Cataloging for Title 44 Programs
      • Federal Depository Library Program (FDLP)
      • FDLP Distribution Unknown
      • Cataloging & Indexing Program (C&I) 
    • Cataloging Priorities
      • Higher Priority Resources
      • Lower Priority Resources
    • Use of Surrogates for PCC Authentication
      • 300 - Physical Description
      • 588 - Source of Description Note
    • Cataloging/Metadata Encoding Levels Policies
      • 1.0 Purpose
      • 2.0 Background and Related Documents
      • 3.0 Guidelines and Standards Consulted
      • 4.0 Coordination with Collection Development Procedures
      • 5.0 General Principles
    • Treatment Decisions for Collections and Analytics
      • Factors to consider for the treatment decision
    • Separate Record Policy
      • Current Policy: Separate-Record Approach
      • Previous Policy: Single-Record Approach
      • Policy Changes and Catalog Maintenance
      • Background
      • Procedures
      • Exceptions
    • Original Cataloging
    • Copy Cataloging
      • Selecting Records for Copy Cataloging
      • Adapting Records
      • Replacing and Exporting Records
    • GPO Sales Program Information
      • Original Cataloging for Sales Program
      • Copy Cataloging for Sales Program
    • Authority Records
  • Bibliographic Cataloging: General Policies
    • Distinguishing Works and Expressions with Identical Authorized Access Points
      • Chronological Editions
      • Language Editions
      • Punctuation in the title proper
      • Use of Part Titles
      • Use of Other Title Information
      • Title Layout on Publication
      • Use of Project Name
      • Colon in Title Proper
    • Relationship Designators (Relator Terms)
    • Different Language Editions
    • Location (Source) of Names and Other Elements Recorded in the Resource Cataloged
      • Statements of Responsibility
      • Technical Report Documentation Page
      • Programs and Projects
    • Adding Authorized Access Points - What to Trace
      • Authorized Access Points in Bibliographic Records
      • Limitations on Names Used as Descriptive Authorized Access Points in the Resource Cataloged
      • Authorized Access Points in Adapted OCLC Records (Copy Cataloging)
      • New GPO Records Created by Cloning Existing Records
  • Bibliographic Cataloging: General MARC Field Policies
    • Formats, Modes of Issuance, Etc
    • Punctuation
      • PCC Policy on ISBD Punctuation
    • Transcription
    • Fixed Fields
      • ELvl - Encoding Level
      • PCC Level
      • I Level
      • 007 - Physical Description Fixed Field 
    • Variable Fields
      • 007 
      • 037 - Source of Acquisition
      • 040 - Cataloging Source
      • 041 - Language Code
      • 050 - Library of Congress (LC); 060 - National Library of Medicine (NLM); 070 - National Agricultural Library (NAL); 082 - Dewey Decimal Classification and Call Number
      • 100/600/700 - Personal Name Access Points
      • 100 - Principal Creator – Personal Name
      • 110/111 - Principal Creator - Corporate/Meeting Name
      • 130/240 - Unique Title for Work or Expression
      • 130 - Unique Title for Work or Expression - No Principal Creator Present
      • 240 - Unique Title for Work or Expression - Principal Creator Present
      • 245 - Title Statement and 246 - Varying Form of Title
      • 245 ‡c - Statement of Responsibility (SOR)
      • 246 - Varying Form of Title
      • 250 - Edition Statement
      • 264 (260 in adapted records) - Production, Publication, Distribution, Manufacture, and Copyright Notice
      • 300 - Physical Description
      • 336 - Content Type, 337 - Media Type, 338 - Carrier Type
      • 490 - Series Statement Field
      • 500, 588 - Title Source, Source of Description Notes
      • 500 - General Note
      • 536 - Funding Information Note
      • 546 - Language Note
      • 6XX - Subject Access Fields
      • 600 - Personal Name Subject
      • 700 - Personal Name Associated with a Work
      • 710/711 - Corporate/Meeting Name Associated with a Work
      • 76X to 78X - Linking Entries
      • 776 - Additional Physical Form Entry
      • 856 - Electronic Location and Access – Historic URLs
  • Bibliographic Cataloging: 074 GPO Item Number
    • Multiparts
    • Item Number Corrections
  • Bibliographic Cataloging: 086 SuDoc Number
    • Sources to Consult
    • Background and General Instructions
    • Multiparts
    • Serials and Integrating Resources
  • Bibliographic Cataloging: 856 Field
    • History
      • PURL Addresses
      • PURL Identifiers
    • PURL Creation and Access
      • Single Part Monographs
      • Multi-Part Monographs and eBooks
      • Continuing Resources
      • Serials
      • Integrating Resources (IR)
      • Live IR
      • Ceased IR
    • Formulating the 856 Electronic Location and Access Field
      • Order of Multiple 856 MARC Fields
      • PURL(s) – 856 40
      • Historic URL – 856 4_
      • Related Resource – 856 42
      • Public Notes – Subfield z
      • Materials Specified Note – Subfield 3
      • Access Status – Subfield 7
  • Bibliographic Cataloging: Monographs
    • Related Chapters/Sections
    • Fixed Fields
      • DtSt: Type of Date/Publication Status
    • Variable Fields
      • 020 – ISBN
      • 037 – Source of Acquisition
      • 088 - Report Numbers
      • 245 ǂc - Statement of Responsibility
      • 250 - Edition Statement
      • 300 - Physical Description
      • 500 - General Note
      • 505 - Formatted Contents Note
      • 520 - Summary, etc.
      • 536 - Funding Information Note
      • 588 - Source of Description Note
    • Related Works and Expressions
      • GPO Guidelines to Consult
      • Other Resources to Consult
      • Related Works and Expressions - Overview
      • Frequently Revised Monographs
      • Language Editions and Translations
      • Revised Editions
      • Summaries
      • Other Relationships and MARC 787
  • Bibliographic Cataloging: Continuing Resources: Serials
    • Sources to Consult
    • General Policies, Procedures, and Practices
      • Definition of Serial
      • Cataloging Decision: Monograph vs. Serial and Frequency of Issuance
      • Numbering - Exceptions to the RDA Principle of Transcription, or “Take What You See”
      • Notification of Cataloging Updates via WebTech Notes
      • Notification of LSCM’s Office of Archival Management (OAM) for Serials Harvesting
      • Updating Collections of Serials
    • MARC Fields
      • Leader /17 (Encoding Level) and 042
      • 010 - Library of Congress Control Number
      • 022 - ISSN
      • 050 - Library of Congress Call Number
      • 060 - National Library of Medicine Call Number
      • 070 - National Agricultural Library Call Number
      • 074 - Item Number
      • 082 - Dewey Decimal Classification Number
      • 086 - SuDoc Number
      • 246 - Varying Form of Title
      • 264 - Production, Publication, Distribution, Manufacture, and Copyright Notice
      • 300 - Physical Description (300 |a )
      • 362, 588, and Any Field Where Designation is Represented
      • 362 - Beginning and/or ending numbering/dates of publication
      • 362 - Determination of Cessation of a Serial When Response from the Publishing Agency is Lacking
      • 500 - Distribution Note
      • 515 - Numbering Peculiarities Note
      • 538 - System Details Note
      • 588 - Source of Description Note
      • 76X--78X - Linking Entry Fields
      • 776 - Additional Physical Form
      • Other Considerations for Linking Entry Fields: Parallel Formats & Works Not Described in Bibliographic Records
      • 856 - Electronic Location and Access
      • Single-record vs. Separate-Record Approach and PURLs
  • Bibliographic Cataloging: Continuing Resources: Integrating Resources: General MARC Field Policies
    • 022 - ISSN
    • 086 - Superintendent of Documents (SuDocs) Stem
      • Classification of Ceased Integrating Resources Being Cataloged for the First Time by GPO
    • 130/240 - Additions to authorized access points representing works
    • 245 - Title
      • Other title information (ǂb)
      • Statement of responsibility (ǂc)
    • 300 – Physical Description
    • 5XX - Notes
      • Order of 5XX notes
      • 588 - Description based on (DBO)/source of title proper note
      • Digital Collections
    • 760-787 – Linking Relationships
      • 773 - Host Item Entry
  • Bibliographic Cataloging: Continuing Resources: Integrating Resources: FDLP Web Archive Resources
    • Overview
    • For more information
    • MARC Fields
      • ELvl/Srce
      • 040 – Cataloging Source
      • 074/086 - Item Number/Government Document Classification Number
      • 130/240 – Main Entry/Uniform title
      • 246 – Varying Form of Title
      • 247 – Former Title
      • 250 – Edition Statement
      • 264 – Publication/Distribution Statement
      •  336 – Content Type
      • 500 – General Notes
      • 520 – Abstract
      • 588 - Source of Description Note
      • 710 – Added Entry – Corporate Body
      • 773 – Host Item Entry
      •  775 – Other Edition Entry
      • 856 – Electronic Location & Access
      • 955 – Local Note
  • Bibliographic Cataloging: Continuing Resources: Selective Registration for ISSN Assignments
      • ISSN Program – General Information
      • ISSN Assignments
  • Bibliographic Cataloging: Continuing Resources: Appendix A: Bibliographic File Maintenance
    • Deletion of Records from the CONSER Database
  • Bibliographic Cataloging: Continuing Resources: Appendix B: Where to find certain CONSER procedures
    • Where to find certain CONSER procedures
  • Bibliographic Cataloging: Continuing Resources: Appendix C: Holding and Item Record Guidance
    • Holdings records for serials
      • General Information
      • Holdings Record Policies:
      • Summary Holdings Statements for Serials & IRs
      • Formatting summary holdings statements
      • Holdings Record Resources
    • Item records for serials
      • General Information
      • Item Record Resources
    • Subscription records
      • General information
      • Subscription record resources
    • Prediction patterns
      • General information
      • Prediction Patterns for Regular Serials
      • Prediction Pattern Resources
  • Bibliographic Cataloging: Congressional Publications
    • Overview
      • Formats
    • Mode of Issuance - Hearings
    • Encoding Level and PCC Authentication
      • 086 – Superintendent of Documents Classification Number
    • 088 - Report Number (House Hearings)
      • Serial Numbers with Committee Designations
      • Serial Numbers without Committee Designations
      • Serial Numbers without Any Designations
    • 1XX – Principal Creator
      • Documents
      • Hearings
      • Prints
      • Reports
    • Other Types of Publications
      • Joint Committee on Taxation
      • 130/240- Unique Title for Work
      • Hearings
      • Reports
    • 245 ǂa – Title Statement
    • 245 ǂb – Remainder of Title
    • 246 - Varying Form of Title
    • 264 - Production, Publication, Distribution, Manufacture, and Copyright Notice
    • 300 ǂb – Other Physical Details
    • 500 – Serial Number Note
    • 500 – Shipping List Note
    • 504 – Bibliography, etc. Note
    • 505 – Formatted Contents Note
    • Star Prints
      • 086 – SuDoc Number
      • 250 – Edition Statement
      • 500 – General Note
    • Addendum/Addenda
      • 086 – SuDoc Number
      • 300 ǂe – Accompanying Material
      • 500 – General Note
      • 856 – PURL
    • Erratum/Errata
      • 086 – SuDoc Number
      • 300 ǂe – Accompanying Material
      • 500 – General Note
      • 856 – PURL
    • Multipart Monographs
      • 500 – General Note
      • 710 – Corporate Name Associated with a Work
  • Bibliographic Cataloging: Public and Private Laws
    • Public Laws
    • Private Laws
    • Instructions
  • Bibliographic Cataloging: Treaties
    • 074- Item Number
    • 086- SuDoc Number
    • 490 and 830- Series
    • 546 and 041- Language
    • Senate Treaty Document Series (Y 1.1/4:)
  • Bibliographic Cataloging: Audiovisual Resources
    • Scope of the Format Visual Resources
    • Definitions of Types of Visual Resources
    • Bibliographic Treatment in the CGP
      • Analytics of Videos
      • Collections of Videos
      • Analytics of Still Images
      • Collections of Still Images
    • MARC Fields for Visual Resources
      • 245
      • 300- Physical Description
      • 655- Genre/Form Terms
  • Bibliographic Cataloging: Braille
    • Braille Publications Treated as Serials
    • PCC Authentication
    • Authorized Access Point
    • Edition Statement
    • Language Note
    • Other Edition Entry
  • Bibliographic Cataloging: Brochures and Recreation/Visitor Guides
    • Serials-of-Convenience Treatment
    • Map Treatment
  • Bibliographic Cataloging: Cartographic Materials
    • Background and Sources Consulted
    • Brochures and Visitor Guides Treated as Maps
    • BLM Surface/Mineral Management Maps
    • Serial Treatment
    • Encoding Level
    • 086 - SuDoc Number
    • 1XX - Principal Creator
    • 130/240 - Unique Title for Work
    • 245 - Title Statement
    • 255 - Cartographic Mathematical Data
    • 300 - Physical Description
    • 500 - Notes
    • 655 - Genre/Form Term
  • Bibliographic Cataloging: Computer Files
    • Procedures to Convert Type "M" (Computer File) Records to Type "A" (Language Material) Records
  • Bibliographic Cataloging: eBooks
    • Overview
    • Disposition of eBooks on CD-ROM
    • MARC Fields
      • 020 – International Standard Book Number
      • 347 – Digital file characteristics
      • 856 – Electronic location and access
      • 955 – Local GPO notes
      • Non-Distributed eBooks
    • Resources to Consult
  • Bibliographic Cataloging: Microfiche
    • Current RDA Policies and MARC Fields (February 2015- )
      • Alterations to the Paper Publication
    • MARC Fields
      • Fixed field
      • 007- Physical Description Fixed Field 
      • 074- Item Number 
      • 264- Production, Publication, Distribution, Manufacture, and Copyright Notice
      • 300- Physical Description
      • 336- Content Type
      • 337- Media Type
      • 338- Carrier Type
      • 500- General Notes
      • 776- Additional Physical Form Entry
    • Overview of Previous Microfiche Policies
      • Early RDA (April 2013-February 2015) 
      • AACR2/LCRI (through March 2013) 
    • Current Procedures for Re-Cataloging Microfiche That Were Previously Described in a Record Utilizing the Single Record Approach
  • Bibliographic Cataloging: Technical Reports
    • Identification of Technical Reports
      • Former Practice
      • Current Practice
    • Monograph or Serial
    • Sources of Information
    • Cataloging Instructions
      • Fixed Fields
      • Variable Fields
    • References
  • Name Authorities: Policy Overview
    • Sources
    • General Policies
    • Working with Existing Authority Records
      • Non-RDA Authority Records
      • Hybrid Authority Records
    • Personal Names
      • Updating Existing Personal NARs
      • Creating New Personal NARs
    • Corporate/Conference Names
      • Updating Existing Corporate NARs
      • Creating New Corporate NARs
      • Conferences
      • Programs and Projects
      • Corporate Names for Parks, Forests, Preserves, etc.
    • Works and Expressions
    • Multipart (Collective) Titles
      • Series
      • Series-Like Phrases
    • Places (Jurisdictional Geographic Names)
  • Name Authorities: RDA, General Policies
    • Field Specific Guidelines
      • ǂu and ǂv in the 046 and 3XX optional fields
      • Source of Information: 670 vs. ǂv in the 046 and 3XX optional fields
      • 046 – Special Coded Dates
      • ǂ2 – Source of Term
      • ǂs (start date or start period) and ǂt (end date or end period)
      • 336 - Content Type
      • 368 - Other Attributes of Person or Corporate Body
      • 370 - Associated Place
      • 371 Address
      • 372 - Field of Activity
      • 373 - Associated Group
      • 377 - Associated Language
      • 4XX - See From Tracing
      • 5XX - See Also From Tracings
      • 670 - Source Data Found
      • 678 - Biographical or Historical Data
  • Name Authorities: General Procedures
    • Optional Fields
    • Research in OCLC
      • Personal Names
      • Corporate/Conference Names
    • How Much Research Should Be Performed … ?
    • When to Consult Additional Sources
    • Tips for contacting agencies
    • How to Recode an Existing NAR from AACR2 to RDA
  • Name Authorities: General Field Specific Guidelines
    • 043 - Geographic Area Code
    • 1XX and 4XX
    • 4XX – See From Tracing
    • 5XX – See Also From Tracings
    • 670 - Source Data Found
    • 678 - Biographical or Historical Data
    • 781 - Subdivision Linking Entry-Geographic Subdivision
  • Name Authorities: 67X Citation Fields
    • 670 - Source Data Found
      • General Guidance
      • Citing Specific Types of Resources
    • 672 - Title Related to the Entity
    • 675 - Source Data Not Found
  • Name Authorities: Personal Names
    • Procedure for ECIP
    • Procedure for CRS Reports
    • General Instructions
    • 046 – Special Coded Dates (RDA 9.3)
      • ǂs and ǂt in the 046 and 3XX optional fields
    • 100 – Authorized Access Point
      • ǂq – Fuller Form of Name
      • ǂd – Birth and/or Death Date
      • ǂc - Titles and Other Words (Professions) Associated with a Name
    • 368 - Other Attributes of Person or Corporate Body
    • 370 - Associated Place (RDA 9.8-9.11)
    • 371 - Address (RDA 9.12)
    • 372 – Field of Activity (RDA 9.15)
    • 373 – Associated Group (RDA 9.13: Affiliation)
    • 374 – Profession or Occupation (RDA 9.16)
    • 375 – Gender (RDA 9.7)
    • 377 - Language (RDA 9.14)
    • 378 – Fuller Form of Name (RDA 9.5)
    • 400 - See From Tracing - Personal Name
    • 510 - Related Corporate Body
    • 678 - Biographical or Historical Data (RDA 9.17)
  • Name Authorities: Corporate Names
    • Notes
    • Sources to Consult
    • Before You Begin
    • MARC Fields
      • 110 - Corporate Name (11.2.2, 11.13.1)
      • 111 - Meeting Name (11.2.2, 11.13.1)
      • 368 - Other Attributes of Corporate Body: ǂa Type of Corporate Body (11.7.1.4)
      • 370 - Associated Place (11.3)
      • 372 - Field of Activity (11.10)
      • 373 - Associated Group (11.5)
      • 410/411 - See From Tracing (11.2.3, 11.13.2)
      • 410 - See From Tracing - Corporate Name (11.2.3, 11.13.2)
      • 411 - See From Tracing - Meeting Name (11.2.3, 11.13.2 )
      • 510/511 – See Also From Tracing (Related Corporate/Conference Name) (Chapter 32)
      • 510 - See Also From Tracing - Corporate Name (Chapter 32)
      • 667 - Nonpublic General Note
      • 678 - Biographical or Historical Data (11.11)
  • Name Authorities: Places
    • 043 - Geographic Area Code
    • 451 - See From Tracing 
    • 670 - Source Data Found
    • 781 - Subdivision Linking Entry-Geographic Subdivision
  • Name Authorities: Works & Expressions: General
    • Related Chapters/Sections
    • Chapter Scope
    • Works vs. Expressions
    • What to Establish in the Authority File
    • Transcription
      • Capitalization
      • Punctuation
      • Initial Articles
    • Name/Title Access Points
    • MARC Fields
      • Access Points
      • 046 - Special Coded Dates
      • 336 – Content Type
      • 370 – Associated Place
      • 377 – Associated Language
      • 380 – Form of Work
      • 4XX – Variant Access Points
      • 667 – Nonpublic General Note
      • EXEMPLARS
  • Name Authorities: Works & Expressions: Public Laws
    • Related Chapters/Sections
    • Chapter Scope
    • Note on Past Practices
    • What to Establish in the Authority File
    • Tips
    • Authorized Access Points of Public Laws
    • Preferred Titles of Public Laws
      • Citation Title vs. Formal Title
    • Capitalization
    • “Embedded” Laws
    • MARC Fields
      • 046 – Special Coded Dates
      • 110 – Heading-Corporate Name
      • 380 – Form of Work
      • 410 - See From Tracing-Corporate Name
      • 670 – Source Data Found
  • Name Authorities: Works & Expressions: Treaties
    • Related Chapters/Sections
    • Chapter Scope
    • Note on Past Practices
    • Works vs. Expressions
    • What to Establish in the Authority File
    • Capitalization
    • Preferred Titles for Treaties
    • Authorized Access Points for Treaties
    • Authorized Access Points for Protocols
    • Dates of Treaties and Protocols
    • When to Recode pre-RDA Treaty NARs to RDA
    • MARC Fields for Treaties and Protocols
      • 046 – Special Coded Dates
      • 370 – Associated Place
      • 380 - Form of Work
      • 4XX – Variant Access Points
    • Examples
  • Name Authorities: AACR2, Corporate Bodies
    • Auth status - 008/33
    • 110 - Corporate Name
    • 111 - Meeting Name
    • 410/411 - Variant Name
    • 5XX - See Also From Tracings
    • 670 - Source Data Found
  • Subject Cataloging: General Policies
    • Library of Congress Subject Headings (LCSH)
    • NASA Thesaurus Terms as Subject Headings
      • Assigning NASA Terms
      • General Policies and Procedures
    • MESH, NAL, and Other Non-LC Subject Headings
    • Library of Congress Genre/Form Terms for Library and Archival Materials (LCGFT)
      • Adding General LCGFT to Bibliographic Records
      • Background Resources for LCGFT
      • Adding LCGFT to Cartographic Records
      • Adding LCGFT to Audiovisual Records
  • Subject Cataloging: Subject Heading Proposals, Background and Tips
    • Tips and Instructions
      • Internet Research
      • Subject Headings Manual (SHM)
      • Searching Minaret
      • Additional Minaret (Class Web) Tips
      • Scope Notes
      • Use of the Dictionary
      • Use of Wikipedia
      • Use of LCSH as a Thesaurus
    • References  
      • Class Web or Minaret
      • SACO Resources
      • SHM (Subject Headings Manual)
      • Print Resources
      • Resources for Geographic Proposals
      • Geographic Print Resources
    • Examples of GPO Subject Proposals
  • Subject Cataloging: Subject Heading Proposals, Workflow
    • Submitting SACO Proposals for Internal Review
    • Producing Associated Bib Records; Exporting Subject Authority Records
    • Submitting SACO Proposals to the Library of Congress
    • Updating Aleph Authority File
  • Subject Cataloging: Name vs. Subject Authority File
    • Overview
    • Instructions
  • Subject Cataloging: Name Headings as Subjects
  • Subject Cataloging: Special Topics, Materials, Subdivisions, Etc.
    • Environmental Impact Statements
    • Legal Topics
    • Research
  • Other Metadata Schemes: Dublin Core
  • Other Metadata Schemes: ONIX
  • Glossary
    • A
    • B
    • C
    • D
    • E
    • G
    • I
    • L
    • M
    • N
    • O
    • P
    • R
    • S
    • T
    • U
    • V
    • W
  • Initialisms and Acronyms
FDLP

Federal Depository Library Program (FDLP) • 732 N Capitol Street, NW, Washington, DC 20401

Privacy Policy

Connect with GPO