BIBCO at UF

1
BIBCO at UF

• An Update Session
• by Jimmie Lundgren
• August 11, 2003

2
What is BIBCO

• An international cooperative program for online
  cataloging the monographic bibliographic record
  component of the Program of Cooperative
  Cataloging (PCC)
• BIBCO began in October of 1995, and many of the
  early participants were former National
  Coordinated Cataloging Program (NCCP) libraries.

3
UF and the PCC

• Before the PCC there was CONSER and UF joined
  this serials cooperative program in 1975 (Naomis
  area)
• Then there was NACO and we contributed name and
  series authority records (Priscillas area)
• Since 1994 we contributed subject authority
  records (SACO, Tatianas area)

4
Pre-BIBCO Factors Favoring UF Joining BIBCO

• We already followed most LC practice and had a
  well-trained cataloging shop
• We were already participating in the National
  Enhance Program for books through OCLC
• We were fully authorized to contribute name,
  series and subject authority records needed for
  works we cataloged

5
We Applied to Join BIBCO in 1998

• In the fall of 1998 Kate Harcourt of Columbia and
  Iris Wooley of Cornell came here and trained us
  in BIBCO.
• Training was not how to catalog, but in the value
  of cooperation and the CORE record and in
  requirements of BIBCO full and core records

6
Quality Review Period

• I became our BIBCO Coordinator and gathered 50
  sample records from our catalogers and sent them
  to Kate Harcourt
• Kate examined them very closely and gave us
  detailed feedback
• In February 1999 we began contributing
  independently through OCLC

7
BIBCO program requirements

• Active NACO participation
• Compliance with the inputting and editing
  standards of the utilities to which they
  contribute the records
• Agreement to abide by the BIBCO Program
  Parameters, including AACR2, ALA-LC Romanization
  tables, Library of Congress Rule Interpretations,
  and MARC 21 bibliographic formats.

8
About the BIBCO record

• Authentication is the process of 1) creating or
  reviewing a non-serial bibliographic record,
  ensuring that its data content and content
  designation conform to BIBCO bibliographic
  practices and other agreed-upon conventions and
  2) adding identifying elements to record to
  indicate degree of authoritativeness of data or
  extent to which record has been reviewed.
• A BIBCO record is a bibliographic record for a
  non-serial item that has been authenticated by at
  least one participant in the BIBCO Program.

9
Why Are BIBCO Records Needed?

• To increase the availability in OCLC or RLIN of
  sufficiently high quality records for books that
  another library can use with little or no review
  or local modification (as we have always used
  DLC)
• Our Copy Cataloging Unit now makes good use of
  BIBCO records from other libraries

10
What is Required for a BIBCO Record?

• Authority control for all access points
• A classification number from LC, Dewey or NLM (we
  use LC, of course)
• Subject analysis if the work requires it using
  LCSH, MeSH, etc. (we use LCSH, of course)

11
3 Exceptions to authority control requirement

• New LC subjects that have been submitted to LC as
  SACO proposals may be entered on records coded as
  BIBCO 
• Series not yet established may be entered as
  untraced (490 0_) on Core records without a
  supporting series authority record in OCLC.
• Even when rules require the addition of a uniform
  title to a record that is coded as BIBCO, it is
  not always necessary to create an authority
  record for the uniform titles (e.g., when no
  x-ref is needed, or no research was performed)

12
Full versus Core

• These are the two levels of BIBCO records for
  entering as originals or for upgrading member
  input in OCLC
• Choice of which level to enter depends on our
  priority level for the item being described
• Initially the BIBCO program strongly promoted
  Core and it was used at some libraries as a tool
  for reducing large backlogs, now it is less
  prominent but still useful

13
Core records

• The PCC Core record standard specifies a minimum
  set of data elements for different types of
  material which must always be included in any PCC
  Core record, yet may also be exceeded, if the
  cataloger deems it necessary.
• Records that lack this minimum set of MARC fields
  cannot be considered to be PCC Core
• Different data elements were specified for each
  format or type of material we only do book

14
Core records are clearly marked

• Distinguished from full by Elvl 4 in fixed field
• Records marked as core often exceed core
  requirements core-plus is designated as core

15
Full record standards

• From the PCC perspective a full-level
  bibliographic record potentially contains more
  detail than a core-level record. The
  specification for a full-level record subsumes
  the data elements specified for PCC Core records.
  A full-level record, in general, reflects the
  following characteristics

16
Description is based on

• The current versions of the Anglo-American
  Cataloguing Rules, at either the second or third
  levels of description,
• The Library of Congress Rule Interpretations, and
  
• The ALA-LC Romanization Tables

17
2) Access includes

• Classification based on one of the schemes
  recognized by MARC 21 for monographs for other
  materials, it is not required
• Subject and/or form access based on one (or a
  combination) of the subject heading systems,
  thesauri, or genre/form lists recognized by the
  MARC 21, as appropriate provide for all subject
  aspects constituting 20 or more of the content
• Entries reflecting the full complement of access
  called for by the cataloging rules all entries
  are justified, from either the description or
  notes

18
3) Record is in machine-readable, MARC 21 form

• It also reflects the content designation of the
  MARC 21 Format for Authority Data where
  applicable as well as the conventions of the
  following associated MARC 21 documentation
• MARC Code Lists for Countries, for Geographic
  Areas, for Languages, for Relators, Sources,
  Description Conventions, and MARC 21
  Specifications for Record Structure, Character
  Sets, and Exchange Media

19
History of UF BIBCO Contributions

• Feb.-Sept. 1999 958 records
• Oct. 1999-Sept. 2000 1864 records
• Oct. 2000-Sept. 2001 1871 records
• Oct. 2001-Sept. 2002 1945 records
• Oct. 2002-July 2003 1250 records
• Usually there are about ¼ as many core as full
  records

20
Chart of UF BIBCO Statistics
21
More points about BIBCO

• Original records must be at least core standard,
  code as core if less than full
• Upgrading of OCLC copy may include correcting or
  adding fields or simply authenticating records
  already full
• Upgrading of DLC less-than-full records
  difference in fixed field srce coding

22
Identifying records as BIBCO

• BIBCO records are identified by field 042 with
  the value pcc. The Cataloging Source Code (srce
  in OCLC, 008, byte 39) has value blank if it
  was originally created or updated by a national
  library. In all other cases, the srce will be
  c. If srce was originally blank, it must
  remain blank, even if modified by a library
  other than a national library. PCC Core records
  have Encoding Level (Elvl in OCLC, Leader, byte
  17) with value 4 and PCC Full records have ELvl
  with value blank.

23
Resources on BIBCO

• BIBCO Participants Manual available in
  Catalogers Desktop
• Includes details about BIBCO cataloging
• Includes Core record specifications and examples
  for each format
• BIBCO Homepage at http//www.loc.gov/catdir/pcc/b
  ibco.html

24
What else?

• Comments
• Questions