1. Legacy system modernization
Moving to Services Platforms
By Wajdi Tahmoush
CX Team Leader, Naseej
2021

2. 2
What is a Legacy System
As Defined by Gartner, “A Legacy system is an information system that may be based on
outdated technologies, but is critical to day-to-day operations”.
Other Definitions:
• A legacy system is not necessarily defined by age. Legacy may refer to lack of support
or a system's incapacity to meet new requirements.
• A Legacy system is a system that meets the needs it was originally designed for, but
doesn’t allow for growth, or interact with newer systems.
• Systems offering a solution instead of offering latest set of capabilities and services.
• Systems with high maintenance cost, high operation cost, no high-availability, and no or
limited scalability and interoperability.
• Systems with high OS and Programming Kit Dependency.
• Systems that don’t adhere to the cloud computing requirements in terms of cloud
security, availability, scalability, and interoperability.

3. 3
A Legacy System from Library Perspective
From Library Perspective, a legacy system is:
• A system that doesn’t allow the library to modify or change its services in response to users’
requirements, standards changes, or emergencies.
• A system that doesn’t open room for adding new services or modifying existing ones.
• A system that doesn’t enable the library to operate in Linked Data Projects.
• A system that does not comply with SEO requirements.
• A system that doesn’t enable the library to offer all its services through a single user experience.
• A system that doesn’t enable simple integrations or enables integration but for a high cost.
• A system that requires duplicate work or data replication to offer different users services.
• A system that doesn’t respond to pandemic implications like “Work from home”
• A system that doesn’t enable the Library to innovate in response to future trends related
to Libraries and Librarianship as identified by the Center for the future of Libraries
http://www.ala.org/tools/future/trends

4. 4
Future Trends relevant to libraries http://www.ala.org/tools/future/trends

5. 5
Legacy Systems in Libraries
• Considering the previous definitions of Legacy systems, most, if not all systems used by
Libraries, are Legacy systems.
• Yes, they may still work, but times have changed. New technologies and user expectations
are making it increasingly risky to hang on to old legacy library management system.
• Libraries require many systems to maintain and manage its content and holding.
• Different systems are used for physical holdings, digital assets, electronic subscriptions, and
reference services, with no room for new services.
• Different users’ interfaces to access different types of information.
• Discovery solutions partially solves the problem but suffer from data replication and
synchronization or lost services related to different content types.
• Even if different systems interfaces issue is solved on the end user interface it is still an issue
with replicated work, limited customization, and different staff experience in managing content.
• No Unified BI management tools for different content types.
• No or extremely limited community collaboration.

6. 6
Technical Trends that Affects Libraries
• Technical Trends are most affecting Libraries Services.
• Technical Trends are directly related to systems and
technologies in use.
• Legacy systems based on old technologies can’t align.
• New trends require cloud services to enable interoperability.
• Interoperability requires new software development with new
trends requirements in mind.
• Classical systems don’t fit, even APIs and Web Services are not
enough.
• Services Platform build on Microservices, and lightweight
communication mechanisms is the solution.
• Cloud based Services are the best choice for libraries through a
Library Services Platform.

7. 7
What is a Library Services Platform
A Library Services Platform is a new approach to deliver all Library services (Management
services, Admin Services, and Users Services) through a single user experience
Library services includes but not limited to:
• Management of Library Holdings (Physical and Electronics).
• Management of Digital Content (Digital Repositories).
• Reference Services (Chatbot, Guides, FAQs, Databases, etc….)
• Users Services:
a. Browse, Search, Locate, and Access resource.
b. Users Profiling, Behavior and Interests identification, Account Management
c. Recommendations, Information Dissemination, Users Preferences
• Admin Services like BI, Analytics Reporting, Collection Developments, Usage Analysis.
• Different backend systems could be in use, but transparent for staff and users through a
simple unified presentation layer.

8. 8
Library Services Platform Components
➢ ILS Services
• Cataloging
• Acquisition
• Inventory
• Circulation
• Users Services
➢ ERM Services
• Databases
• Subscriptions
• Access privileges
• eHolding
• eUasge
➢ Digital Content
• Digital Collections
• Digital Items
• eUsers
• Access privileges
• Digital Presentation
Physical Collection Digital Assets
Electronic Resources
Scalability Integration
Index/Search Mobility Messaging Bus
Security AI
➢ Medad VLA
• Virtual Assistance
• FAQs
• Library Guides
• Ask a Librarian
• Databases List
Reference Services

9. 9
Library Services Platform Architecture
Presentation Layer:
• Deliver all users and Staff interfaces through a
unified user experience.
Integration Layer:
• Enables all internal and external integrations through
a secured unified Microservices APIs gateway.
Application Layer:
• All systems features and functions as Microservices
APIs. Handlers like image server and media streaming
Index Layer:
• Offers all indexing and Search capabilities
through metadata and FT search engines.
Data Layer:
• Digital Storage, Databases, File system, system logs

10. 10
Library Services Platform Benefits
• Offers all current and future Library services through single platform and unified customer
experience.
• Based on open-source software enabling scalability & code changes (like Folio, Fedora, Drupal).
• Native Web Interfaces for all components including Staff and Admin interfaces.
• Native and built-in linked data support and SEO compatibility.
• Unlimited customizations and configurations as enabling/disabling services based on library
needs.
• Scalability and room for new services development.
• Enables library innovations and building services for different trends.
• Seamless integration between all different platform components.
• Interoperability and integration capabilities with other system like SIS and LMS through
Microservices APIs.
• No duplicate work or need for data replication. Shared data storage, shared indexes, and unified
access to all library services and holdings.

11. 11
Library Services Platform Benefits
• All current and future Library services through single platform and unified customer experience.
• Highly secured, scalable, reliable, and high availability
• Based on open-source software enabling scalability and code changes (Folio, Fedora, Drupal).
• Native Web Interfaces for all components including Staff and Admin interfaces.
• Native and built-in linked data support and SEO compatibility.
• Unlimited customizations and configurations; enabling/disabling services based on library needs.
• Room for new services development.
• Enables library innovations in different trends.
• Seamless integration between all different platform components.
• Interoperability and integration capabilities with other system like SIS and LMS through
Microservices APIs.
• Empowers Communities through Collaboration.
• No duplicate work or need for data replication. Shared data storage, shared indexes, and unified
access to all library services and holdings.

12. 12
Services Platform vs. Legacy systems
Microservices, containers, continuous integration and
delivery are critical tools in the digital transformation
For any clarifications or additional information don’t hesitate to contact me:
wajdi.tahmoush@naseej.com
Mobile: 009613117147