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: Continuing Resources: Serials

Bibliographic Cataloging: Continuing Resources: Serials

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

Sources to Consult

Use this section in conjunction with the following sources:

  • RDA and LC-PCC PS
    • CONSER Cataloging Manual (CCM). (When using a particular module in the Cataloger’s Desktop version, always check for an updated version of that module on the CONSER web site. It is expected, but not known, that the Cataloger’s Desktop version of the CCM will incorporate these updates on a quarterly basis.)
    • CONSER Editing Guide (CEG). (When using a particular module in the Cataloger’s Desktop version, always check for an updated version of that module on the CONSER web site. It is expected, but not known, that the Cataloger’s Desktop version of the CEG will incorporate these updates on a quarterly basis.)
  • CONSER Standard Record. SEE: RDA CONSER Standard Record (CSR) Metadata Application Profile.
  • CONSER - Cooperative Online Serials Program of the PCC
  • CONSER – Serials Cataloging Issues
  • CONSER RDA Cataloging Checklist
  • CONSER RDA Core Elements
  • CONSER MARC 21 to RDA Core Elements
  • Notes for Serials Cataloging (2nd ed. By Geer & Caraway or 3rd edition with revisions by Genereux & Moeller)
  • PCC Provider-neutral E-resource MARC Record Guidelines
  • PCC Guidelines for Enhancing & Editing non-RDA Serial Records
  • RDA CONSER Standard Record (CSR) Metadata Application Profile
    • Report of Multiple Format Linking Group 
  • PCC Guidelines for the 264 Field
  • Copy Cataloging: Working with Existing Copy
  • Electronic Access and Location in Bibliographic Records: Standard Operating Procedure 422 [internal GPO document]  

General Policies, Procedures, and Practices

Definition of Serial

The RDA definition of serial is located in Table 2.1 within: RDA 2.13.1.3: Recording Modes of Issuance.

Serial: A resource issued in successive parts, usually with numbering, that has no predetermined conclusion (e.g., periodical, a monographic series, a newspaper). Includes resources that exhibit characteristics of serials, such as successive issues, numbering, and frequency, but whose duration is limited (e.g., newsletters of events) and reproductions of serials.

Cataloging Decision: Monograph vs. Serial and Frequency of Issuance

For guidance in determining the specific type of resource, consult LC-PCC PS for 2.1: Basis for Identification of the Resource: Mode of Issuance: Monograph vs. Serial

Consultation with the supervisor is highly recommended anytime that the cataloger is uncertain whether or not to treat a work as a serial.

Serials Cataloged as Monographs

In general, regard the upper limit of frequency for serial treatment to be every five years. If volumes of a serial work are issued less frequently than every five years (i.e., six+ years), then catalog those volumes as monographs.

Exception: The presence of a PCC authenticated serial record in OCLC, or a long lifespan, e.g., twenty years or more, would support serial treatment of a title, even if issues were more than five years apart. (Examples: CGP 355795 and 813792)

Monographs Cataloged as Serials ("Serials-of-Convenience")

Frequently revised monographs may be cataloged as serials according to one of the categories below. This practice is referred to as creating a “serial-of-convenience.” In 2020, CONSER confirmed that this type of serial record may be authenticated as PCC and assigned an LCCN. When cataloging is complete, new editions of the same work are checked in as serial issues, rather than creating a new bibliographic record for each revision of the work. Typically, the year of publication is used as issue numbering for the library catalog.

  • Frequency of Issuance

    Frequently issued works may be cataloged as serials-of-convenience if they fit either of the following descriptions:

    • Ephemeral works (e.g., brochures) that are reprinted every few years (i.e. issued every five years or more frequently) with only minor editorial changes
    • Works issued irregularly, with some gaps that qualify for serial treatment (i.e., every five years or more frequently) and some gaps that do not qualify
      • This includes works issued as formal editions, where the edition statements can serve as serial numbering designations.
  • National Park Service and U.S. Fish and Wildlife Service Publications

    All newly received National Park Service (NPS) and U.S. Fish and Wildlife Service (FWS) brochures and maps must be cataloged as serials-of-convenience, authenticated as PCC, and assigned LCCNs. GPO established this practice in 2020 after observing over many years that these titles are always updated, though the frequency of updates varies greatly. (Examples: CGP 1136664, 1149746, and 1179386)

    For all of the above NPS and U.S. Fish and Wildlife Service publications, jacket numbers should be recorded in the OPAC Note field of the item record rather than in a 500 note in the bibliographic record.

    Example:
    CGP 982976

    Item #983047-10 (2015 issue)

    Bibcatinfo-image
    NPS braille publications should always be cataloged as serials-of-convenience, since they are routinely updated. (Example: CGP 1163571)

