Review on Koha Order Module/plugin API
Dear Koha Developers, Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha. The API draft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs... We have had it posted for review in the Swedish user group - but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin. Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document. When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site. Please leave comments before 21 September 2020. /Swedish Koha User Group - the book vendor module/plugin task group
Hello Ola, I have no idea of what the final purpose is but I kind of understood from your document you want to achieve automatic input of biblio data from vendors directly. https://wiki.koha-community.org/wiki/Biblios_endpoint_RFC The route to get biblio data from koha is implemented in 19.11 but the one to push to koha is still missing (can't find out which bz it is). I'd be really interested into seeing some community route implementing order operations through the api. There is already one existing to interact with Koha vendor data, if of any help: https://wiki.koha-community.org/wiki/Acquisitions_vendors_endpoint_RFC -> implemented One of my concern, the one implementing purchase suggestions operation is also still a big work in progress: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314 Maybe nice to file a bug in bugzilla like "Route to create, list, update, delete an order basket" or something of the like so that anyone can followup? If you do so, please add me to the CC's :) Kind regards, Arthur On 07/09/2020 16:40, Ola Andersson wrote:
Dear Koha Developers,
Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha.
The APIdraft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs...
We have had it posted for review in the Swedish user group – but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin.
Pleaseshare thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document.
When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site.
Please leave comments before 21 September 2020.
/Swedish Koha User Group – the book vendor module/plugin task group
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://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/
Kia ora Ola (and the Swedish Koha users group) First of all I'd like to say its great to see you are wanting to help improve Koha. I haven't had a chance to read the full proposal, but it's great to see anyone wanting to contribute. Ill try to have a proper read and leave some feedback. Ngā mihi mahana Chris On Tue, 8 Sep 2020, 3:13 am Arthur Suzuki, <arthur.suzuki@biblibre.com> wrote:
Hello Ola,
I have no idea of what the final purpose is but I kind of understood from your document you want to achieve automatic input of biblio data from vendors directly.
https://wiki.koha-community.org/wiki/Biblios_endpoint_RFC
The route to get biblio data from koha is implemented in 19.11 but the one to push to koha is still missing (can't find out which bz it is).
I'd be really interested into seeing some community route implementing order operations through the api.
There is already one existing to interact with Koha vendor data, if of any help:
https://wiki.koha-community.org/wiki/Acquisitions_vendors_endpoint_RFC -> implemented
One of my concern, the one implementing purchase suggestions operation is also still a big work in progress: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314
Maybe nice to file a bug in bugzilla like "Route to create, list, update, delete an order basket" or something of the like so that anyone can followup? If you do so, please add me to the CC's :)
Kind regards,
Arthur On 07/09/2020 16:40, Ola Andersson wrote:
Dear Koha Developers,
Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha.
The API draft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs...
We have had it posted for review in the Swedish user group – but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin.
Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document.
When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site.
Please leave comments before 21 September 2020.
/Swedish Koha User Group – the book vendor module/plugin task group
_______________________________________________ Koha-devel mailing listKoha-devel@lists.koha-community.orghttps://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 Koha-devel@lists.koha-community.org https://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/
Hi Ola, Firstly, it's great to see the Swedish users group getting involved and asking for feedback. Everyone works better when we all work together. I'm still digesting the proposal as it stands, but I don't see any issues with anything that expands the API capabitiies of Koha.. As Arthur suggested, it would be great to see enhancements exposing some more of the acquisitions functionality via the existing REST developments. I'm not entirely sure I understand the suggested flow however; but it does sounds sami-familiar as a flow from my work with EDI. Have you considered what already exists in Koha? Do Swedish vendors support EDI at all and could this perhaps be an option..? I'm sure there's an ORDER message flow that allows for vendor first interactions where you create a basket of items at the vendor, then Koha grabs that basket to allow the Koha end processing and pushed it back to the vendor for the next step etc. I'll keep an eye on this discussion and contribute what I can, many thanks for the inclusion. *Martin Renvoize* <https://www.ptfs-europe.com> Development Team Manager Community Release Manager (19.11, 20.05) *Phone:* +44 (0) 1483 378728 *Mobile:* +44 (0) 7725 985 636 *Email:* martin.renvoize@ptfs-europe.com *Fax:* +44 (0) 800 756 6384 www.ptfs-europe.com Registered in the United Kingdom No. 06416372 VAT Reg No. 925 7211 30 The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. If you think that you have received this email message in error, please email the sender at info@ptfs-europe.com On Tue, 8 Sep 2020 at 07:07, Chris Cormack <chris@bigballofwax.co.nz> wrote:
Kia ora Ola (and the Swedish Koha users group)
First of all I'd like to say its great to see you are wanting to help improve Koha. I haven't had a chance to read the full proposal, but it's great to see anyone wanting to contribute.
Ill try to have a proper read and leave some feedback.
Ngā mihi mahana Chris
On Tue, 8 Sep 2020, 3:13 am Arthur Suzuki, <arthur.suzuki@biblibre.com> wrote:
Hello Ola,
I have no idea of what the final purpose is but I kind of understood from your document you want to achieve automatic input of biblio data from vendors directly.
https://wiki.koha-community.org/wiki/Biblios_endpoint_RFC
The route to get biblio data from koha is implemented in 19.11 but the one to push to koha is still missing (can't find out which bz it is).
I'd be really interested into seeing some community route implementing order operations through the api.
There is already one existing to interact with Koha vendor data, if of any help:
https://wiki.koha-community.org/wiki/Acquisitions_vendors_endpoint_RFC -> implemented
One of my concern, the one implementing purchase suggestions operation is also still a big work in progress: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314
Maybe nice to file a bug in bugzilla like "Route to create, list, update, delete an order basket" or something of the like so that anyone can followup? If you do so, please add me to the CC's :)
Kind regards,
Arthur On 07/09/2020 16:40, Ola Andersson wrote:
Dear Koha Developers,
Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha.
The API draft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs...
We have had it posted for review in the Swedish user group – but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin.
Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document.
When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site.
Please leave comments before 21 September 2020.
/Swedish Koha User Group – the book vendor module/plugin task group
_______________________________________________ Koha-devel mailing listKoha-devel@lists.koha-community.orghttps://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 Koha-devel@lists.koha-community.org https://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 Koha-devel@lists.koha-community.org https://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/
The main problem I see with Koha's API for this, is the fact that our current workflow Basket > Orderlines > close basket > receive is sometimes too complicated for vendors. Meaning they don't expect to understand that much how Koha does things internally. I faced this when I wrote the GOBI plugin, which had a pretty similar spec. We could add the option to auto-create a basket (that's part of the original orders spec) and we definitely should have a route to add records. It really depends on how much we can make the external system adapt to Koha. Otherwise, you should take the plugin route, unfortunately. El lun., 7 sept. 2020 a las 12:14, Arthur Suzuki (< arthur.suzuki@biblibre.com>) escribió:
Hello Ola,
I have no idea of what the final purpose is but I kind of understood from your document you want to achieve automatic input of biblio data from vendors directly.
https://wiki.koha-community.org/wiki/Biblios_endpoint_RFC
The route to get biblio data from koha is implemented in 19.11 but the one to push to koha is still missing (can't find out which bz it is).
I'd be really interested into seeing some community route implementing order operations through the api.
There is already one existing to interact with Koha vendor data, if of any help:
https://wiki.koha-community.org/wiki/Acquisitions_vendors_endpoint_RFC -> implemented
One of my concern, the one implementing purchase suggestions operation is also still a big work in progress: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314
Maybe nice to file a bug in bugzilla like "Route to create, list, update, delete an order basket" or something of the like so that anyone can followup? If you do so, please add me to the CC's :)
Kind regards,
Arthur On 07/09/2020 16:40, Ola Andersson wrote:
Dear Koha Developers,
Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha.
The API draft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs...
We have had it posted for review in the Swedish user group – but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin.
Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document.
When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site.
Please leave comments before 21 September 2020.
/Swedish Koha User Group – the book vendor module/plugin task group
_______________________________________________ Koha-devel mailing listKoha-devel@lists.koha-community.orghttps://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 Koha-devel@lists.koha-community.org https://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/
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
Hi Ola, I've only skimmed the document, but I really dislike the proposal. It's not really describing an API. It's describing a non-standard workaround. I've seen integrations like this before, but I wouldn't recommend them, especially not for a new development. I'd suggest that the Koha plugin provides an API where the Vendor Service can send the JSON in the body of a background POST request using AJAX. Once that POST request is complete, they could then offer a link to navigate to Koha. That link would be to the Koha plugin and include an identifier returned by the earlier AJAX POST request. In Koha, the user logs in and sees the Vendor Service order as shown by the Koha plugin, and then you can action that order from there however you like. Easy. You would need to provide authentication credentials to the Vendor Service, but that's a reasonable thing to do when consuming an API. I hope that helps. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Ola Andersson Sent: Tuesday, 8 September 2020 12:41 AM To: koha-devel@lists.koha-community.org Subject: [Koha-devel] Review on Koha Order Module/plugin API Importance: High Dear Koha Developers, Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha. The API draft is described here: <https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BN s0dk/edit#heading=h.jtxo4681sgpr> https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs 0dk/edit#heading=h.jtxo4681sgpr We have had it posted for review in the Swedish user group - but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin. Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document. When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site. Please leave comments before 21 September 2020. /Swedish Koha User Group - the book vendor module/plugin task group
Hi again Ola, Apologies if my previous email came across as rude or aggressive. That certainly wasn't my intention. I can be overly enthusiastic about technology and overly focus on details. I am very excited by the work you have in mind. I think that it's great that the Swedish Koha User Group has created a task group for creating a Order module/plugin for Koha. That use case seems like a good candidate for a Koha plugin. I do have critical feedback for the proposed design, but one of the advantages of Koha plugins is that it is easy to iteratively develop them. Actually, I also have a few more questions. You mention that you haven't hired a contractor yet, but you've proposed a particular design. I'm guessing that design is coming from the Vendor? I wonder if it would be worthwhile having that vendor get in touch with us. I suspect that the Koha community would be able to give the best advice if we knew more about the Vendor service. Going back to the proposed design, if I understand correctly, I think you may run into issues doing the HTTP POST with the base64 encoded JSON data to Koha when unauthenticated, as the user will be prompted with a login screen that will perform another HTTP request to Koha, which means your "order" field will be lost. But maybe I'm missing something. Thanks for posting to the listserv, and looking forward to hearing more. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of dcook@prosentient.com.au Sent: Tuesday, 8 September 2020 11:44 AM To: 'Ola Andersson' <ola.andersson@ltu.se>; koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] Review on Koha Order Module/plugin API Hi Ola, I've only skimmed the document, but I really dislike the proposal. It's not really describing an API. It's describing a non-standard workaround. I've seen integrations like this before, but I wouldn't recommend them, especially not for a new development. I'd suggest that the Koha plugin provides an API where the Vendor Service can send the JSON in the body of a background POST request using AJAX. Once that POST request is complete, they could then offer a link to navigate to Koha. That link would be to the Koha plugin and include an identifier returned by the earlier AJAX POST request. In Koha, the user logs in and sees the Vendor Service order as shown by the Koha plugin, and then you can action that order from there however you like. Easy. You would need to provide authentication credentials to the Vendor Service, but that's a reasonable thing to do when consuming an API. I hope that helps. David Cook Software Engineer Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 From: Koha-devel <koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org> > On Behalf Of Ola Andersson Sent: Tuesday, 8 September 2020 12:41 AM To: koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> Subject: [Koha-devel] Review on Koha Order Module/plugin API Importance: High Dear Koha Developers, Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha. The API draft is described here: <https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BN s0dk/edit#heading=h.jtxo4681sgpr> https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs 0dk/edit#heading=h.jtxo4681sgpr We have had it posted for review in the Swedish user group - but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin. Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document. When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site. Please leave comments before 21 September 2020. /Swedish Koha User Group - the book vendor module/plugin task group
Hi again Ola, By seeing the email from David (and previous one from Martin), I just realize I focused on the "API matter" , and "Plugin matter" went completely out of my scope :) I guess you know already but plugins could be a great way to expand Koha API current capabilities by providing "contrib" routes (api extensions provided by plugins). Then, you could use plugin to leverage your developments from the "hassle" of submitting your changes to the community. Work done for the plugin could then maybe be reused at a later time to get integrated to koha with much less effort. Also about authentication, Koha Api also support "Basic Auth", which might help you get rid of user having to log in (again?), given the consumer app holds the koha user password in its data. Good luck! On 08/09/2020 15:27, dcook@prosentient.com.au wrote:
Hi again Ola,
Apologies if my previous email came across as rude or aggressive. That certainly wasn’t my intention. I can be overly enthusiastic about technology and overly focus on details. I am very excited by the work you have in mind.
I think that it’s great that the Swedish Koha User Group has created a task group for creating a Order module/plugin for Koha. That use case seems like a good candidate for a Koha plugin. I do have critical feedback for the proposed design, but one of the advantages of Koha plugins is that it is easy to iteratively develop them.
Actually, I also have a few more questions. You mention that you haven’t hired a contractor yet, but you’ve proposed a particular design. I’m guessing that design is coming from the Vendor? I wonder if it would be worthwhile having that vendor get in touch with us. I suspect that the Koha community would be able to give the best advice if we knew more about the Vendor service.
Going back to the proposed design, if I understand correctly, I think you may run into issues doing the HTTP POST with the base64 encoded JSON data to Koha when unauthenticated, as the user will be prompted with a login screen that will perform another HTTP request to Koha, which means your “order” field will be lost. But maybe I’m missing something.
Thanks for posting to the listserv, and looking forward to hearing more.
David Cook
Software Engineer
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Online: 02 8005 0595
*From:*Koha-devel <koha-devel-bounces@lists.koha-community.org> *On Behalf Of *dcook@prosentient.com.au *Sent:* Tuesday, 8 September 2020 11:44 AM *To:* 'Ola Andersson' <ola.andersson@ltu.se>; koha-devel@lists.koha-community.org *Subject:* Re: [Koha-devel] Review on Koha Order Module/plugin API
Hi Ola,
I’ve only skimmed the document, but I really dislike the proposal. It’s not really describing an API. It’s describing a non-standard workaround. I’ve seen integrations like this before, but I wouldn’t recommend them, especially not for a new development.
I’d suggest that the Koha plugin provides an API where the Vendor Service can send the JSON in the body of a background POST request using AJAX. Once that POST request is complete, they could then offer a link to navigate to Koha. That link would be to the Koha plugin and include an identifier returned by the earlier AJAX POST request.
In Koha, the user logs in and sees the Vendor Service order as shown by the Koha plugin, and then you can action that order from there however you like. Easy.
You would need to provide authentication credentials to the Vendor Service, but that’s a reasonable thing to do when consuming an API.
I hope that helps.
David Cook
Software Engineer
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Online: 02 8005 0595
*From:*Koha-devel <koha-devel-bounces@lists.koha-community.org <mailto:koha-devel-bounces@lists.koha-community.org>> *On Behalf Of *Ola Andersson *Sent:* Tuesday, 8 September 2020 12:41 AM *To:* koha-devel@lists.koha-community.org <mailto:koha-devel@lists.koha-community.org> *Subject:* [Koha-devel] Review on Koha Order Module/plugin API *Importance:* High
Dear Koha Developers,
Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha.
The APIdraft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs...
We have had it posted for review in the Swedish user group – but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin.
Pleaseshare thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document.
When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site.
Please leave comments before 21 September 2020.
/Swedish Koha User Group – the book vendor module/plugin task group
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://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/
Hi, Many thanks for the feedback on our outreach the other day. We will get back to the list with replies to the different questions raised by everyone in the coming days. I am not responding to each and every one now. As some have mentioned this is a first spec which can be further developed in iterations going forward. The order flow setup in its early form were initially proposed by one of our larger book vendors and expanded by the group, we intend in the first iterations to stick to it. This means we have something working, supporting our librarians ordering thousands of books from vendors, requesting this feature. I don’t see a collision between the proposed “punch-out” sending data once and the user continuing in the Koha client and a more refined handshake and redirect on succeed setup. We might be able to support both scenarios in the API and depending on vendor capacities and implementation they choose one over the other. The existing Koha API:s seem too divided/segmented for one vendor to call several API:s for every order. Rather we will have the plugin include the logic to, once order data has reach the plugin, together with the Koha user, using HTML forms, decide on what to do and how to store it (preferably using API:s) into Koha.. I hope this further explains the setup we had in mind. Thanks again for the feedback – keep it coming 👍 /Swedish order module/plugin task group Från: Ola Andersson Skickat: den 7 september 2020 16:41 Till: koha-devel@lists.koha-community.org Ämne: Review on Koha Order Module/plugin API Prioritet: Hög Dear Koha Developers, Here in Sweden we have started a task group in the Swedish Koha User Group to build a Order module/plugin to Koha that allow automatic influx of order data directly from a book vendor into Koha. The API draft is described here: https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs... We have had it posted for review in the Swedish user group – but we are thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin. Please share thoughts on the API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and anyone looking at the Google docs above can send comments/suggestions into the document. When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site. Please leave comments before 21 September 2020. /Swedish Koha User Group – the book vendor module/plugin task group
participants (6)
-
Arthur Suzuki -
Chris Cormack -
dcook＠prosentient.com.au -
Ola Andersson -
Renvoize, Martin -
Tomas Cohen Arazi