Case Study on Cloud Based Library Software as a Service: Evaluating EZproxy

There is a growing relationship between academic libraries and cloud computing. Therefore, understanding the beginnings and the current use of cloud base services in libraries is important. This will help understand the factors that libraries should consider in the future. The purpose of this paper is to better understand the future implementation of the cloud based software in academic settings. Using cloud based, web based, and other remote services may bring both advantages and disadvantages, some of which this paper will bring out. First, a brief literature review of the academic literature, and a review of available general-purpose cloud-based library products are conducted. Next, a real-life scenario for a mid-sized New Zealand institution of higher education is evaluated. This case involves moving from a locally hosted version of EZproxy to a cloud based version with support from the vendor. As this information system decision is an important one, this paper makes a contribution to the available literature and can be informative for librarians. In conclusion, academic libraries will gradually involve more pervasive use of cloud based systems. The examples of important factors to be considered in future decisions include timing and staffing.

💡 Research Summary

The paper examines the growing relationship between academic libraries and cloud computing, focusing on Software‑as‑a‑Service (SaaS) models and, in particular, on the migration of the EZproxy authentication proxy from a locally hosted installation to a vendor‑managed cloud service. After a brief literature review that traces the evolution of remote access—from early IP‑based authentication in the 1990s to the introduction of EZproxy as a tool that enabled off‑campus access for journal databases—the authors map the current landscape of cloud‑based library products. They list major vendors (ExLibris, OCLC, ProQuest, EBSCO, etc.) and the types of services they provide (library management systems, discovery layers, cataloguing tools), highlighting the principal advantages of cloud delivery: reduced capital expenditure on hardware, lower ongoing IT staff workload, automatic updates, and scalability.

The paper then shifts to a concrete case study at a mid‑sized New Zealand university. EZproxy was first installed locally in 2006 on a Windows server, later moved to Red Hat Linux in 2014, and has been maintained by the institution’s IT staff with support from the vendor’s listserv. The local deployment costs roughly US $400 per year in licensing, with internal backups of about 500 MB of log data. Security responsibility rests with the university, and any breach could lead to termination of database access by providers.

In the cloud‑hosted model, OCLC assumes monitoring, patching, backup, and recovery duties. The annual fee rises dramatically to NZ $1,500–4,000, plus a modest implementation charge. The authors outline the trade‑offs: reduced internal staffing burden and guaranteed vendor‑managed security versus new risks such as potential “man‑in‑the‑middle” attacks during LDAP/AD authentication, loss of direct control over data sovereignty, and possible latency increases because the service is hosted in an Australian data centre while most users are in New Zealand and many databases reside in the United States. Deployment speed for new databases also slows—from a two‑hour internal turnaround to an estimated two‑day vendor process—potentially affecting user experience in fast‑changing teaching environments.

Timing of migration is discussed in relation to the university’s existing Voyager library system, which is slated for retirement. The authors argue that when the next generation library platform is likely to be cloud‑based, moving EZproxy to the cloud concurrently would be logical, eliminating the need for a dedicated on‑premise server. They stress that any decision must weigh cost increases against staffing stability (e.g., potential turnover or budget cuts), security policy compliance, and the institution’s overall satisfaction with current service levels.

The conclusion reiterates that cloud‑based applications are no longer limited to resource databases; they now intersect with student‑facing tools such as Dropbox, Google Docs, and Office 365. Libraries must therefore align their services with growing information‑literacy competencies. EZproxy’s SaaS offering appears to be the most sustainable long‑term solution for the case institution, provided that financial, security, and performance considerations are carefully balanced. The study contributes a practical decision‑making framework that other academic libraries can adapt when evaluating local versus outsourced, cloud‑hosted library systems.