[Koha-devel] Circulation API Question

Stephen Graham s.graham4 at herts.ac.uk
Fri Feb 22 08:57:04 CET 2019


Hi Katrin – thanks for the link, I’d over looked that one.

Are there any people familiar with the ILS-DI interface? I cannot see a way of finding out if a book I have on loan has got a hold/reservation on it. I can see the other way round – if I have a hold on a item/title. I’m using:

service=GetPatronInfo&patron_id=<ID>&show_holds=1&show_loans=1&show_contact=0

But I cannot see anything that indicates there is a hold on an item that I have on loan (there definitely is one!)

Stephen

From: koha-devel-bounces at lists.koha-community.org <koha-devel-bounces at lists.koha-community.org> On Behalf Of Katrin Fischer
Sent: 22 February 2019 07:30
To: koha-devel at lists.koha-community.org
Subject: Re: [Koha-devel] Circulation API Question


Hi Stephen,

I think the REST API in 17.11 doesn't have enough functionality for what you want to do yet, but ILS-DI will probably work.

You can see the progress on the REST API endpoints here:
https://wiki.koha-community.org/wiki/REST_api_RFCs

Hope this helps,

Katrin
On 20.02.19 12:25, Stephen Graham wrote:
Hi All – we have a locally developed mobile app. It’s mainly used for stuff like campus wayfinding, but there is also a notifications section. We are thinking of adding Koha notifications to this area – e.g. if the user needs to return a book because there is a reservation and/or it’s reached max renewals, if there is a reservation for them to collect etc.

I just trying to get a feel for the best way of doing this – using one of the Koha API services. We are currently on 17.11. I’m looking at https://wiki.koha-community.org/wiki/APIs_and_protocols_supported_by_Koha , and there are two possible methods that jump out at me:


  *   ILS-DI
  *   Restful HTTP Service/HTTP API (not sure where the RESTful service is up to development wise, but I don’t think we have the https://wiki.koha-community.org/wiki/Koha_/svc/_HTTP_API service set up on our Koha)

We could always write our own solution, but would rather use a Koha “supported” one. At the moment it looks like we might use the ILD-DI method. Are there any other recommend/better ways?

Cheers, Stephen




_______________________________________________

Koha-devel mailing list

Koha-devel at lists.koha-community.org<mailto:Koha-devel at lists.koha-community.org>

http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel

website : http://www.koha-community.org/

git : http://git.koha-community.org/

bugs : http://bugs.koha-community.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20190222/15085b1d/attachment-0001.html>


More information about the Koha-devel mailing list