Implementing koha at iima
Download as PPTX, PDF1 like597 views
The document discusses the Vikram Sarabhai Library's experience implementing the open source integrated library system (ILS) Koha. Some key points: 1) The library needed to upgrade its old ILS to better support features like web 2.0, federated searching, and digital collections. It chose Koha due to its flexibility and low cost as an open source option. 2) Implementing Koha was a long process that involved migrating data, validating records, identifying requirements, and drawing workflows. All staff were involved in planning and testing. 3) Initial returns have been positive, including streamlined recommendation, acquisition, and circulation processes. Future plans include SMS integration and a mobile interface.
Implementing koha at iima
- 1. Implementing KOHA in libraries The Vikram Sarabhai Library Experience H Anil Kumar Librarian, Indian Institute of Management Ahmedabad July 1, 2014
- 2. Open Source Software • Software that is free • Includes the original source code used to create it • Users can modify it • Right of redistribution – new products! • Software may be free but the distributor may charge for services - customization, installation, training, maintenance (AMC), etc
- 3. Open Source Software • OSS is created and maintained by developers collaborating across nations • Release Early, Release Often and Listen to Users – OSS development process (Linus’s Law) • Outcome and its Quality (not Profit) that drives OS developers – personal pride in seeing their working solutions adopted • IPR of OSS belong to anyone who helps to build it or simply uses it • IS NOT LOCKED BY ANY ONE VENDOR OR INSTITUTION
- 4. Advantages of OSS • Flexibility to customise • No restriction on use • Low cost • Quality – distributed expertise • Use of open standards • Now - use of convenient platforms like windows versions • Developing a module for one customer (who pays) benefits others. • Since solution is adopted internationally – you have a global product!
- 5. Disadvantages of OSS • When we go for large customisation – Unanticipated costs – Integration with new versions – Scalability and speed – Internal expertise - management and adoption - different from commercially available software – Risk is high in institutional adoptions – Success has many fathers and failure has none • Lack of coordination in development (Indian requirements!) • Inadequate technical support need more choices • No guarantee of addressing the bugs or regular new versions or support
- 6. ILS and OSS • Integrated Library System and library automation • Quick and Continuous Change in technologies in and around libraries • ILS has not kept pace. Example: Web 2.0 • Collections have become digital – Federated search, ERM, Discovery, etc • Price is an issue – justified? • Business models need to look at development partnerships with vendors rather than just “sale and supply” • At the most we have “maintenance and support relationships”
- 7. ILS Trends • Most commercial software are around many decades and hence are mature. • No space for new products? • ‘Understanding’ of technology among library professionals / users is better today than yester years – hence demand for customisation has increased • Forced Migrations (Marshall Breeding) – Vendor abandonment – Need to move from legacy systems – Exit from bad marriages with vendors – Exit from bad marriages with consortia
- 8. ILS Software • CDS / ISIS • LIBSYS, Alice, SOUL, Libsuite, SLIM, etc • Libsys Premia, Liberty, VTLS, New SOUL, etc • Open Source Software solutions
- 9. Open Source ILS Avanti /Micro LCS Emilda Evergreen Firefly Koha LearningAccess ILS Pytheas Openbiblio phpMyLibrary PMB New Gen Lib WEBLIS
- 10. Why did we do it? • Needed to upgrade • User pressure – Book recommendation – Searching – Web 2.0 • Looked at different options – Upgrade Libsys – VTLS, Liberty, etc – OSS • Zeroed onto OSS and then Koha
- 11. Things that were important • Distinct digital space for Users • Distinct digital space for Staff • Good communication between system and user • Admin convenience in managing the work • Flexibility in reports
- 12. Long process • Identified support provider • Discussions on planning and next steps • Manpower planning • Strategy – Migrate the data – Validate the existing records – decided to do it in Koha – List the requirements • Process – Migration with help of IT staff – All staff involved in drawing up the flow chart for each division • Books (recommendation, acquisition, processing, etc) • Periodicals • Circulation • OPAC • Administration
- 13. Learning • Involve all staff • Identify support organisation • Teach and train the service provider • Change in mindset and approach to a new ILS • Time is always short and implementation is always long – in customisation • Compromise on things that are staff centric and do not compromise on user centric needs • Adopt standard versions – do not go for large scale customisation that needs to change the software architecture • Need to think of upgrading to new versions!
- 14. Summary • Immediate returns: – Recommendation process streamlined and transparent – Book acquisition improved in efficiency – User feedback is encouraging – Circulation management has improved – Integration with Discovery • Future – SMS integration and Mobile interface – Serials and bound volumes management • Helps in team building??? • It is a real challenge but a rewarding experience!