Implementing KOHA in librariesThe Vikram Sarabhai Library Experience

H Anil KumarLibrarian, Indian Institute of Management Ahmedabad

July 1, 2014

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

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

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!

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

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”

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

ILS Software

• CDS / ISIS• LIBSYS, Alice, SOUL, Libsuite, SLIM, etc• Libsys Premia, Liberty, VTLS, New SOUL, etc• Open Source Software solutions

Open Source ILS

Avanti /Micro LCSEmildaEvergreenFireflyKohaLearningAccess ILS

PytheasOpenbibliophpMyLibraryPMBNew Gen LibWEBLIS

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

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

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

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!

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!

Thanks

anilkumar@iimahd.ernet.in