SUL Shared Bib Implementation QA Betsy Simpson Chair
SUL Shared Bib Implementation Q&A Betsy Simpson Chair, Cataloging and Metadata University of Florida George A. Smathers Libraries December 21, 2011 January 5, 2012
Agenda • Introduction • Rationale • Chronology • Issues • Timeline • Local Implementation
Introduction What is an SUL shared bib? • SUL = State University Libraries • One bib record for each title • Separate holdings and items for each SUL • SUL Aleph client (SBU 01) FAMU, FAU, FGCU, FIU, FSU, NCF, UF, UNF, USF, UWF
Rationale • More efficient • Allows for greater centralization • Fosters collaborative collection development • Timely
Chronology • 2008: TSPC Single Bibliographic Task Force • 2008 -2009: CSUL Single Bibliographic Task Force • 2009 -2011: Single Bib Pilot Project (FSU, USF, UF) • 2011: CSUL directive
Issues • Bib merge • Ongoing workflow • Data loading
Bib Merge • OCLC Reclamation • Tag treatment • Clean-up
Ongoing Workflow • Strategic Direction for SUL Catalogers • SUL Guidelines and Procedures for the Shared Bibliographic Catalog • SUL-wide tables configuration
Data Loading • Bib record sets • Routine bib loads • Proprietary data
Timeline • January 2012 f 2 f meeting at FCLA (Cataloging, Acquisitions) Full test merge • February 2012 f 2 f meeting at FCLA (Access Services) Functional testing in all areas Refine policies and procedures • March 2012 Testing and training Refine policies and procedures
Timeline • April 2012 Testing and training Refine policies and procedures • May 2012 Testing and training Finalize policies and procedures • June 2012 Final testing Bib change cutoff Migration to shared bib
Local Implementation • Steering Group Betsy Simpson, Cataloging Steve Carrico, Acquisitions Michele Crump, Access Support Susy Potter, Legal Information Center Linnea Danielsen, Health Science Center Library • E-mail UFShared. Bib@uflib. ufl. edu • Lib. Guide http: //guides. uflib. ufl. edu/sharedbib
Questions?
- Slides: 13