decorative old campus image

CONSER Standard: What's New

To: Technical Services Staff
From: Steven Arakawa for CPDC
Date: 8/03/2007 issue date/ 08/15/2007 3:40 PM revision date)

At this time, Yale policy is to catalog all new [original] serials according to the new CONSER standard level. Records cataloged prior to implementation should not be updated to follow the new standard. Use this checklist as an aide-memoire and as a record of all instances where Yale policy deviates from the standard. However, the cataloger is expected to become familiar with the CONSER Standard Record document cited under RELATED DOCUMENTS.

When to create a new record (Major vs. Minor Changes) . Catalogers should consult Appendix A in the CONSER Standard Record documentation.

Fixed Fields. Leader On Voyager, code as full (_ [blank]). For cataloging directly on Connexion, code as "Full-level input by OCLC" (I).

Fixed Fields: 006/007/008. A number of fixed fields are no longer required. If a fixed field is not required, the standard value entered is No Attempt to Code (NOT blank).

Fixed Fields: 006/007 Only 1st two bytes are required. On Voyager, clicking on the format tab (e.g. Microform or Map or Notated Music) represents the first byte. The second byte is the "Specific Material Designation," i.e., the top line after the NEW button is clicked. EXCEPTION: For preservation microfilm (NOT purchased), enter all values required under:

In the current preservation cataloging procedures document, the detailed breakdown of 007 fields is given at the head of the purchased microfilms section. For serials, follow the guidelines in this table only for preservation record 007 fields, i.e. records for microfilm created locally:

Fixed Fields: 008

i. Only these codes are required:

  • Publication Status [OCLC: DtSt]
  • Dates [OCLC: Dates]
  • Country of publication [OCLC: Ctry]
  • Type of resource [OCLC: SrTp]
  • Form of item [OCLC: Form]
  • Government Publication (only if applicable) [OCLC: GPub]
  • Successive/Latest entry [OCLC: S/L]
  • Language [OCLC: Lang]
  • Cataloging source [OCLC: Srce] *

*Note on Cataloging Source: use d NOT c for original cataloging. If a minimal level (Encoding Level 7) CONSER record is upgraded to standard level, delete the 042 msc authentication code but retain the "c" value in the Cataloging Source 008 fixed field.

Form of original Item [OCLC: Orig] item is required only for microform.

ii. No longer required:

  • Frequency [OCLC: Freq]
  • Regularity [OCLC: Regl]
  • Conference Publication [OCLC: Conf]

On Orbis, enter the following for the non-required fields:

| No attempt to code

The "pipe" will probably be prompted on the OCLC serial template with Connexion 2.0.

Do not use fixed field value _ [blank], because _ represents specific values depending on the byte number/character position.)

iii. The following 008 fields are optional. Use the OCLC default values as indicated.

  • Nature of the Entire Work [OCLC: EntW] Default value: _
  • Nature of contents [OCLC: Cont] Default value: _

Variable Fields

041 Language Code

Use only $a

130/240 Uniform Title

Not required. For language editions and translations, omit the 130 but make a 730 field with $l for language and a 775 (Other edition available) linking field for other language editions, or a 765 (Original language entry) for the original of the translation.

EXCEPTIONS. Required for:

  • monographic series conflicts (008 Type of serial m). However, Yale generally does not create bibliographic records for monographic series. Uniform title will continue to be made for series authorities.
  • generic titles (Bulletin, Newsletter)
  • generic titles combined with a chronological designation (Quarterly report)
  • collocating legal titles (e.g., Laws of United States, with 110 for United States and 240 for the law).

Yale policy. If the absence of a 130 results in retrieval or interpretation problems for acquisitions or public services, the cataloger may add 130/240 to the appropriate bibliographic records retroactively. Note that CONSER does not recommend applying the guidelines for differentiating uniform titles to newspapers or other special types of materials (such as rare serials) at this time.

245 ($b) Other title

Not required for acronym or fuller form of the title or for other title that includes the issuing body name. Not required for any parallel title. Statement of responsibility ($c) not required. CONSER records cataloged at minimal (EL 7) level will have a 245 $c, because the issuing body will not have an authority record. See also 550 below.

246 Variant Title

New tags:

Parallel title: 246 11
All other variants, including acronyms: 246 13
Minor title change: 246 1_ $i ... : $a

260 Publication, distribution, etc.

$a Only the first named place of publication is transcribed (2nd place is not transcribed even if in U.S. and first place is not).

$b Name of publisher is still required.

<$c> Date of publication is not required. For guidelines when there is no formal publishing statement, refer to Appendix A of the CONSER Standard Record Documentation.

300 Physical Description

Yale policy: Required for all tangible resources, e.g. printed serials. [CONSER standard: Not required for printed serials; required for non-print tangible electronic serials, e.g. CD-ROMs, DVDs, CDs. Neither Yale nor CONSER require the 300 for remote electronic resources, e.g. online journals]

310 Current Frequency

Required (if known)

321 Former Frequency

CONSER Standard: Not required for new cataloging, i.e. for backfiles. Continue the practice of recording the current frequency in 310 and the former frequency in 321 for ongoing frequency changes. There is now no limit on the number of former frequencies that can be recorded when performing maintenance.

