UNSW Library uses Relais with Alma. We are currently using Relais v2014.3.1 and plan to upgrade to v2016 shortly. Pickup locations can come over to Alma via NCIP for both Relais versions. This is how we've configured our Relais environment: Pickup Location can be reviewed/updated by running TableMaintenance.exe in Relais installation folder (e.g. C:\Relais 2016\TableMaintenance.exe).…

The cloud-based Clio system integrates tightly with Alma through NCIP (NISO Circulation Interchange Protocol), which is a protocol that enables, among other things, interoperability between stand-alone interlibrary loan systems such as Clio or ILLiad (often referred to as broker systems) and an ILS such as Alma.  With this new NCIP communication between Clio and Alma,…

The InnReach system may be integrated with Alma as a broker system, similar to other broker systems that are integrated with Alma. Below are some comments with regard to how to set up an InnReach\Alma integration. 1. Integrating Alma with InnReach requires the Innovative DCB component. This component is supplied by Innovative in order to…

Prospector is the direct consortial borrowing [DCB] network in use at the Colorado Alliance of Research Libraries. The network utilizes the INN-Reach shared catalog system (by Innovative Interfaces Inc.). When implementing the integration between Alma and INN-Reach, the Alliance made use of the PHP script written by Ian Chan, Head of Library Technology Initiatives and Development at…

n December of 2015, Alma began supporting NCIP Borrowing renewal messages. Implementing this added functionality in the ILLiad to Alma NCIP workflow required a second ILLiad addon, a server one, so that the renewal messages can be sent automatically without staff intervention. This addon updates the due date in Alma. It does not receive renewal…

Background The Alma NCIP Application profile mandates two elements in every incoming NCIP message, as part of the InitiationHeader: 1. AgencyID This element must contain the Alma institution code. In NCIP v2 messages this element is the AgencyId element, found in the FromAgencyId and the ToAgencyId elements on the InitiationHeader. For example: <FromAgencyId> <AgencyId>60UNIV_INST</AgencyId> </FromAgencyId>…

At Swinburne University Library we have recently upgraded our Relais inter-library loans system to use PDS for authenticating users and Alma for user/group authorisation. In this blog post we'll detail why and how to do this to aid other Relais/ExLibris sites. Why Historically with our Relais system user accounts had to be manually created for…

This is an attempt to more fully document the ILLiad System Addon for Alma, it's evolution, and to provide current code. Extensive documentation for configuring ILLiad and Alma to use this version of the addon are included. This version of the addon is based upon the NCIP Addon Bill Jones at the IDS Project originally…

At Willamette University we recently implemented the ILLiad add-on for NCIP based integration with Alma. We now have it in place for both borrowing and lending requests for ILL materials. We are a member of the Orbis Cascade Alliance, so we run this in tandem with Alma Resource Sharing which we use for Summit borrowing…

Alma and ILLiad may be integrated so that borrowing requests get automatically "pushed" from Alma into ILLiad, where they continue their lifecycle as ILLiad requests. Together with the NCIP based integration, this creates a full Alma/ILLiad workflow such that: A borrowing request is created in Alma, via Primo or through any other discovery interface. Alma…