<div dir="auto">Hi gaetan,<div dir="auto"><br></div><div dir="auto">Thanks for that - the talk has now been scheduled for Tuesday afternoon.</div><div dir="auto"><br></div><div dir="auto">Cheers, alex</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 17 Mar 2017 11:38, "Gaetan Boisson" <<a href="mailto:gaetan.boisson@biblibre.com">gaetan.boisson@biblibre.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've added you to the topics in the google doc, you can pick a time when you want to talk about this. can only make it in the afternoons, tuesday to friday. Would tuesday afternoon work for you?<br>
<br>
<br>
Le 15/03/2017 à 10:11, Alex Sassmannshausen a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Gaetan,<br>
<br>
Yes, for sure — I would be more than happy to present this at the hackfest!<br>
<br>
Alex<br>
<br>
<br>
Gaetan Boisson writes:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Alex,<br>
<br>
Would you consider presenting this work at the hackfest?<br>
<br>
I'd be very interested!<br>
<br>
Cheers,<br>
<br>
<br>
Le 22/02/2017 à 07:52, Alex Sassmannshausen a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hugo Agud writes:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Alex<br>
<br>
Wow! it sounds great.. I will try to do my best with this bug ;)<br>
</blockquote>
Fabulous! Let me know if you need a pointer.<br>
<br>
Alex<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Kindest Regards<br>
Hugo<br>
<br>
2017-02-21 11:57 GMT+01:00 Alex Sassmannshausen <<a href="mailto:alex.sassmannshausen@gmail.com" target="_blank">alex.sassmannshausen@gmail.co<wbr>m</a>>:<br>
<br>
Hello Kohites!<br>
<br>
Andrew and I have just finished a second major revision of our proposed<br>
interlibrary loans module for Koha. The code and bug can be found at<br>
[<a href="https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7317" rel="noreferrer" target="_blank">https://bugs.koha-community.<wbr>org/bugzilla3/show_bug.cgi?id=<wbr>7317</a>].<br>
<br>
We believe the code has now reached the maturity it requires for wider<br>
engagement, and, more importantly, it's now reached the maturity that it<br>
should be easy to get it up and running relatively easily in your<br>
development environments.<br>
<br>
Unfortunately we cannot deploy the module using sandboxes because<br>
backends are implemented as separate code projects.<br>
<br>
And we would *love* your comments thoughts and concerns about the module<br>
if you are interested in ILL!<br>
<br>
The final comment on the bug contains basic documentation for the Module<br>
as a whole, and also some installation instructions. But for reference,<br>
I've attached the same document to this email too.<br>
<br>
Below you will find some further high-level background and a roadmap of<br>
what we would like to achieve.<br>
<br>
For now, if you're interested in this module:<br>
• have a look at the bug, and get involved in the discussion!<br>
• try to set up the module in your dev environment. It should work<br>
easily on dev boxes and dev installs that track master.<br>
• let us know if you face any issues!<br>
• start a conversation with us if you might be interested in creating a<br>
backend for your country's / organization's ILL workflows.<br>
<br>
Finally, if you don't have access to a development environment, but you<br>
would be interested in becoming involved in this project, get in touch<br>
and we might be able to provide you with access to a testing<br>
environment!<br>
<br>
Best regards,<br>
<br>
Alex Sassmannshausen<br>
<br>
PTFS Europe<br>
<br>
1 High-level background<br>
═══════════════════════<br>
<br>
The ILLModule aims to provide a core framework against which different<br>
ILL workflows can be implemented within Koha. It achieves this by<br>
using 2 new tables as data store, and by using an extensible backend<br>
system to create 'connectors' to ILL providers.<br>
<br>
The data store consists of the illrequests and the<br>
illrequestattributes tables. The former is a traditional table that<br>
stores essential values associated with an ILL request. The later is<br>
a key/value store, linked to a row in the former. This store can be<br>
used to store arbitrary data provided by a backend.<br>
<br>
The backends implement highly customizable workflows for several core<br>
steps in the ILL management process.<br>
<br>
At the same time, each backend can extend the core steps (called<br>
defined as the `core_status_graph` in Koha/Illrequest.pm) with their<br>
own additional steps (defined as the `status_graph` in a backend's<br>
Base.pm).<br>
<br>
Each of these steps, both core and extensions, in turn can define any<br>
number of 'stages' required to complete each individual step.<br>
<br>
Each step has access to a template include file, which can dispatch on<br>
'stage'. This is mirrored by each step having a sub in a backend's<br>
Base.pm, which once again can dispatch on 'stage'. The subs in<br>
Base.pm have access to the full data store provided by the ILLModule;<br>
similarly the template includes have full access to Koha template<br>
features, including access to custom JS blocks through which, for<br>
instance, external APIs can be called.<br>
<br>
The main aim of this Koha module was to provide a core that is<br>
comprehensive enough to store core data to only have to implement ILL<br>
once in Koha, whilst being extensible enough so that virtually any ILL<br>
workflow can be implemented against this core.<br>
<br>
We believe we have achieved this. I'd be very interested to hear from<br>
you if you believe you have a workflow that cannot be captured by this<br>
(obviously, third party tools that do not provide API access will be<br>
virtually impossible to seamlessly integrate into Koha).<br>
<br>
2 Roadmap<br>
═════════<br>
<br>
The roadmap starts from the current release of code on the bugzilla<br>
issue.<br>
<br>
• Publication of mature beta level code (21 February 2017)<br>
⁃ public testing<br>
⁃ public discussion<br>
⁃ dogfooding<br>
<br>
• Augment core functionality (~ June 2017)<br>
⁃ add advanced configuration options for the core module<br>
⁃ add a standard system for configuring backends<br>
⁃ allow for an 'unmediated workflow'<br>
⁃ finalise 'generic requests' workflow<br>
<br>
• Meet Koha QA standards (~ July 2017)<br>
• Add unit tests to core ILLModule<br>
• Ensure UI respects Koha standards<br>
• Ensure Core code passes qa scripts<br>
<br>
• Addition of Documentation<br>
⁃ contributing a chapter to the Koha manual<br>
⁃ ensure all pod information is correct and complete<br>
⁃ ('writing your own backend' tutorial?)<br>
<br>
• Provide consistent error handling<br>
⁃ standard means through which a backend can 'throw' an error.<br>
⁃ replace uses of die with this standard route<br>
<br>
• Integration into Koha core in Koha 17.11<br>
<br>
_____________________________<wbr>__________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-communi<wbr>ty.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.o<wbr>rg/cgi-bin/mailman/listinfo/ko<wbr>ha-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org<wbr>/</a><br>
</blockquote>
______________________________<wbr>_________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-communit<wbr>y.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.or<wbr>g/cgi-bin/mailman/listinfo/koh<wbr>a-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org<wbr>/</a><br>
</blockquote></blockquote></blockquote>
<br>
-- <br>
Gaetan Boisson<br>
Chef de projet bibliothécaire<br>
BibLibre<br>
<a href="tel:%2B33%280%296%2052%2042%2051%2029" value="+33652425129" target="_blank">+33(0)6 52 42 51 29</a><br>
108 rue Breteuil 13006 Marseille<br>
<a href="mailto:gaetan.boisson@biblibre.com" target="_blank">gaetan.boisson@biblibre.com</a><br>
<br>
______________________________<wbr>_________________<br>
Koha-devel mailing list<br>
<a href="mailto:Koha-devel@lists.koha-community.org" target="_blank">Koha-devel@lists.koha-communit<wbr>y.org</a><br>
<a href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel" rel="noreferrer" target="_blank">http://lists.koha-community.or<wbr>g/cgi-bin/mailman/listinfo/koh<wbr>a-devel</a><br>
website : <a href="http://www.koha-community.org/" rel="noreferrer" target="_blank">http://www.koha-community.org/</a><br>
git : <a href="http://git.koha-community.org/" rel="noreferrer" target="_blank">http://git.koha-community.org/</a><br>
bugs : <a href="http://bugs.koha-community.org/" rel="noreferrer" target="_blank">http://bugs.koha-community.org<wbr>/</a></blockquote></div></div>