362 1 Dates of Publication/Designation (unformatted)

  • Unformatted note (362 1 rather than 362 0) should now be used as long as the information is known.
  • Use the form Began with ... <and, if necessary> ; ceased with ... whether or not the item is actually in hand.
  • CONSER standard no longer requires use of abbreviations or conversion of numbers to Arabic numeral or AACR2/rev. capitalization; the cataloger can transcribe as found or use the standard abbreviations/capitalization
  • For numbering changes ("new series"), CONSER option is to enter in 362 or 515 "whichever is clearer." We recommend using 515.

[4xx]/8xx Series

Series transcription is not required. If the series is to be traced, use 8xx only, even if "series is traced the same": do not use 440.

Reminder: qualifier is required for the series tracing if there is a conflict even though it is not required for the serial itself.

If the series has an ISSN $x, use 490 1/830.

500 General Note

Required: source of title and issue on which the description is based. The Description Based On (DBO) note is required even if the first issue is in hand, but can be expressed as Description based on the first issue if the designation is recorded in 362 1.

The DBO note is combined with the source of title note. Because the source of title note is required, catalogers will need to cite the chief source even if it is the title page. You're encouraged to not abbreviate.

500 __ $a Description based on first issue; title from title page.

Required: 500 note for latest issue consulted (LIC) at the time of cataloging if an issue later than the first is available. This is a separate 500 field from the DBO note. Use Final issue consulted if the last issue is in hand. This note is also required whenever the bibliographic record is recataloged, e.g. when the frequency changes.

For reprints use the 500 note; 534 should only be used by LAC (Library and Archives Canada).

506 Restrictions on Access Note
Cf. 590 below

Yale Policy. For subscription journals that are remote electronic resources, this note is always added:

506     ‡a Access restricted by licensing agreement.

The note is not made for non-subscription remote electronic resources.

530 Additional Physical Form Available Note

Not made. 776 with $i is sufficient.

538 System Details Note

Direct access. Not required unless it is necessary to indicate the type of operating system or make/model of computer needed to run.

Remote access: Note is made only if the resource is accessed other than through WWW.

550 Issuing Body Note

Yale policy. Do not make a 550 note; always create a national level authority record and trace the issuing body.

CONSER standard requires making an issuing body note (or transcription in 245 $c) if a heading is traced that is not backed up by an authority record. In such cases, the CONSER record is assigned a minimal level encoding level and assigned the authentication code msc in 042. When Yale upgrades a member record to EL _ by making an authority record for the heading, the 550 field should remain in the record.

If there is an existing NAR for the body, any variant form appearing on a new serial that can be a valid reference on a NAR should be added to the NAR.

580 Linking Entry Complexity Note

Not required. Use linking entry fields instead, combined with $i. IMPORTANT: The first indicator of the linking field must be set to display (i.e., first indicator 0 NOT 1; when the 580 was required and applied, the 78x first indicator was set to 1). If the first indicator is not set to display, the linking function in the OPAC will not work.

590 Local note
Cf. 506 above.

Yale Policy. For subscription journals that are remote electronic resources, this note is always added:

590     ‡a Access is available to the Yale community.

The note is not made for non-subscription remote electronic resources.

710 Added Entry -- Corporate Name

Yale policy. Original cataloging. Required for issuing body any any other traced headings. All heading(s) must be established in the national authority file.

Yale policy. Cataloging copy. For now, NACO authorized catalogers should create an authority record for any heading used in a non-CONSER member copy record with Encoding Level _ or I. (New cataloging but not recon titles). Upgrade any new minimal level serial record to full level following the new standards. Requirement may be revisited if the number of records to be established becomes onerous. Guidelines for establishing corporate names are usefully summarized in Appendix A of the CONSER Standard Record Documentation: see "Establishing Corporate Headings." See Appendix A also for guidelines on whether to use 110 or 710: see "Main Entry Heading."

730/740 Added Entry -- uniform title/Added entry -- uncontrolled related title

Not required if it duplicates a linking field. EXCEPTION: For language editions and translations, omit the 130 but make a 730 field with $l for language and a 775 (Other edition available) linking field for other language editions, or a 765 (Original language entry) for the original of the translation.

776 Additional Physical Form Entry

Used with $i; 530 is not made.

8xx Series Added Entry

See 4xx above. If a series is traced, only the 8xx field is required; it is no longer justified by 4xx. Field 830 is used instead of 440 to facilitate authority work for CONSER catalogers who use Connexion linked authorities and for some authority control vendors. Exceptionally, make a 4xx if a $x subfield is needed for the series ISSN, but use 490 1/830 even if the series is "traced the same."

856 Electronic Location and Access

Yale policy. No link from print record to the remote resource. However, if there is a separately cataloged record for the remote resource, that record may have a link, even if the URL is local or password protected. CONSER option allows single record for print/electronic; this is not followed by Yale. CONSER does not permit URLs for locally restricted sites; this is not followed by Yale.


CONSER Standard Record Documentation (PDF includes the CONSER Standard Metadata Profile [MAP])

CONSER Standard Record page (Includes LCRIs)

Task Force for Serial Access Records: Final Report

Cornell AACR/ISO abbreviations:

CONSER Standard Copy Cataloging Checklist

CONSER Standard Record: Maintenance Guidelines for Acquisitions and Serial Support

[TOC] | Cataloging at Yale | [Optional Link]

NOTE: Examples may require Arial MS Unicode font to be viewed correctly on web browser.
Copyright © 2007 Yale University Library
Last updated: < 15-Aug-2007 3:40 PM -->