<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi all,<br>
<br>
Jonathan suggested to change the ergonomy of the "Overdue
notice/status triggers" tool. Our plan is to work on the database
structure to be able to set up more than 3 reminder levels and
Jonathan suggested that we gather together every rules in just one
tab. This way, we won't be limited by the number of reminder level
anymore.<br>
<br>
I like the idea because we will have a quick overview of every
rules and have a more flexible tool. Note that a part of this
development is to add also the ability to set up default rules
which means fewer rules if you have the same one for every patron
type. On the other hand, if you have a lot of specific rules, we
will have a bigger table...<br>
<br>
For now, we can choose to keep either the original ergonomy (X
tabs) or go for a new one (1 tab) which I like better (better
overview, with the new table structure, we will have search and
sort options, etc.).<br>
<br>
Any opinions for or against this new ergonomy?<br>
<br>
Thanks! <br>
<br>
<div class="moz-signature">
<style type="text/css">
.moz-signature {
color: #FFFFFF;
}
.sig_inlibro {
padding-top : 2px;
color: #888888;
font-family : "Trebuchet MS", verdana;
font-size: 90%;
}
.sig_content {
border-top: 2px solid #DDDDDD;
border-bottom: 2px solid #BFD13D;
background-color : #F6F6F6;
padding-left:10px;
}
.sig_inlibro a:visited, .sig_inlibro a:hover, .sig_inlibro a:link {
text-decoration: none;
color: #005B85;
}
.nom {
color: #005B85;
font-weight : bold;
}
.inlibro, .in {
color: #BFD13D;
}
.libro {
color: #005B85;
}
.in, .libro {
font-size : 120%;
}
.desc {
margin-bottom: 0;
padding-bottom: 5px;
}
.small {
font-size: 80%;
}
.tagline {
color : #00BCE4;
}
.sig_footer {
padding-left : 10px;
background-color : #EEEFEA;
}
</style>
<div class="sig_inlibro">
<div class="sig_content"> <span class="nom">François
Charbonnier,</span><br>
<span class="tagline small">Bibl. prof. / Chef de produits</span><br>
<p class="desc small"> Tél. : (888) 604-2627<br>
<a href="mailto:francois.charbonnier@inLibro.com">francois.charbonnier@inLibro.com</a>
</p>
</div>
<div class="sig_footer"> <span class="in">in</span><span
class="libro">Libro</span> <span class="tagline small">|
pour esprit libre |</span> <a class="small"
href="http://www.inLibro.com">www.inLibro.com</a> </div>
</div>
</div>
Le 2014-08-20 04:42, Jonathan Druart a écrit :<br>
</div>
<blockquote
cite="mid:CAJzKNY59QoGYV+W2_6OoYEYoN3LvZ-oXbP3zJOypUaEftVOMhQ@mail.gmail.com"
type="cite">
<pre wrap="">Salut François,
</pre>
<blockquote type="cite">
<pre wrap="">manage more than 3 notification levels
</pre>
</blockquote>
<pre wrap="">See bug 9296, MJ Ray already submitted some work for that (but seems stuck).
How do you plan to implement that? How would be the DB table structure?
I am not sure the pref is needed here, the number of tab could be
manage on the interface (with some JS: + add a tab, - remove a tab).
The page tools/overduerules.pl is quite dirty, I suppose you will
refactore it and create a new module (using DBIC), isn't it?
</pre>
<blockquote type="cite">
<pre wrap="">notice fee management
</pre>
</blockquote>
<pre wrap="">I development something like that (not rebased on master), see branch
MT9888: <a class="moz-txt-link-freetext" href="http://git.biblibre.com/biblibre/kohac/commit/4f1ca08d13876439ef035af26e8f47833a90bc3a">http://git.biblibre.com/biblibre/kohac/commit/4f1ca08d13876439ef035af26e8f47833a90bc3a</a>
I linked the "fixed_fines" value to the overdue rules instead of the notice.
Actually it is not at all the same goal, but it could help...
</pre>
<blockquote type="cite">
<pre wrap="">Overdue Notice/Status triggers tool
</pre>
</blockquote>
<pre wrap="">I am not sure to understand the "on hold" checkbox. It should be
checked on the last tab only, isn't it?
Do you plan to refactore/export into a module (and add unit tests) for
the overdue_notices.pl cronjob?
What about reworking on the tools/overduerules.pl ergonomic? Maybe it
could be better to have 1 line by rules (with all delay, mtt,etc.) and
remove tabs. Just a suggestion.
Good luck! :)
Jonathan
2014-08-19 22:41 GMT+02:00 Francois Charbonnier
<a class="moz-txt-link-rfc2396E" href="mailto:francois.charbonnier@inlibro.com"><francois.charbonnier@inlibro.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hello all,
This is a quick reminder in case you haven't noticed this email.
We are going to start the developments next week.
If you are working on something similar, think your work would conflict with
ours, now is a good time to let us know! ;^)
And thanks in advance for any comments, thoughts, suggestions you would
have.
Cheers!
François
François Charbonnier,
Bibl. prof. / Chef de produits
Tél. : (888) 604-2627
<a class="moz-txt-link-abbreviated" href="mailto:francois.charbonnier@inLibro.com">francois.charbonnier@inLibro.com</a>
inLibro | pour esprit libre | <a class="moz-txt-link-abbreviated" href="http://www.inLibro.com">www.inLibro.com</a>
Le 2014-08-15 09:50, Francois Charbonnier a écrit :
Hello all,
Halland County Library in Sweden is going to sponsor new features. Their
goals are to :
manage a reminder fee when a reminder is sent
manage different reminder delays depending on whether the item is
reserved or not, and is free of charge or has a rental fee.
We will start from a development inLibro did to manage invoices and fixed
costs that goes along
(<a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092">http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092</a>). Since, it
hasn't been upstreamed yet, we will close this report and re-work it for a
better integration with the new features.
The requirements were thought to comply Halland County Library needs but
also to be flexible and fulfill different settings. We also paid attention
to keep Koha's behaviour, so libraries can keep their original set up if
they doesn't need these new features.
Here, you will find the RFCs :
<a class="moz-txt-link-freetext" href="http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement">http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement</a>
Any comments, thoughts, suggestions are very welcome!
Thanks
François
--
François Charbonnier,
Bibl. prof. / Chef de produits
Tél. : (888) 604-2627
<a class="moz-txt-link-abbreviated" href="mailto:francois.charbonnier@inLibro.com">francois.charbonnier@inLibro.com</a>
inLibro | pour esprit libre | <a class="moz-txt-link-abbreviated" href="http://www.inLibro.com">www.inLibro.com</a>
_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a>
_______________________________________________
Koha-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Koha-devel@lists.koha-community.org">Koha-devel@lists.koha-community.org</a>
<a class="moz-txt-link-freetext" href="http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel">http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel</a>
website : <a class="moz-txt-link-freetext" href="http://www.koha-community.org/">http://www.koha-community.org/</a>
git : <a class="moz-txt-link-freetext" href="http://git.koha-community.org/">http://git.koha-community.org/</a>
bugs : <a class="moz-txt-link-freetext" href="http://bugs.koha-community.org/">http://bugs.koha-community.org/</a>
</pre>
</blockquote>
</blockquote>
<br>
</body>
</html>