CHAPTER TWO
LITERATURE REVIEW
This chapter examines four well-known library management systems that are
currently in use, emphasizing their features, architecture, development tools, and
advantages and disadvantages. Senayan, Evergreen, and Koha Library are some of
these systems. Using UML models such context and sequence diagrams, the
evaluation identifies important design elements pertinent to the creation of the library
management system. It also identifies gaps that need to be filled and draws lessons
from current features.
2.1 Review of System 1: Koha Library
2.1.1. Description of System
Koha is an open-source Integrated Library System (ILS) used worldwide by public, school, and
special libraries. It was developed in New Zealand by Katipo Communications and first
implemented in 2000. Koha supports full cataloging, circulation, acquisitions, serials
management, patron management, and OPAC (Online Public Access Catalog) services.
Figure 2.1 User interface of Koha Library Management System
Models of the System:
Context Model: Koha integrates with different library departments and external systems like
MARC databases and Z39.50 servers.
Figure 2.2 Context model of Koha Library Management
The context model of the Koha Library Management System illustrates how the system
interacts with both internal and external entities to support comprehensive library
operations. At the center of the model is the Koha LMS, which serves as the core
platform for managing various library functions such as cataloging, circulation, and user
services. Internally, the system interacts with library departments including cataloging,
acquisitions, circulation, and administration, enabling staff to manage records, track
loans, generate reports, and configure system settings. Externally, the system connects
with patrons, who use the online public access catalog (OPAC) to search for materials,
place holds, renew items, and manage their library accounts.
The model also shows Koha’s integration with MARC (Machine-Readable Cataloging)
databases, which are used to import standardized bibliographic records, facilitating
efficient and accurate cataloging. Additionally, Koha interacts with Z39.50 servers,
allowing users—particularly librarians—to search and retrieve bibliographic data from
other libraries and external catalogs. This enhances cooperative cataloging and
minimizes duplication of effort. Overall, the context model highlights Koha’s ability to
bridge internal operations with external data sources and user interfaces, making it a
robust and flexible solution for modern library management.
Sequence Diagram: A typical booking flow starts when the guest searches a Login → A
patron searches a book → System queries catalog → Displays result.7
Figure 2.3 Sequence model of Koha Library Management System
The sequence diagram illustrates the interaction between different actors and system
components within the Koha Library Management System during a typical user session.
The process begins when the librarian logs into the system, enabling a patron (user) to
access the library services through a browser interface. Once logged in, the user is
presented with various display options and selects the option to search the library
catalog. This request is passed from the browser to the Koha server, which processes
the query and returns the relevant catalog results to the browser for display. The user
then views the catalog to check book availability or other bibliographic details. If
needed, the user can perform an additional search to refine or explore further results,
which again triggers a request from the browser to the Koha server. After locating the
desired materials, the user proceeds to manage their loans, which may involve
renewing borrowed items, checking due dates, or placing holds. Finally, a message
labeled "Serrin" appears in the diagram, likely indicating a session closure or librarian
acknowledgment, although its exact purpose is unclear due to possible labeling
inconsistency. Overall, this sequence diagram clearly demonstrates the dynamic
exchange of information between users, interfaces, and backend systems, providing
insight into the operational workflow of the Koha system.
Features of the System:
Koha Library Management System offers a web-based interface for both staff and
users, including OPAC for end-user access. It provides full cataloging support with
MARC 21 standards, circulation and patron management, and barcode scanning
functionality. Additionally, it supports acquisitions and serials management, offers a
multilingual and customizable interface, and enables comprehensive reporting and
statistics generation.
Development Tools: Koha is developed using the Perl programming language and
utilizes either MySQL or MariaDB as its database. It runs on the Apache web server,
with Linux—preferably Debian—as the operating system. The interface is entirely web-
based, built with HTML, JavaScript, and CSS. Koha uses Git for version control and
incorporates tools such as Zebra as its primary search engine, with optional support for
Elasticsearch.
2.1.2. Review of the Good Features
Koha is a completely free and open-source library management system supported by a
large global community of developers and users. It offers web-based access for both
patrons and staff, with full compliance with MARC 21 and Z39.50 standards. The
system is highly customizable and scalable, featuring frequent updates and
comprehensive documentation. Additionally, it supports RFID integration, barcode
systems, and provides multi-language and multi-branch capabilities.
2.1.3. Review of the Bad Features
Koha has a few drawbacks, including the need for technical knowledge during
installation and ongoing maintenance. New users unfamiliar with MARC standards may
face a steep learning curve. Additionally, the default interface can appear outdated
without customization. Performance may decline with very large databases if not
properly optimized, and out-of-the-box integrations with modern tools are limited,
although the system is extendable.
2.1.4. Summary of the System Review
Koha has a few drawbacks, including the need for technical knowledge during
installation and ongoing maintenance. New users unfamiliar with MARC standards may
face a steep learning curve. Additionally, the default interface can appear outdated
without customization. Performance may decline with very large databases if not
properly optimized, and out-of-the-box integrations with modern tools are limited,
although the system is extendable.
2.3 Review of System 2 : Evergreen Library
2.2.1. Description of System
Evergreen is an open-source Integrated Library System (ILS) used by libraries to
manage their catalogues, circulation, and user services. It was developed to support
large consortia and has grown into a robust system serving hundreds of libraries
worldwide. Evergreen is designed with scalability, flexibility, and community
collaboration in mind. Its architecture supports everything from a single-branch public
library to complex networks of library systems.
Figure 2.4 User interface of Evergreen
Models of the System
Context Model :The Evergreen system connects various user roles including Librarians,
Patrons, and Administrators to a central server. These users interact with the system
through web browsers or client applications. The context model outlines how users
communicate with the server and how external services (e.g., cataloging services like
OCLC or digital libraries) are integrated.
Figure 2.5 Context model of Evergreen
The context model of the Evergreen Library Management System illustrates how the
system serves as a central hub that connects key user roles librarians, patrons, and
administrators as well as various external services. Librarians interact with the
Evergreen system to perform daily operational tasks such as cataloging, circulation, and
user support. They also serve as intermediaries between patrons and administrators
when issues require higher-level intervention. Administrators, on the other hand,
manage system configurations, user permissions, policy enforcement, and technical
oversight, ensuring the system runs smoothly and securely. Patrons access the system
through web browsers or client applications to search the catalog, place holds, manage
loans, and view account information. In addition to user roles, the Evergreen system
integrates with external services such as cataloging databases (e.g., OCLC), digital
libraries, and third-party tools to enhance functionality and resource availability. This
context model highlights Evergreen's flexibility, its user-oriented architecture, and its
ability to interoperate with external platforms to support modern library operations.
Sequence Diagram : A typical interaction, such as "Borrowing a Book", follows this
sequence: Patron logs in via the user portal - Patron searches the catalogue - Patron
places a hold or requests a book Librarian receives the request, locates the book, and
checks it out - System updates inventory and user records.
Figure 2.6 Sequence model of Evergreen
Features of the System:
Evergreen offers a wide range of features, including an OPAC (Online Public Access
Catalogue), circulation functions such as check-in, check-out, and renewals, as well as
support for holds and reservations. It provides robust cataloging tools with MARC
editing capabilities, comprehensive reporting tools, and user account management. The
system also supports multi-branch and consortia setups, acquisitions and serials
management, and includes dedicated interfaces for both staff and patrons.
Development Tools:
Evergreen is primarily written in Perl and JavaScript, and it uses PostgreSQL as its
database. The system runs on the Apache web server and features a web-based staff
client and OPAC, although older versions included a standalone client. It is typically
deployed on Linux systems, particularly Debian-based distributions. Version control is
managed through Git, with repositories hosted on GitHub and supported by the
community. Evergreen is usually deployed on-premises or hosted by service providers
such as Equinox.
2.2.2. Review of the Good Features
Evergreen is highly customizable due to its open-source nature and offers robust
support for large networks, including multi-branch and consortia environments. It
benefits from strong community support and active development, along with detailed
reporting capabilities and fine-grained user access control. The system integrates with
external services such as Z39.50 servers and SIP2 for self-check machines. Its modular
architecture allows for easier updates and plugin support, and it includes powerful tools
for cataloging and acquisitions.
2.2.3. Review of the Bad Features
Some Agoda users have reported discrepancies between hotel listings and actual
conditions. Additionally, communication delays between Agoda and hotel partners may
result in booking errors. The customer support system, especially for post-booking
changes, lacks responsiveness in certain regions (Kim, 2022).
2.2.4. Summary of the System Review
Evergreen is a powerful, scalable, and community-driven library management system
ideal for public library consortia and institutions seeking a customizable open-source
solution. While it offers extensive features and flexibility, it requires a competent IT team
for installation, support, and ongoing maintenance. Its advantages in cost and
configurability make it a preferred choice for libraries with complex needs and limited
budgets. However, smaller libraries or those lacking technical resources might face
challenges in deployment and use.
2.3 Review of System 3: Senayan Library
2.3.1. Description of System
SLiMS (Senayan Library Management System) is an open-source library management
system developed in Indonesia. It is widely used in schools, universities, and public
libraries across Southeast Asia. SLiMS is web-based and provides a comprehensive set
of tools for cataloging, circulation, user management, digital archive access, and
reporting.
Models of the System
Context Model: SLiMS interacts with users (librarians and patrons), external metadata
databases (e.g., ISBN or MARC sources), and digital content repositories.
Figure 2.7 context model of Senayan
sequence: Patron logs into SLiMS OPAC - Searches for a book - System fetches -
matching records from the catalog database - Results are displayed with location and
availability information
Figure 2.7 Sequence model of Senayan
Features of the System:
SLIMS features a web-based interface and an OPAC with advanced search and filter
options. It supports digital document uploads and archiving, as well as MARC21 and
ISO 2709 standards. The system offers multilingual support, advanced reporting and
statistics, and integration with QR codes and barcodes. Additionally, it includes
customizable user interfaces and templates, along with robust membership
management and overdue tracking capabilities.
Development Tools:
SLIMS is developed using PHP as its primary programming language and utilizes MySQL as its
database. It runs on the Apache web server and is compatible with both Linux and Windows
operating systems. The system incorporates frameworks and libraries such as jQuery and
Bootstrap, with version control managed through GitHub via its official repository. Its interface is
entirely web-based, built with HTML, JavaScript, and CSS.
2.3.2. Review of the Good Features
SLIMS is fully open-source and free to use, offering a user-friendly and intuitive
interface. It is easy to install and configure, with support for digital archives and
multimedia content. The system provides strong localization and multilingual
capabilities, is backed by an active community with regular updates, and is compatible
with barcode and QR code systems. Additionally, it offers excellent reporting features.
2.3.3. Review of the Bad Features
SLIMS has limited scalability for very large or complex library environments, and its
performance may slow down under high data loads without proper optimization. It offers
limited third-party integrations out of the box and is less modular compared to
enterprise-grade systems like Koha. Additionally, its user permissions and role
management features are relatively basic.
2.3.4. Summary of the System Review
SLiMS is a practical and powerful open-source library management system ideal for
small to medium libraries. It combines essential features with ease of use and
community-driven support. While it may lack some of the advanced capabilities and
scalability of larger systems, SLiMS makes up for it with simplicity, accessibility, and
active development—making it a valuable tool for institutions seeking a cost-effective
digital library solution.
References
Equinox Software. (n.d.). Evergreen ILS. Retrieved from [Link]
Katipo Communications. (2000). Koha Library Management System. Retrieved from
[Link]
Kim, S. (2022). User experience challenges in third-party booking platforms: A study on
Agoda. Journal of Online Systems, 17(3), 112-118.
Ministry of Education and Culture, Indonesia. (n.d.). SLIMS – Senayan Library
Management System. Retrieved from [Link]
Open Library Foundation. (n.d.). Evergreen Documentation. Retrieved from
[Link]
Zhang, L., & Yu, H. (2021). Comparative Study of Open-Source Library Management
Systems. International Journal of Library and Information Science, 13(2), 89–101.