1 / 69

Introduction to Yale Core

Introduction to Yale Core . The New Default Standard for Yale Catalog Records 1/31/08. What is Yale Core? . New default standard for Yale original cataloging New standard follows recommendations of the CMS Task Force on Core Level Cataloging

tuwa
Download Presentation

Introduction to Yale Core

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to Yale Core The New Default Standard for Yale Catalog Records 1/31/08

  2. What is Yale Core? • New default standard for Yale original cataloging • New standard follows recommendations of the CMS Task Force on Core Level Cataloging • New standard supports CMS 2007 vision statement goals • Follows completely the PCC/BIBCO Core Record Standard for Description & Access (including subject access & classification) • Follows selectively the PCC/BIBCO Record Standard for name & series authorities (Yale authorities guidelines for non-pcc records will be followed instead)

  3. Why Yale Core? • More staff time needed for non-traditional knowledge organization projects • Research indicates PCC/Core standard saves time (and following the Yale authorities guidelines should save a little bit more) • New cooperative cataloging environment is more tolerant of the “floor” concept on which core is based: CONSER standard, institution records

  4. Core & Quality • Number of records that can be coded pcc should not change—Yale authority record guidelines are not changing • Aim of core is to provide sufficient information for identification & retrieval by the user—but not necessarily one’s cataloging peers • Cataloging will always respond to actual user feedback but will invest less time anticipating the effect on potential users • Streamlined records could affect user searching and data-mining—but slow processing time is also a loss of service

  5. Core Record Components • General core guidelines on: • Variable number & code fields • Variable data fields • Authority Control • Fixed Fields (including Leader) • Special descriptive guidelines for non-print formats

  6. Variable Number & Code Fields • Required: • 010 <retain if on the record; add if on the item> • 020 <for a multipart, only the set 020 required> • 035 <OCLC # & YL numbers> • 040 • 042 <only if all headings are authorized> • 050 <required if used for location; recommended if not> • All other control fields are NOT REQUIRED, notably: • 041 <exception: req. for Video, Cartographic> • 043

  7. 245 246 <use cataloger judgment> 250 <if applicable> 260 300 4xx <if applicable> 500 <only for source of title proper, if other than chief source> 501 <With note; applied only to publisher b/w> 502 <dissertation note> 505 <only if multipart volumes have individual titles> 533 590 <if applicable> Required Descriptive Fields

  8. 546 Language notes (including “Translated from the …” when no 240 can be readily ascertained) 500 Notes to justify access points 500 Notes to justify publication date 500 Index notes 504 Bibliography notes 520 Summaries <Exception: required for video> 505 Table of contents not required (but required for individual volume titles) 534 Original version notes 500 Errata slips Descriptive Fields NOT Required Include:

  9. Variant Title Access • 246: Cataloger judgment rather than LCRIs, e.g. writing out numbers • Take limitations of the local catalog into account—variant title access if title proper has ampersand • Only the title proper requires a justifying note if applicable; justifying variant titles is not required. • Use: 246 3# $a <title> • Instead of: 246 $i <note> $a <variant title> • Instead of: 246 14, 246 30, 246 31, 246 18, etc.

  10. Required Access Fields (1) • 1xx (including 130) or 1xx/240 required if applicable <240 only if readily available BUT required for music> • 7xx is required if applicable for all fields that would normally be assigned to a full record • 4xx/8xx is required if applicable for all fields that would normally be assigned to a full record • Generally trace all new series • SAR is not required for a new series unless it is standing order, classed-together analyzed, or needs references

  11. Required Access Fields (2) • 6xx • Required for primary subjects • Not required for secondary (“less than 20%”) subjects • Subjects assigned should be as specific as necessary; overly broad subjects should not be assigned just because the record is cataloged at core level

  12. Required Access Fields (3) • 6xx • Not restricted to a set number of subjects • Some topics can only be expressed with multiple subjects • Required to follow SCM instructions for multiple subjects unless a local exception is documented • Documented local (YUL) practices must be followed, e.g. LGBTQ tracing; LC local practices (e.g. topical subjects for Anglo-American fiction) are not followed • If no SCM or local instructions, use cataloger judgment in assigning primary subjects

  13. Examples: 6xx • Primary vs. Secondary (shaded)

  14. Examples: 6xx • Single subject appropriate: core & full would be the same

  15. Examples: 6xx • Multiple subjects appropriate: core & full would be the same

  16. Examples: 6xx • Class of person subject required by H 1330; shaded subject is secondary

  17. Required Access Fields (4) • If LC classification is used for the location, assign a complete call number following the new (minimal) shelflisting guidelines • Classification should be at the same level of specificity used for a full record • If a call number is not assigned for the location, assign an LC class number in 050 #4; class number is all 050 elements before $b; continue to assign call numbers for sml locations flagged for LSF • Non-LC call numbers, including accession numbers, continue to be assigned based on local practice; LC class number in 050 #4 is not required but should be included if readily available

  18. Authority Control • Follow the same procedures applied to full level cataloging under Authority Control for Catalog Librarians. • All headings must be validated against the national authority file(s): LC, OCLC, or LCDB • New authority record is made for: • Heading requiring cross-references • To distinguish a new heading from an existing heading • Classed-together analyzed series or multipart • Series or multipart on standing order • Any unestablished heading on a record to be contributed as 042 pcc • Research worth documenting in 670

  19. Fixed Fields • Leader: Same as full level, but Encoding Level: 4 • 006 Not required • 007 Required if applicable • 008 Required

  20. Fixed Fields • 008 required for all formats; all appropriate codes are assigned, per Bibliographic Formats and Standards • Remember: • if the record is not pcc, 008 Cataloging Source d • if the record is pcc, 008 Cataloging Source is c • Exception: some codes are not required for the CONSER Standard Record (but technically CONSER Standard is not Core) • 007 required on all non-print formats; all appropriate codes are assigned

  21. Additional Descriptive Guidelines • Serials: follow YUL application of CONSER standard • Video: in addition to Books fields: 028, 041, 511, 520, 538, 546 are required

  22. Additional Descriptive Requirements • Monographic Electronic Resources, in addition to Books fields: • 300 required for direct access; not required for remote • 500 <if applicable>: Source of edition note, Accompanying material note • 520 <if not apparent from the description> • 538 • 856 for remote access • Generally apply CONSER standard when cataloging electronic serials & integrating resources

  23. Additional Descriptive Requirements • Sound Recordings: • 028, 041, 505 (for compilations), 511, 520 (if not obvious from the description), 546 • 500 <if applicable>: Accompanying material, Label name & issue/matrix number, Form of composition/Medium of Performance, Compact Disc note) • Printed/Manuscript Music: • 024 2#, 028, 041 • 500: form of composition/medium of performance, publisher/plate number • 546

  24. Additional Descriptive Requirements • Cartographic: • 034 <Coded Cartographic Mathematical Data> • 041 • 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> • 546 • 552 $o if applicable <Entity & Attribute Overview>

  25. And remember… • If a user believes a record cataloged at core level needs more description/access, the record will be revised retroactively (generally by Catalog Management) • Cataloger has the option to go beyond the required elements for core at the point of cataloging, but this should be case by case, not across the board • Special collection cataloging can upgrade a core level record to serve the collection’s needs, or apply an across the board policy within the unit • If all of the access points on a core record are supported by national authority records, contribute the core record as pcc core!

  26. Core & Derived Cataloging • Member copy is not edited to core level from full level • If less-than-full member copy needs to be upgraded, fields not required by the core standard should be left in the record, provided that the information is accurate & observes standards • Apply the same procedure used for less-than-full member copy to variant edition cataloging

  27. Last thoughts-- • The Yale Core Record will provide enough information for identification and retrieval by the user; it does not anticipate all the needs of all users, including your cataloging peers • The Yale Core Record provides a "floor" or foundation on which others can build if they choose to do so • Think of Core as a challenge to use your cataloger's judgment in a new way to further our institutional goals • Have fun! And don't agonize!

  28. Yale Core Standards Background • Task Force on Core Level Cataloging Final Reporthttp://www.library.yale.edu/cataloging/Core%20Level%20TF%20Final%20Report%20rev421.doc • Catalog & Metadata Services Vision Statementhttp://www.library.yale.edu/cataloging/Vision%20Statement%20010107.doc

  29. National Level Core Standards • Bibco Core Record Standardshttp://www.loc.gov/catdir/pcc/bibco/coreintro.htmlAlso available at Tools & Resources: General Reference (Library of Congerss/PCC, item 9.) http://www.library.yale.edu/cataloging/toolsreference.htm • OCLC Guidelines for Full, Core, and Abbreviated-Level Cataloginghttp://www.oclc.org/bibformats/en/onlinecataloging/default.shtm#BCGGBAFC

  30. Exercises • For each exercise set, there will be a brief record and a list of variable fields • Assume the information in the brief record variable fields is correctly transcribed • Check off the variable/fixed fields that you would be required to add to a Core record • Provide appropriate tagging for highlighted fields (light purple) • Answers: Unrequired fields are highlighted

  31. Exercise 1: Brief Record

  32. Exercise 1: Variable Fields

  33. Exercise 1: Variable Fields

  34. Exercise 1: Core Record

  35. Exercise 2: Brief Record

  36. Exercise 2: Variable Fields

  37. Exercise 2: Variable Fields

  38. Exercise 2: Core Record

  39. Exercise 3: Brief Record

  40. Exercise 3: Variable Fields

  41. Exercise 3: Variable Fields

  42. Exercise 3: Core Record

  43. Exercise 4: Brief Record

  44. Exercise 4: Variable Fields

  45. Exercise 4: Variable Fields

  46. Exercise 4: Core Record

  47. Exercise 5: Brief Record

  48. Exercise 5: Original Record (Screen 1)

  49. Exercise 5: Original Record (Screen 2)

  50. Exercise 5: Variable Field

More Related