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. Bibliographic Cataloging: Technical Reports

Bibliographic Cataloging: Technical Reports

  • Last Updated: July 25, 2023
  • Published: February 14, 2022

Identification of Technical Reports

Technical reports provide the results of scientific and technical research. They are typically narrow in scope and usually report on a single research effort. Although they may report on more than one experiment or research effort, they do not provide the wide range of information and theory that is provided in general scientific and technical publications. Most are organized in the same way. The initial paragraphs normally include background information and the objectives of the research efforts undertaken. The research methodology is described. Problems encountered and the limits imposed by the research methods are covered. The final paragraphs or sections are devoted to the results, analysis of results, conclusions, and recommendations.

Former Practice

There is more than one definition for technical reports. For cataloging purposes, GPO previously identified technical reports based on one or more of three definitions.1 In addition, GPO considered “all documents to be technical reports that:

  1. Belong to a technical report series or to a series that primarily includes technical reports.
  2. Contain a technical report documentation page, bibliographic data sheet, research report page, or other similar page.” Ibid.

In 2015, GPO’s Library Services & Content Management took the opportunity to review its definition and practice for cataloging technical reports. In that same year, GPO joined the TRAIL (Technical Report Archive & Image Library) initiative and was in the process of revising its Cataloging Guidelines. As a result, GPO has changed its practice as follows: “belonging to a technical report series” is still a criterion for technical reports, but containing a “technical report documentation page, bibliographic data sheet, research report page, or other similar page” is not.

Current Practice

Effective September 1, 2016, with the publication of this chapter of the Cataloging Guidelines, GPO now applies the following definitions or criteria to identify technical reports for cataloging purposes:

  1. GPO considers all documents to be technical reports that belong to a technical report series or to a series that primarily includes technical reports. (This criterion is self-sufficient; no other criteria need be met or considered.) 

    If a document does not meet this criterion, then proceed to definition number 2. For cataloging purposes, documents that meet definition number 2 below, plus one additional definition from numbers 3-5 below, are considered to be technical reports.
     
  2. *(Required, unless criterion 1 is met) A report giving the scientific results of research or developmental investigations or other technical studies in the sciences, technology, engineering, or agriculture. It is not a compilation of data. Technical reports are usually concerned with only one specific subject or a few related subjects and provide information of more than transient interest. They are not administrative or legal in nature, nor do they concern the activities of the issuing agency. (GPO definition, compiled from parts of other definitions and personal communications from subject matter experts)

    If a document meets this definition, then it must meet one additional definition from numbers 3-5 below, in order to be considered a technical report.
     
  3. A report giving details and results of a specific investigation of a scientific or technical problem.--ALA Glossary
     
  4. A brief, generally unbound, interim report covering ongoing research in general areas of science and technology (Excludes: social sciences, economics, and "soft" sciences).—Library of Congress’ Descriptive Cataloging Manual (DCM)
     
  5. From: OCLC. Bibliographic Formats and Standards, 4th ed.
     
    1. “According to ANSI Z39.23 (1983), … a technical report is a document that gives the result of research or developmental investigations, or both, or other technical studies. . . A technical report is initially submitted to the person or body for which the investigation was carried out or by which it was sponsored. Copies of it may subsequently be made available in limited quantities. . . , but these copies are not produced commercially and are not available from booksellers or other commercial sources. . . . Technical reports are usually published irregularly, either in series or as separate monographs. Technical reports are not typeset but are reproduced from typescript by near-print processes, and they are usually concerned with only one specific subject or with a few closely related subjects.”--3. Special Cataloging Guidelines, 3.3 Technical Reports
       
    2. “… an item that is the result of scientific investigation or technical development, testing, or evaluation, presented in a form suitable for dissemination to the technical community.”-- Fixed-Field Elements: Cont = Nature of Contents 
       
  6. GPO formerly considered all documents that contained a technical report documentation page, bibliographic data sheet, research report page, or other similar page, to be technical reports. This former, second self-sufficient criterion (the first was series) no longer applies. While many technical reports will contain such a report page or data sheet, this is no longer a consideration for identifying technical reports.

When in doubt, do not treat the publication as a technical report.

Examples of technical reports:

Example:

1. OCLC *904623722
245 10 On the relationship between the length of season and tropical cyclone activity in the North Atlantic basin during the weather satellite era, 1960-2013
830 0 NASA technical publication ; ǂv 2014-218199.

This belongs to a technical report series, meeting definition 1 above.

Example:

2. OCLC *841296278
245 10 Application of welded steel sandwich panels for tank car shell impact protection …

This does not belong to a series, however, the material clearly fits the definition of a technical report.

Example:

3. OCLC *907476640
245 10 Design criteria for adaptive roadway lighting …

This does not belong to a series, but clearly fits the definition of a technical report.

Example:

4. OCLC *905003191
245 10 Improving access to foundational energy performance data …
830 0 NREL/TP ; ǂv 5500-61543.

This belongs to a technical report series, meeting definition 1. (If it did not belong to a series, the cataloger would determine that it meets the definition of a technical report.)

Example:

5. OCLC *922576959
245 10 CyFall : ǂb a cyber-network game scenario …
830 0 ARL-TR (Aberdeen Proving Ground, Md.) ; ǂv 7024.

This belongs to a technical report series. (If it did not, it still fits the definition of a technical report.)

Examples that are not technical reports:

Example:

1. OCLC *905542987
245 00 Safety evaluation report related to the license renewal of Limerick Generating Station, Units 1 and 2 : ǂb Docket Nos. 50-352 and 50-353 / ǂc U.S. Nuclear Regulatory Commission, Office of Nuclear Reactor Regulation.

This document does not belong to a series. Rather than meeting one of the definitions of a technical report, this is a safety evaluation report which fulfills the licensing responsibilities of the issuing agency—it is not research per se. Reports of a legal or administrative nature, or reports that deal with the activities of the issuing agency do not meet definition 2. Having a bibliographic data sheet is no longer a criterion of a technical report.

Example:

2. OCLC *903900380
245 10 Long-term bridge performance high priority bridge performance issues …

This document does not belong to any series. Having a Technical report documentation page is no longer a criterion of a technical report. From the abstract: “The Long-Term Bridge Performance (LTBP) Program was initiated to collect, store, and analyze the data necessary to better understand high priority bridge performance issues. The success of the program depends on first being able to identify the most important performance issues bridge owners face. To identify these issues, input from those bridge owners and other key stakeholders was sought. As part of this outreach, bridge experts in 15 State transportation departments were interviewed and asked to name the performance issues in their bridge inventory that are most common and/or most difficult to solve. The findings of these interviews are included in this report. To supplement these interviews and identify high priority issues related to bridge substructures, a workshop on substructure performance issues was held. The findings from the interviews and the substructure workshop were used to develop a list of 22 high priority performance issues. From this list, a shorter list of six bridge performance issues was recommended as the first group of issues for study under the LTBP Program.”

The research and results of this report are broader in scope than that of the typical technical report, and are performed in order to identify issues for study in the issuing agency’s Long-Term Bridge Performance Program. Reports that deal with the activities of the issuing agency, or reports of an administrative or legal nature do not meet definition 2.

Example:

3. OCLC *227937101
245 10 History of operations research in the United States Army …

This document belongs to a series, but not a technical report series. This manifestation was accessed from the Defense Technical Information Center (DTIC), and, like many of their online reports, has a Report documentation page--however, this is no longer a criterion. From the abstract:

  • “In this, the first of three planned volumes, Dr. Charles R. Shrader has for the first time drawn together the scattered threads and woven them into a well-focused historical narrative that describes the evolution of OR in the U.S. Army, from its origins in World War II to the early 1960s. … he has managed to provide a comprehensive history of OR in the U.S. Army …”

Obviously, this history is not a technical report, even though it includes DTIC’s Report documentation page.

Example:

4. OCLC *910560879
245 10 SAFETEA-LU 1808 : ǂb CMAQ evaluation and assessment : phase I final report …
246 1 Safe, Accountable, Flexible, Efficient, Transportation Equity Act: a Legacy for Users
246 1 ǂi Title on technical report documentation page: ǂa SAFETEA-LU 1808 : ǂb Congestion Mitigation and Air Quality Improvement Program evaluation and assessment -- phase 1 final report
610 20 Congestion Mitigation and Air Quality Improvement Program (U.S.) ǂx Evaluation.

This document does not belong to a series. Having a Technical report documentation page is no longer a criterion. From the abstract of this 150 page report:

  • “In SAFETEA-LU Section 1808, Congress required the U.S. Department of Transportation, in consultation with the Environmental Protection Agency, evaluate and assess the direct and indirect impacts of a representative sample of Congestion Mitigation and Air Quality (CMAQ) –funded projects on air quality and congestion levels. This study responds to that request by analyzing 67 CMAQ-funded projects … The study team also conducted additional analyses of the selected set of CMAQ-funded projects to estimate their cost-effectiveness at reducing emissions of each pollutant.”

From the table of contents:

        “4.  Project Analysis and Selection Practices that Support Effectiveness---------------------50
         Emissions Reduction Cost-Effectiveness----------------------------------------------------------------50
         Examples of Good Practices---------------------------------------------------------------------------------60
         Next Steps---------------------------------------------------------------------------------------------------------66”

This is the final report of phase 1 of a Congressionally mandated evaluation of the issuing agency’s Congestion Mitigation and Air Quality Improvement Program—it is not research per se. Reports of a legal or administrative nature, or reports that deal with the activities of the issuing agency do not meet definition 2.

Monograph or Serial

Technical reports that qualify to be serials based on the definition for serials in the RDA Glossary are cataloged following the instructions for serial cataloging listed in the GPO Cataloging Guideline: Serials.

Sources of Information

The sources of information used to catalog technical reports are generally the same as those used for other language (meaning textual or printed) materials. Information is taken from one of the preferred sources mentioned in RDA 2.2.2 (see Bibliographic Cataloging: General Policies), or from the report documentation page, bibliographic data sheet, etc. Generally, take information, such as the performing organization, sponsoring or funding body, contract, grant, or task numbers, etc., only from the resource itself, not from external sources, such as the agency’s web site.

Cataloging Instructions

For specific input conventions, detailed field/subfield definitions, etc., consult:
MARC 21 Format for Bibliographic Data 
OCLC. Bibliographic Formats and Standards. 4th ed.

Fixed Fields

1. Cont: Nature of Contents:

Code “t” for technical report

2. DtSt: Type of Date/Publication Status and Date 2

DtSt: Use code “e” (detailed date) for all technical reports, if the information is readily available in the document. Use if the issue date includes year and month, or year, month and day. If only the year of publication is given in the document, then use code “s” (single date).
Date 2: Enter 2-4 numbers for either: month (mm__), or month plus day (mmdd). Follow MARC instructions.
(For the 264ǂc, shown in the example below, see the 264ǂc – Date of Publication, Distribution, Manufacture, etc. section, under “Variable Fields.”)

Example:

DtSt: e
Date 1: 2013, Date 2: 11__ (If no day on piece, leave the final two characters of Date 2 blank)
264 ǂa Washington, D.C. : ǂb U.S. Department of Transportation, ǂc November 2013.
500 “November 2013.”

Variable Fields

General Guidance on Special Technical Report Fields

If any of the information appropriate for one of the technical report fields is already being used elsewhere in the record (title, series, publisher’s name, statement of responsibility, etc.), it is, nevertheless, repeated in the relevant special technical report fields. This redundancy is a deliberate reversal of the previous GPO policy of not repeating such information in the specific technical report fields. It is made in the interest of simplicity, in order to avoid excessive deliberation. No harm is done by this slight redundancy; in fact, the different fields record separate data elements even if the data is redundant.

Example:

513 Technical report.
830 Technical report (United States. Federal Highway Administration)

Required Fields

The following special fields are required in GPO technical report catalog records, if applicable:

027 Standard technical report number

(Required when information is available)
See the section below, 027 – Standard Technical Report Number, for more detail.

513 Type of report and period covered note

(Required when information for subfield “a” is available)

Subfield “a” -- Type of report
Subfield “b” -- Period covered
See the section below, 513 – Type of Report and Period Covered Note, for more detail.

536 Funding Information Note

(Required when information is available)

