230 likes | 237 Views
This article discusses the implementation of Aleph 500 at the British Library, including the integration of various library locations and the benefits and challenges of the system. It also highlights the transformative experience and future developments.
E N D
Integrating the British library: implementation of Aleph 500 Alan Danskin Data Quality & Authority Control Manager. Sistema integrado de gestión bibliotecaria: motor de cambio 24th September 2008, Biblioteca Nacional, Madrid.
The British Library - Locations St Pancras, London Boston Spa, W. Yorks. Colindale, London Humanities Reading Room
British Library National Lending Library for Science and Technology British Museum Dept. of Printed Books India Office Library and Records National Central Library National Reference Library of Science and Invention British Institute of Recorded Sound British National Bibliography National Newspaper Library
Legacy systems (simplified) SPACE DSC Systems PALAS WLN ICARUS LOCAS Acquisitions Systems SPHOA BLAISE SPIS BLC edit FINANCE StP. OPAC Catalogue Bridge BLPC ABRS
Complex architecture Complex dependencies Bureau Service High support costs Obsolete hardware/software High risk No UNICODE support Poor user experience Lack of agility Constraint on collaboration Low web profile Redundancy and duplication of data in silos Catalogue maintenance expensive and difficult Legacy architecture
‘Vision’ for Integrated Library System • Simplifies BL technical architecture • Interfaces between different parts of BL • Uses international standards • Open to external user systems
Guiding principles for ILS • ‘Off the peg’, unmodified package • BL will modify business processes around the package • ‘Satellite’ systems only when impossible for ILS to provide business need • Priority to acquisitions, cataloguing and OPAC (but take account of document supply)
ILS Programme • Procure and implement package • Migrate data from legacy systems • Develop interfaces • ‘Satellite’ systems (if any) • External systems • Modify business processes • Wind-down legacy systems • Future developments
ILS Project Timeline • 23 April 2002 Advert placed in OJEC (Official Journal of the European Community) • 14 May 2002 DCMS accepted ILS Business Case • 20 Dec 2002 Contract signed with Ex Libris • 22 March 2004 First new record added to ILS • 1 June 2004 Internal processing starts on ILS • 29 June 2004 Reading rooms live using ILS OPAC • 7 September 2004 Web OPAC live using ILS • July 2006 Aleph Version 17 Upgrade
Some implementation statistics • 16 Legacy systems replaced • 1000+ staff trained • 75.3 million records migrated • 12 million UKMARC records converted to MARC 21 • 5 character sets replaced by UNICODE £1,000,000 p.a. saved on external systems costs
Transformative experience • Profound change to public view of collections • Re-engineering of collection processing • Previously by function • Now separate workflows for monographs & serials • Re-use of data • Investment in catalogue maintenance and data enhancement • LC/NACO name authority alignment • Deduplication • Retrospective conversion Integration of digital collections
Retrospective catalogue conversion Aleph implementation
Out of scope • Circulation module not implemented • Import/Export • Satellite systems Archives and manuscripts • Shelfmarking
What’s next • Integrated search interface • ILS • Archives and Manuscript • Sound recordings Aleph Version Upgrade • Decision pending on implementation in late 2009 • ILS Contract • Expires in 2012
Conclusion • Motor for change • Huge volume of work • Substantial financial savings • Ongoing costs • Created new opportunities