1. A new open source library services platform
Richard Levy
VP, SaaS Innovation
EBSCO

2. The Quest for interoperbility and integration
Search & Discovery
e.g. Blacklight, VUFind, Encore, Enterprise, Koha, ElasticSearch
LMS/ILS
e.g. Millennium, Symphony, Aleph
ERM
e.g. eRM essentials, 360 resource manager, Coral
Library Services Platform
('Next generation') Unified library resource management system A next generation of (cloud based) 'unified resource management' (URM) systems is available that combine the functions of the 'conventional' library management systems (LMS/ILS) and the electronic resource management (ERM) systems. They are most commonly being called 'Library Services Platforms' Search & Discovery
The search and discovery function for library users is increasingly being delivered via 'Discovery (vertical search) Services' which are separate from the underlying library resource management system (LMS/ILS). The conventional (OPAC) way to access library catalogues has not kept pace with user expectations. These discovery services provide a unifiedsearch and discovery approach across different types of library material. Unlike 'metasearch' these services are based on a single unified index (like Google) derived by 'harvesting' metadata from content providers( e.g. publishers) and intermediaries (e.g. ebook services) and the library's local systems such as the LMS/ILS and Institutional Repository (IR) etc. In this way the user gets a single approach to search across electronic (typically e-journal) and print resources. Electronic Resource Management
ERM systems evolved to 'fill the gap' left by conventional library management systems (LMS or ILS) in the management of electronic resources Library Management System (LMS) [Integrated Library System (ILS) in US parlance]
A library management system (LMS), also known as an integrated library system (ILS), can be considered as an enterprise resource planning (ERP) system for a library. It forms a suite of integrated functions to manage a diverse range of functions within a library. They are predominately focused on the management of print resources and so libraries employ separate systems (spreadsheets or and ERM system) to manage e-resources. A new generation of Library Services Platforms is replacing the LMS/ILS

3. CONSOLIDATION In library automation Fewer ILS Options
Vendor Consolidation
Fewer ILS Options
Monolithic Systems
What has happened in the ILS space: If in your library you were doing an RFP 10 years ago, you might have choices from 10 different systems. 5 years ago there may have been 5 systems. Today, there may only be 2.5 choices. The market is shrinking, big companies are getting bigger. The reduction in choice impacts the services and products we can buy. Once you buy an ILS, you also have less choice within the platform. This effects how libraries make decisions regarding automation.

4. Interoperability, Decoupling“
…tight coupling that precludes integrating discovery and resource management products from separate vendors eliminates choice.”
By Marshall Breeding The Future of Library Resource Discovery A white paper commissioned by the NISO Discovery to Delivery (D2D) Topic Committee

5. Why FOLIO?
Most library systems are top down, prefabricated and designed to lock the library in to a single monolithic system
There is little to no input from libraries in terms of architecture, purpose, function and development
A community catalogue in the Cloud run by one provider is still a fortress
Discovery and Management systems evolved separately and should be evaluated accordingly on their own distinct merits and benefit to user experience
Staff workflows should be built flexibly around serving the user better: not a one size fits all approach
What would happen if library and tech communities collaborated together to build the system of the future?
EBSCO is not an iLS company, however we are interested in a healthy library systems market
-All EBSCO systems interoperate with an ILS / LSP
-Health of our company is threatened by ILS market consolidation
We decoded to support FOLIO financially, and with staff involvement in order to
Improve choice for libraries around the world, includiing for EBSCO products and services
Support innovation I

6. LSP / Next Gen ILS Market
Closed systems
Limited APIs
Discovery + ILS
The current generation of systems do an OK job of connecting to things that we all know about and agree upon. For example, connecting to Gobi and YBP – because that’s an important resource for any library. Same say with a self-check system. You have a 3M system, most automation companies can manage that. The problem becomes: what happens when you have a new, a local, or an emerging requirement? Something new or something unique for your library – that’s when the problem arises. It’s something that wasn’t considered when the system was developed. Now you need to somehow get the new requirement into the dresser drawer. How, for example, if you have a mix of public and academic libraries do you get functionality geared for a public library? The answer is – you probably don’t or it becomes very difficult. That’s where you get wedged-in by the current closed system model.
Bundled packaging
Platform Limitations

7. How do we drive innovation for new and emerging services?
LSP Market
How do we drive innovation for new and emerging services?
The current generation of systems do an OK job of connecting to things that we all know about and agree upon. For example, connecting to Gobi and YBP – because that’s an important resource for any library. Same say with a self-check system. You have a 3M system, most automation companies can manage that. The problem becomes: what happens when you have a new, a local, or an emerging requirement? Something new or something unique for your library – that’s when the problem arises. It’s something that wasn’t considered when the system was developed. Now you need to somehow get the new requirement into the dresser drawer. How, for example, if you have a mix of public and academic libraries do you get functionality geared for a public library? The answer is – you probably don’t or it becomes very difficult. That’s where you get wedged-in by the current closed system model.