Subfield “a” -- Text of note
Subfield “b” -- Contract number
Subfield “c” -- Grant number
Subfield “d” -- Undifferentiated number associated with the material that identifies a funding or contract-related number
Subfield “e” – Program element number
Subfield “f” – Project number
Subfield “g” – Task number
Subfield “h” – Work unit number

See the section below, 536 – Funding Information Note for more detail.

027 – Standard Technical Report Number

(Required when information is available)

A Standard Technical Report Number (STRN) is included only if it is found on a publication and specifically designated as an STRN. All other report numbers are entered in the 088 field. An STRN must appear on the technical report page to be treated as an STRN. If an STRN appears in different forms throughout a document, the form that appears on the technical report page is preferred.

GPO spacing conventions are observed when recording STRNs. If an STRN has been established in a series authority record as a series-like phrase, it is recorded in the 088 field not the 027 field. If it has been established as a series, it is recorded in the 490/830 field, not the 027 field.

An STRN number is formulated according to International Standard Technical Report Number (ISRN), ISO 10444, or Standard Technical Report Number Format and Creation, ANSI/NISO Z39.23-1997 or Standard Technical Report Number (STRN), Format and Creation, ANSI Z39.23-1983. For more details on the structure of an STRN see MARC 21 Format for Bibliographic Data: 027.

Example:

027 ǂaFYHU/PF/2--80/12+MAGN
027 ǂaWBK-MTT--89/64--DE
027 ǂaMETPRO/ED/SR-77/035

110/710 – Corporate Name Authorized Access Point

Non-federal bodies are given authorized access points if they appear either: (a) on the bibliographic data sheet in conjunction with a corresponding contract, grant, or other funding number, or, (b) in a formal statement, such as a statement of responsibility, on the preferred source of information. No contract, grant, or other funding number is necessary if the body’s name appears in a formal statement on the preferred source.

Sponsors are only given authorized access points when they also function as the author, issuing body, or publisher.

110 – Main Entry: Corporate Name

Corporate bodies, including non-Federal bodies, are entered in the 110 field when the work cataloged meets one of the categories in 19.2.1.1.1.

See the section above, 110/710 – Corporate Name Authorized Access Point, for general guidance on providing authorized access points for corporate bodies.

245ǂc – Statement of Responsibility

"Sponsored by ...", "Prepared for ..." and similar statements may be recorded in full in the statement of responsibility for technical reports, even when they are not inextricably combined with "Prepared by ..." statements. For efficiency, the entire statement may be recorded in the statement of responsibility, as long as it includes a corporate body that is “responsible for the creation of, or contributing to the realization of, the intellectual or artistic content of” the resource. The part of the statement relating to the corporate body financing the work, or simply the corporate body’s name, may then be repeated in the 536 subfield a.

Example:

Document: Prepared for Y
536: Prepared for Y

Document: Prepared by X, prepared for Y
245: ǂc prepared by X ; prepared for Y. OR
245: ǂc prepared by X.
536: Prepared for Y

Document: Prepared by X for Y
245: ǂc prepared by X for Y. OR
245: ǂc prepared by X.
536: Y

Document: Prepared for Y by X
245: ǂc prepared for Y by X.
536: Y

Contract, grant, or other funding numbers may be recorded as part of the statement of responsibility, when appropriate.

Example:

245 [Title] / ǂc Transport Inc. under contract number 12345.

264ǂc – Date of Publication, Distribution, Manufacture, etc.

Use the detailed date (month, day, year) if readily available in the document. If the day is not given, record the month and year.

Example:

264 ǂa Washington, D.C. : ǂb U.S. Department of Transportation, ǂc November 2013.

500 – General Note

The performing body or organization may be recorded in this field, if its name does not appear on the preferred source of information. Most commonly, it will appear in the “Performing Organization” field of the Report documentation page/Bibliographic data sheet, in conjunction with a corresponding contract, grant, or other funding number.

Example:

OCLC *911203080
245 10 Long-term pavement performance Ohio SPS-1 and SPS-2 dynamic load response data processing
500 “Performing organization: Engineering & Software Consultants, Inc.”—Technical report documentation page.
536 Office of Infrastructure Research and Development, Federal Highway Administration ǂb DTFH61-12-C-00002
710 2 Engineering & Software Consultants.

