decorative old campus image

Yale Core Checklist

To: Catalogers
From: Steven Arakawa for CPDC
Date: (Mar. 24 2008 issue date/ 03/24/2008 10:16 AM revision date)

General Guidelines

  1. Yale Core-Level is now the default, not the option. Additional data may be added to a given record on a case by case basis, but generally not across the board. Special collections can require additional data across the board to serve the collection's needs
  2. Additional cataloging data will be added to the record at the request of users. Catalog Managment Team is expected to receive most requests via CatProblems. If CMT cannot resolve, the problem will be routed to the appropriate cataloger.
  3. If all of the access points on the Yale core record are supported by national authority records, contribute the record as pcc core (042 pcc, Cataloging Source c). Keep in mind that pcc core requires a 050 _4 classification number.
  4. Don't edit down: When upgrading minimal or less-than-full member, vendor, or LC copy to core level, you will often find that the record includes fields not required by the core standard that would be required or included in a full record. Leave such fields in the record, provided that the information is accurate & observes standards. Apply the same principle when basing variant edition cataloging on a full level bibliographic record. Do not edit member copy to core level from full level.

Fixed Fields

Leader: Encoding Level (ElvL): 4 is the default value. Retain 4 even if additional fields are added on a case-by-case basis. If variant edition cataloging is derived from a full record, leave the Encoding Level at full if the original record was DCF:a. If the Encoding Level of the original record was DCF:_ or i, use Encoding Level 1.

006 Not required <exception for electronic resources; under review>

007 When appropriate (for microfilm, sound recordings, video, etc.), same requirements as full

008 Required. Use Cataloging Source d. If all headings are backed up by authority records, the record has an 050 _4, & the description is current AACR2, use Cataloging Source c (and add 042 pcc).

General Requirements for Variable Fields

Variable fields. Required fields for control numbers and codes:

Tag Comment Tag Comment
010 Retain on record; add if on item 040  
020 For multipart sets, only the 020 for the set is required 042 If all headings are established, there is a 050 _4, & description follows current AACR2, make a 042 with the pcc code
035 OCLC & YL number, any additional numbers required by the cataloging unit 050 _4

Required if used for the location; recommended if not.
Required for remote resources.
Classification should be at the same level of specificity used for a full record. See also CALL NUMBER

Variable fields. Required fields for description:

Tag Comment Tag Comment
245   500 For source of title only; additional requirements for some non-print formats
246 3_ Use cataloger judgment; not required to follow LCRIs; use 3_ for all 246 fields 501 Publisher bound with note
250 Required if applicable 502 Dissertation note
260   505 Contents note required only for multiparts with individual titles
300   533 Reproduction note
4xx Required if applicable 590 Local note

CAUTION: Table above presents notes in MARC numerical order. The note order following AACR2 should be: 500, 502, 505, 501, 533, 590

NEW. Notes to justify access (main entry or added entries) are not required for core-level records. However, if a heading is not represented by an authority record, and the usage can only be documented by a note, the cataloger should either create an authority record or make a (quoted) note, so that some record of usage is recorded.

Variable fields. Required fields for access.

Tag Comment

Required if applicable

1xx/240 Required for music only. For other formats, required if applicable if the uniform title is readily available.
4xx/8xx Required if applicable
7xx Required if applicable. Assign the same number of added entries as you would for a full record.

6xx. If applicable, required for primary subjects. Primary subjects should be as specific as the ones that would be assigned for a full level record. Remember that some topics can only be expressed with multiple headings. If there are specific Subject Cataloging Manual (SCM) instructions to assign an array of subject headings, follow SCM. Follow documented local practices for special subject tracings. BUT: what SCM calls "LC practice" is LC's local practice and is not required.

852 (CALL NUMBER). Classification should be at the same level of specificity used for a full record. If YUL local practice requires local classification, use local classification in 852; assign an LC class number in 050 _4 if readily available. A 050 _4 is required for remote electronic resources, even though a call number is not assigned in 852. A full call number is required for LSF.

Authority Control

Continue to follow previously established YUL guidelines for heading validation. For documentation, see

Unlike PCC core, YUL core does not require that every heading on the bibliographic record be supported by an authority record. Continue to follow previously established YUL guidelines for when to contribute a new authority record to the national authority file. For documentation, see

Even though YUL guidelines only require authority records to be made for a limited set of conditions, in many cases all headings on a bibliographic record will be supported by a national authority record. In that case, if the record also has a 050 _4, contribute it as PCC core.

Non-Book Formats

Cartographic Materials. In addition to the general required fields/data:

034 <coded cartographic mathematical data>


255 <$a required, $b required if applicable>

352 <digital graphic representation>

500 <if applicable>: relief, date of situation, digital datasets, unique number

534 <if applicable>


552 $o if applicable <entity & attribute overview>

Continuing Resources (Serials & Integrating Resources) . Follow the YUL version of the CONSER Standard rather than the YUL core guidelines.

Electronic Continuing Resources. Follow the YUL version of the CONSER standard.

Electronic Monographic Resources. Follow the general guidelines, but:

300 field is required only for direct access; 300 is not required for remote electronic resources

500 Required: source for title proper, source of edition, accompanying material

520 Required if not apparent from the description


856 Required for remote access resources

Music (Printed or Manuscript). In addition to the general required fields/data:

024 2_, 028, 041, 546

500: Form of composition/medium of performance, publisher/plate number

Sound Recordings. In addition to the general required fields:

028 Second indicator 1 should be used; this will cause the information in 028 to display in Orbis as a note.

041, 511, 546

518 Date/Time/Place of Event. Not required by PCC core, but make a note.

500 In addition to source of title proper notes: accompanying material, form of composition/medium of performance, compact disc note. Label name & issue/matrix number should be recorded in 028; duplicating the information in 500 is not required.

520 Required if not obvious from the description

Video. These fields are required in addition to the general required fixed fields:

028, 041, 511, 520, 538, 546


Introduction to Yale Core (PPT)

Yale Core Record Cheat Sheet (Word)

Bibco Core Record Standards

OCLC Guidelines for Full, Core, and Abbreviated-Level Cataloging

Task Force on Core Level Cataloging Final Report, June 1, 2007 (Word)


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

NOTE: Examples may require Arial MS Unicode font to be viewed correctly on web browser.
Copyright © 2008 Yale University Library
Last updated: < 24-Mar-2008 10:16 AM -->
URL: http: