1. OPEN SOFTWARE FOR LIBRARIES: Current Trends and Issues Marshall Breeding Director for Innovative Technology and Research Vanderbilt University Library Founder and Publisher, Library Technology Guides http://www.librarytechnology.org/ http://twitter.com/mbreeding 29 March, 2011 Modelos de negocio y de gestión de contenidos con software libre

2. Abstract Libraries have a natural affinity with open source software, and many have implemented it for their strategic automation infrastructure, including ILS and discovery systems. In his analysis of the library automation industry, Breeding tracks the pace of adoption of open source library automation. Come hear his perspectives on the current and emerging trends of open source in the industry relative to proprietary products and how it fares relative to broader trends such as comprehensive resource management, cloud computing, and new-generation discovery.

3. Context: Basic library automation trends  Transition away from legacy Integrated Library System model  Transition into new genre of Library Services Platforms  Large-scale consolidation of automation: regional, state-wide, national  Converged workflows: Print, electronic, digital  Increased reliance on cloud technologies: multi-tenant software-as-a-service  Enterprise-level infrastructure  Platform of open APIs for customized functionality and interoperability

4. What are the trends in the adoption of Open Source library management software by libraries Adoption Patterns by Libraries

5. Recent ILS Industry Contracts CompanyProduct200920102011 OCLCWorldShare Management Services184 Innovative InterfacesSierra 206 Ex LibrisAlma824 SirsiDynixSymphony -126122 Innovative Interfaces, Inc.Millennium453932 The Library CorporationLibrary.Solution304348 Ex LibrisAleph473925 VTLS Inc.Virtua182213 Polaris Library SystemsPolaris ILS332353 BiblionixApollo558779 ByWater SolutionsKoha74454 PTFS LibLimeLibLime Academic Koha 7 PTFS LibLimeLibLime Koha 4427 Equinox SoftwareEvergreen181521 Equinox SoftwareKoha 6

6. ILS Turnover Report

7. ILS Turnover Report -- Reverse

8. Does open source result in higher or lower satisfaction by libraries that have adopted it for library management systems? Perceptions of Open Source

9. Perceptions Survey – Open Source Interest

10. Perceptions Survey – Perceived functionality

11. Perceptions Survey – ILS Satisfaction

12. Business Models

13. US: Commercial involvement dominates  Almost all installations of open source ILS products in the United States involve contracts with commercial companies  Mostly hosted by the commercial support company  A very small minority of independent installations  Consortial arrangement:  Consortial office provides support to libraries  Commercial firm provides support to consortial office

14. International scenarios  Internationally support is often provided though government agencies or non-governmental organizations  Need for translations and to implement local functionality  CONABIP: Developing Koha for Bibliotecas Populares en Argentina  National Library of Philippines: provides Koha for all public libraries  EIFL: Pilot implementations of Koha and Evergreen in developing nations  Spain : Koha – Kobli for governmental libraries  Bireme / UNESCO: development of ABCD as an open source LMS based on CDS/ISIS technologies

15. The business of open source  Many Commercial companies with interest in open source library automation products  Revenue sources  Conversion of data from incumbent system  Installation / configuration  Training  Support / Help desk  Hosting  Sponsored Development

16. Proprietary software business model  Software License Fee  Conversion, Installation, training  Annual maintenance for upgrades, service, support (~15 percent)  Hosting (optional)

17. Business realities  Same cost exist elements for any major software development projects  Software engineers to develop business application  Quality assurance  Administration / Govenance  Data Migration  Implementation  Hosting infrastructure  Service and support

18. Revenue sources  Open source software based entirely on services or contributed effort  Proprietary software revenues derived from Licensing plus modest (15%) maintenance and service fees  Both Open source and Proprietary software moving toward subscriptions-based SaaS

19. Open Source Governance  Some entity needs to manage the overall project – Otherwise Chaos ensues  Ownership of intellectual property (trademarks, copyrights, patents)  Provide legal and administrative support  Strategic leadership: trajectory of development  Represent key stakeholders: developers, institutional implementers, end-users  Provide tools for development, codebase management, distribution  Manage personnel resources  Enforce and manage quality control  Examples: Apache Software Foundation, Kuali Foundation,

20. Software as a service (multi-tenant)  Open source or proprietary  All-inclusive subscription fee  Hosting  Maintenance (always up-to-date)  Support  Annual fee scaled to the size and complexity of library

