Skip to content

Commit

Permalink
Update Core library systems “open-source-systems”
Browse files Browse the repository at this point in the history
  • Loading branch information
ken committed Sep 30, 2024
1 parent 4f5e6fd commit d8fe0b4
Showing 1 changed file with 8 additions and 6 deletions.
14 changes: 8 additions & 6 deletions core-library-systems/open-source-systems.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,27 +6,29 @@ tags:
- Library systems
- LSP
- LMS
published: true
layout: enhanced
nav_order: 6
parent: Core library systems
---

# Open Source Systems

In the last decade or so open source software became a defining factor in how librarians perceived ‘open’ library systems. Open source library systems such as Koha gained market share were often seen in terms of a ‘battle’ with the more common proprietary solutions.

With the rise of cloud computing, software ‘platforms’ have come to dominate. Because the solution is hosted in the cloud, rather than implemented on local servers, the underlying technology becomes of less concern. These platforms, including Library Services Platforms (LSPs) typically embrace open source components and combine them with proprietary solutions.

The value of a ‘platform’, as opposed to a software ‘product’ comes not only from its own features, but from its ability to connect to external solutions, data, and processes. To do this it needs to be ‘open’ in terms of data and the ability to integrate, via (typically open) application programming Interfaces (APIs), with other products which may be developed by customers or provided by other independent software vendors (ISVs). This, open interoperability, perspective is now a more fruitful way to consider open library systems.
The value of a ‘platform’, as opposed to a software ‘product’ comes not only from its own features, but from its ability to connect to external solutions, data, and processes. To do this it needs to be ‘open’ in terms of data and the ability to integrate, via (typically open) application programming Interfaces (APIs), with other products which may be developed by customers or provided by other independent software vendors (ISVs). This, open interoperability, perspective is now a more fruitful way to consider open library systems. See: [Open library systems – a new perspective](https://www.kenchadconsulting.com/wp-content/uploads/2022/12/Open-library-systems-KenChad-May2022.pdf). Ken Chad. Higher Education Library Technology \[HELibTech] Briefing Paper No. 7, May 2022.

*In the last decade or so open source software became a defining factor in how librarians perceived ‘open’ library systems. Open source library systems such as Koha gained market share were often seen in terms of a ‘battle’ with the more common proprietary solutions. With the rise of cloud computing, software ‘platforms’ have come to dominate. Because the solution is hosted in the cloud, rather than implemented on local servers, the underlying technology becomes of less concern. These platforms, including Library Services Platforms (LSPs) typically embrace open source components and combine them with proprietary solutions. The value of a ‘platform’, as opposed to a software ‘product’ comes not only from its own features, but from its ability to connect to external solutions, data and processes.*

## Benefits of open source systems

According to Jisc there are a range of benefits to libraries using open source systems including:

- **Lower costs:** Open source offers a lower total cost of ownership than traditional library systems. There are none of the traditional license costs associated with open source. Libraries are able take advantage of the reduced costs the cloud offers by reducing local support and hosting costs (if it is supported and hosted by a third party).
- **No lock-in:** Libraries are, in a sense, removed from the traditional lock-in associated with library systems. There is a greater opportunity to pick and choose components, and take advantage of what is, generally, better interoperability with open source solutions. Related to this is also the idea that open source is more sustainable: If a vendor goes out of business the software may disappear or be sold-on. With open it is always available, and there is usually a community involved in it to continue its development.
- **Adaptation and Innovation:** Connected to the above is the greater capacity that libraries have to innovate with open systems and software. There is no need to await the next update or release, instead in either isolation or collaboratively, can develop the functionality required. This enables much more agile services and systems, as well as ensuring user expectations are exceeded.
- **A richer library systems ecosystem:** A less direct impact of open source is a richer library systems ecosystem. This is both in terms of the library solutions available (a healthier marketplace with both proprietary and open solutions) and in terms of collaboration and engagement between libraries themselves. Libraries are able to collaborate and share code on the functionality and fixes they require. Indeed, there are open source systems such as Evergreen, which were developed as an open source library system for a consortial approach
* **Lower costs:** Open source offers a lower total cost of ownership than traditional library systems. There are none of the traditional license costs associated with open source. Libraries are able take advantage of the reduced costs the cloud offers by reducing local support and hosting costs (if it is supported and hosted by a third party).
* **No lock-in:** Libraries are, in a sense, removed from the traditional lock-in associated with library systems. There is a greater opportunity to pick and choose components, and take advantage of what is, generally, better interoperability with open source solutions. Related to this is also the idea that open source is more sustainable: If a vendor goes out of business the software may disappear or be sold-on. With open it is always available, and there is usually a community involved in it to continue its development.
* **Adaptation and Innovation:** Connected to the above is the greater capacity that libraries have to innovate with open systems and software. There is no need to await the next update or release, instead in either isolation or collaboratively, can develop the functionality required. This enables much more agile services and systems, as well as ensuring user expectations are exceeded.
* **A richer library systems ecosystem:** A less direct impact of open source is a richer library systems ecosystem. This is both in terms of the library solutions available (a healthier marketplace with both proprietary and open solutions) and in terms of collaboration and engagement between libraries themselves. Libraries are able to collaborate and share code on the functionality and fixes they require. Indeed, there are open source systems such as Evergreen, which were developed as an open source library system for a consortial approach

## **Open source library systems**

Expand Down

0 comments on commit d8fe0b4

Please sign in to comment.