FDLP

Bibliographic Cataloging: General MARC Field Policies

Formats, Modes of Issuance, Etc

Consult and follow the instructions in the specific sections (serials, congressional publications, etc.) of the Cataloging Guidelines as well as those below.

Punctuation

Program for Cooperative Cataloging (PCC) Policy on ISBD Punctuation (announced on April 2, 2019).

  • Original Cataloging
    • GPO exercises option 1 of phase 1 to continue the current practice of including terminal periods.
  • Copy Cataloging
    • PCC Records
      • Leave the punctuation as is.
      • Do not add omitted terminal periods to descriptive fields when exporting PCC records from OCLC to the CGP.
    • Non-PCC Records
      • Do not add terminal periods omitted in fields eligible under the policy.
      • Per the PCC policy, the terminal periods may be omitted in the following fields. Frequently used fields are highlighted.

chart gen marc field policy

Transcription

Follow the transcription rule from RDA Appendix B.4: “For transcribed elements, use only those abbreviations found in the sources of information for the element.” GPO will follow RDA 1.8.1-1.8.2 and substitute Arabic numbers for roman numerals. GPO local practice follows capitalization from the Chicago Manual of Style.

See also: Cataloging Guidelines: Bibliographic Cataloging: Serials: Numbering – Exceptions to the RDA Principle of Transcription, or “Take What You See

Fixed Fields

ELvl - Encoding Level

PCC Level

  • Whenever possible, catalog records at PCC level.
  • This applies to original and copy cataloging.
  • All access points in a PCC record must be authorized, including personal names.

I Level

  • Encode records at I Level in the following situations
    • A personal name or other type of access point cannot be authorized. See instructions Bibliographic Cataloging: General Policies.
    • Congressional publications and other priority titles with uncontrolled access points, which are to be updated to PCC once the access points have been authorized.

Variable Fields

037 - Source of Acquisition

  • Follow GPO spacing conventions for numbers.
  • Do not include an address.
  • Retain an address already recorded in this field.
  • Do not use brackets.

‡a – Stock number

  • Add only non-GPO stock numbers to records.
  • See GPO Sales Information in Bibliographic Cataloging: Overview.

‡b – Source of stock number/acquisition

  • Record the source agency in abbreviated form.
037 003-000-00174-2 ‡b GPO
037 199716177 ‡b NASA
037 Cat 1311 C ‡b IRS
037 ED 241671 ‡b ERIC

Multi-part Monographs and Serials

  • Record each stock number in a seperate 037 #a
  • Include qualifying information to identify each stock number in parentheses.
037 003-000-00175-8 (v.1) ‡b GPO
037 033-000-00176-4 (v.2) ‡b GPO

040 - Cataloging Source

‡e - pn (Provider-Neutral)

  • While most GPO records for online resources are provider-newtral, some are not, such as Federal Depository Library Program Web Archive records. 
  • When adapting a record that is not provider neutral but contains "e pn," remove that #e, or, if appropriate, convert the record to provider neutral
    • This action would not be appropriate for certain projects that may utilize specific practices.
  • On a more general level, never change a record that is provider neutral to one that is not regardless of the coding in 040 #e.

050 - Library of Congress (LC); 060 - National Library of Medicine (NLM); 070 - National Agricultural Library (NAL); 082 - Dewey Decimal Classification and Call Number

  • Do not modify any classification or call numbers assigned by other institutions
  • Add 050 fields only to Congressional publications abd ECIP titles.
  • Add 062 fields only to ECIP titles
  • Do not delete or modify these fields unless assigned by GPO
  • Retain these fields in both OCLC master records and CGP records if one or more of trhe following criteria are met:
    1. it is a Congressional or ECIP publication
    2. it has second indicator 0 (zero)
    3. It has first indicator 0 (zero) (item is in NAL) andthe symbol “AGL” or “NLM” is in the 040 field.
    4. the record is already PCC-level before being adapted by GPO

Derived records

  • When deriving from an LC record containing a 050 field with second indicator 0 (zero), a new record for a different format of the same work/expression
    • Retain the 050 and/or 082 fields in the new record.
    • Change the indicators "#4" (blank 4) or "04" 
  • GPO retains the call number in the new record, because the classification was assigned by LC for another format of that work/expression.

Deriving from CGP 1000585:
040   DLC ‡b eng ‡e rda ‡c DLC
050 00 E599.H4 ‡b H13 2016
082 00 975.7/915 ‡2 23
245 00 H.L. Hunley recovery operations / ‡c
   edited by Robert S. Neyland, Heather G. Brown.
300   xxiii, 320 pages, foldout :
  ‡b illustrations, some color ; ‡c 28 cm
338   volume ‡b nc ‡2 rdacarrier

 

to create CGP 1007274:
040   GPO ‡b eng ‡e rda ‡e pn ‡c GPO
050 #4 E599.H4 ‡b H13 2016
082 04 975.7/915 ‡2 23
245 00 H.L. Hunley recovery operations / ‡c
   edited by Robert S. Neyland, Heather G. Brown.
300   1 online resource (xxiii, 321 pages):
  ‡b illustrations, some color
338   online resource ‡b cr ‡2 rdacarrier

100 - Principal Creator – Personal Name

  • For more information, see Bibliographic Cataloging: General Policies.
  • When principal responsibility among persons is not indicated and there is no corporate body creator according to RDA 19.2.1.1.1. use the first author listed on the resource as the principal creator.
CGP 1009562
100 1_ Borowski, Stanley K., ‡e author.
245 10 Affordable development and demonstration of a small nuclear thermal rocket (NTR) engine and stage: how small is big enough? / ‡c Stanley K. Borowski [and eight others].
[Record contains no 700 fields]
PURL
  • Do not establish name authority records (NARs) for personal name principal creators. Take the following actions:
    • Search the national authority file for the established form of the name.
    • When the name is not established:
      • Enter the fullest form of the name found on the resource.
    • Exception
      • When the fullest form of the name found on the resource conflicts with a name authority record:
        • Establish the authority record for the personal name.
      • Exception
        • Establish NARs for all personal name principal creators and other personal name access points on records for:
          • Congressional publications
          • Congressional Research Service publications
          • ECIP publications
CGP 1092369
110 1_ United States. ‡b Congress. ‡b House. ‡b Committee on the Judiciary, ‡e interviewer.
245 10 Interview of: James Comey / ‡c Committee on the Judiciary, joint with the Committee on Government Reform and Oversight, U.S. House of Representatives.
700 10 Comey, James B., ‡c Jr., ‡d 1960- ‡e interviewee.
PURL
CGP 1098461
100 1_ Brown, Cynthia ‡c (Legislative attorney), ‡e author.
245 10 Hatch Act restrictions on federal employees' political activities in the digital age / ‡c Cynthia Brown.
PURL