21. Development Resources CompanyDevSupSalesAdminOtherTotal Ex Libris170231544413512 Follett Software Company8714386490365 Innovative Interfaces, Inc.8315843243311 SirsiDynix Corporation84166512356380 Serials Solutions805046457237 Axiell5766343534226 The Library Corporation3991281328199 Polaris Library Systems2742152 86 VTLS Inc.244812818110 Koha ByWater Solutions31233113 Catalyst IT3 BibLibre43 Koha Total (estimated)15 PTFS51688 155 Evergreen Equinox Software6523521

22. Models of Openness

23. Programming levels  Systems software development: professional software engineer using languages such as C++, Microsoft.Net, Java, JEEE  Systems integration and extension: mid-level programmers with knowledge of scripting languages such as PHP, Ruby, Perl, Python  Works with application programming interfaces (APIs) to create new functionality or manipulate date from an existing business system

24. Closed Systems Circulation Acquisitions Cataloging Staff Interfaces: End User Interfaces: Data Stores: Functional modules: No programmable Access to the system. Captive to the user Interfaces supplied by the developer Programmer access:

25. Standard RDBM Systems Circulation Acquisitions Cataloging Staff Interfaces: End User Interfaces: Data Stores: Functional modules: Database administrators can access data stores involved with the system: Read-only? Read/write? Developer shares database schema Programmer access:

26. Open Source Model Circulation Acquisitions Cataloging Staff Interfaces: End User Interfaces: Data Stores: Functional modules: All aspects of the system available to inspection and modification. Programmer access: Database Administrator or SQL Programmer Software Engineer

27. Open API Model Circulation Acquisitions Cataloging Staff Interfaces: End User Interfaces: Data Stores: Functional modules: Core application closed. Third party developers code against the published APIs or RDBMS tables. Programmer access : Published APIs Programmer / Integrator

28. Open Source / Open API Model Circulation Acquisitions Cataloging Staff Interfaces: End User Interfaces: Data Stores : Functional modules : Core application open. Third party developers code against the published APIs or RDBMS tables. Published APIs Programmer access: DBA Software Engineer Integrator

29. Application API exposed to External Applications Core Functionality / Business Logic Application Programming Interfaces Public Interface Staff Interface Reports Module Delivered Interfaces use proprietary programming Core Software Data stores RDMS API External applications

30. Legacy ILS Model + protocol Circulation BIB Staff Interfaces: Holding / Items Circ Transact UserVendorPolicies $$$ Funds CatalogingAcquisitionsSerialsOnline Catalog Public Interfaces: Application Programming Interfaces Protocols: SIP2 NCIP Z39.50 OAI-PMH Self-Check Interlibrary Loan System Interlibrary Loan System

31. Legacy ILS Model / External API Circulation BIB Staff Interfaces: Holding / Items Circ Transact UserVendorPolicies $$$ Funds CatalogingAcquisitionsSerialsOnline Catalog Public Interfaces: Application Programming Interfaces / Web Services Protocols: SIP2 NCIP Z39.50 OAI-PMH External Systems & Services Flexible Interoperability

