Skip to main content
  • GPO
    • U.S. Government Publishing Office
    • govinfo
    • U.S. Government Bookstore
    • Ben's Guide to the U.S. Government
  • Contact Us
  • Login
FDLP
  • Collection Tools
    • Claims
    • DSIMS
    • Item Lister
    • List of Classes
    • Reporting Publications
    • FDLP eXchange
    • PURL Usage Reporting Tool
    • Shipping Lists
    • Shipping List this Week
    • WEBTech Notes
    • UNION-L
    • CGP on GitHub
    • FDLP LibGuides
  • Requirements & Guidance
    • Regulations
    • Guidance
    • Instructions
    • Collections & Databases
    • Promotion
    • FDLP eXchange Tips
  • Preservation
    • Preservation at GPO
    • Trusted Digital Repository ISO 163663:2012 Audit and Certification
  • About The FDLP
    • Superintendent of Documents
    • Federal Depository Libraries
    • Depository Library Council
    • FDLP Academy
    • Events and Conferences
    • FDLP Training
    • FDLP Events Calendar
    • Projects
    • Partnerships
    • File Repository
    • Mission & History
    • The Essential FDLP
    • 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
    • Regional Depositories' OCLC Holding Symbols to GPO Cataloging
  1. Home
  2. GPO Cataloging Guidelines
  3. Name Authorities: Policy Overview

Name Authorities: Policy Overview

  • Last Updated: February 01, 2023
  • Published: November 10, 2021

GPO's participation in NACO is limited to the following:

  • With the exception of certain titles that do not need to be established (see SHM H 1435), all names and titles used as subjects in 6XX fields of bibliographic records must be confirmed in the OCLC authority files. This includes personal names, corporate/conference names, works and expressions (previously called uniform titles), and jurisdictional geographic names that appear in the 6XX fields of bibliographic records. A temporary exception may be made for Congressionals or other priority titles, when names used in these as subjects (fields 600, 610, or 611) are in the process of having NACO records prepared.
  • For names and titles used as author or title descriptive access points in bibliographic records (fields 1XX, 7XX, and 8XX), consult the specific sections below: Personal Names, Corporate/Conference Names, Works and Expressions, and Places. In all cases, Congressionals or other priority titles may be produced with unauthorized access points (at I level), as a temporary measure, while name authority work for these is still in process.
  • Errors: Transcription and other errors occurring in existing authority records are corrected if they were created by GPO or traced as authorized access points in a GPO bibliographic record.

Personal Names

Name authority records (NARs) are created or updated for personal names used as subjects in GPO bibliographic records.

Whether NARs are created or updated for personal names used as non-subject access points depends upon the type of publication cataloged.

Whether NARs are comprehensive or brief depends upon the cataloger’s research.

Congressional, CRS, LC Law, and ECIP Publications

  • All personal name access points (MARC 100, 600, 700) must be authorized in bibliographic records for publications from the following sources:
     
    • Congress
    • Congressional Research Service (CRS)
    • Law Library of Congress (LC Law)
    • Electronic Cataloging in Publication (ECIP)
       
  • Create a NAR if none exists.
     
  • Update an existing NAR if needed to correct an erroneous access point or to help users identify the person.

Other Publications

  • For publications which are not from Congress, CRS, LC Law, or ECIP:
     
    • Subject (MARC 600) fields:
      • Create a NAR if none exists.
         
    • Associated agent (MARC 100/700) fields:
      • To determine whether a NAR should be created, see the policy in Bibliographic Cataloging: General MARC Field Policies, 100/700 - Personal Name Access Points.
         
    • Any MARC X00 field:
      • Update an existing NAR if needed to correct an erroneous access point or to help users identify the person.

Comprehensive Name Authority Records

  • 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: RDA, Personal Names.
     
    • Exception: Create a brief name authority record if warranted according to the guidance below.

GPO Practice

  • 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:
     
    • Fuller form of name
    • Profession or occupation
    • Other term of rank, etc.
      • e.g., ǂc Ph. D.
    • Associated institution
      • Use the authorized access point for the corporate body when possible; modify punctuation as needed for clarity.
      • e.g., ǂc (Of the United States Government Publishing Office)

Brief Name Authority Records