On the technical report documentation page of this resource, “Engineering & Software Consultants, Inc.” appears in the “Performing Organization” field, and DTFH61-12-C-00002 appears in the “Contract or Grant No.” field.

tech report image

513 – Type of Report and Period Covered Note

(Required when information for subfield “a” is available)

This field is only used for technical reports. Information for this field may be taken from one of the preferred sources mentioned in RDA 2.2.2, or from the report documentation page, bibliographic data sheet, etc.

The type of technical report and period covered note is entered only when the information is found in the publication being cataloged. Punctuation and spacing, but not necessarily capitalization, should be transcribed as it appears on the document. The technical report documentation page is preferred as the source of the information if the same or similar wording is found elsewhere on the publication. This note is still entered, even if the same information is transcribed elsewhere in the catalog record (i.e. title, series statement, etc.).

The preferred source of information for ǂa (type of report) is the “type of report” section of the report documentation page, bibliographic data sheet, etc. The preferred source of information for ǂb (period covered) is the “period covered” section of the report documentation page, bibliographic data sheet, etc. Subfield “a” is mandatory, so if a publication lacks information about the type of report, the 513 field is not entered at all, even if there is information about the period covered.

Subfield “a,” Type of report is mandatory in the 513 field. It is used when the wording on the document indicates what kind of report it is.

Example:

Quarterly progress report.
Interim report.
Final report. 
Contractor report.
Research report. 
Technical report.

Any wording on the technical report documentation page, in the space marked "Type of report", should be transcribed in the 513 field, even if it repeats information given elsewhere in the cataloging record, for instance, in the series note or in the title.

If different but similar wording appears on other sources, prefer the form of information on the documentation page.

Example:

Documentation page: Technical
Title page: Technical report
513 field: Technical.

Subfield “b,” Period covered, is used for the inclusive dates of coverage of the report. This information is normally given on the documentation page in the area labeled "Period covered." Since subfield “a” is mandatory in the 513 field, if a publication lacks information about the type of report, the 513 field is not entered at all, even if there is information about the period covered. A 513 field having only subfield “b” will not validate.

Example:

Documentation page: Oct 80 - July 1983
513 field: Oct 80 - July 1983

Punctuation and spacing, but not necessarily capitalization, should be transcribed as on the document.

536 – Funding Information Note 

(Required when information is available)

Funding information for any publication is included in field 536, to identify financial sponsorship, as well as contract, grant, project, task, and work unit or other funding numbers.

No indicators are defined for the 536 field. These subfields are:

Subfield “a” -- Text of note (Information concerning the sponsors or funding agencies)
Subfield “b” -- Contract number
Subfield “c” -- Grant number
Subfield “d” – Undifferentiated number associated with the material that identifies a funding or contract-related number
Subfield “e” – Program element number
Subfield “f” – Project number
Subfield “g” – Task number
Subfield “h” – Work unit number

Subfield “a” is used to record the corporate body financing the work. This body will typically be named in a "Sponsored by ..." or "Prepared for ..." statement on a preferred source, or it will appear in the space labeled "Sponsoring agency name and address" on the technical report documentation page. Either the complete unabbreviated statement from the preferred source, or only the name itself from the documentation page, may be used. A third alternative is to transcribe the name from the documentation page’s "Sponsoring agency name and address" space, preceded by the words “Sponsored by.” If a "Sponsored by ...", "Prepared for ..." or similar statement appearing on a preferred source is not recorded in the statement of responsibility, it should be transcribed in full in the 536 subfield a. Include the sponsoring body in the 536 subfield “a,” even if the same body also appears in the 264 or 260 field.

Example:

264 _1 Washington, DC : ǂb U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research, ǂc [2016]
536 ǂa Sponsored by U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research

OR

264 _1 Washington, DC : ǂb U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research, ǂc [2016]
536 ǂa U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research

Subfield “a” does not include the body which is named as the “performing” body or organization. A “performing” body is included in either the statement of responsibility or a 500 note. See the sections 245ǂc – Statement of Responsibility and 500 – General Note00 – General Note above.