110/111 - Principal Creator - Corporate/Meeting Name

Original Cataloging

  • Record a corporate body or meeting name that meets one or more of the categories in RDA 19.2.1.1.1 is recorded in field 110/111 as the principal creator of the work.
  • The work authorized access point of a derived record does not need to match the work AAP of the original record.

GPO Practice 

    • In addition to commonly encountered categories of 19.2.1.1.1, such as annual reports, commission reports, legislative hearings, conference proceedings, maps, and laws, GPO enters the following types of resources under a corporate body principal creator:
      • GAO reports
      • Environmental impact statements and other environmental assessments, plans, etc., in which the corporate body makes recommendations and/or plans, or outlines a particular strategy that should be taken

CGP 903493

110 1_ United States. ‡b Government Accountability Office, ‡e author.

245 10 Preliminary results of work on FAA facility conditions and workplace safety / ‡c Gerald L. Dillingham.

700 1_ Dillingham, Gerald Lee, ‡d 1947- ‡e author.

PURL

CGP 848469

110 2_ Bowdoin National Wildlife Refuge Complex (Agency : U.S.), ‡e author.

245 10 Draft comprehensive conservation plan and environmental assessment: Bowdoin National Wildlife Refuge Complex, Montana …

PURL

Copy Cataloging

  • Do not modify existing DLC, AGL, NLM, BIBCO, and CONSER records to change the existing authorized access points.
  • For other existing records, either add or remove 110/111 field, in accordance with RDA 19.2.1.1.1, or for the special types of resources listed in the Original Cataloging section (note: Add link to the preceding section).

130/240 - Unique Title for Work or Expression

For more information, see: Bibliographic Cataloging: General Policies: Distinguishing Works and Expressions with Identical Authorized Access Points and Language Editions.

RDA/LC-PCC PS:

2.3.2.1
2.3.2.2
6.2.2.2
6.27.1
6.27.1.9
6.27.3

Work or Expression Authorized Access Points

  • Work authorized access points are constructed in two ways:
    • The principal creator (1XX) and the preferred title (245)
      • For the majority of government resources, the preferred title is taken from manifestations of the work.
    • The preferred title (245) only
  • The following elements of a title proper are considered part of the preferred title:
    • ‡a - Title
    • ‡n - Number of part/section of a work
    • ‡p - Name of part/section of a work
    • Remainder of title (‡b) is not considered part of the preferred title.

Breaking Work or Expression Authorized Access Point Conflicts

  • When the work or expression AAP of a newly cataloged record conflicts with the AAP of an existing record, the 130 or 240 field adds to the title proper found in the 245 ‡a, ‡n, ‡p of a different work or expression.
  • This distinguishes the AAP of the work or expression from that of a different work or expression.
  • When the AAP for the existing, different work or expression consists of a preferred title (245 field) combined with a creator or agent (1XX field)
    • Add a 240 field to differentiate the access points.
  • When the AAP for the existing, different work or expression consists of a preferred title only (245 field but no 1XX field)
    • Add a 130 field to differentiate the access points.

130 - Unique Title for Work or Expression - No Principal Creator Present

For more information, see, 130/240 – Unique Title for Work or Expression.

  • Use this field to break conflicts, when the work authorized access point embodied by the record consists only of a title, without a principal creator.
    • The bibliographic record will contain a 245 field, and possibly a 130 field, but no 100, 110, or 111 field.
  • Incorporate additional identifying elements by adding a 130 field containing the preferred title plus a parenthetical qualifier.
    • Usually, a qualifier is added to the title proper, which comprises the 245 ‡a, ‡n, and/or ‡p.
    • Occasionally (more common in serials), a 130 would be constructed for the work being cataloged, that conflicts with the 130 of a different work.
      • In such cases, an additional element might be added to the 130 field. 
130 0_Bulletin (New York State Museum : 1945)
245 10 Bulletin / ‡c New York State Museum.
130 0_Bulletin (New York State Museum : 1976)
245 10 Bulletin / ‡c New York State Museum.

240 - Unique Title for Work or Expression - Principal Creator Present

For more information, see, 130/240 – Unique Title for Work or Expression.

  • Use this field to break conflicts, when the work authorized access point embodied by the record consists of a title and a principal creator.
    • The bibliographic record will contain a 245 field and a 1XX field.
  • Incorporate additional identifying elements by adding a 240 field containing the preferred title plus a parenthetical qualifier.
    • Usually, a qualifier is added to the title proper, which comprises the 245 ‡a, ‡n, and/or ‡p.
    • Occasionally (more common in serials), a 240 would be constructed for the work being cataloged, that conflicts with the 240 of a different work. In such cases, an additional element might be added to the 240 field.
110 1_ United States. ‡b Congress. ‡b House. ‡b Committee on Armed Services, ‡e author.
240 10 Hearing on National Defense Authorization Act for Fiscal Year 2016
245 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 and oversight of …

110 1_ United States. ‡b Congress. ‡b House. ‡b Committee on Armed Services, ‡e author.
240 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 (2015)
245 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 and oversight of …

110 1_ United States. ‡b Congress. ‡b House. ‡b Committee on Armed Services, ‡e author.
240 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 (2015 February 25)
245 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 and oversight of …

110 1_ United States. ‡b Congress. ‡b House. ‡b Committee on Armed Services, ‡e author.
240 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 (2015 March 18)
245 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 and oversight of …

110 1_ United States. ‡b Congress. ‡b House. ‡b Committee on Armed Services, ‡e author.
240 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 (2015 March 18 : ISIL)
245 10 Hearing on National Defense Authorization Act for Fiscal Year 2016 and oversight of …

(some are hypothetical):

110 1_ United States. ‡b Government Printing Office. 245 10 Annual report.

110 1_ United States. ‡b Government Printing Office.
240 10 Annual report. (1933-1945)
245 10 Annual report.

110 1_ United States. ‡b Government Printing Office.
240 10 Annual report. (1992-2013)
245 10 Annual report.

