Hi Jonathan: Thanks. I'll keep that in mind. We might need to use it for a certain project, so that's good to know.
I'm a bit wary of using third-party software for Koha that we don’t maintain ourselves though :/. Is there any chance that BibLibre might be looking to merge the code into the community codebase? David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Druart Sent: Wednesday, 23 July 2014 6:14 PM To: David Cook Cc: Petter Goksøyr Åsen; [email protected] Subject: Re: [Koha-devel] RFC: /svc/ API 2014-07-23 5:03 GMT+02:00 David Cook <[email protected]>: Hi David, > I only heard of BibLibre's "koha-restful" recently. I didn't > thoroughly review the code, but it appears that it only uses IP-based > authentication at the moment. I think it was missing all the > functionality that I desired as well, so I decided not to use it. BibLibre wrote koha-restful to fix the lack of possibilities IDS-DI can provide. We are highly open-minded to contributions (merge request, patches, etc.), if you find some time :) If you want to add features, you can send us a patch at dev_patches AT biblibre DOT com You can find more information about it into README file and opac/rest.pl documentation on http://git.biblibre.com. Cheers, Jonathan > -----Original Message----- > From: Petter Goksøyr Åsen > [mailto:[email protected]] > Sent: Wednesday, 23 July 2014 12:11 PM > To: David Cook > Subject: SV: [Koha-devel] RFC: /svc/ API > > > David Cook wrote: >> Since there are an indeterminate number of third-party software >> systems using the existing API, I'd recommend versioning and using v2 >> to handle things more RESTfully. > > I agree. We should think twice before breaking existing integrations > and workflows. > > I am also interested to hear peoples opinions about Koha's HTTP APIs > in > general: > - do you want them expanded? for what use cases? > - and more importantly: should Koha's templates make use of i'ts own APIs? > > My library certainly think this could be a fruitful direction for Koha > to go, and want to help make it happen. But if there is no big > interest in the community in this approach, we'll more likely to fork > and/or contribute to Biblibre's koha-restful instead of patching the svc and > ILS-DI APIs. > > Regards, > Petter Goksøyr Åsen > Deichmanske bibliotek / Oslo Public Library > > > > _______________________________________________ > Koha-devel mailing list > [email protected] > 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/ _______________________________________________ Koha-devel mailing list [email protected] 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/
