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: General Procedures

Name Authorities: General Procedures

  • Last Updated: November 25, 2024
  • Published: November 10, 2021

Optional Fields

For the optional fields in a name authority record, include or add these fields whenever the information is readily available in the resource being cataloged, and can quickly be added. No significant research should be done, and no extra sources need be consulted, to find values for the optional attributes in a name authority record.

Research in OCLC

Personal Names

  • When creating a personal name authority record (NAR), search the OCLC bibliographic file in addition to the Name Authority File (NAF): 
    • Keyword search using terms from the work cat
      • e.g., "robert b miller" "american institutes for research"
    • Browse search by personal name
      • e.g., miller, robert b

Citing Catalog Sources in Authority Records

  • Add a 670 NAR citation for any transcribed names (“usage”) and unauthorized access points found in the OCLC bibliographic file (“catalog”) when both of the following conditions are met:
    • Results retrieved in the OCLC bibliographic file are clearly for the person represented by the NAR
    • Retrieved bibliographic records (“catalog sources”) provide biographical information not already present in the NAR’s 670 citations

Example:

Work cat (CGP 1200796) citation in draft NAR:

670__ Development of a taxonomy of human performance. Design of a systems task vocabulary, 1971: ǂb t.p. (Robert B. Miller) Literature cited (Miller, R. B.)

Searching and browsing of the OCLC bib file revealed publications written by the same person under different names:

oclcimage1
oclcimage2

Each bibliographic record was opened to confirm similar subject matter and to check for additional personal name usage (transcribed in 245 or 500).

Resulting citation in NAR:

670 __ OCLC, May 24, 2022 ǂb (access points: Miller, Robert B. (Robert Bruce), 1910- , Miller, Robert Bruce, 1910- ; usage: Robert B. Miller)

Citing Non-Catalog Sources in Authority Records

  • Whenever possible, use non-catalog sources to verify biographical details that appear in catalog sources.
  • Whenever possible, provide 670 citations from non-catalog sources to justify additions to names in authorized access points.

Example:

no2018141858

100 1_ Bright, Michael R. ǂq (Michael Richard), ǂd 1978-

670 __ United States. Congress. Senate. Committee on Banking, Housing, and Urban Affairs. Nominations of Elad Roisman, Michael R. Bright, Rae Oliver Davis, and Dino Falaschetti, 2018: ǂb t.p. (Michael R. Bright, of the District of Columbia, to be President, Government National Mortgage Association) p. 2 (Michael Bright; career as a Senate staffer; Mr. Bright; leading voice on housing finance policy) p. 48 (Michael Richard Bright; date of birth: 29 Sept. 1978; place of birth: Warren, Ohio)

The middle name “Richard” and birth year of 1978 are both justified by the text viewed on page 48 of the work cited, not from a bibliographic record.

Using Data from Catalog Sources in Access Points

  • Under rare circumstances, authorized access points for persons may be formed using information from unauthorized access points found in existing bibliographic records (that is, from access points created by catalogers but not established in the NAF). 
  • Although these biographical details cannot be verified by GPO, their use in an authorized access point is permitted by the NACO Participants’ Manual, pages 21-22.
  • Generally, for access points found in the OCLC bibliographic file which have not become a person’s authorized access point, add a variant access point (MARC 400 field) to the person’s NAR.
    • Reminder: Check the NAF to ensure none of the added variants conflict with an authorized access point (MARC 1XX field).

Example:

[Hypothetical example]

100 1_ Hill, Robert B., ǂd 1934-

400 1_ Hill, Robert B. ǂq (Robert Bernard), ǂd 1934-

400 1_ Hill, Robert Bernard, ǂd 1934-

670 __ OCLC, Sept. 24, 2022 ǂb (access points: Hill, Robert B. (Robert Bernard), 1934- , Hill, Robert Bernard, 1934- ; usage: Robert B. Hill)

