User Tools

Site Tools


library_services_platform

What is a LSP?

Library Services Platform (LSP) is the accepted term for what were known as 'next generation' of library systems They provide capabilities to manage print and electronic resources in a single (unified) system and consequently replace conventional Library Management Systems (LMS/ILS) and Electronic Resource Management (ERM) systems.For more information systems see the Library Services Platform entry on Higher Education Library Technology (HELibTech) wiki

The HELibTech briefing papersalso include useful perspectives about library systems and related technologies and issues. They include

  1. Library management system to library services platform. Resource management for libraries: a new perspective
  2. Rethinking the library services platform
  3. The new role of the library in teaching and learning outcomes
  4. The student consumer and the rise of e-textbook platforms
  5. The rise of library centric reading list systems


Rethinking the Library Services Platform (LSP) By Ken Chad. UKSG eNews 27 November 2015
In a complex ecosystem no single integrated LSP will meet the needs of libraries. Using print management as one of the defining factors for an LSP is the ‘LMS/ILS tail wagging the LSP dog”. A more user centred approach is needed. Comparing LSPs with enterprise resource planning systems (ERPs), Ken suggests that we may see a similar development to what Gartner has characterised as the ‘postmodern’ ERP. They predict a “ a more federated, loosely coupled ERP environment” and Ken suggests this could be the path forward for LSPs if vendors do more to open up their platforms.



Making the business case
What business imperatives do these next generation systems need to meet? For example some vendors claim that the characteristics of cloud, unified resource management and new approaches to workflow will reduce the total cost of ownership (TCO).

Jisc LMS change project 'Checklists
From the Jisc LMS change project website:-
“Checklists of functionality are typically used within Library system tendering processes to ensure that Mandatory / Optional functionality is met. We should recognise that this is useful as a safeguard against almost unexpected failing (as any short listed system unlikely to be missing any core functionality) and to capture local / national requirements (for example, relating to UK ILL/DD operations). The traditional UK Core Specification (UKCS) and recent Unified Library Resource Management Specification (ULRMS) – both referenced from the HE Library Technology wiki – serve precisely these purposes.
The checklists provided here have a somewhat different purpose in mind – to assist in defining the functional components, the boundaries and the critical areas for any systems or process development in the library space. The list extends far beyond the boundaries of what might be called the ‘local library management system’ and even the ‘library service platform, to enable service managers to:

  • Think out of the local and library boxes
  • Scope systems, related developments and change projects
  • Identify required and potential touch points with other institutional systems
  • Identify required and potential relationships with external services
  • Engage in clear constructive dialogue with suppliers, developers and service partners
  • Address matters arising in service road maps, contracts and project plans”
library_services_platform.txt · Last modified: 2019/07/10 14:39 by 109.149.81.116