Cataloging Decision: When Mode of Issuance Is Ambiguous

For guidance in determining the specific type of resource, see LC-PCC PS for 2.1: Basis for Identification of the Resource.

For serials published online, the cataloger might find only the most current issue posted. A publisher’s choice to post online only the most current issue or edition of a work does not mean that previous issues/editions have ceased to exist as discrete publications. A decision to catalog as a serial cannot be contingent upon the simultaneous presence online of all issues or editions. See: Integrating Resources: a Cataloging Manual, IR1.2.2: “If the current issue is available online as a separate issue but back issues no longer exist as discrete issues, still catalog the resource as a serial.”

As an example, in the following case, numerous monograph records for earlier revised editions of this work existed in the ILS and in OCLC, and are found in archival PURLs. A title issued in numerous revised editions may be cataloged as a serial instead of as an integrating resource or as multiple monographs. When cataloged as a serial, the edition statements are recorded as designations of issues (RDA 2.6: Numbering of serials). The frequency of the revisions, however irregular, supports serial treatment. See:

Example:

OCLC # 856540482 / CGP system no. 000907273
     Title: Learn about the United States : ǂb quick civics lessons.

  •      PURL 1: 856 40 ǂ3 Latest issue ǂu 

         PURL 2: 856 40 ǂ3 Archived issues ǂu 

Example:

OCLC #609214511 / CGP system no. 000813792
     Title: Sailing directions (enroute). ǂp East coast of South America

  • PURL: ǂ3 Latest edition only: ǂu 

Replacement of Monograph Records with a Serial Record

When a serial record replaces ILS monograph records: 1) the monograph records are deleted from the CGP; and 2) GPO holdings for the monograph records are removed in OCLC. Additionally, the holding and item records need to be transferred, or added to the newly created serial record. For guidance on completing the collapsing process, see: Collapsing Monograph Records.docx

Classification of Ceased Serials Being Cataloged for the First Time by GPO

When GPO catalogs a serial title for the first time for the CGP, and that manifestation of the serial already has ceased, the cataloger searches for a record for a different format (i.e., for a different manifestation). If a record is found for a different format of the ceased serial, the SuDoc number (or one of the SuDoc numbers) in that record is used. If no records are found for the title, the cataloger may use the SuDoc number of a record for a later or earlier title, regardless of the format of that record. If no such records are found, the cataloger should use a SuDoc stem from one of the agency’s category classes (see GPO Classification Manual, chapter 2), such as its General Publications or Handbooks, Manuals, and Guides classes, and assign a unique Cutter number. Due to the title's ceased status, this is a departure from the usual serials classification practice of assigning unique SuDoc stems to live titles.

Example:

OCLC 862810095 / CGP system no. 000912828
074 0971-B (online)
086 0 T 70.2:EX 7/3/
130 0 Explosives newsletter (United States. Bureau of Alcohol, Tobacco, and Firearms)
245 10 Explosives newsletter.
362 1 Began with: June 1997; ceased with: August 2000.

Numbering - Exceptions to the RDA Principle of Transcription, or “Take What You See”

Within RDA there are several exceptions to the general RDA principle of transcription for numbering. Serials catalogers should be aware of:

Example:
RDA Instruction Action Example
1.8.3: Numbers expressed as words Substitute numerals for numbers expressed as words. Designation appears on issue as Book Four: represent in the record as book 4
1.8.4 Inclusive Numbers When recording inclusive dates and other inclusive numbers, record both the first and last number in full. Designation appears on issue as 1961-2: represent in the record as 1961/1962
2.6.1.4: Recording numbering of serials Substitute a slash for a hyphen, as necessary, for clarity. Designation appears on issue as 1999-2000: represent in the record as 1999/2000
2.6.2.3: Recording numeric and/or alphabetic designation of first issue of part of sequence If the designation consists of a year and a number that is a division of the year, record the year before the number. Designation appears on the issue as 1-97: represent in the record as 97-1