The middle name “Bernard” and birth year of 1934 are both taken from unauthorized access points in existing bibliographic records. The accuracy of these details could not be confirmed by a reasonable amount of additional research. Nevertheless, the information is used to distinguish the authorized and variant access points in this NAR from n92802682 and n79017954.

Bibliographic File Maintenance

  • When establishing a NAR for a person who already exists in the OCLC bibliographic file, maintenance may be needed for the Library of Congress (LC) catalog. For information about when and how to report records to LC, see Guidelines for reporting NACO BFM.

Example:

A GPO cataloger created a name authority record:

no2022100199

100 1_ Whitehead, Joan M.

400 1_ Whitehead, Joan Margaret

670 __ OCLC, July 25, 2022 ǂb (access points: Whitehead, Joan; Whitehead, Joan M.; Whitehead, Joan Margaret; usage: Joan Whitehead; Joan M. Whitehead)

The cataloger then performed a Browse search in the LC catalog for AUTHORS/CREATORS beginning with: Whitehead, Joan

There was one result: https://lccn.loc.gov/73169541

At the time of the cataloger’s search, the access point in LCCN 73169541 was: Whitehead, Joan. Because the access point represented the same entity as the new NAR but did not match the 100 in the NAR, it met the criteria for NACO’s Reportable BFM.

The cataloger emailed [email protected] to report that BFM was needed for LCCN 73169541 due to the creation of no2022100199.

Corporate/Conference Names

Before adding a new corporate name to the authority file, always search the OCLC authority file to see if the name is already established. If no record for the name is found, additionally search the OCLC authority file for any possible earlier (predecessor) names. One way to do this, is to conduct a keyword search using the parent body (should one exist), plus only one (at a time) of the following significant keywords. For example, when establishing: "United States. Environmental Protection Agency. Management Information Systems Division," enter the keywords: "Environmental Protection Agency Management." Conduct two additional searches: "Environmental Protection Agency Information," and: "Environmental Protection Agency System*." Use wildcards as needed to retrieve differing forms of a keyword.

If you find a similar name to the one you are creating, you must determine the relationship between the two names through research. For example: consult the publication in hand (the resource being cataloged), the Internet (including uncataloged publications found there), back issues of Carroll's Federal Directory, and of course, make phone calls or send emails. If you identify the existing authority record as the immediate predecessor, link the two records using properly coded reciprocal 510 or 511 fields. Only link immediately consecutive names; do not link names that are "twice removed." If a different type of relationship is found between your name and the existing name, and you feel it is important to bring out, you may add that information, reciprocally, to both records in the appropriate fields. Sometimes, it is helpful to add a 667 note such as: "cannot link directly to: [insert other name]," or "not same as: [insert other name]."

How Much Research Should Be Performed … ?

Perform the following research:

1. Quickly check the work cataloged and the agency Web site, to see if either contains a history section, which may include the very information you are seeking.

2. Search Carroll's Federal Directory for the name you are establishing (or updating). Use the year of Carroll's that matches the resource cataloged (or the closest year available). Next, search Carroll's Federal Directory for the similar, pre-existing name you found in OCLC. For this name, start with the same issue of Carroll's used to search for the name you are establishing, but if not found, search the next issue of Carroll's that matches (or comes closest to) the year cited in a 670 field of the OCLC record for the similar, pre-existing name. If both names are found, work your way through the intervening years of Carroll's (you may sample every few years), in order to identify name changes. This research may prove to be either conclusive or inconclusive.

Examples of a conclusive relationship:

Example:

a. A linear name change is identified. (Record the relationship)

