We run a VuFind based service called Sabre. You can read the background to it here, but essentially it is a catalogue for searching the bibliographic holdings of the University of Sussex, the University of Brighton and the local NHS libraries providing a key service to our joint BSMS Medical School students and staff who have access to these libraries.
VuFind is an open source based library catalogue software service which sits on top of the a SOLR index.
When we set up sabre the code was modified to adapt it to working with, at the time, two different library systems (the NHS was added a couple of years later). The key change was how the system made a real time check of an item’s availability and status, this needed to know which library, or libraries, had the item in question and make the request to their system, rather than just connecting to one system for every record. Much of this was adapted from the University of Swansea who had, coincidentally, done something similar at the time.
Due to the internal changes we have made we have stayed on the same version of VuFind, rather than upgrading to new releases. While the work to re-implement this into a VuFind version 2 codebase should be achievable, it’s something we have never allocated time to do.
In July the University of Sussex moved to Alma. There was no Alma driver for VuFind (VuFind has a number of ‘out the box’ drivers for different originating LMS/ILS though no one using VuFind had yet needed to create one for Alma). However Alma does come with a number of APIs which should make creating such a thing possible.
You can see the specification for the required data here.
One surprise is that though Alma has many APIs around bibliographic records, it has no one api for retrieving a list of items, along with their location/type, classmark, loan status and due date if on loan. It’s common in libraries to have a MARC based bibliographic record to describe a work, and a separate list of items; their loan rules, shelfmark and availability, provided separately so it is common for systems to provide a simple api call for this information, and I would say it is a fairly common use case, for example our reading list system also needs to retrieve this information.
Having said this, the information is available, just not in one API call, as far as I can tell.
My method is as follows. To start with we have the unique control number / bib id for this record, which Alma calls an MMS. With this we can get a list of Holdings IDs for the record. These are not items, they are locations (locations define rules such as loan length as well as specifying which building / section it is in), and each location contains items.
The response looks a little like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <holdings total_record_count="2"> <holding link="https://api-na.hosted.exlibrisgroup.com/almaws/v1/bibs/9963106302461/holdings/2283709200002461"> <holding_id>2283709200002461</holding_id> <library desc="Library">USL</library> <location desc="Short">SHORT</location> <call_number>BJ 53 BLO</call_number> </holding> <holding link="https://api-na.hosted.exlibrisgroup.com/almaws/v1/bibs/9963106302461/holdings/2283708100002461"> <holding_id>2283708100002461</holding_id> <library desc="Library">USL</library> <location desc="Core">CORE</location> <call_number>BJ 53 BLO</call_number> </holding> <bib_data link="https://api-na.hosted.exlibrisgroup.com/almaws/v1/bibs/9963106302461"> <mms_id>9963106302461</mms_id> <title>Corporate responsibility /</title> <author>Blowfield, Mick.</author> <isbn>019958107X (paperback)</isbn> <complete_edition>Second edition.</complete_edition> <place_of_publication>Oxford :</place_of_publication> <publisher>Oxford University Press</publisher> <network_numbers> <network_number>(OCoLC)ocn656767624</network_number> <network_number>(DLC) 2011420565</network_number> <network_number>(UK-BtUSL)1098559-44sus_inst</network_number> </network_numbers> </bib_data> </holdings>
From this we have two holdings for this MMS, and we have the IDs for both.
We can now call an api which lists all items for a holdings.
This returns everything you could ever want to know about each item. Except its due date. We need to call this for each Holdings, and obviously we can only make these calls once the first api had returned it’s response.
Finally, we can get any current loans for the record, which includes the due date for each. We can map the item id returned here with those returned above.
So that gets what we need. However this method requires at least three API calls. For a record with multiple copies in multiple locations/libraries this could be much more.
One way to alleviate this was to use curl_multi which can make a number of curl requests at once. This improved the speed of my code by quite a bit. I did do some comparison tests which annoyingly I don’t have to hand as I write but it was in the order of seconds. This isn’t an ideal solution. It calls the first ‘get holdings’ call and the current loans call at the same time, once they have both been returned it has resumed. Better would be for the script to start calling the api for the list of items for each holdings api as soon as the holdings list has been returned. Instead the current loans api may hold it up. I guess the correct solution would involve some sort of threads to handle the two sides of this (one side, get holdings list, and then items for each holdings, the other side, get current loans) and then once each of these has finished the results can be merged and returned.
In any case, I’m sharing the code here, it may be of use to the VuFind community, and to anyone else wanting item availability for Alma. You can also see the script working (at the time of writing) here.