For decisions about treatment for such terms as “premier” and “sample” issues, consult: LC-PCC PS for 2.1.2.3: Resource Issued in More than One Part.

See also: RDA Appendix D 1.2: ISBD Punctuation and D 1.2.4.3: Numbering (Serials.)

Notification of Cataloging Updates via WebTech Notes

Upon completion of a new serial record for the CGP, or upon completion of a record’s closure due to cessation or to a title change, inform the FDLP community of the action via a WebTech Note.

Notification of LSCM’s Office of Archival Management (OAM) for Serials Harvesting

Upon completion of a new serial record for the CGP, cue GPO LSCM’s Office of Archival Management (OAM) to harvest existing issues, and to place the PURL on the automated “scheduler” to capture future issues at the expected increment (monthly, quarterly, annually, etc.).

When it is determined that a serial has ceased and the record has been closed, notify OAM staff to ensure that all available issues have been archived and to redirect the PURL to the archival directory of issues harvested by GPO. However, the PURL will remain pointed to the agency Web site if GPO has a permanent public access partnership with the agency, or if OAM deems the agency’s site for its archived issues to be stable. Communicate either situation to OAM using either:

PURL Worksheet (preferred)
or
Email – for lengthy and/or complex requests

Updating Collections of Serials

For an unusual treatment of annual reports, see the following records that treat updating collections of annual reports from national programs within USDA’s Agricultural Research Service as integrating resources. Use OCLC or the CGP to scan the title phrase “Project annual reports from National Program …”

Initially, GPO analyzed each annual report, but the quantity of cataloging records became burdensome. Furthermore, in a Depository Library Council (DLC) meeting with GPO librarians, a DLC Council member questioned the efficacy of analyzing hundreds of short-lived technical reports (usually with 5-year-lifespans). This cue legitimated the switch to cataloging the entire collections.

For detailed instructions on cataloging integrating resources, see Bibliographic Cataloging: Integrating Resources.

MARC Fields

Leader /17 (Encoding Level) and 042

For the sake of encoding and authentication, GPO is considered a national bibliographic agency that participates in PCC’s CONSER; therefore, serials are cataloged at Full-level (for which the value for the encoding level is “blank”) and authenticated in 042 as “pcc.” When a lower-than-full level serial record needs to be adapted by GPO, upgrade the record to PCC standards articulated broadly and specifically in CONSER guidance documents.

010 - Library of Congress Control Number

Library of Congress Control Number assignments are issued via stickers to individual catalogers. Consult your supervisor for annual allocations of stickers, and for replenishments as needed through the year.

022 - ISSN

See Selective Registration for ISSN Assignments.

050 - Library of Congress Call Number

Retain in all records.

060 - National Library of Medicine Call Number

Retain in PCC level records when found.

070 - National Agricultural Library Call Number

Retain in PCC level records when found.

074 - Item Number

Do not remove item numbers from a record for a tangible serial, such as the print, that is no longer distributed in that format, but was distributed in the past. (Also, see the section “500 – Distribution Note.”)

082 - Dewey Decimal Classification Number

Retain in all records.

086 - SuDoc Number

Some SuDoc numbers for serials contain additional characters after the SuDoc stem, such as a cutter. In researching the SuDoc numbers of individual issues of the serial (in ACSIS or the Shelflist, for example), especially the earliest ones, the cataloger may find a situation such as the following hypothetical example:

TD 4.8/2:L 47 1st issue found with this SuDoc stem plus cutter
TD 4.8/2:L 47/992 2nd issue
TD 4.8/2:L 47/993 3rd issue
TD 4.8/2:L 47/994 [etc/]

Currently, GPO convention is to enter the SuDoc number in the 086 field with an ending slash, even when the SuDoc number of the first issue lacks a slash. This convention indicates that additional issues are available, which have book numbers (individual issue designations) following the slash. Consequently, for the above example:

086 0_ TD 4.8/2:L 47/

See also: Replacement of Monograph Records with a Serial Record

246 - Varying Form of Title

The “CONSER MARC-to-RDA Core Elements” guidance illustrates the basic preferred encoding for parallel titles, and for variant titles, including later titles proper (for minor title changes). These are listed under MARC encoding 246. “Record initialisms/acronyms of the title proper not chosen as the title proper in field 246 rather than other title information,” either as: 246 1# ǂa [Variant title], or as: 246 1# ǂi [Note:] ǂa [Variant title].

For citing the particular issue or range of issues having a later title proper that is a minor title change, use either of the terms: issue/issues or volume/volumes. The term “issue/issues” is preferred. Free-text notes that introduce variant titles are exemplified by, but not limited to, the following examples.

Example:

246 1 ǂi Title from serial home page: ǂa [Variant title]
246 1 ǂi Title on newsletter index screen: ǂa [Variant title]
246 1 ǂi Title from source code: ǂa [Variant title]
246 1 ǂi Issue for spring/summer 2012 has title: ǂa [Later title proper]
246 1 ǂi Issues for 1978-1983 have title: ǂa [Later title proper]
246 1 ǂi Some issues have title: ǂa [Variant title]
246 1 ǂi Some issues also have title: ǂa [Variant title that appears in addition to title proper]
246 1 ǂi Also known as: ǂa [Variant title for initialisms/acronyms not recorded as other title information]
246 1 ǂi Also known as: ǂa Red book
246 1 ǂi At head of title: ǂa [Variant title that could be mistaken for title proper]

264 - Production, Publication, Distribution, Manufacture, and Copyright Notice

264 ǂc: Date of publication: Follow the CONSER RDA CSR metadata application profile, under Date of publication, 2.8.6: “Serials: Record the publication date(s) of first and/or last issue if the dates are known and the first and/or last issues are in hand.” Do not apply the following instruction in RDA 2.8.6.5: “If the first and/or last issue, part, or iteration is not available, supply an approximate date or dates by applying the instructions at 1.9.2.” See also the CONSER RDA Cataloging Checklist, under 17c, Date of publication.

See GPO Sales Information in Bibliographic Cataloging: Overview.

300 - Physical Description (300 |a )

GPO always includes a 300 field, including for open serials, e.g.,

Example:

300 ǂa volumes
300 ǂa 1 online resource (volumes)

In the second example above, the type of unit - “(volumes)” - is provided per RDA 3.4.1.10: Incomplete Resource. GPO follows RDA 3.4.1.10 but not its alternative or the LC-PCC Policy Statement for 3.4.1.10 for the alternative.

362, 588, and Any Field Where Designation is Represented

See section: General Policies: Numbering.

362 - Beginning and/or ending numbering/dates of publication