b. Both names co-exist simultaneously. (Usually, no relationship is recorded. A 667 note may be added, in the form of "Not same as [other name]" or "Do not confuse with [other name]."

Negative evidence may also be considered conclusive. Examples:

Example:

a. Multiple name changes are found in between the two names; and two or more of these are not found in the OCLC authority file. No relationship is recorded. Option: if two intervening names are found in Carroll's which are not in OCLC's authority file, and the linear progression appears straightforward, you may search OCLC's bibliographic file for these names. If one or more are found, and the task of recording this progression appears to be fairly straightforward, you may apply the option in number 3 below, of establishing one or more of these names from the bibliographic records found in OCLC.

b. Two name changes are found, so that the two bodies you are seeking are linked to the same intervening body. If the intervening body is found in the OCLC authority file, all 3 bodies can be sequentially linked. If the intervening body is not found in the OCLC authority file, no relationship is recorded. You may, however, add a 667 note to the records for both bodies, in the form of "Cannot link directly to [other name]" or "Unable to link directly to [other name]." At the same time, you may also include the information found in Carroll's about the intervening body in a 670 note. Follow the name of the intervening body with "[no access point in OCLC, (insert date searched)]." (Or: "[no publications in OCLC database, (insert date searched)]") See LC-PCC PS 32.1.1.3: Earlier names not likely to be needed as relationships.

3. Now, you should search OCLC's bibliographic file for the intervening corporate body. If not found, you are done. However, if you do find the name in even one bibliographic record in OCLC, you may create an authority record for this name, with the caveat that the name is transcribed in the descriptive portion of the record. If the name is only found in access points (1XX, 6XX, 7XX) but not in the description (245, 260, 264, 5XX), do not create an authority record for it. If the name is found in the description, create an authority record for this intervening corporate body, formatting the first 670 in accordance with Name Authorities: 67X Citation Fields, OCLC Database. Be selective. You may list multiple usages that seem to be accurate transcriptions, and multiple headings that adhere to the rules under which the record was created. Once you create the authority record for the intervening corporate body, link it to its predecessor and successor records, and remove any preliminary 667 notes and "[no publications in OCLC database]" phrases. [Note: the procedure just described is somewhat out of sequence. This paragraph, which begins with "Now, you should search OCLC's bibliographic file," should logically occur after the third sentence in the paragraph just above this, after "no relationship is recorded." This somewhat illogical sequence is offered as a time-saver, since: (1) the information recorded from Carroll's provides a convenient place-holder, and (2), this information usually remains in the record since publications are not usually found in OCLC.]

Examples of an inconclusive relationship:

Example:

a. Only one or none of the names are found in Carroll's.
b. The names found in Carroll's are different, and cannot be matched with those you are seeking.

If searching Carroll's is inconclusive, contact the agency via phone call or email, asking if a direct relationship can be identified between the two names. If not, your research is completed, and you may establish the new corporate body without recording any relationship.

While the above research may seem excessive when similarly named corporate bodies are only cited in publications that may be 35 or more years old, surprises have come up, when the earlier name has persisted, and only recently changed to the name that is being established. It is worth a couple of hours of research to identify or dismiss such relationships, in order to expand user access to successors and predecessors.

When to Consult Additional Sources

If research in OCLC does not result in any possible related names, it is usually not necessary to consult any additional sources beyond the resource cataloged. However, if the resource cataloged is not issued by the entity whose name you are establishing in the authority file, do consult at least one additional source. This guidance would apply to all names, corporate or personal, that are needed as subjects for the resource cataloged (unless said name also issued the work). For a corporate body, it will usually suffice to consult its Web site, in addition to the resource cataloged. For a personal name, a few searches on the Internet will usually suffice to determine the preferred name. GPO's local policy is based on its experience that publications issued by an entity tend to be more accurate in rendering their name than publications not issued by them.

Therefore, for corporate bodies, GPO prefers the name found in items issued by that body. When a resource is not issued by a corporate body, consult an additional source such as its Web site, which is issued by that body. If the name on the Web site or other source issued by the body differs from the name in the resource cataloged, use the name on the Web site as the preferred name, and the name on the resource cataloged as the variant name. Use the resource cataloged as the first 670, even though the name cited therein was not chosen for the 1XX. Use the Web site (or other source issued by the body) as the second 670. Many USGS reports (in various series) exemplify this situation.

Example:

On the t.p. of the resource cataloged: "prepared in cooperation with City of Hopkinsville, Kentucky, Community Development Services." This body did not issue this USGS report, therefore, consult: City of Hopkinsville, Community and Development Services Web site: "City of Hopkinsville, Community and Development Services." [Note the addition of the word "and" after "Community."]

Thus: 1101 Hopkinsville (Ky.). ǂb Community and Development Services

4101 Hopkinsville (Ky.). ǂb Community Development Services

670 Flood-inundation maps for an 8.9-mile reach of the South Fork Little River at Hopkinsville, Kentucky, 2013: ǂb PDF t.p. (City of Hopkinsville, Kentucky, Community Development Services)

670 Community and Development Services, City of Hopkinsville [Ky.] Web site, Apr. 9, 2013. [Note: no ǂb is needed, because it would add nothing to the ǂa, which itself adds nothing to the 1XX.]

What if the Web site contains the same exact name as the item—should the Web site still be cited even though it contains no additional information? In this situation, when the item is not issued by the body, go ahead and cite the Web site in an additional 670, even though the name found is redundant. Thus:

Example:

On the t.p. of the resource cataloged: "prepared in cooperation with the Massachusetts Department of Fish and Game, Division of Ecological Restoration."

1101 Massachusetts. ǂb Department of Fish and Game. ǂb Division of Ecological Restoration

670 Estimated sediment thickness, quality, and toxicity to benthic organisms in selected impoundments in Massachusetts, 2013: ǂb PDF t.p. (Massachusetts Department of Fish and Game, Division of Ecological Restoration)

670 Massachusetts Department of Fish and Game, Division of Ecological Restoration Web site, Apr. 10, 2013.

When searching the Internet for names, in the situations described above, generally avoid citing Wikipedia. This instruction applies to names, not to subjects. For the Wikipedia policy on subjects, see Subject Cataloging: Subject Heading Proposals, Background and Tips. For names, use sources other than Wikipedia whenever possible.

Tips for contacting agencies

  • Take time to identify knowledgeable contacts. Use the agency's Web site, or Carroll's Federal Directory.
  • Do your homework first so you can determine, identify, and develop your questions.
  • Begin with: "Hello, I'm calling/emailing from the U.S. Government Publishing Office."
  • Explain what we do, why, and what your questions have to do with this.
  • Use layperson language, not cataloger language. Instead of using the term "corporate body," which might connote "corporations," speak in terms of "government authors and issuing bodies of publications," for which we provide "access points" for searching.
  • Explain what you found, and what you don't know.
  • Ask open-ended questions.

How to Recode an Existing NAR from AACR2 to RDA

  • Change coding in Rules ("z") and 040 (ǂe "rda") to identify the record as RDA.
  • Ensure the 1XX is RDA compliant. If it is not, change it.
  • If you change the 1XX, enter the former 1XX in a 4XX field. Add a ǂw to this 4XX field using either of the following values: (a) nnea for an old, valid AACR2 heading, or, (b) nne for a valid RDA variant access point. In case of doubt, use nnea. Don't forget to apply the rules of NACO Normalization to ensure that this 4XX does not normalize to the same form as the 1XX. If it does, remove it.
  • If there is a 7XX field in the record:
    • If the 7XX field matches the 1XX field, delete the 7XX field.
    • If the 7XX field has a 2nd indicator 4, delete the 7XX field.
    • If the 7XX and the 1XX field do not match, then do not delete the 7XX field.
  • At the time of the re-coding, add references (4XX and 5XX) and 670 citations to the authority record as needed, either with new information, or using information already contained in the record. You may optionally add optional fields such as 046, 368, 37X, etc., if the information is readily and speedily available. Otherwise, do not add any optional fields.
  • 5XX references in AACR2 format do not need to be changed to RDA. They are acceptable under PCC rules.
  • If present, delete the MARC 667 instruction to re-evaluate before use in RDA.

 

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