Language Editions and Translations

  • Language editions are
    • issued by the same body
    • published simultaneously or nearly simultaneously.
    • Translations are
      • issued by an entity other than the issuing body of the original expression
      • published at a later time
    • Both language editions and translations are treated the same way in respect to expression authorized access points.
      • Only add a 130 or 240 field when there is evidence that another language version exists either in OCLC or the CGP.
        • Use a 130 or 240 field containing the preferred title of the original work followed by the language of the particular expression (RDA/LC-PCC PS 6.27.3).
  • Original English edition:


    245 03 An easy guide to breastfeeding.



    Chinese edition:


    130 0_Easy guide to breastfeeding. ‡I Chinese


    245 10 Hua ren fu nü ji qi jia ting : ‡b mu lu wei yang jian yi zhi nan.



    Original English edition:


    100 1_Sodipo, Michael Olufemi, ‡e author.


    245 10 Mitigating radicalism in Northern Nigeria / ‡c by Michael Olufemi Sodipo.



    French edition:


    100 1_Sodipo, Michael Olufemi, ‡e author.


    240 10 Mitigating radicalism in Northern Nigeria. ‡l French.


    245 10 Atténuer le radicalisme dans le nord du Nigeria / ‡c par Michael Olufemi Sodipo.



    Original Russian edition:


    100 1_Nefëdkin, A. K. ‡q (Aleksandr Konstantinovich), ‡e author.


    245 10 Voennoe delo chukcheĭ : ‡b seredina XVII-nachalo XX v. / ‡c A.K. Nefëdkin.



    English edition:


    100 1_Nefëdkin, A. K. ‡q (Aleksandr Konstantinovich), ‡e author.


    240 10 Voennoe delo chukcheĭ : ‡b (mid-17th to early 20th century) / ‡c Alexander K. Nefëdkin ; translated by Richard L. Bland.



    GPO Practice: Language Editions Already Cataloged without Unique AAPs

    • When cataloging another translation or language version of a work and the authorized access point of that expression is not unique:
      • Inform a supervisor of the situation.
      • If the staff member who cataloged the record is still at GPO, they will add the appropriate unique title.

    245 - Title Statement and 246 - Varying Form of Title

    GPO Practice

    • When recording inaccuracies in titles, use the text, “Corrected title” in subfield ‡i of the 246 field, rather than follow the example in RDA 2.20.2.4 of “Title should read.”

    245 14 The U.S. State Department's inadequate response to human rights concerns in Bolivia : ‡b the case of American Jacob Osreicher



    246 1# ‡i Corrected title: ‡a U.S. State Department's inadequate response to human rights concerns in Bolivia : ‡b the case of American Jacob Ostreicher

    245 ‡c - Statement of Responsibility (SOR)

    GPO Practice

    • Follow the omission option in RDA 2.4.1.5.
      • Add the statement in brackets, [and X others], where X represents the number of personal names or corporate body names presented in the resource minus one for the author given as the principal creator.
      • Do not provide additional authorized access points for the omitted authors.
      • Exception
        • For Congressional publications, list all personal name authors and provide additional authorized access points for all of them
    • For Federal government corporate bodies, generally transcribe up to three names.
      • When the inclusion of more than three corporate bodies is considered important, confer with a supervisor.
    • Include additional authorized access points for all names listed in the SOR.
    • Do not include affiliations in statements of responsibility. GPO follows the optional omission of nonessential information per RDA 2.4.1.4.

    246 - Varying Form of Title

    GPO Practice

    • When recording inaccuracies in titles, use the text, “Corrected title:” in subfield ‡i

    250 - Edition Statement

    • Record Braille edition statements if present
    • If no edition is associated with the Braille statement on the item being cataloged, then the Braille notation is included in MARC 546 only, unless a supplied edition statement is needed to differentiate expressions with identical titles.

    264 (260 in adapted records) - Production, Publication, Distribution, Manufacture, and Copyright Notice

    ‡a - Place of Production, Publication, Distribution, Manufacture

    GPO Practice

    • Do not add the address to the name of a place.
    • Retain addresses in existing records
    • When the place of publication is unkown, follow LC-PCC PS 2.8.2.6:
      • Supply a probable place of publication.
      • Do not use [place of publication not identified]
      • Use the location of the head office of the lowest body listed as the probable place of publication.
    • ‡b - Name of Publisher

      GPO Practice

      • If multiple publishers are named in a document, always include the first named publisher.
        • Also include the Federal agency related to the SuDoc.
        • Optionally, record other publishers if important for access.

      ‡c - Date of Publication

      GPO Practice

      • When the date of publication is unknown, follow LC-PCC PS 2.8.6.6:
        • Supply an approximate date of publication in brackets with a question mark.
        • Do not use [date of publication not identified].
      • For general publications, not technical reports, do not include the month in the 264 ‡c even if it appears on the piece.
        • When copy cataloging, if the month has already been included in the 264 ‡c, do not change it in the OCLC record, but remove the month before exporting to Aleph.

      GPO Sales Statement

      300 - Physical Description

      • Always include this field, including for open serials.

      ‡b - Other Physical Details

      GPO Practice

      • Use the general term illustration or illustrations to describe all types of illustrative content of a resource
      • Apply cataloger’s judgment to determine if it is important for the description of the resource to use the specific terms, especially maps, listed in RDA 7.15.1.3.
      • Specific terms may be used instead of or in addition to illustration(s).
      • Do not use the terms charts or tables.
      • If other terms have already been supplied in a record being adapted, do not remove them, unless incorrect.

      336 - Content Type, 337 - Media Type, 338 - Carrier Type

      • When needed, use multiple 33X fields rather than repeating subfield ‡a.
      • If these fields already contain ‡b type codes, do not remove them.
        • When type codes are absent, do not supply them.
      • These fields may be added to AACR2 records to enhance access.

      490 - Series Statement Field

      GPO Practice

      Transcription and Tracing Decisions

      Transcribe, but do not trace, series for the following situations when no authorized form is found to exist:

      • Series of short duration (determined by other elements in bibliographic records and cataloger judgment, e.g., multiple analytics all of which were published in the same year, but none published thereafter, or few analytics that bear a series statement over an undefined interval)
      • Series not issued by a U.S. Federal government agency
      • Series with indeterminate publication status (e.g., continued growth is uncertain)
      • Series that have ceased.

      For situations described above, transcribe a series statement in a 490 field with a 1st indicator coding of “0” for “series not traced.” Otherwise, continue to transcribe and trace series in 490/8XX fields, for which a 490 field is coded “1” (1st indicator) for “series traced.”

      When in doubt, only transcribe the series statement (490 0_).

      This decision aligns with current Program for Cooperative Cataloging (PCC) guidance that allows an option not to trace series in PCC records. This option supplants a former requirement to trace series in PCC records.

      Series not traced CGP 1003002

      1001 United States. Defense Business Board, author.


      24510 Focusing a transition, challenges facing the new administration : a report.


      4900 DBB report ; FY16-5     → Series transcribed (only) because publication status of  
      the series is yet indeterminate



      Series traced CGP 978462

      1001 Benaka, Lee R., author. 
      24510 Action plan for fish release mortality science. 
      4901 NOAA technical memorandum NMFS-F/SPO ;  160    Series transcribed  
      830 0 NOAA tech. memo. NMFS-F/SPO ; 160.    → Series traced because this is a long-running series supported by an underlying series authority record  

      Alphanumeric Series-like Phrases

      Alphanumeric phrases that qualify as a series are recorded in a series statement rather than in a report number field. In government documents, such phrases are typically numbered statements of the name, initialism, or part of the name of the government agency from which the series emanates. (See: Series Training for PCC Participants, Session 12: Series-Like Phrases, p. 4)

      CGP 678631
      490 1_NOAA-TM-NMFS-SWFSC ;‡v 359
      830 _0 NOAA-TM-NMFS-SWFSC ; ‡v 359.
      [No MARC 088 field for Report Number]

      ISSN and Series/Subseries

      Transcribe the ISSN of a series/subseries in 490 ‡x when it appears on the resource, but do not record it in the 8XX field.

      When adapting OCLC master records, retain ISSNs in both the 490 and 8XX fields, but remove the ISSN from the 8XX field before exporting to the CGP.  

      490 1_ Area handbook series, ‡x 1057-5294

      830 _0 Area handbook series.

      Series Numbering as Transcribed Data

      Transcribe series numbering in subfield 490 ‡v.

      Editions with Identical Series Numbering

      Occasionally, an agency publisher re-assigns an identical series volume number to different analytics within the series. Apply the following section of Library of Congress Rule Instruction 1.6G, Numbering within Series: Editions with Identical Series Numbering, dated June 2006:

      When a revised edition of an existing work or an edition of an existing work (e.g., translation) is issued by the same publisher in the same series, the publisher may assign a new series number or the original series number to the revision, translation, etc. In the latter case, proceed as if no duplication of numbering exists.

      Original work: CGP 816589
      086 A 13.88:SRS-137
      245 Early forestry research in the South
      260 … ‡c [2011]
      4901 General technical report SRS ; ‡v 137
      830 0General technical report SRS ; ‡v 137.

      Revised expression of the work: CGP 1003450
      086 A 13.88:SRS-137/2016
      245 Early forestry research in the South
      250 Slightly revised, redesigned, and reprinted September 2016.
      264 … ‡c September 2016.
      4901 General technical report SRS ; ‡v 137
      830 0General technical report SRS ; ‡v 137.

      Additionally, it is appropriate to update the Series Authority

      Record (SAR) with a Series Numbering Peculiarities Note (MARC 641), e.g.:

      130 General technical report SRS

      641 Some issues with repeated numbering (e.g., 137).

       

      500, 588 - Title Source, Source of Description Notes

      Consult and follow all documentation cited in this section, including:

      • RDA/LC-PCC PS:
        • 2.17.2
        • 2.17.2.3
        • 2.17.13
        • 2.17.13.3
      RDA ElementForm of NoteMARC Field
      2.17.2.3: Title Source Title from ... 500 - General Note
      2.17.13: Note on Issue, Part, or Iteration Used as the Basis for Identification of the Resource Description based on ...; Title from ... 588 - Source of Description Note
      2.17.13 and 2.17.2.3 combined Description based on ...; title from ... 588 - Source of Description Note
      When is a simple 500 note used, and when is a combined 588 note required?

      See the table below for links to examples of notes to use in specific situations.

      FieldMode of IssuanceManifestation/SituationLink to Examples
      500 Monographs Single-part tangible (print, microfiche, DVD, etc.) monographs and multipart monographs as applicable (per RDA 2.1.2.3) Examples
      588 Serials & Integrating Resources ALL Examples for Serials Examples for IRs
      588 Monographs ALL ONLINE Online Monographs Examples
      588 Monographs Multipart monographs when applicable (per RDA/LC-PCC PS 2.17.13.3) Multipart Monographs Examples
      588 ALL When basing description on a different format than the one being cataloged Examples When Basing Description on a Different Format than the One Being Cataloged

      All online resources utilize the combined 588 note, regardless of their mode of issuance. The table below basically extends the examples found in the Provider-Neutral E-Resource MARC Record Guide.

      FieldSituationLink to Examples
      588 ALL ONLINE RESOURCES Online Monographs Examples Examples fpr Serials & Multipart Monographs Examples

      When is a simple 500 note used, and when is a combined 588 note required?

      Below is an alternatively organized table, which may be used instead of the two preceding tables.

      FieldSpecific SituationFormatMode of IssuanceLink to Examples
      500 Single-part tangible (print, microfiche, DVD, etc.) monographs and multipart monographs as applicable (per RDA 2.1.2.3) Tangible (print, microfiche, DVD, etc.) Monographs Examples
      588 ALL ONLINE RESOURCES Online ALL >Online Monographs Examples Examples for Serials Examples for IRs Multipart Monographs Examples
      588 Serials & Integrating Resources ALL Serials & Integrating Resources Examples for Serials Examples for IRs
      588 Multipart monographs when applicable (per RDA/LC-PCC PS 2.17.13.3) ALL Monographs Multipart Monographs Examples
      588 ALL ALL Examples When Basing Description on a Different Format than the One Being Cataloged
      • Use the form: Title from caption, Title from cover, etc., whether in a 500 or in a 588 combined note.
        • Do not use the forms: Caption title, Cover title, etc.

      Examples When Basing Description on a Different Format than the One Being Cataloged:

      For more information, see: Provider-Neutral E-Resource MARC Record Guide: MARC Element: 588, column labeled “Notes” and CONSER Cataloging Manual: 8.1.1 – see final “Situation #2,” “Description based on” example and asterisked note below.

      For specific guidance for serials, see 588 – Source of Description Note in Bibliographic Cataloging: Serials.

      • Months may be abbreviated in viewed dates.
      • When citing the title source, use specific terms such as title page, cover, caption, etc. when possible.
      • Only use the general term “title screen” when other terms are not adequate or applicable.

      Original Cataloging

      • Base the description on the format being cataloged when the bibliographic information from the tangible and online formats are the same.
      • When the tangible format record provides evidence that the online version lacks a title page, cover, etc., that is present in the tangible version, or, for serials, an earlier issue(s):
        • Use the note “588 Description based on print (or microfiche, CD-ROM, etc.) version record.”

      Copy Cataloging

      • When adapting a record containing, for example, a “588 Description based on print version record” note, implement one of the following options in both the OCLC master and CGP records:
        • Retain the “588 Description based on print version record” note.
        • Change the note so that you base your description on the format being cataloged.

      588 Description based on online resource; title from title page (viewed Nov. 18, 2016).

      500 - General Note

      Distribution Note – Formats Never Distributed

      • These instructions refer only to formats that were never distributed.
        • If a resource was distributed at one time and is no longer distributed, it is still considered distributed.
      • For specific guidance on distribution notes in serials, see 500 – Distribution Note in Bibliographic Cataloging: Serials.

      In records for publications identified by LTS staff as for administrative or official use only, include these notes:

      • For administrative use only, or, For official use only.
      • Not distributed to depository libraries.

      The specific note, “Not distributed to depository libraries,” is only included in administrative or official use only publications.

      OCLC *42333264, CGP 511176
      086 HE 20.3402:SCI 2/2
      500 "For administrative use only."
      500 Not distributed to depository libraries.
      [No item number in record]

      Format Not Distributed Notes

      Tangible Formats - Distributed Only Online

      • In the record for a tangible version of a publication distributed only in an online version, include a 500 note that reads "[Tangible format] not distributed to depository libraries."
        • Always specify the type of tangible format.
      • 500 Print format not distributed to depository libraries. (In record for print format)
        500 Microfiche format not distributed to depository libraries. (In record for microfiche format)
        500 DVD format not distributed to depository libraries. (In record for DVD format)
        500 Computer disc format not distributed to depository libraries. (In record for computer disc format)

        Sales Information Notes

        536 - Funding Information Note

        • Funding notes may be used for any type of resource.
        • For more information, see Bibliographic Cataloging: Technical Reports, 536 - Funding Information Note [Add link to that section]

        546 - Language Note

        • Per RDA/LC-PCC PS 7.12.1.3 and MARC 21, 546 field, add a 546 note as well as an 041 field when a resource is in a language other than English or contains a language(s) in addition to English.

        ‡b Information Code or Alphabet - Braille Publications (RDA 7.13.4.4)

        • Record the type of Braille in subfield b.

        GPO Practice

        • Transcribe the wording as presented on the resource.

        546 ‡b Contracted (Grade II) Braille transcript

        6XX - Subject Access Fields

        For more information, see Subject Cataloging: General Policies.

        600 – Personal Name Subject

        • Establish all personal names used as subjects.
        • Create or update such name authority records when used as subjects.

        700 - Personal Name Associated with a Work

        • For more information, see 100 - Principal Creator - Personal Name [Add link to that section] for guidance on authority work.
        • When a corporate body or meeting name is recorded as the principal creator and persons appear in a statement of responsibility, trace those names in 700 fields, according to the first exception in 6.27.1.3 (Collaborative Works): “Corporate bodies as creators.”

        710/711 - Corporate/Meeting Name Associated with a Work

        • For more information, see Bibliographic Cataloging: General Policies.

        GPO Practice

        • Always include authorized access points for Federal agencies when they are responsible for issuing, preparing, or authoring resources, or, when they are the basis of the SuDoc classification.
          • This guidance applies when the name of the Federal issuing body does not appear on the resource.
        • Add AAPs only for the lowest units of the corporate bodies presented hierarchically in statements of responsibility or publishing statements.

        76X to 78X - Linking Entries

        Background

        Understand the concepts and terminology in MARC 21 for Bibliographic Data: Linking Entries. Linking entry fields comprise fields 760-787, and are referred to as fields 76X-78X. The “target item*” is represented by the bibliographic record which contains the linking entry field. The “related item” is cited in the linking entry field of the target item’s record.

        * Usage of the term “item” in this section of MARC 21, does not conform to the FRBR definition of item.

        Field(s) in related record …become(s) subfield in linking entry
        1XX ‡a
        130, 245 ‡t
        240 ‡s
        250 ‡b

        Subfields ‡a, ‡t, ‡s, and ‡b comprise the citation portion of the linking entry/field, or citation for short. In order to simplify the following instructions, only subfields ‡a, ‡t, and ‡s will be considered to comprise the citation portion of the linking entry/field, or citation. (Subfield ‡b will still be included in the linking entry field.)

        Original Cataloging

        For original cataloging, use the following format:

        7XX XX [‡i Note if appropriate:] [Citation, consisting of one of the following: ‡t, ‡a plus ‡t,‡a plus ‡s, or occasionally, ‡a plus ‡s plus ‡t when ‡t is not redundant* of ‡s] ‡b [edition statement] ‡x [ISSN] ‡w [LCCN] ‡w [OCLC number]

        *redundant, in this context, means with the exception of the qualifier (i.e., the text within parentheses)

        Basic Procedures:

        1. Paste OCLC number to which the linking field directs.
        2. Select and click on the “Insert from cited record”:
          1. From the pop up menu that appears after right-clicking.


          2. Or

          3. From the drop down menu that appears under “Edit.”
        3. Remove subfields ‡h, ‡d and ‡z.
        4.    

          As of April 2017, LSCM’s ILS Team has advised that retaining these fields would negatively impact searching.

        5. Remove the ‡t if it is redundant (except for the qualifier) of ‡s.
        6.    

          When removing subfields, you may need to adjust the punctuation, for example, by removing a period.

        7. Add a ‡i note if relevant.

        Example: 776 08 ‡i [Note if appropriate:] [Citation, consisting of one of the following: ‡t, ‡a plus ‡t, ‡a plus ‡s, or occasionally, ‡a plus ‡s plus ‡t when ‡t is not redundant of ‡s] ‡b [edition statement] ‡x [ISSN] ‡w [LCCN] ‡w [OCLC number]

        • If the record to which you are linking does not contain certain elements/fields, such as an LCCN, ISSN, edition statement, 1XX, or 240, then these elements will not appear in the linking entry provided by the macro.
        • If relevant, enter the ‡i note after the macro populates the field.
        • Since OCLC does not provide the subfield delimiter and code for a leading subfield a, you will need to insert these following the ‡i note when the entry begins with subfield a.

        Monograph:
        776 08 851189994 [After inserting OCLC number 851189994 , select/click on “Insert from cited record,” which generates the field below]

        776 08 Hill, Matthew J. ‡t Computational investigation of gear windage. ‡d Cleveland, Ohio : National Aeronautics and Space Administration, Glenn Research Center, 2012 ‡w (OCoLC)851189994

        Modify the above macro-supplied entry to form:
        776 08 ‡i Online version: ‡a Hill, Matthew J. ‡t Computational investigation of gear windage ‡w (OCoLC)851189994

        Serial:
        776 08 31406418 [After inserting OCLC number 31406418, select/click on “Insert from cited record,” which generates the field below]

        776 08 Library and Information Technology Association (U.S.). ‡s LITA newsletter (Online). ‡t LITA newsletter ‡x 1079-123X ‡w (DLC)sn 94004077 ‡w (OCoLC)31406418

        Modify the above macro-supplied entry to form:
        776 08 ‡i Online version: ‡a Library and Information Technology Association (U.S.). ‡s LITA newsletter (Online) ‡x 1079-123X ‡w (DLC)sn 94004077 ‡w (OCoLC)31406418

        Manual Modification is Necessary in the Following Two Situations:

        Except for removing redundant ‡t, there are only two situations where the citation portion (‡a, ‡s, and ‡t) of the linking field generated by the OCLC macro, requires manual modification by the cataloger:

        Except for removing redundant ‡t, there are only two situations where the citation portion (‡a, ‡s, and ‡t) of the linking field generated by the OCLC macro, requires manual modification by the cataloger:

        1. 130/245 Translations and Other Language Editions/Versions

        The macro will generate a citation containing only the related record’s 245‡a text in ‡t. Manually precede this with the text from the related record’s 130 field, all in ‡t separated by a period. In other words, combine the related record’s 130/245 in a single ‡t, separated by a period.

        NOTE: When examples refer to the citation, only the citation portion of the linking field is shown.

        Related record:
        CGP  998274
        Change the macro-generated citation from:
        776 08 ‡t Hua ren fu nü ji qi jia ting.
        To form the linking entry:
        130 0_ Easy guide to breastfeeding. ‡l Chinese.
        245 10 Hua ren fu nü ji qi jia ting : ‡b mu lu wei yang jian yi zhi nan.
        to:
        776 08 ‡t Easy guide to breastfeeding. Chinese. Hua ren fu nü ji qi jia ting
        776 08 ‡i Print version: ‡t Easy guide to breastfeeding. Chinese. Hua ren fu nü ji qi jia ting ‡w (OCoLC)960907957
        Explanation:

        This practice follows guidance in the CONSER Editing Guide/Variable Data Fields/76X-78X Linking Entries/Linking Entry Fields—General Information: scroll down to: FORM OF LINKING ENTRY: (f) 130/245 -- ‡t. In addition, scroll down to the two examples below under (f). (The first example is: ‡t Hung qi. English. China report. Red flag.) Other documentation such as MARC 21 was consulted, however, the only examples found for 130/245 languages/translations were in the CONSER Editing Guide—no examples were found for monographs.

        MARC 21 for Bibliographic Data: Linking Entries explicitly states that, in the linking entry field, ‡s is taken from the related record’s 240, while ‡t is taken from the related record’s 130 and/or 245. Therefore, we code both the related record’s 130 and 245 in ‡t – which is NOT repeatable. Consequently, we must combine these in a single subfield t. Incidentally, a common misunderstanding is that the related record’s 130 field is recorded as ‡s in the linking field. The misunderstanding seems to be that preferred titles with additional identifying elements (formerly known as uniform titles) belong in ‡s of the linking field. Actually, the MARC convention for this is more discrete than theoretical—it is simply that the related record’s 130 and 245 go in ‡t, while only the related record’s 240 goes in ‡s.

        2. Other 130/245 Monographs and Integrating Resources, Except Treaties

        This situation is limited to monographs and integrating resources, because the OCLC macro generates the desired result for serial records. However, when linking to a record that records the authorized access point for a treaty title in the 130 field, accept the result of the macro.

        The macro will generate a citation containing only the related record’s 245‡a text in ‡t. Manually replace this with the text from the related record’s 130 field.

        Related record:
        CGP 970685
        Change the macro-generated citation from:
        776 08 ‡t Domestic violence.
        To form the linking entry:
        130 0_ Domestic violence (United States. Department of Justice. Office of Justice Programs. Office for Victims of Crime)
        245 10 Domestic violence.
        to:
        776 08 ‡t Domestic violence (United States. Department of Justice. Office of Justice Programs. 
        776 08 ‡i Online version: ‡t Domestic violence (United States. Department of Justice. Office of Justice Programs. Office for Victims of Crime) ‡w (OCoLC)938817163
        Related record:
        CGP 970208  
        Change the macro-generated citation from:
        776 08 ‡t Prepare for emergencies in tribal nations.
        To form the linking entry:
        130 0_ Prepare for emergencies in tribal nations (Northeast edition)
        245 10 Prepare for emergencies in tribal nations.
        to:
        776 08 ‡t Prepare for emergencies in tribal nations (Northeast edition)
        776 08 ‡i Print version: ‡t Prepare for emergencies in tribal nations (Northeast edition) ‡b [Northeast edition] ‡w (OCoLC) 958934062

        However, when linking to a treaty record:

        Related record:
        CGP  797553 
        Do not modify the macro-generated citation
        776 08 ‡t Protocol amending tax convention with Luxembourg
        To form the linking entry:
        130 0_ Convention Between the United States of America and the Government of the Grand Duchy of Luxembourg for the Avoidance of Double Taxation and the Prevention of Fiscal Evasion with Respect to Taxes on Income and Capital ‡d (1996 April 3). ‡k Protocols, etc., ‡d (2009 May 20)
        245 10  Protocol amending tax convention with Luxembourg : ‡b message from the …
          776 08 ‡i Online version: ‡t Protocol amending tax convention with Luxembourg ‡w (OCoLC)704434393
        Copy Cataloging

        If linking entry fields in an OCLC record that GPO is editing contain the pagination (‡h), publisher (‡d), or other data that GPO would normally remove, keep that data in the OCLC master record, but remove it from the CGP version of the record (i.e., prior to export). However, you may correct mistakes in the linking fields of a master record, change the indicators in a linking field, and add a subfield i note. The examples below demonstrate changes that are allowed to the master record. When editing a record to make a specific correction or revision, it is acceptable to not make any of these changes. For general guidance on copy cataloging, see the copy cataloging section of Bibliographic Cataloging: Overview.

        Original record contains:
        530     Also available in print.
        776 1_ [entry]

        The cataloger may remove the 530 note, and change the 776 to:
        776 08 ‡i Print version: [entry]

        Original record contains:
        530     Also available online.
        776 0_ [entry]

        The cataloger may remove the 530 note, and change the 776 to:
        776 08 ‡i Online version: [entry]

        However, original record contains:
        530     Also available online at the Dept. of Justice web site. Address as of 7/1/2002: http://www.usdoj.gov/eoir/vll/intdec/lib%5Findecitnet.html; current access is available via PURL.
        776 1_ [entry]

        The cataloger may not remove the 530 note (because it contains critical historic data for archiving), but may change the 776 to:
        776 08 ‡i Online version: [entry]

        Or, the cataloger may leave these fields as is, if making a specific correction or revision.

        Original record contains:
        580    Revised and cumulated as: United States. Supreme Court. Official reports of the Supreme Court.
        787 1_ United States. Supreme Court. ‡t Official reports of the Supreme Court ‡x 0364-0973 ‡w (DLC)sc 78002344 ‡w (OCoLC)2532452

        The cataloger may remove the 580 note, and change the 787 to:
        787 08 ‡i Revised and cumulated as: ‡a United States. Supreme Court. ‡t Official reports of the Supreme Court ‡x 0364-0973 ‡w (DLC)sc 78002344 ‡w (OCoLC)2532452

        Or, the cataloger may leave these fields as is, if making a specific correction or revision.

        Finally, in all situations of copy cataloging, the cataloger may merely change the first indicator of linking entry fields from a 1 to a 0 (zero), without removing the corresponding 530 or 580 notes. This is because, in some library online catalogs, linking entry fields with a first indicator of 1 do not display. Consequently, it is a service to change the first indicator to 0, so that the link will display, even if the title or citation within the link already displays in the 580 or 530 note.

        776 - Additional Physical Form Entry

        See 76X to 78X- Linking Entries above for general guidance.

        For the ‡i note, use either:
        Print version:
        Online version:
        Microfiche version:
        CD-ROM version:
        DVD version:
        Optical disc version:
        Other notes are permitted if documented in PCC guidance, specific GPO guidelines, or if approved by a supervisor.

        When adapting microfiche records, change “‡c Original” to “‡i Print version:” and apply the “insert from cited record” macro to add the citation.

         

       

       

Back to Top

GPO Cataloging Guidelines

Introduction
Cataloging/Metadata Policy-making Process
Cataloging Policy and Documentation Committee (CPDC)
GPO Cataloging Guidelines Review and Revision
GPO Cataloging Guidelines: Organization and Structure
Examples
List of Standards
Bibliographic
Classification
Other Metadata Schemes
Other
Cooperative Associations
Questions
Bibliographic Cataloging
Overview
Authoritative Status of the Catalog of U.S. Government Publications
GPO Records in OCLC and Record Maintenance
Sources
What LSCM Catalogs
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
5.1 General Cataloging/Metadata Workflows - Individual Records
5.2 Project and Retrospective Cataloging
5.3 Batch Processing of Record Sets
5.4 Categories of Federal Information Products
5.5 922 Codes
6.0 Cataloging Levels Chart
Treatment Decisions for Collections and Analytics
Factors to Consider for the Treatment Decision
Separate Record Policy
Background
Procedures
Exceptions
Original Cataloging
Copy Cataloging
Adapting PCC Pre-RDA Records
Adapting Non-PCC Pre-RDA Records
Authenticating Non-PCC Pre-RDA Records as PCC
Replacing and Exporting Records
Cataloging Non-distributed Formats (for C&I)
GPO Sales Program Information
Authority Records
General MARC Field Policy 490 – Series Statement Field
General MARC Field Policy 856 – Historic URLs
General MARC Field Policies
Formats, Modes of Issuance, Etc.
Punctuation
Program for Cooperative Cataloging (PCC) Policy on ISBD Punctuation
Transcription
Fixed Fields
ELvl - Encoding Level
Variable Fields
037 - Source of Acquisition
040 - Cataloging Source
050 - LC Call Number
060 - NLM Call Number
070 - NAL Call Number
082 - Dewey Decimal Classification Number
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 - SOR
246 - Varying Form of Title
250 - Edition Statement
264 - Production, Publication
GPO Sales Statement
300 - Physical Description
336 - Content, 337 - , 338 -
490 - Series Statement Field
500, 588 - Title Source, Source of Description Notes
500 - General Note
536 - Funding Info 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
074 GPO Item Number
Multiparts
Item Number Corrections
086 SuDoc Number
Sources to Consult
Background and General Instructions
Multiparts
Serials and Integrating Resources
Microfiche
Current RDA Policies and MARC Fields (February 2015- )
MARC Fields
Overview of Previous Microfiche Policies
Re-Cataloging Microfiche
Congressional Publications
Fixed Fields
Leader/17- Encoding Level
Leader/18 - Descriptive Cataloging Form
008/39 - Cataloging Source
Variable Fields
037 - GPO Sales Stock Number
042 - Authentication Code
050 - LC Call Number
086 - SuDoc Classification Number
088 - Report Number
1xx - Principal Creator
130/240 - Unique Title for Work
245 - Title Statement
250 - Edition Statement
264 - Publication Statement
264 - Distribution Statement
300 - Physical Description
500 - General Notes
504 - Bibliography, etc. Note
505 - Contents Note
Technical Reports
Identification of Technical Reports
Monograph or Serial
Sources of Information
Cataloging Instructions
Fixed Fields
Variable Fields
General Guidance on Special Technical Report Fields
027 – Standard Technical Report Number
513 – Type of Report and Period Covered Note
536 – Funding Information Note
Public and Private Laws
Public Laws
Private Laws
Instructions
Treaties
074 - Item Number
086 - SuDoc Number
490 and 830 - Series
546 and 041- Language
Senate Treaty Document Series (Y 1.1/4:)
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 Math Data
300 - Physical Description
500 - Notes
655 - Genre Term
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
Continuing Resources
Selective Registration for ISSN Assignments
GPO’s automated submission of continuing resources for ISSN assignments
GPO’s selective registration of continuing resources for ISSN assignments
Inclusion criteria
Exclusion criteria
Serials
Sources to Consult
Policies, Procedures, Practices
Definition of Serial
Monograph vs. Serial and Frequency of Issuance
When Mode of Issuance Is Ambiguous
Replacement of Monograph Records with a Serial Record
Ceased Serials Cataloged for the First Time GPO
Numbering–Exceptions to RDA Principle of Transcription
Notification of Cataloging Updates via WebTech Notes
Notification of OAM for Serials Harvesting
Updating Collections of Serials
MARC Fields
Leader /17 (Encoding Lvl) & 042
010 - LC Control Number
022 - ISSN
050 – LC Call Number
060 – NLM Call Number
070 – NAL Call Number
074 - Item Number
082 - Dewey Decimal Classification Number
086 - SuDoc Number
246- Varying Form of Title
264 - Production, Publication
300 - Physical Description (300|a )
362, 588, and Any Field Where Designation Is Represented
500 - Distribution Note
515 - Numbering Peculiarities
538 - System Details Note
588 - DBO/Source of Title Proper Note
Language for “Description Based on” Note
Print Version Record Used As Basis of Description for Online Version
76X--78X– Linking Entry Fields
776 – Additional Physical Form
Cessation of print version, continuation online version
Cessation of serial due to format and title change
Microform serials and GPO practices for linkages
Former, discontinued practice for linking microform serials to other manifestations
Current practice for linking microform serials to other manifestations
Other Considerations for Linking Entry Fields
Parallel formats
Works linked but not described in bibliographic records
856 – Electronic Location & Access
Single- vs. Separate-Record Approach and PURLs
Appendix A: Bibliographic File Maintenance: Deletion of Records from the CONSER Database
Appendix B: Where to Find Certain CONSER Procedures
Integrating Resources
086 - SuDoc Number
130 - Authorized Access Point for Work
245 - Title
Other Title Information ($b)
Statement of Responsibility ($c)
300 - Physical Description
5XX - Notes
Order of 5xx Notes
588 - DBO/Source of title proper note
580/760-787 - Linking Relationships
Computer Files
Procedures to Convert Type "M" to Type "A" Records
eBooks
Overview
Disposition of eBooks on CD-ROM
MARC Fields
020 – International Standard Book Number
347 – Digital file characteristics
856 – Electronic location and access
New records, or non-GPO adapted records
Existing GPO records
955 – Local GPO notes
New record, acquired directly by cataloger
New record, acquired by acquisitions team
Existing GPO record, updated to include eBook
Non-Distributed eBooks
074 – Item number
500 – General note on distribution
588 – Description Based on Note
856 – Electronic location and access
OCLC Holdings
Export to Aleph
Resources to Consult
Name Authorities
Background
Instructions to Consult
Policy Overview
Personal Names
Congressional Publications
Other Publications
Corporate/Conference Names
Variant Names
Conference Authority Records
Programs and Projects
Corporate Names for Parks, Forests, Preserves, etc.
Works and Expressions
Multipart (Collective) Titles
Series
Series-Like Phrases
Places (Jurisdictional Geographic Names)
General Procedures
Optional Fields
Research in OCLC
How Much Research Should Be Performed . . . ?
When to Consult Additional Sources
Tips for Contacting Agencies
General Field Specific Guidelines
043 - Geographic Area Code
1xx and 4xx
4XX - See from Tracing
5XX - See Also from Tracing
670 - Source Data Found
678 - Biographical or Historical Data
781 - Subdivision Linking Entry - Geographic Subdivision
RDA
General Policies
Hybrid Records in RDA Name Authority Records
When to Recode an Existing NAR to RDA
How to Recode an Existing NAR from AACR2 to RDA
Field Specific Guidelines
$u and $v in the 046 and 3XX Optional Fields
Source of Information: 670 vs. $v in the 046 and 3XX Optional Fields
046 – Special Coded Dates
$2 – Source of Term
$s (start date or period) $t (end date or period)
336 - Content Type
368 - Other Attributes of Person or Corporate Body
370 - Associated Place
371 – Address
372 – Field of Activity
373 – Association Group
377 – Associated Language
4XX – See from Tracing
5XX – See Also from Tracings
670 – Source Data Found
678 – Biographical or Historical Data
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)
Corporate Names
Notes
Sources to Consult
Before You Begin
MARC Fields
110 - Corporate Name
Places Associated with the Corporate Body
Associated Institution
Names Containing the Word "Services"
111- Meeting Names
368 - Other Attributes of Corporate Body, $a Type of Corporate Body
370 - Associated Place
372 - Field of Activity
373 - Associated Group (11.5)
410/411 - See from Tracing
Initialism or Acronyms in Capital Letters
Variants for Names Containing Ampersands
410 - See from Tracing - Corporate Name
Variant Names Entered Subordinately
Place Names As Jurisdictions vs. Locations
Variant Names Entered Directly
Variants for Names Containing the Term “Inc.” or “Incorporated”
411 - See from Tracing - Meeting Name
Additional Identifying Element(s) for Initialisms/Acronyms in Variants for Meeting Names
510/511 – See Also from Tracing
Relationships and Relationship Designators
Mergers
510 - See Also from Tracing - Corporate Name
Hierarchical Superior Relationship
667 - Nonpublic Gen Note
678 - Biographical or Historical Data (11.11)
Works and Expressions
046 – Special Coded Dates (RDA 6.4 and 6.10)
130 – Authorized Access Point
336 – Content Type (RDA 6.9)
370 – Associated Place (RDA 6.5)
377 – Associated Language (RDA 6.11)
380 – Form of Work (RDA 6.3)
410/430 – Variant Authorized Access Points
667 – Nonpublic General Note
670 – Source Data Found
EXEMPLARS
Places
043 - Geographic Area Code
451 - See From Tracing
670 - Source Data Found
781 - Subdivision Linking Entry-Geographic Subdivision
AACR2
General Policies
Hybrid Records in RDA NARs
When to Recode an Existing NAR to RDA
How to Recode an Existing NAR from AACR2 to RDA
Field Specific Guidelines
5XX - See Also from Tracings
Personal Names
100 – Authorized Access Point
$q - Fuller Form of Name
400 – See from Tracing-Personal Name
678 – Biographical or Historical Data (RDA 9.17)
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
Places
043 - Geographic Area Code
451 - See from Tracing
670 – Source Data Found
781 - Subdivision Linking Entry-Geographic Subdivision
Subject Cataloging
General Policies
LC Subject Headings
NASA Thesaurus Terms As Subject Headings
MESH, NAL, and Other Non-LC Subject Headings
LC Genre/Form Terms for Library and Archival Materials
Adding General LCGFT to Bibliographic Records
Background Resources for LCGFT
Adding LCGFT to Cartographic Records
Adding LCGFT to Audiovisual Records
Subject Heading Proposals, Background, and Tips
Tips and Instructions
Internet Research
Subject Headings Manual
Searching Minaret
Add'l Minaret (Class Web) Tips
Scope Notes
Use of the Dictionary
Use of Wikipedia
Use of LSCH As a Thesaurus
References
Class Web or Minaret
SACO Resources
Subject Headings Manual
Print Resources
Resources for Geographic Proposals
Geographic Print Resources
Examples of GPO Subject Proposals
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
Name vs Subject Authority File
Overview
Instructions
Name Headings As Subjects
Special Topics, Materials, Subdivisions, Etc.
Environmental Impact Statements
Legal Topics
Research
Other Metadata Schemes
Dublin Core
ONIX
Glossary
Initialisms and Acronyms
List of Major Changes to the Cataloging Guidelines

yellow question mark flat

Questions on the GPO-specific practices outlined in the guidelines should be submitted via askGPO. Please indicate "Cataloging: Policies & Practices" in the subject area.