<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:DengXian;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@DengXian";
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Segoe UI Light";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Hi Ola,<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>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. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>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.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>You would need to provide authentication credentials to the Vendor Service, but that’s a reasonable thing to do when consuming an API. <o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>I hope that helps.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>David Cook<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Software Engineer<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Prosentient Systems<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>72/330 Wattle St<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Ultimo, NSW 2007<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Australia<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Office: 02 9212 0899<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'>Online: 02 8005 0595<o:p></o:p></span></p></div><p class=MsoNormal><span style='mso-fareast-language:ZH-CN'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='mso-fareast-language:ZH-CN'>From:</span></b><span lang=EN-US style='mso-fareast-language:ZH-CN'> Koha-devel <koha-devel-bounces@lists.koha-community.org> <b>On Behalf Of </b>Ola Andersson<br><b>Sent:</b> Tuesday, 8 September 2020 12:41 AM<br><b>To:</b> koha-devel@lists.koha-community.org<br><b>Subject:</b> [Koha-devel] Review on Koha Order Module/plugin API<br><b>Importance:</b> High<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'>Dear <span style='color:black'>Koha Developers</span>,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'>Here in Sweden we have started a <span style='color:black'>task group</span> 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. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'>The API<span style='color:black'> draft</span> is described here: </span><span lang=SV style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'><a href="https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs0dk/edit#heading=h.jtxo4681sgpr"><span lang=EN-GB>https://docs.google.com/document/d/13EIWxTlN3Wo-8OtJuwu5serQu-dl-zdpK1qY5BNs0dk/edit#heading=h.jtxo4681sgpr</span></a></span><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'><o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'>We have had it posted for review in the Swedish user group – but <span style='color:black'>we</span> <span style='color:black'>are</span> thinking it would be valuable to get the larger Koha community to give feedback before we hire contractors to build the module/plugin.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif'>Please<span style='color:black'> </span>share thoughts <span style='color:black'>on </span>the <span style='color:black'>API and how to best implement it in Koha from a developer/QA perspective. All comments are appreciated and </span>anyone looking at the Google docs above can send comments/suggestions into the document.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif;color:black'>When the API is becoming more stable and comments have been looked at we could move it into the Koha wiki site.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif;color:black'>Please leave comments before 21 September 2020.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-size:14.0pt;font-family:"Segoe UI Light",sans-serif;color:black'>/Swedish Koha User Group – the book vendor module/plugin task group<o:p></o:p></span></p></div></body></html>