1 / 61

Introduction to the (YUL) Bibliographic Standard Record for Printed Books

Introduction to the (YUL) Bibliographic Standard Record for Printed Books . The New Default Standard for Yale Catalog Records Based on the BIBCO Standard Metadata Application Profile 12/14/09/Rev. 1/04/10. What’s New? . New default standard for Yale original cataloging

JasminFlorian
Download Presentation

Introduction to the (YUL) Bibliographic Standard Record for Printed Books

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 the (YUL) Bibliographic Standard Record for Printed Books The New Default Standard for Yale Catalog Records Based on the BIBCO Standard Metadata Application Profile 12/14/09/Rev. 1/04/10

  2. What’s New? • New default standard for Yale original cataloging • New standard is derived from the BIBCO Standard Record for Printed Books (implemented 1/04/10) • Is consistent with CMS 2007 vision statement goals • YUL follows completely the Metadata Application Profile (MAP) of the PCC/BIBCO Standard Record for Printed Books (including subject access & classification) • YUL follows selectively the PCC/BIBCO Record Standard for name & series authorities (Yale authorities guidelines for non-pcc records will be followed instead)

  3. Behind PCC’s Bibliographic Record Standard (BSR) • New cooperative cataloging environment is more tolerant of the “floor” concept on which core is based: CONSER standard, institution records • PCC has redefined its core and full level standards and replaced them with a single standard • The new BIBCO standard for the most part follows the former PCC core standard (with some tweaking)

  4. Quality Issues • Number of records that can be coded pcc should not change—Yale authority record guidelines are not changing • Aim of standard 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. Scope • PCC guidelines apply to printed books, printed theses, and microform only • Guidelines do not apply to rare books; PCC is planning to issue a separate standard • For serials, follow the CONSER standard • PCC has not yet developed standards for media, online resources, and special collections • Continue to follow current YUL and PCC default standards for media [i.e. core] and special collections [based on unit decisions]; revisit when the new standards are published

  6. Standard Record Components • General guidelines on: • Fixed Fields (including Leader) • Variable number & code fields • Variable data fields • Authority Control

  7. Fixed Fields • Leader: • Encoding Level. <blank> [submitted as pcc]; 4 or i [submitted as BSR but not as pcc] • 006 Not mandatory • 007 Not mandatory by PCC but-- • Mandatory for reformatting units (all fields) • 007 and SMD are mandatory for non-reformatting units • Remember: 007 is still required for non-book formats • 008 Required—but requirements are considerably abridged!

  8. Changes to 008 Mandatory Elements Still Mandatory: No Longer Mandatory • 06 Type of date • 07-10 Date 1 • 11-14 Date 2 • 15-17 Place of Publ. • 23 Form of Item • 35-37 Language • 38 Modified Record Code • 39 Cataloging Source • 18-21 Illustrations • 22 Target Audience • 24-27 Nature of Contents • 28 Govt. Publ. • 29 Conference • 30 Festschrift • 31 Index • 33 Literary Form • 34 Biography

  9. Cataloging on OCLC • If OCLC default 008s have not changed on Jan. 4, continue to enter all valid codes in the Connexion fixed fields; code as pcc or non-pcc BSR as appropriate • Use ELvl <blank> with 042 pcc and Source c [all headings are backed by authority records and BSR descriptive standards are followed] • Use ELvl i with Source d and no 042 [BSR standards are followed but not all headings have authority records]

  10. Cataloging on Orbis • Macro is available to convert 008 to BSR • If the record is 042 pcc: Encoding Level is <blank>; 008 Cataloging Source is c. • PCC: description & access follow the BSR AND the headings are supported by NACO authority records or LCSH, AND 050 _4 • If the record is not pcc (no 042): Encoding Level is 4; 008 Cataloging Source is d • YUL BSR with Cataloging Source d follows PCC BSR for description and access BUT not all headings are backed up by NACO/LCSH authority records AND/OR no 050 _4

  11. 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> • 041 NEW. Was not required for PCC core; recommended for YUL; required if your record is coded for pcc • 040 • 042 <only if all headings are authorized> • 050 <required > • All other control fields are NOT REQUIRED, notably--043

  12. Required Descriptive Fields • 245 • 246 <use cataloger judgment> • 250 <if applicable> • 260 If there are multiple places, only the first one listed is now required; if place/publisher are not evident, just use [S.l.] and [s.n.]—don’t go out of your way to determine these • 300 BSR doesn’t require $c YUL continues—for the time being • 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; see LCRI 2.7B> • 533 • 546 NEW– if not evident from description • 590 <if applicable>

  13. Descriptive Fields NOT Required Include: • 240 assign only if it can be readily ascertained • 500 Notes to justify access points • 500 Notes to justify publication date • 500 Index notes • 504 Bibliography notes • 520 Summaries • 505 Table of contents not required (but required for individual volume titles) • 534 Original version notes • 500 Errata slips

  14. 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. • NEW Indicators: • 246 11 for parallel titles <MAP to be revised; see FAQ> • 246 13 $a <title> for all other title variants • Instead of: 246 $i <note> $a <variant title> • Instead of: 246 14, 246 30, 246 18, etc.

  15. Required Access Fields (1) • 1xx (including 130) or 1xx/240 required if applicable <240 only if readily available> • 4xx/8xx is required if applicable • Generally trace all new series • SAR is not required for a new series unless it is standing order, classed-together analyzed, or needs references • For a record coded PCC, SAR is not required if the series is 490 0_

  16. Required Access Fields (2) • 7xx is based on cataloger judgment • From the MAP: • “Use judgment in assessing each item. Assign a complement of added entries that covers the significant relationships associated with the work, expression, or manifestation of which the item is a part. The inclusion and importance of added entries are intended to reflect individual cataloger’s judgment and/or local policy, in the context of shared cataloging.”

  17. Required Access Fields (3) • 6xx • Required for primary subjects • Not required for secondary (“less than 20%”) subjects • Subjects assigned should be as specific as necessary—this was a requirement for PCC core and is even more the case with the PCC BSR

  18. Required Access Fields (4) • 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

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

  20. Examples: 6xx • Single subject appropriate.

  21. Examples: 6xx • Multiple subjects appropriate:

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

  23. 050 _ 4 • If LC classification is used for the location, assign a complete call number in 050 _4 following the (minimal) shelflisting guidelines • Classification should be at the same level of specificity used for a full record • Non-LC call numbers, including accession numbers, continue to be assigned in 852 based on local practice; LC class number in 050 #4 is not required but should be included if readily available.

  24. Authority Control • Follow the same procedures described in 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

  25. Beyond the Default Guidelines • If a user believes a record cataloged at standard 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 the standard at the point of cataloging, but this should be case by case, not across the board • Special collection cataloging is out of scope • If all of the access points on a YUL standard record are supported by national authority records, contribute the record as pcc (BSR)!

  26. Derived Cataloging • Member copy—including PCC records created prior to the implementation--is not edited to meet the new standard • Member copy—add 300 $c if not on the BSR copy • If less-than-full member copy needs to be upgraded, fields not required by the BSR should be left in the record, provided that the information is accurate & follows AACR2 & the LCRIs. • Apply the same procedure used for less-than-full member copy to variant edition cataloging

  27. Last thoughts-- • The YUL BSR 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 YUL BSR provides a "floor" or foundation on which others can build if they choose to do so • Think of the new standard as a challenge to use your cataloger's judgment in a new way to further our institutional goals • If you can contribute the YUL record as pcc, do it! • The guidelines may be revised as PCC & OCLC clarify application

  28. National Level Standards • Catalog Policy SharePoint site. The slides, exercises, and answers will be posted here, along with the Bibco PDFshttps://collaborate.library.yale.edu/cpdc/Policies/Forms/AllItems.aspx • Cataloging at Yale/Policies & Procedures (look for the BSR section). A checklist. • http://www.library.yale.edu/cataloging/indexgeneral.htm • Bibco Standard Record Announcement: Links to the Implementation/MAP document, a FAQ, & the Task Group Final Reporthttp://www.loc.gov/catdir/pcc/bibco/BSRAnnouncement.pdf • Also available at Tools & Resources: General Reference (Library of Congress/PCC, item 9.) http://www.library.yale.edu/cataloging/toolsreference.htm

  29. CAUTION! • The Bibco site still has a link to the Aug. 31 version of the BSR • There appear to be significant differences between the Aug. 31 and the Nov. 23 MAPs, so please do not use the Aug. 31 version as a reference • The OCLC workform will not accommodate fill characters until Connexion is updated—there is no fixed schedule.

  30. Exercises

  31. Exercises • For each exercise set, the relevant list of variable fields will be displayed: • Assume the information in the variable fields is correctly transcribed • Check off the variable/fixed fields that you would be required to include in the YUL BSR • Provide appropriate tagging for highlighted fields (exercise 4)

  32. Exercise 1

  33. Exercise 1: Variable Fields (1 of 2)

  34. Exercise 1: Variable Fields (2 of 2)

  35. Exercise 1. Fixed Fields 008 1 of 2 Continued

  36. Exercise 1. Fixed Fields 008 (2 of 2)

  37. Exercise 2

  38. Exercise 2: Variable Fields (1 of 2)

  39. Exercise 2: Variable Fields (2 of 2)

  40. Exercise 2. Fixed Fields 008 (1 of 2) Continued

  41. Exercise 2. Fixed Fields 008 (2 of 2)

  42. Exercise 3

  43. Exercise 3: Variable Fields (1 of 2)

  44. Exercise 3: Variable Fields (2 of 2)

  45. Exercise 3. Fixed Fields 008 (1 of 2) Continued

  46. Exercise 3. Fixed Fields 008 (2 of 2)

  47. Exercise 4

  48. Exercise 4: Variable Fields 1 of 2

  49. Exercise 4: Variable Fields 2 of 2

  50. Exercise 4. Fixed Fields 008 (1 of 2) Continued

More Related