FOLIO: The Future of Library Is Open: Satbir Chauhan, K. Kandhasamy and N. Sakthivel
FOLIO: The Future of Library Is Open: Satbir Chauhan, K. Kandhasamy and N. Sakthivel
FOLIO: The Future of Library Is Open: Satbir Chauhan, K. Kandhasamy and N. Sakthivel
satbir.chauhan@outlook.com
2
Doctoral Researcher, Department of Library and Information Science, Faculty of Art, University of Delhi,
New Delhi – 110007, Delhi, India; Kandhasamy5050@gmail.com
3
Library Assistant, Jio Institute, Navi Mumbai – 410206, Maharashtra, India;
n.sakthivel@jioinstitute.edu.in
Abstract
Ranganathan's 5th law of library science says that libraries never become stagnant. While financial constraints are
a common challenge for libraries, user expectations are continuously growing. To meet and exceed user expectations,
libraries must embrace new technologies and software solutions. Open-source options have proven to be particularly
beneficial for nonprofit organizations like libraries. Looking to the future, as libraries continue their digital transformation,
many library automation software, especially traditional library management systems (ILS), are becoming outdated. In
response to the diverse requirements of libraries, the architecture of Library Services Platforms (LSP) offers enhanced
flexibility and functionality within a unified platform. Among the various LSPs that have emerged over the past seven years,
FOLIO has demonstrated rapid development and progress. Upon exploration, it becomes evident that FOLIO's developers
have prioritized a micro-services architecture, emphasizing apps over modules. This approach provides a comprehensive
multitasking app environment, a user-friendly Dashboard for quick access, efficient data management, and much more.
The user-friendly nature of FOLIO sets it apart from traditional Integrated Library Systems (ILS), which may lack such ease
of use. Despite its abundant features, FOLIO is still relatively under-recognized in India. This paper aims to discuss the
distinctive features of FOLIO, it’s potential as a comprehensive solution for libraries, and whether it can effectively replace
traditional ILS systems.
Keywords: Future of Librariesi Is Open (FOLIO), Future of Libraries is Open (FOLIO), Integrated Library System (ILS),
Library Services Platform (LSP), Open-Source Software (OSS)
Products; Extensive Metadata Management; Exposed between the architecture of both is given in Figures 2
APIs for Interoperability and Extensibility; and Polyglot and 3.
programming i.e. coding in multiple languages (Breeding,
2015; Grant, 2012; Pradhan, 2019).
5. FOLIO
FOLIO LSP has its roots in the Open Library Environment
4. Monolithic vs Micro-services
(OLE) project, which was initiated in 2008. In 2016, “The
Traditionally, ILS is developed using a monolithic Open Library Foundation” was established to increase
architecture, where the programme is created as a single the sustainability of libraries. The foundation initiated
entity with a single codebase that houses all the capabilities an open-source project for and by libraries. Due to
and components. A contemporary strategy known as that, in 2016, the foundation (in association with Index
“micro-service architecture” separates the application Data, EBSCO, and Open Library Environment (OLE))
into smaller, independent services that communicate with collaboratively developed the Future Of Libraries Is Open
one another using simple protocols. The way application (FOLIO), an open-source micro-services framework-
is organized and deployed is the primary distinction based LSP to create a new way of catering library services
between monolithic and micro-service architecture. with the open-source software. With FOLIO, libraries can
The LSP follows the micro-services architecture access a modern and flexible system that is constantly
approach. Graphic illustration of the basic difference evolving to meet their needs. It ensures maximum
community participation, adoption, and contribution; It
is modern Cloud-based, multi-tenant, services-oriented,
Powerful to manage the full spectrum library workflows,
and flexible to configure in many ways, anyone can
build on or extend. (Index Data, 2023). FOLIO helps
to manage all types of libraries and libraries of various
sizes. Currently, the FOLIO platform and its ERM are
growing progressively, and many libraries are starting to
implement it. Globally, there are more than 100 institutes
that implement the FOLIO LSP. For example, Stanford
University, Texas A&M University, Duke University,
Lehigh University, University of Chicago, University of
Figure 2. Monolithic architecture. Colorado, and Jio Institute in India. Library of Congress,
National Libraries of Australia are planning to implement modules. Stripes handle typical duties like data gathering,
(Enis, 2022). The first version of FOLIO was Aster released routing, authentication, and localization. The developers
in January 2019; the upcoming version of FOLIO is Poppy and designers can take advantage of the following
and will be released in 2023. resources available on the FOLIO UX website to create
FOLIO apps with MOTIF:
5.1 FOLIO Architecture - UX prototypes: Contains interactive mock-ups
which demonstrate the look and feel of FOLIO apps
Folio features a modular architecture that enables many
- UX guidelines: Documentation regarding FOLIO
parts to interoperate and communicate via a shared
design components
framework. The core of FOLIO is the Okapi gateway
- UX assets: This includes fonts, colors, and icons and
(Figure 4), which makes it possible to integrate with
these are downloadable.
loosely coupled apps (micro-services) and functional
- FOLIO library: Consisting of all the components
cohesion that offer a variety of features, including
used to design apps
analytics, circulation, acquisitions, and inventories
(Murray, 2023).
5.2.2 API Support
5.2 Features of FOLIO FOLIO’s API (Application Programming Interface),
which facilitates interoperability and interaction
The essential features of FOLIO LSP are discussed here
with other systems and services, is one of its primary
under six major heads.
characteristics. The FOLIO API is based on REST
(REpresentational State Transfer) principles, which
5.2.1 User Interface/ User Experience (UI/UX)
means that it communicates with the FOLIO server using
One of the pivotal elements of FOLIO is its User Interface common HTTP methods like GET, POST, PUT, and
(UI) design. FOLIO has set some guidelines to promote DELETE. To share data, it uses JSON (JavaScript Object
an aligned vision for developers, consistency, and ease of Notation).
use across all apps. FOLIO does have its design system The Okapi, an API-Gateway is used by FOLIO to
called MOTIF. The MOTIF outlines FOLIO apps’ visual manage several modules that include acquisitions,
style, patterns, components, and interactions. MOTIF circulation, users, analytics, and other aspects of library
is implemented using Stripes, a front-end framework management. Okapi divides web service endpoints into
explicitly developed for FOLIO. The Stripes make it two categories: (1) APIs for general module and tenant
possible that one can create FOLIO apps with very minimal management; so-called “core”, and (2) endpoints for
coding. It provides a set of reusable UI components and interacting with business-logic-specific interfaces given by
1) Create a folder – Open it – Right Click – Open 4. It is far ahead of the current generation of ILSs,
Terminal – Paste these commands in order: particularly in managing e-resources.
vagrant init --minimal folio/release-core
2) Create a file named VagrantFile in same folder and
add below code:
7. Limitations
Vagrant.configure(“2”) do |config| 1. The major limitations of FOLIO in its present
config.vm.box = “folio/snapshot” form are (as observed) -
config.vm.provider “virtualbox” do |vb| 2. The involvement of commercial vendors could
vb.memory = 24576 disturb FOLIO’s open-source status in future;
vb.cpus = 2 3. Production-level implementation of FOLIO
end is quite difficult and requires sound technical
end understanding;
vagrant up 4. Many libraries may not be able to meet the
vagrant ssh minimum requirements to implement FOLIO; The
3) In your browser, hit localhost:3000 (initial basic Hardware/IT infrastructure requirements
credentials: diku_admin/admin) are:
Based on the hands-on experience of this LSP it • High resource requirements (Single server
appears that the microservices architecture or called apps with containers)
(in FOLIO) is an enhanced version of modules from ILS • Min 24 GB of RAM (40 GB RAM is
that is more efficient and easier to use. The User Interface proffered)
is quite simple and impressive; Dashboard has the option • 350 GB SSD
of full customization and management for quick access • 8-core CPU
or widgets, Integrated ERM system reduces dependency 5. It does not offer much scope for localization; Also,
on other software. The multitasking app environment there is little support for regional languages or
increases its ease of access. The courses app allows one local variations.
to create and manage course reserves. It has open-source
project support for reporting called LDP (Library Data
Platform), acting as a relational database and can create 8. Conclusion
custom tables to import non-FOLIO data. In terms of manpower, financial resources, and machine/
material resources, open-source software provides the best
6. Findings solution for libraries facing budget constraints. Libraries
typically employ different software for various services.
The obvious advantages of an open-source LSP over an For repositories, options include DSpace and Eprints; for
open-source ILS are - Library Management Systems (LMS), there are choices
1. The LSPs like FOLIO offer a variety of software like Koha and Libsys; and for discovery services, libraries
on one platform with choice-oriented services. may utilize EDS or VuFind. As libraries expand and offer
By using this software, the library won’t have more services, the number of software products they need
to manage/maintain several software or may also increase. However, maintaining a large number
subscriptions; of software applications can be challenging and requires
2. The technology and architecture behind such expertise. This is where Library Service Platforms (LSPs)
software make it a futuristic product; like FOLIO come into play. FOLIO offers flexibility,
3. So far deployments of FOLIO are less in number features, functionality, and sustainability, shaping the
across the globe, but history tells us that it future of libraries to be open. While the current Integrated
happens with each piece of new technology. The Library System (ILS) attempts to add multiple modules
library community must start acknowledging like Electronic Resource Management (ERM) to address
such technologies to remain compatible with the the situation, in a real-time environment, it may struggle
changing world; and to sustain the same infrastructure and architecture as
FOLIO. Presently, FOLIO does not include an Online Mukhopadhayay, P. (2002). Progress of library man-
Public Access Catalog (OPAC), but this issue will be agement software: An Indian scenario. Vidyasagar
resolved by incorporating the Searchwork open-source University Journal of Library and Information Science,
OPAC developed by Stanford University. Additionally, 1-15. Available at: https://core.ac.uk/download/
the application of artificial intelligence in early library pdf/333967026.pdf
experiences is an ongoing discussion in both FOLIO and Murray, P. (2023). Welcome to the folio wiki. The Open
other emerging LSPs, indicating its potential to become Library Foundation: FOLIO project. Available at: https://
the primary software for all types of libraries due to the wiki.folio.org/
growing trust within the library community. Okapi-FOLIO community (2023). Okapi guide and refer-
ence. Available at: https://github.com/folio-org/okapi/
blob/master/doc/guide.md
9. References Pradhan, P. (2019). Library Services Platform (LSP): An
overview. INFLIBNET, 26(1), 12-22. Available at:
Bareau, V. (2019A). The codex metadata model. The Open
https://www.researchgate.net/publication/333816851_
Library Foundation: FOLIO project. https://wiki.folio.
Library_Services_Platform_LSP_An_Overview
org/pages/viewpage.action?pageId=1415393
Sources from FOLIO:
Bareau, V. (2019B). Available at: The codex vision. The Open
FOLIO Community (2023). FOLIO: Open Source Library
Library Foundation: FOLIO project. Available at: https://
Services Platform. FOLIO: The Future of Libraries Is
wiki.folio.org/display/PLATFORM/The+Codex+Vision
Open. Available at: https://www.folio.org/
Breeding, M. (2015). Library services platforms: A maturing
FOLIO Community (2023). All guidelines. FOLIO UX
genre of products. American Library Association, 51(4).
docs. UX prototypes, guidelines and assets. FOLIO UX.
https://journals.ala.org/ltr/issue/download/509/259
Available at: https://ux.folio.org/docs/all-guidelines/
Enis, M. (2022). Open for growth: Open source platforms
FOLIO Community (2023). FOLIO Documentation.
on the rise. Library journal. Available at: https://www.
Available at: https://docs.folio.org/docs/
libraryjournal.com/story/Industry%20News/Open-for-
FOLIO Community (2023). FAQ · FOLIO UX docs · UX
Growth-Open-Source-Platforms-on-the-Rise
prototypes, guidelines and assets. FOLIO UX. Available
Grant, C. (2012). The future of library systems: Library ser-
at: https://ux.folio.org/docs/faq/
vices platforms. Information Standards Quarterly, 24(4),
FOLIO Community (2023). FOLIO Developers: Reference
4. https://doi.org/10.3789/isqv24n4.2012.02
- API documentation. The Open Library Foundation:
Index Data. (2023, March 27). FOLIO - Open Source Library
FOLIO Project. Available at: https://dev.folio.org/refer-
Management System: Index Data. https://www.index-
ence/api/
data.com/folio/
FOLIO Community (2023). FOLIO Developers: Developer
Kortick, Y. (2021). Trends in physical and electronic
and system administrator tutorials. Available at: https://
resource usage in U.S. Academic libraries. Ex
dev.folio.org/tutorials/
Libris. Available at: https://exlibrisgroup.com/blog/
changing-priorities-trends-in-physical-and-electronic-
resource-usage-in-us-academic-libraries/