Libraries now have the opportunity to move away from the proprietary integrated library system (ILS) model where the library contracts with a single vendor for the license, migration assistance, and support. The alternative is to move to an Open Source Library System (OSLS), which eliminates the costs associated with the licenses and maintenance contracts entirely. Sounds great, but what does that mean for the library that still needs migration assistance, ongoing support, and maybe even hosting from a "vendor?"
Fear not! There are many ways to get help evaluating the options, planning the migration, converting the library to the new OSLS and getting the support you need from service providers.
This webinar helps clarify the differences between the proprietary ILS model and the new OSLS model, including what it means for the library staff and budget.
First of 2-part series on OSLS. Today: introduction / orientation to OS and how it works. Differences between an OSLS and ILS, Benefits what’s going on in libraryland I am library technology consultant. Lots of work recently on OSLS projects.
What does that mean? OSLS versus ILS
PINES is the statewide public library consortium (aka lending network) - P ublic I nformation N etwork for E lectronic S ervices -union catalog -2 million bib records -9 million item. Georgia Public Library Service (GPLS) – manages PINES KOHA Developed by Katipo Communications for the Horowhenua Library Trust Needed system that could connect branch libraries to central library over ordinary phone lines Y2K issue forced the deadline NewGenLib – most used in India (as of 2007, 122 libraries) PMB - France OPALS – school libraries OLE – doesn’t exist yet
Developed in 16 weeks. Launched launched 1/1/2000 (Y2K) – special library First us library in 2005 Ohio, USA-- Nelsonville Public Library 2002 first public library in the U.S. to adopt the open-source ILS • 7 Branches • 350,000 items • 620,000 circulation, annually • 40,000 borrowers Of 1000 libraries internationally, only 312 are in the US Primary market: Small International School Special But….more and more publics Liblime (2005) made a big impact in the U.S. 285 with Liblime support (170 publics) 2 with ByWater support (both academic) 2 with PTFS support (1 public) 23 independent (9 publics) – DIY Two User Groups French has been active for quite some time KUDOS is just getting started Website just launched: kudos.koha.org Developers Well developed network of international contributors (committers) – 80ish Core development team is “elected” by community for each new release
102 libraries (94 publics) All consortia members except 8: SC - Calhoun County, Dorchester County, Fairfield County, , York County French Link (IN) Kent County (MD) Killeen City (TX) Marshall Public (MO) Designed for 270-member LENDING CONSORTIUM whose MEMBERS COLLABORATE but have DIFFERENT POLICIES Developed over two years (2005-2007) Evergreen designed to 1. handle LARGE INDEXING AND TRANSACTION LOADS 2. HIGHLY CONFIGURABLE POLICIES for each member Three state-wide project selected Evergreen: Georgia PINES, Michigan Evergreen, Evergreen Indiana Consortia: SITKA (BC) Conifer (Ontario) Natural Resources Canada 7 individual libraries Coming: NELINET (New England) North Texas Regional Library System (NTRLS) South Carolina State Library (SC LENDS) Mahatma Education Society (India) King County Library System? SC LENDS: “ By using open source, SC LENDS libraries estimate that they will save more than $200,000 a year in software licensing costs. “ Will launch new service: South Carolina Library Evergreen Network Delivery System The initial pilot group of 11 libraries, which includes South Carolina State Library, provides direct service to 1.3 million people in 10 counties and has 2.5 million books and serial volumes (FY2006 data). When the pilot group finishes migrating in the fall of 2009, SC LENDS will then be the second-largest Evergreen consortium. More libraries will come on board in 2010 and beyond.
Small library choosing Evergreen: William Jessup serves 500 students Large libraries choosing Koha: Howard County: Volumes: 998,613 Annual circ: 4,787,081 Consortia choosing Koha SEK-n-Find (Southeast Kansas Library Consortium) Large and Consortia: South Central Library System (WI): Volumes: 3,041,649 Annual circ: 11,262,790
Define some terms: Commonly used: FOSS = Free Open Source Software Means: Freely downloadable Source code can be viewed and modified and redistributed But there is more…. [And licensed]
Open Source software is licensed software: Both share: free, can modify and redistribute BUT Key difference in “how” you can use it: GPL states “derived works must be available under same license” while BSD license need only “acknowledges the authors”
Some say BSD is “more free” because there are no restrictions for how it is used…. With the GPL license applies to both Koha and Evergreen neither the product nor derivation will get rolled into a proprietary, commercial product So, yes it is “less free” in the sense that it limits exactly “how someone can build upon it” but….
The GPL license ensures that everything that goes into Evergreen and Koha will remain Free and Open Source All improvement will benefit libraries who will always have Free access to this software Term for this…..[Copyright vs. copyleft]
Copyright: allows author to prohibit others from reproducing, adapting, or distributing copies of the author's work Copyleft: every person who receives a copy of a work permission to reproduce, adapt or distribute the work as long as any resulting copies or adaptations are also bound by the same copyleft licensing scheme. e.g. GNU General Public License, Creative Commons ShareAlike license Evergreen and Koha use copyleft (not copyright) to ensure the freedoms are preserved, even when the work is changed or added to.
Besides the differences between licensing… Intellectual property copyright versus OS copyleft licensing Other important differences between ILS and OSLS Costs….
To say the least…. There is no doubt, that you will save money on licensing by choosing OSLS because there is NO Cost for this….
Software maintenance…same thing Updates area freely available (and frequent)
With current ILS – ILS vendor and support provider go hand-in-hand Innovative supports Millennium SirsiDynix support Unicorn, Horizon and Symphony TLC supports Carl Example: start with Liblime, switch to ByWater, then move to even cheaper support option provided by local consortia! Start out needing lots of support Maybe need migration assistance for some libraries Then develop in house expertise so need less help Then local consortia takes on roll of providing first level support to all members… [consortia doing this today]
Currently four companies that can offer support for Koha and Liblime…. These companies can provide more than support….. Offer today: OSLS support Hosting Migration Some training Could also contract with them to provide service level guarantees if necessary They could also do security audits of the software – not “their” software so it would still be a 3p audit
Support means first level support. Who you call. Additional support is provided by community and/or commercial provider. Another model is the State agency providing the first level of support…..
State Library can provide support. And you may not even need a support contract…..
Evergreen: at least one library William Jessup University Koha: 75 libraries (22 publics) don’t have support contracts including Viborg SD: pop. 832 Hopewell NJ: pop. 2000 Castleton VT: pop. 4372 All small and rather “off the grid” so there could be lots more…
Here’s something we’ve never been able to do before…. To me, more exciting than the savings in costs we get from NOT having to pay for the licesning and maintenance costs… We can develop our own software so that it works how we want it to work. What is (is not) development…..
With an ILS, you may be able to ‘customize” Make minor tweaks Choose configuration settings Why this isn’t “development”: Usually limited as to what can and cannot be done The “vendor” holds all the cards. You hold the checkbook. What is “development” then?
You are in charge of how the software is going to work Why does this matter? ….
Ever had a service that you wanted to offer but couldn’t? Ever had to develop some strange procedures into order to enforce policies that didn’t really fit with tho how the software worked? Ever paid to have something customized by the vendor? Took too long Came out bizarre? I hear you saying….but we don’t have a developer!......
Contract with your support vendor for development Hire a programmer to make the changes you need for your workflow Partner with a group of libraries to fund development of a needed module Contribute to development work in progress to expedite release schedule Integrate an existing 3P software product with the OSLS Koha v. 3.2 Release Manager Galen Charlton <gmc@liblime DOT com> from LibLime Release Maintainer To be determined upon release Quality Assurance Manager Position Open - email koha-devel if you'd like to be considered Documentation Manager Nicole C. Engard <nce@liblime DOT com> from LibLime Interface Design Manager Owen Leonard <zivot@zivotdesign.com> from Zivot Design and Nelsonville PL Translation Manager Chris Cormack <chris@bigballofwax.co.nz> from Catalyst
Other ways it should be happening…. Remember about those cost savings with licensing and software maintenance?...
Development is a really good place to reinvest those savings…. [Review each scenario above] This is why I am reluctant to say “an OSLS will save you money” Yes it could But maybe it should just create an opportunity to do better things with that money
Horizon consortia in CT 48 public libraries, 20 k-12 schools Installed Koha CONFIGURE Pilot tested at three libraries Identified development requirements Got quote from Liblime ($1.2 million) to things needed on Day One Installed Evergreen CONFIGURE MUCH closer to ready for Day One Created OS ILS team (software coordinator, OS implementation coordinator) (dumped Network Specialist position) Partnering with Equinox, PTFS, ByWaters and KCLS for support and development
And more importantly [twins separated at birth]
Lots of promise with Open Source. Works for some now but not for others. Full promise can only be realized if we all get involved. PROS / CONS exercise
Don’t issue the same old same old RFP RFPs get you what you’ve always gotten: Proprietary ILS Consider: RFP for services only Write the RFP for what you really need Eliminate the RFP entirely
Install Koha Install Evergreen Try them out for yourself. Bibliomation: defines functional requirements, define what is needed on day one, see what’s missing in each product, find out what it would cost to develop missing pieces. Talk to other libraries looking at similar options
![Free is Just the Tip of the Iceberg: Open Source Library System Software Lori Bowen Ayre [email_address] METRO Webinar October 6, 2009](https://image.slidesharecdn.com/ayreoslsfreetipiceberg-091023122916-phpapp02/85/Open-Source-Library-System-Software-Free-is-Just-the-Tip-of-the-Iceberg-1-320.jpg)