8. Community
Open Source
Modern
Modular
Supported
Now, what is the next step? How do we move forward? So the next step for us is a collaboration, of which EBSCO is part. This will be an open source library services platform – that’s the goal. And the collaboration that is coming together is here to solve some of the issues that we see in the marketplace.
First, it will be open source, and you need to understand the licensing, as that will underscore the motivation of the parties involved. We are committed to this being truly open source platform using the Apache 2 license – which is the most open and permissive license available. Large commercial ILS suppliers can use this for their own software and build application around it.
It will be community driven. A group of peers that provide input, direction and resources. EBSCO is not an ILS vendors. Who are those peers? OLE – a group of around 12 libraries who are members of the collaboration. They will bring vision and requirements to the collaboration. Second group – other libraries who are not OLE members. There is a development organization, Index Data, who has been developing for some time. Based in Copenhagen and the US, experienced in open source software. EBSCO is funding the work that Index Data is doing. Also, other automation organizations. We mentioned our ILS partners – we have communicated this plan to those partners. If you are a commercial vendor, you may say “this sounds scary”. We however do not want to steal business, we want to help vendors as they move forward with the development of their system. Many smaller ILS vendors in particular will be able to use the platform as the basis for their next generation offering.
Modern means – all resources from the ground up both e and p, and it will use a central knowledge base to help drive linking and data requirements. Modern in structure and architecture. And supporting linked open data – not just to publish to the discovery layer, but to manage at the platform layer.
Modular. We do not mean modules as we see it today. We see a future where there is a marketplace of modules – and let’s consider them apps that allow libraries to choose what works best for their system. What this means that libraries can say – I want this app from this vendor, that app from another vendor.
And fully supported. EBSCO will provide support. Our research showed that someone has to provide support – and we want this to be a competitive marketplace so libraries can choose from different providers (remember – risk mitigation).
FOLIO an open source LSP built to support ILS functions and to encourage community innovation

9. Modular Apps built on an open, extensible platform
Cat
ERM
Circ
Rpt
Acq
ILL
Circ 2
Rpt 2
New App
Adm
App 1
“Radical Modularity”
App marketplace
Customized solutions by library
Microservices architecture
Why can’t the LSP be more like our phones – flexible and customizable? The phone comes with certain apps bundled in – if you have an iPhone you get Apple Maps for instance. But if you prefer the user interface and functionality of Google maps, you can download the app and your phone (read: platform) automatically recognizes Google maps and it interoperates with other apps on your phone.
Also – if you want functionality that doesn’t exist as a standard app on your phone – you can find it in the App store, download it (either for free or for a fee) and use it on your platform.
Modular Apps
built on an open, extensible platform

10. FOLIO Marketplace – a world of Apps

11. PHASE 1 [ Open Source Tools to Run the Library ]
Core ILS Functions
Resource Management (e+p)
Acquisitions
Cataloging
Circulation
Discovery Integration
Integrated Knowledgebase(s)
User – Rights Management
APIs throughout to connect to important services

12. PHASE 2 [ Extending Library Value to New Areas ]
Extensible and Interoperable Apps
Content Management Systems
Data Mining
Grant Management
Institutional Repositories
Learning Management Systems
Linked Data
Research Data
Predictive Analytics

13. The Code is Out There

14. FOLIO TIMELINE PHASE 1 PHASE 2 NOW 2015: FOLIO planning begins
Extended Apps / LMS
NOW
FOLIO
Announcement
Open Library Foundation
Announced
FOLIO Pre-work idea phases, early partners
Availability of FOLIO Apps to Run Library (ILS)
Platform and initial exemplar app
Open
Repositories
SIGs
Form
2015
June
2016
Aug
2016
Sept
2016
Oct/Nov
2016
2018
Regular code releases
Library Technology Reaching New Heights
PHASE 1
PHASE 2
2015: FOLIO planning begins

15. FOLIO is a COMMUNITY focused on innovation: -Academic libraries, -OLE Partners, -Index Data, -EBSCO & others

16. FOLIO: The Engaged Community is Growing

17. FOLIO: The Engaged Community is Growing

18. Join the FOLIO community @ FOLIO.org

19. FOLIO Community Growth
+ Budapest

20. JOIN THE COMMUNITY!

21.
Get involved!

22. PARTICIPATE IN COMMUNITY DISCUSSIONS

24. Thank You ! \