This is an old revision of the document!
Ken Chad Consulting has set up this wiki to promote the development of standard, open and re-usable specifications for library systems. We hope this service will not only help to reduce costs in library technology procurement but facilitate an open dialogue among all interested stakeholders to help develop the functionality of library related systems.
Open, free to use content
Content is free to re-use. Most content (e.g. the Library Services Platform Specification (below) is licensed under a Creative Commons CC-0 license
“You can copy, modify, distribute .. the work, even for commercial purposes, all without asking permission.” This does not apply of course to *external* content which is accessed by (URL) links and which will have it own specific licensing regime associated with it.
Open to all
Please feel free to sign up to this wiki and make changes. You can also use the 'Discussion' tab at the top of each page to make comments about things in general or specific system requirements.If you have a specification that you'd be happy to share please get in touch with Ken ( firstname.lastname@example.org ) and we'll see how we can make the information available.
Looking for an alternative way to describe needs that can help in finding or developing innovative solutions?
Take a look at the JOBS-TO-BE-DONE approach.The ‘jobs-to-be-done’ methodology is widely used where organisations are looking for new /innovative ways to understand customer ‘needs’. The underlying assumption is that users (staff, students, researchers etc) ‘hire’ (not always with money but rather in terms of time and effort) products and services to get jobs done. This approach is practical and very focussed on looking at the world from a user’s/customer’s perspective.The user might be a member of library staff or and end user -student, researcher member of the public etc
NOTE: Links to the UK Core Specification have been deleted as the UKCS had become out of date
see separate page -Library Requirements
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 unified search 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
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 focussed 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
Library systems for public libraries: A new approach to specifying requirements
18th June (10.30 to 12.30
A meeting is being convened at CILIP on 18th June (10.30 to 12.30 ) to look at potential ways forward regarding a library systems requirement . The UK Core Specification (UKCS) has been a great success but is now out of date and the requirements no longer meet the needs of public libraries or reflect the changes in the offerings from library system vendors. A number of stakeholders including library system vendors and librarians are already interested in participating
The initiative will focus on the needs of *public* libraries at this stage. The Gcloud arrangement for library management systems is up for renewal in 2016 so this is a good time for a review. The best way forward is *necessarily* a new version of the UKCS. I think the issues goes wider.
My outline agenda is:
· Background/Introduction/What is the problem we need to solve?
· Potential solutions/approaches
· Actions –what we do we need to do-and who will do it?