From: Osullivan L. <L.O...@sw...> - 2011-03-22 11:53:03
|
Hi Graham, I wouldn't rule out a bug with the Ex Libris Restful services - I have a similar one on Voyager where CanRenew is always set to "Y" regardless of the reality. I have reported the issue to Ex Libris and they have confirmed it is a bug. I recommend that you do the same - they seem pretty keen to fix them as I believe this will have an impact on Primo... Cheers, Luke From: Seaman, Graham [mailto:Gra...@rh...] Sent: 22 March 2011 10:41 To: vuf...@li... Subject: [VuFind-Tech] aleph holds This is really an Aleph question rather than a Vufind question, but I'm getting no response from the Aleph list so thought I would try here. I'm trying to use the Aleph RESTful interface to manage holds from Vufind. Some of our users are allowed to hold material which is on the shelf (using Z305-ON-SHELF), so whether an item can be held depends both on the item and on the patron. The Aleph web front end manages to untangle this combination so that it can warn the user that the hold option is not available before the user has filled in the form and attempted to make the hold. I would assume that I could do something equivalent using the RESTful interface, but can't find a permutation which lets me know whether a patron can hold a particular item. Calls such as /rest-dlf/patron/[patronid]/record/[recordid]/items/[itemid] always return <hold> with 'allowed="Y"'. I can let the user go as far as requesting the hold, at which point the request will fail if the user can't do it, but I don't like to make users fill in a form and only tell them they're not allowed to after the event. I've looked at the aleph patch VUFIND-386 on Jira, but as far as I can see that doesn't solve this particular problem (I can't test it as it is based on a version of vufind a bit too distant from mine to be able to simply merge it in). Any other Aleph users around with a suggestion? Do I need to find some way to reconfigure the REST server output? Thanks Graham |