32. Consolidated index Search Engine Unified Presentation Layer Search: Digital Coll ProQuest EBSCO … JSTOR Other Resources New Library Management Model ` API Layer Library Services Platform Learning Management Enterprise Resource Planning Stock Management Self-Check / Automated Return Authentication Service Smart Cad / Payment systems Discovery Service

33. Open source version of legacy models? or New opportunities to support modern libraries? Is Open Source ILS transformative

34. Opening up Library Systems through Web Services and SOA: Hype or Reality? This report aims to assess the current slate of major library automation systems in regard to their ability to provide openness through APIs, Web services, and the adoption of SOA. Library Technology Reports Nov/Dec Issue 2009 by Marshall Breeding

35. Opening up Library Systems through Web Services and SOA: Hype or Reality? “We also note that the two open source systems lag behind proprietary systems in terms of customer-facing APIs that result in tangible activities which extend functionality or enable interoperability.” Library Technology Reports Nov/Dec Issue 2009 by Marshall Breeding

36. Opening up Library Systems through Web Services and SOA: Hype or Reality? “The APIs available to library programmers continue to be quirky and less than comprehensive, even from the vendors with the strongest offerings in this area.” Library Technology Reports Nov/Dec Issue 2009 by Marshall Breeding

37. Open Systems  Achieving openness has risen as the key driver behind library technology strategies  Libraries need to do more with their data  Ability to improve customer experience and operational efficiencies  Demand for Interoperability  Open source – full access to internal program of the application  Open API’s – expose programmatic interfaces to data and functionality

38. Library Services Platform  Possible new term for the successor to the ILS  ILS now viewed as print-centric  Next Generation systems must serve as platforms to connect external systems as well as to deliver internal functionality  Delivered Functionality + library created extensions + interoperability

39. Current Open Source ILS Products

40. Competing Models of Library Automation  Traditional Proprietary Commercial ILS (print centric)  Millennium, Symphony, Polaris  Traditional Open Source ILS (print centric)  Evergreen, Koha  Hybrid Approach  Sierra Services Platform (Innovative Interfaces)  Library Services Platforms  Ex Libris Alma, Serials Solutions Alma, Kuali OLE, OCLC WorldShare Management Services

41. Koha  Originally developed in 1999 for small group of libraries in New Zealand, Horowhenua Library Trust by Katipo Communications, production use by Jan 2000  Gained widespread use in the United States around 2004-05 and has seen steady growth in use  Wide international adoption  Used in many thousands of libraries. 1,573 represented in lib-web-cats, with many large groups not yet registered.

42. Companies involved with Koha  ByWater Solutions. Provides hosting and support services for libraries in the United States  PTFS – LibLime. Provides development, hosting, and support for “LibLime Academic Koha” and “LibLime Koha”  PTFS Europe. Service, hosting and support for Koha in the United Kingdom and parts of Europe.  BibLibre. Provides development, hosting and support primarily to libraries in France  Catalist IT: provides development, hosting and support for libraries in Australia an New Zealand  Libéo: Service and suppor for Koha to libraries in Canada  Equinox Software, Inc. Provides development, support, and hosting for Koha to libraries in the United States. Most of the company’s business is based on Evergreen.  Orex. Service and support for Koha in Spain  Organizadatos: Service and support for Koha in Columbia and other parts of Latin America  Librotech: Based in Norway to promote and provide service and support for Koha in Scandinavia.  Katipo Communications. Service and support for Koha in New Zealand. Previously sold its interests in Koha to LibLime, but has since reinstated its involvement.

43. National Projects to deploy Koha  Philippines: A systematic effort to install Koha in the public libraries sponsored by the state libraries  Spain: Koha-Kobli  (Koha Biblioteca)  http://kobli.bage.es/  Argentina. CONABIP (Comisión Nacional de Bibliotecas Populares)  Customized version of Koha: DigiBepe  http://www.conabip.gob.ar/faq/digibepe

44. Koha Worldwide

45. Evergreen  Originally developed by the Georgia Public Library System for the PINES consortium of public libraries in Georgia  PINES includes most of the small and mid-sized public libraries in Georgia, but not the largest urban areas (Atlanta, Cobb County, etc)  Equinox Software, Inc. launched as a separate company in Feb 2007, including most of the team that originally created Evergreen within GPLS.  Evergreen now used in over 1,000 libraries, primarily in the United States and Canada. Some recent international deployments

46. Evergreen Worldwide

47. Kuali OLE  Mellon funded project to create new enterprise level automation platform for research libraries  1-year planning project led by Duke University  Manage resources of all formats  More than an ILS / Less than an ILS  Community Source / Open Source

48. OLE Project: Phase I  Planning and Design Phase  Develop Vision + Blueprint  Work with consultants with expertise in SOA and BPM  Instill community ownership of OLE  Recruit partners for Phase II

49. Kuali OLE Project: Phase II  2-year build project led by Indiana University  $2.38 million from Mellon matched by capital and in-kind contributions by development partners  Community source reference implementation  Create software based on OLE blueprint from current project  Early software in 18-24 months  High level of investment and commitment to implementation

50. Comparative Issues:  Koha: (ILS)  Used in a wide range of library sizes and types  Very broad international deployment with translations into many languages  Many support companies in various countries and regions  Evergreen (ILS)  Created initially for library consortia, and has since followed that pattern. Very few instances for single libraries  Concentrated in US, Canada, initial deployments in Europe  Perceived as more complex to implement than Koha  Kuali OLE: (LSP)  Enterprise-level software for academic and research libraries  No libraries yet in production

51. Questions and discussion