130 likes | 218 Vues
An ILS with CJK Functionality: Implementation and Impact T he Experience of the University of Michigan Library. Michael Meng April 5, 2006 CEAL, San Francisco. Outline. About the UM integrated library system Timeline for i mplementation
E N D
An ILS with CJK Functionality: Implementation and Impact The Experience of the University of Michigan Library Michael Meng April 5, 2006 CEAL, San Francisco
Outline • About the UM integrated library system • Timeline for implementation • Post-implementation syndrome: three levels of analysis • Staff, Workflow, Technology • Selected issues for discussion • Indexing • The Google project • Conclusion
About the UM ILS • Aleph by Ex Libris • Strong CJK functionality • First implemented version: 16 • Along with SFX and Search Tools (Metalib) • System version upgraded annually • System service pack reviewed and updated monthly • 3 servers: production, development, training
Timeline for Implementation • September 2002: implementation process began • April 2003: data conversion began • June 2003: SFX went alive • April 2004: training for staff began • June 2004: final production load of all records • July 8, 2004: SWITCHED TO PRODUCTION • Fall 2004: Search Tools (Metalib) • March 2005: RLIN21 Implemented • Fall 2005: OCLC Connexion Implemented • Fall 2005: version 17 implemented • Summer/Fall 2006: version 18 to be implemented
Post-Implementation Syndrome: • Three Levels of Analysis • Staff • Workflow • Technology
Staff • Training as a continued process • Documentation • Roman vs. non-roman • Cataloging vs. acquisition • Central vs. local
Workflow • Central vs. local • Integrated vs. exceptional • Communication • Coordination • Collaboration
Technology • Qualitative vs. quantitative • Front stage vs. back stage • Data manipulation • Utilities • Z39.50, Z-Server
Selected Issues for Discussion • Indexing • Google • the impact of a massive digitization project
Impact of the Google Project • Bibliographic control • Single bib policy • Holding vs.item • Optical Character Recognition • Display of CJK scripts • Full-text search
Conclusion • Learn to be a system librarian and think like a programmer • Join committee, discussion groups (NAAUG), and talk to colleagues • Work closely with central processing units • Fit in with the mainstream workflow and never be exceptional • Be vocal for your unit/languages, but don’t become a “troublemaker”