Clear guidance, including examples and descriptions of former practice, is found in:

  • CONSER Editing Guide (CEG): Variable data field 362
  • CONSER Cataloging Manual: Module 8. Numbering (Fields 362, 515, 588) (Updated version at: http://www.loc.gov/aba/pcc/conser/more-documentation.html, as of May 2016. Specific link: http://www.loc.gov/aba/pcc/conser/word/Module8.docx)
  • CONSER Cataloging Manual: Module 31.8. Remote Access Electronic Serials: Numbering (fields 362,588)

Inferring first or last issue from the print version: This practice is most commonly employed when creating the record for the online version, and the first online issue or beginning date is unknown. The beginning dates of the print version, when known, may be given in a 362 1# field. Give this note in addition to the “Description based on note” to provide justification for the fixed field beginning date.

Example:

362 1# Print began with: Vol. 3, no. 1 (Jan. 1984). 

Do not give a 362 1# “Print began with” note when the beginning date of the print or other original format is not known. Give an unknown* fixed field date in this case.” (CEG) (*Note: such as 199u, 19uu, or 200u)

362 - Determination of Cessation of a Serial When Response from the Publishing Agency is Lacking

When verification of a serial’s suspected cessation cannot be confirmed with the publishing agency, then cautious judgment should be exercised to make that determination. For example, in 2013, the cataloger had to consider the serial’s publication status and found the following data:

Example:

245 00 GLOBE offline.
260 Washington, DC : ǂb GLOBE Program, ǂc [1997]-
310 Semiannual
362 0_ Fall 1997-
588 Latest issue consulted: March 2003.

Because of the lapse in issues for a ten-year period and a lack of success in eliciting a response from the agency, the cataloger confidently added to the above variable fields the following statement in a separate 362:

362 1_ Ceased publication.

However, it is not uncommon for gaps and other irregularities in issuance to occur, especially during periods of fiscal restraint, so act conservatively when making this determination.

500 - Distribution Note

If no issues of a serial have been distributed in a particular format, a 500 note that reads "Format not distributed to depository libraries" should be included in the record for that format. This note would most commonly appear in the print record for a serial that is only “distributed” to the Federal Depository Library Program online. However, many older serials, unlike monographs, were distributed in the past in print, microfiche, or direct electronic format, but later ceased such tangible distribution in favor of the online version. Distribution of such serials changed from tangible distribution to “online only” or “EL only.” In such cases, the note “Format not distributed to depository libraries" is inaccurate, since libraries will have parts of these serials on their shelves. In such cases, use in the appropriate print, microfiche, or direct electronic record such a note such as:

500 No longer distributed to depository libraries in a physical form.

or

500 Format no longer distributed to depository libraries.

In most cases, catalogers updating such older serial records need only retain the existing “No longer distributed …” note. Any such “no longer distributed” notes may be edited to include the following final phrases:

500 No longer distributed to depository libraries in a physical form “as of [date].”

500 No longer distributed to depository libraries in a physical form “after [designation or year of last distributed issue, or year in which the last issue was distributed].”

or

500 Format no longer distributed to depository libraries “as of [date].”

500 Format no longer distributed to depository libraries “after [designation or year of last distributed issue, or year in which the last issue was distributed].”

515 - Numbering Peculiarities Note

For extensive examples of numbering peculiarities, see Notes for Serials Cataloging (2nd edition by Geer & Caraway or 3rd edition with revisions by Genereux & Moeller), and CONSER Editing Guide (CEG), 515: Numbering Peculiarities Note.

538 - System Details Note

Closure of serial records often requires edits to the MARC 538 subfields that introduce the original URLs. For instructions, see: SOP 422 – Electronic Access and Location in Bibliographic Records [internal GPO document], section entitled “Publications No Longer Available.”

588 - Source of Description Note

Clear guidance, including examples and descriptions of former practice, is found in:

  • CONSER Editing Guide (CEG): Variable data field 588
  • CONSER Cataloging Manual (CCM): Module 8. Numbering (Fields 362, 515, 588)
  • CONSER Cataloging Manual (CCM): Modules 31.8. Remote Access Electronic Serials: Numbering (fields 362, 588) and 31.3.4
Example:

For Online examples, see:

Provider-Neutral E-Resource MARC Record Guide: MARC Element: 588, column labeled “Serials & Integrating Resources (IRs)”

CEG 588       (Updated version as of May 2016)

CCM 31.3.4 and 31.8       (Updated version as of May 2016)

 

For Tangible examples, see:

CEG 588         (Updated version as of May 2016)

CCM 8.1.1

Language for “Description Based on” Note

Do not use the phrase “Identification of the resource based on:” found in RDA 2.17.13.3, to describe the serial issue that serves as the basis of description. Instead, use the phrase “Description based on:" as instructed in LC-PCC PS for 2.17.13, the RDA CONSER Standard Record (CSR) Metadata Application Profile, and CONSER RDA Core Elements.

Example:

588 Description based on: Volume 1, issue 1 (Feb. 2016).

Although the description based on (DBO) and latest issue consulted (LIC) notes typically reflect transcribed designation, catalogers may abbreviate months in viewed dates.

Example:

588 Latest issue consulted: GFA-21 (July 2010) (viewed Aug. 19, 2013).

Print Version Record Used As Basis of Description for Online Version

For online serials, generally do not use the print version as a basis for description. Exceptions to this occur when agencies’ own serial archives or GPO’s digital repository, FDsys/govinfo, serve as the basis for the electronic record description, and contain substantially fewer issues/volumes than the print version, or contain issues that lack title pages, covers, etc. that are present in the print version. In these cases, use the print version as the basis for description to justify title, title variants, statements of responsibility, etc., that otherwise would be lost. The following text should be used in a 588 field in such cases:

588 Description based on print version record.

Similar situations also occur for longstanding print titles for which only one or a few online issues can be found. One example occurs when adapting a Hathi-Trust record that is based on the print version, when only the latest issue is available to the cataloger (example: OCLC *604986725). In this case, retain the description based on print version, but update the “Latest issue consulted” note to identify the most recent online issue that is viewed. The “latest issue consulted” note that is corollary to the “Description based on print version record” note nevertheless reflects the online version.

Example:

588 Description based on print version record.
588 Latest issue consulted: Volume 1, number 4 (April 2014) (viewed May 14, 2014).

76X--78X - Linking Entry Fields

Consult and follow:

  • CONSER Cataloging Manual, Module 14 and 31.15
  • Report of Multiple Format Linking Group (Note: Some modifications have been made to the examples in this section.)
  • Bibliographic Cataloging: General MARC Field Policies: 76X to 78X - Linking Entries

776 - Additional Physical Form

In general, the 776 field is used to indicate that the title in the cataloging record is (or was) available in an additional format. The 780/785 fields should not be used when a simple format change (but no title change) has occurred, even if one of these formats has been discontinued in favor of another. An exception is made if a title change accompanies a format change; in this case, the 780/785 fields are used (see example below of The Japan Foundation newsletter).

In addition, CONSER policy is to prefer the use of the 776 ǂi to record the format of the record being referenced, rather than a 530 field. When upgrading a serial record substantially, GPO catalogers should update the 776 treatment, as shown below.

530 Some issues also available via Internet from the ASTOR web site.

776 1 ǂc Original ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031

[is updated to:]

Example:
530 Some issues also available via Internet from the ASTOR web site. [Field deleted; but may be retained according to cataloger judgment]
776 08 ǂi Print version: ǂt Hazardous substances & public health ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031
776 08 ǂi Online version: ǂt Hazardous substances & public health (Online) ǂw (DLC) 00220202 ǂw (OCoLC)32623365
530 Also issued in print.
776 1 ǂt Hazardous substances & public health ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031
[is updated to:]
530 Also issued in print. [Field deleted]
776 08 ǂi Print version: ǂt Hazardous substances & public health ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031

For general guidance on updating 776 and related fields, see “For copy cataloging” in the section, 76X-78X in: Bibliographic Cataloging: General MARC Field Policies.

Cessation of Print Version but Continuation of Online Version

The 776 field (not 780/785 fields) also is used when a print version ceases publication but the online manifestation continues. This relationship is noted in ǂi of the 776 in both the print and online records. Cf. CONSER Cataloging Manual, Part 3, Special Types of Continuing Resources. Module 31, Remote Access Electronic Serials (Online Serials). Section 31.15, Linking Relationships.

Cessation of Print Version but Continuation of Online Version - Examples:

When a simple format change (but no title change) has occurred, the 780/785 fields should not be used even if one of these formats has been discontinued in favor of another.

Example:

Print version: OCLC *1640226 / CGP system no. 000245524
DtSt d Dates 1938, 2013
130 0 Social security bulletin (Washington, D.C. : 1938)
245 10 Social security bulletin.
362 0 Vol. 1, no. 1-3 (Mar. 1938)-
362 1 Ceased in print with: Vol. 73, no. 3 (Aug. 2013).
776 08 ǂi Continued online: ǂt Social security bulletin (Washington, D.C. : 1938 : Online) ǂx 1937-4666 ǂw (DLC) 2006230180 ǂw (OCoLC)48798071

Example:

Online version: OCLC *48798071 / CGP system no. 000590301
DtSt c Dates 1938, 9999
130 0 Social security bulletin (Washington, D.C. : 1938 : Online)
245 10 Social security bulletin ǂh [electronic resource].
362 0 Vol. 1, no. 1-3 (Mar. 1938)-
776 08 ǂi Print version, 1938-2013: ǂt Social security bulletin (Washington, D.C. : 1938) ǂx 0037-7910 ǂw (DLC)sn 40029327 ǂw (OCoLC)1640226

Cessation of Serial Due to Both Format Change and a Title Change

When a publication ceases due to a format change and a title change, use a 776 field along with 780/785 fields.

Example:

OCLC *4102509
DtSt d Dates 1973, 2006
245 04 The Japan Foundation newsletter.
362 1 Began in Aug. 1973; ceased with v. 31, no. 4 (Apr./May 2006).
776 08 ǂi Online version: ǂt Japan Foundation newsletter ǂw (OCoLC)626408149
785 04 ǂt Japan Foundation email magazine ǂw (DLC) 2010254029 ǂw (OCoLC)665072395

Example:

OCLC *626408149
DtSt d Dates 1973, 2006
245 04 The Japan Foundation newsletter ǂh [electronic resource].
362 1 Print began in Aug. 1973. Ceased with v. 31, no. 4 (Apr./May 2006).
776 08 ǂi Print version: ǂt Japan Foundation newsletter ǂx 0385-2318 ǂw (DLC) 84645788 ǂw    (OCoLC)4102509
785 04 ǂt Japan Foundation email magazine ǂw (DLC) 2010254029 ǂw (OCoLC)665072395

Example:

OCLC *665072395
DtSt c Dates 2004, 9999
245 04 The Japan Foundation email magazine ǂh [electronic resource].
362 1 Began with: Vol. 1 (Oct. 1, 2004).
580 Absorbed the print and online formats of the Japan Foundation newsletter in 2006.
780 00 ǂt What’s new mail service ǂw (DLC) 2010254030 ǂw (OCoLC)665072119
780 15 ǂt Japan Foundation newsletter ǂx 0385-2318 ǂw (DLC) 84645788 ǂw (OCoLC)4102509
780 15 ǂt Japan Foundation newsletter ǂw (OCoLC)626408149

Microform Serials and GPO Practices for Linkages

In the early 2000s, GPO began a practice of discontinuing microfiche serials when an online equivalent had been cataloged. The intent was to inform users that microfiche would no longer be distributed to depository libraries and that GPO would distribute only in EL format or possibly in conjunction with the print format (if cataloged). Below is an example of what the microfiche and EL records looked like after they were edited in the OCLC database.

Former, Discontinued Practice for Linking Microform Serials to Other Manifestations
Example:

OCLC *47143583 / CGP system no. 000534136
DtSt c Dates 1990, 9999
245 00 Hazardous substances & public health ǂh [microform] : ǂb a publication of the Agency for Toxic Substances and Disease Registry.
362 0 Vol. 1, no. 1 (Nov. 1990)-
530 Some issues also available via Internet from the ASTOR web site.
580 Continued by the online version.
776 1 ǂc Original ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031
785 10 ǂt Hazardous substances & public health (Online) ǂw (DLC) 00220202 ǂw (OCoLC)32623365

Example:

OCLC *32623365 / CGP system no. 000595127
DtSt c Dates 1990, 9999
245 00 Hazardous substances & public health ǂh [electronic resource].
362 1 Print began with vol. 1, no. 1 (Nov. 1990).
530 Also issued in print.
580 Continues the microfiche version.
776 1 ǂt Hazardous substances & public health ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031
780 10 ǂt Hazardous substances & public health ǂw (DLC) 2004231814 ǂw (OCoLC)47143583

The above practice was discontinued ca. 2005. In current practice, simple relationship information is provided in 776 ǂi rather than in 580 notes, as shown in th4e following examples.

Current Practice for Linking Microform Serials to Other Manifestations
Example:

OCLC *47143583 [microform version]
DtSt c Dates 1990, 9999
245 00 Hazardous substances & public health ǂh [microform] : ǂb a publication of the Agency for Toxic Substances and Disease Registry.
362 0 Vol. 1, no. 1 (Nov. 1990)-
580 Continued by the online version. [Field should be deleted]
776 08 ǂi Print version: ǂt Hazardous substances & public health ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031
776 08 ǂi Online version: ǂt Hazardous substances & public health (Online) ǂw (DLC) 00220202 ǂw (OCoLC)32623365

Example:

OCLC *32623365
DtSt c Dates 1990, 9999
245 00 Hazardous substances & public health ǂh [electronic resource].
362 1 Print began with vol. 1, no. 1 (Nov. 1990).
580 Continues the microfiche version. [Field should be deleted]
776 08 ǂi Print version: ǂt Hazardous substances & public health ǂx 1076-8920 ǂw (DLC)sn 91023417 ǂw (OCoLC)23110031
776 08 ǂi Microfiche version: ǂt Hazardous substances & public health ǂw (DLC) 2004231814 ǂw (OCoLC)47143583

Other Considerations for Linking Entry Fields: Parallel Formats & Works Not Described in Bibliographic Records

Parallel Formats

When linking works with 77X-78X fields, be careful to consider the same physical format for horizontal (776), chronological (780/785), and other related works (787).

Specifically for chronological (predecessor/successor) relationships reflected in 780/785, do not link to a different format when that chronological link can be made to the same format.

Works Linked but Not Described in Bibliographic Records

Also consider the admissibility of linkages to works for which no bibliographic records exist, as given in CONSER Editing Guide, Section E. 76X-78X, Linking Entry Fields General Information:

Linking entry fields may be used to provide notes and computer access for related titles for which there is no record online (e.g., a 780 field may be given for the earlier title when the title is known, even though there is no record on [i.e., in] the database).

When the cataloger knows for certain that another, related work exists, it must be included as a linking field entry in the record for the work being cataloged, whether or not it has been described in a bibliographic record.

Example:

The linking field conveys information about a chronologically-related work (in the example below, a predecessor work) for which a record is not identified. In this case, the linking fields lack record control numbers (ǂw):

     245 00 ǂa European journal of medicinal chemistry

     780 00 ǂt Chimica therapeutic

[Source: CONSER Cataloging Manual, Section 31.15]

856 - Electronic Location and Access

Spend time locating the best and most comprehensive URL (meaning "location") for a serial.

Some examples of such locations are given below, as these may appear unusual to catalogers who mostly catalog monographs:

OCLC Number PURL
609214511 856 40 ǂ3 Latest edition only ǂu 
845104850 856 40 ǂu 
48991874

856 40 ǂ3 Latest issue only ǂu http://publications.usa.gov/USAFileDnld.php?PubType=P&PubID=9801&httpGetPubID=0&PHPSESSID=ud7r87ahom3g6io6hfhs3pqpo4 

856 40 ǂ3 Archived issues ǂu

823178322 856 40 ǂu http://purl.fdlp.gov/GPO/gpo32752 
682455267 856 40 ǂu  http://purl.fdlp.gov/GPO/gpo19888

Keep the PURLs of current (live) serials connected live to the agency Web site, but notify OAM to put the PURL on the scheduler, as instruct ted in the "Notification of LSCM’s Office of Archival Management (OAM) for Serials Harvesting" section of this article.

When issues of a serial appear online in separate locations, then two PURLs are allowed, typically to provide access to “Current issue(s)” and “Archived issues.”

Example:

OCLC *70144088
856 40 ǂ3 Current issues ǂu 
856 40 ǂ3 Archived issues ǂu 

Single-record vs. Separate-Record Approach and PURLs

Older GPO records for print, microfiche, or direct electronic resources that followed the single-record approach may contain PURLs. The cataloger may need to update such an existing record for a tangible format which was created according to the single-record approach and thus contains a PURL (even though the cataloger would not include a PURL when creating a new record for a tangible format). A PURL in a single-record approach description should match that of the online manifestation of the same work or expression (or title, to use a simpler term). The cataloger often needs to “split” the single-approach record into two records into one each - the existing tangible record and a new online record. Therefore, when creating the new online record for such a title, use the same PURL that is found in the tangible record. Do not create a new PURL for this same title. It is acceptable to use the older formulated PURL.

Records that reflect different works or expressions should have different PURLs. Each work or expression in an online manifestation should have its own PURL (or PURLs). When a title changes, a bibliographic record that reflects the new work or expression in online format is created with a new PURL. To summarize: New records for title changes receive new PURLs.

See SOP 422 – Electronic Access and Location in Bibliographic Records [internal GPO document] for more information.

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