Portions of "Sponsored by ...", "Prepared for ..." and similar statements that have been recorded in the statement of responsibility for technical reports, may be repeated in the 536 subfield a. Specifically, the part of the statement relating to the corporate body financing the work, or simply the corporate body’s name, may be repeated. If a "Sponsored by ...", "Prepared for ..." or similar statement appearing on a preferred source is not recorded in the statement of responsibility, it should be transcribed in full in the 536 subfield a.

Example:

Document: Prepared for Y
536: Prepared for Y

Document: Prepared by X, prepared for Y
245: ǂc prepared by X ; prepared for Y. OR
245: ǂc prepared by X.
536: Prepared for Y

Document: Prepared by X for Y
245: ǂc prepared by X for Y. OR
245: ǂc prepared by X.
536: Y

Document: Prepared for Y by X
245: ǂc prepared for Y by X.
536: Y

Sponsors are only given authorized access points (in field 710 or 110) when they also function as the author, issuing body, or publisher. See example under section, 710 – Added Entry: Corporate Name.

Use designated subfields for funding and contract-related numbers, such as contract, grant, project, task, and work unit numbers. The numbers in subfields ǂb through ǂh are transcribed as the data appears on the publication. Do not apply GPO spacing conventions for numbers (also known as General Number Spacing Policies). The preferred source for these numbers is the documentation page. Do not use an unformatted 536 note. The sponsoring body should be included in the ǂa, and all numbers should be included in the designated subfields.

Subfields ǂe, ǂf, ǂg and ǂh may not be used with subfield ǂd, therefore, if needed, use two 536 fields to cover all funding and contract-related numbers in the document.

Subfields “b,” “c,” and “d” formerly appeared in the Monthly Catalog contract number index. All of the 536 field is currently (as of August 2016) indexed in the following CGP searches: WRD (all keywords), WNO (all notes), and in Advanced Search, searching in: All Notes, Technical Report Number, and Contract Number.

The 536 field should be formatted as follows:

Example:

536 ǂa Office of Infrastructure Research and Development, Federal Highway Administration ǂb DTFH61-12-C-00002

OR

536 ǂa Sponsored by Office of Infrastructure Research and Development, Federal Highway Administration ǂb DTFH61-12-C-00002

Example:

536 ǂa Sponsored by U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research ǂb A 2223 ǂd DOE 40-550-75

OR

536 ǂa U.S. Nuclear Regulatory Commision, Office of Nuclear Regulatory Research ǂb A 2223 ǂd DOE 40-550-75

Field 536 does not end with a mark of punctuation unless the field ends with an abbreviation, initial/letter, or other data that ends with a mark of punctuation.

710 – Added Entry: Corporate Name

For convenient reference, the following guidance is repeated, with a minor addition, from the above section, 110/710 – Corporate Name Authorized Access Point.

Non-federal bodies are given an authorized access point if they appear either: (a) on the bibliographic data sheet (often in the “Performing Organization” field) in conjunction with a corresponding contract, grant, or other funding number, or, (b) in a formal statement, such as a statement of responsibility, on the preferred source of information. No contract, grant, or other funding number is necessary, if the body’s name appears in a formal statement on the preferred source.

Example:

500 “Performing organization: Engineering & Software Consultants, Inc.”—Technical report documentation page.
536 Office of Infrastructure Research and Development, Federal Highway Administration ǂb DTFH61-12-C-00002
710 2 Engineering & Software Consultants.

bib-cat report-2

Example:

245 [Title] / ǂc prepared by Leidos, Inc. for the National Cancer Institute.
710 2_ Leidos, Inc.

Sponsors are only given authorized access points when they also function as the author, issuing body, or publisher.

Example:
264 _1 Washington, DC : ǂb U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research, ǂc [2016]
536 ǂa Sponsored by U.S. Nuclear Regulatory Commission, Office of Nuclear Regulatory Research
710 2_ U.S. Nuclear Regulatory Commission. ǂb Office of Nuclear Regulatory Research.

References

1GPO Cataloging Guidelines, 2002. Fourth edition. U.S. Government Printing Office, page 176.

 

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