GPO Practice

  • 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., ǂd active 1964
             
        • 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., ǂc (Author of Development of a taxonomy of human performance)

      Corporate/Conference Names

      New corporate name authority records, including those for conferences, are created, and existing authority records are updated for all publications requiring corporate body access points, including main entries (110 and 111 fields), subject added entries (610 and 611 fields), or added entries (710 and 711 fields).

      Variant Names

      Variant forms of corporate names appearing in publications cataloged after an authority record has been created are added to existing records.

      Conference Authority Records

      These are not created for individual conference papers nor are conference access points included in bibliographic records for individual papers.

      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 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 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, RDA, Corporate Bodies 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 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, RDA, Works and Expressions.

      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.) (This 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, RDA, 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)
    • 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
    • 6.0 Cataloging Levels Chart
    • 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
      • Adapting PCC Pre-RDA Records
      • Adapting Non-PCC Pre-RDA Records
      • Authenticating Non-PCC Pre-RDA Records as PCC
      • Replacing and Exporting Records
    • GPO Sales Program Information
      • Original Cataloging for Sales Program
      • Copy Cataloging for Sales Program
    • Authority 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
    • Variable Fields
      • 037 - Source of Acquisition
      • 040 - Cataloging Source
      • 050 - Library of Congress (LC); 060 - National Library of Medicine (NLM); 070 - National Agricultural Library (NAL); 082 - Dewey Decimal Classification and Call Number
      • 100/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: 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
      • Related Chapters/Sections
      • Related Resources
      • Related Works and Expressions - Overview
      • Frequently Revised Monographs
      • Language Editions and Translations
      • Revised Editions
      • Summaries
    • Unspecified Relationships and MARC 787
  • 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: Continuing Resources: Selective Registration for ISSN Assignments
      • ISSN Program – General Information
      • ISSN Assignments
  • 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
  • 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: Appendix A
    • Appendix A: Bibliographic File Maintenance: Deletion of Records from the CONSER Database
  • Bibliographic Cataloging: Continuing Resources: Appendix B
    • Appendix B: Where to Find Certain CONSER Procedures
  • Bibliographic Cataloging: Continuing Resources: Appendix C
    • 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
      • 050 - Library of Congress Call Number
    • 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
      • 050 – Library of Congress Call Number
      • 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 Visitor Guides Treated as Books or Continuing Resources
  • 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: Background
    • Instructions to Consult
  • Name Authorities: Policy Overview
    • Personal Names
      • Congressional, CRS, LC Law, and ECIP Publications
      • Other Publications
      • Comprehensive Name Authority Records
      • Brief Name Authority Records
    • Corporate/Conference Names
      • Variant Names
      • Conference Authority Records
      • 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: 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
  • 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: RDA, General Policies
    • Hybrid Records in RDA Name Authority Records (NARs)
    • When to Recode an Existing NAR to RDA
    • How to Recode an Existing NAR from AACR2 to RDA
    • 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: RDA, 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: RDA, Corporate Names
    • Notes
    • Sources to Consult
    • Before You Begin
    • MARC Fields
      • 110 - Corporate Name
      • 111 - Meeting Name
      • 368 - Other Attributes of Corporate Body, ǂa Type of Corporate Body
      • 370 - Associated Place
      • 372 - Field of Activity
      • 373 - Associated Group (11.5)
      • 410/411 - See From Tracing
      • 410 - See From Tracing - Corporate Name
      • 411 - See From Tracing - Meeting Name
      • 510/511 – See Also From Tracing (Related Corporate/Conference Name)
      • 510 - See Also From Tracing - Corporate Name
      • 667 - Nonpublic General Note
      • 678 - Biographical or Historical Data (11.11)
  • Name Authorities: RDA, Works & Expressions
    • 046 – Special Coded Dates (RDA 6.4 and 6.10)
    • 130 – Authorized Access Point
    • 336 – Content Type (RDA 6.9)
    • 370 – Associated Place (RDA 6.5)
    • 377 – Associated Language (RDA 6.11)
    • 380 – Form of Work (RDA 6.3)
    • 410/430 – Variant Authorized Access Points
    • 667 – Nonpublic General Note
    • 670 – Source Data Found
    • EXEMPLARS
  • Name Authorities: RDA, Places
    • 043 - Geographic Area Code
    • 451 - See From Tracing 
    • 670 - Source Data Found
    • 781 - Subdivision Linking Entry-Geographic Subdivision
  • 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
    • 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
      • SHM Subject Headings Manual
      • 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
  • List of Major Changes to the Cataloging Guidelines
FDLP

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

Privacy Policy

Connect with GPO