RFC for overdue notice enhancements
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 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092). 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 : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement Any comments, thoughts, suggestions are very welcome! Thanks François -- François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
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 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> 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 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092). 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 : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement
Any comments, thoughts, suggestions are very welcome!
Thanks
François
-- François Charbonnier, Bibl. prof. / Chef de produits
Tél. : (888) 604-2627 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com>
inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org 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/
You might want to check out http://splitter.koha-community.org for bugs touching the same files that are already in the works. On 19 Aug 2014 21:41, "Francois Charbonnier" < francois.charbonnier@inlibro.com> wrote:
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 francois.charbonnier@inLibro.com inLibro | pour esprit libre | www.inLibro.com 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 ( http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092). 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 : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement
Any comments, thoughts, suggestions are very welcome!
Thanks
François
-- François Charbonnier, Bibl. prof. / Chef de produits
Tél. : (888) 604-2627 francois.charbonnier@inLibro.com inLibro | pour esprit libre | www.inLibro.com
_______________________________________________ Koha-devel mailing listKoha-devel@lists.koha-community.orghttp://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 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/
Great tool, would be nice to have it linked on http://dashboard.koha-community.org/ Marc Am 20.08.2014 07:46, schrieb Renvoize, Martin:
You might want to check out http://splitter.koha-community.org for bugs touching the same files that are already in the works.
You can send me a pull request on gitorious for this or any other features you want in the dashboard Chris On 20 August 2014 8:02:17 pm NZST, "Marc Véron" <veron@veron.ch> wrote:
Great tool, would be nice to have it linked on http://dashboard.koha-community.org/
Marc
Am 20.08.2014 07:46, schrieb Renvoize, Martin:
You might want to check out http://splitter.koha-community.org for
bugs
touching the same files that are already in the works.
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org 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/
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hi, I put the link on the wiki start page - seemed like a good spot :) Katrin Am 20.08.2014 um 10:02 schrieb Marc Véron:
Great tool, would be nice to have it linked on http://dashboard.koha-community.org/
Marc
Am 20.08.2014 07:46, schrieb Renvoize, Martin:
You might want to check out http://splitter.koha-community.org for bugs touching the same files that are already in the works.
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org 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/
Salut François,
manage more than 3 notification levels 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?
notice fee management I development something like that (not rebased on master), see branch MT9888: http://git.biblibre.com/biblibre/kohac/commit/4f1ca08d13876439ef035af26e8f47... 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...
Overdue Notice/Status triggers tool 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 <francois.charbonnier@inlibro.com>:
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 francois.charbonnier@inLibro.com
inLibro | pour esprit libre | www.inLibro.com 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 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092). 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 : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement
Any comments, thoughts, suggestions are very welcome!
Thanks
François
-- François Charbonnier, Bibl. prof. / Chef de produits
Tél. : (888) 604-2627 francois.charbonnier@inLibro.com
inLibro | pour esprit libre | www.inLibro.com
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org 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 Koha-devel@lists.koha-community.org 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/
Salut Jonathan, Hi all, My answers bellow. François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> Le 2014-08-20 04:42, Jonathan Druart a écrit :
Salut François,
manage more than 3 notification levels 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?
Thanks for the heads-up. MJ's DB design looks like what we had in mind. We are going to base our development on MJ's work and submit a follow-up to his patch. The idea is to work first on the database design and then, on the UI. About the syspref VS some JS to manage the tabs, we will see that point when designing the UI. And no, we don't plan on refactoring the code.
notice fee management I development something like that (not rebased on master), see branch MT9888: http://git.biblibre.com/biblibre/kohac/commit/4f1ca08d13876439ef035af26e8f47... 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...
Thanks but it won't be necessary. We already have work done for this part. :^)
Overdue Notice/Status triggers tool I am not sure to understand the "on hold" checkbox. It should be checked on the last tab only, isn't it?
Nope. The idea is to have different set ups for available items and on-hold items (from the first letter to the last one). If the item is "on-hold" (another patron put an hold on it), you may want to send your patron a notice with a shorter delay to get back the items more quickly. With this new option, one could set up new rules specific to "on-hold" items. For example, the first letter could be sent after 7 days for an available book and after 2 days for a book if a patron requested it on hold.
Do you plan to refactore/export into a module (and add unit tests) for the overdue_notices.pl cronjob? We will add unit tests for our develpments but we haven't planned any refactoring.
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. Sounds like a good idea. I'll check with our client first.
Good luck! :)
Thanks!
Jonathan
2014-08-19 22:41 GMT+02:00 Francois Charbonnier <francois.charbonnier@inlibro.com>:
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 francois.charbonnier@inLibro.com
inLibro | pour esprit libre | www.inLibro.com 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 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092). 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 : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement
Any comments, thoughts, suggestions are very welcome!
Thanks
François
-- François Charbonnier, Bibl. prof. / Chef de produits
Tél. : (888) 604-2627 francois.charbonnier@inLibro.com
inLibro | pour esprit libre | www.inLibro.com
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org 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 Koha-devel@lists.koha-community.org 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/
Hi all, 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. 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... 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.). Any opinions for or against this new ergonomy? Thanks! François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> Le 2014-08-20 04:42, Jonathan Druart a écrit :
Salut François,
manage more than 3 notification levels 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?
notice fee management I development something like that (not rebased on master), see branch MT9888: http://git.biblibre.com/biblibre/kohac/commit/4f1ca08d13876439ef035af26e8f47... 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...
Overdue Notice/Status triggers tool 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 <francois.charbonnier@inlibro.com>:
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 francois.charbonnier@inLibro.com
inLibro | pour esprit libre | www.inLibro.com 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 (http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11092). 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 : http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement
Any comments, thoughts, suggestions are very welcome!
Thanks
François
-- François Charbonnier, Bibl. prof. / Chef de produits
Tél. : (888) 604-2627 francois.charbonnier@inLibro.com
inLibro | pour esprit libre | www.inLibro.com
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org 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 Koha-devel@lists.koha-community.org 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/
Le 15/08/2014 15:50, Francois Charbonnier a écrit : > Hello all, Hi François, > Here, you will find the RFCs : > http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement About the replacement cost, a question/an idea : the amount, iiuc, is ADDED to the price in items table. Would it be relevant to have 2 other options: * the default replacementprice is REPLACING the items.replacementprice * the default is a % of additionnal fee. I'm not sure there's a real case for the 1st, but I'm sure that, for some libraries, the "overhead" for an overdue document is something like 20% of the initial price. Purchase price = 20USD (or CAN ;-) ) replacementprice = 20 + 4 = 24USD. -- Paul Poulain - Owner / Associé-gérant Tel : +33 4 91 81 35 08 http://www.biblibre.com Open Source software for libraries Logiciels Libres pour les bibliothèques et les centres de documentation
Salut Paul! Answers bellow! François Charbonnier, Bibl. prof. / Chef de produits Tél. : (888) 604-2627 francois.charbonnier@inLibro.com <mailto:francois.charbonnier@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> Le 2014-08-25 07:56, Paul Poulain a écrit : > Le 15/08/2014 15:50, Francois Charbonnier a écrit : >> Hello all, > Hi François, > >> Here, you will find the RFCs : >> http://wiki.koha-community.org/wiki/Overdue_Notice_Enhancement > About the replacement cost, a question/an idea : the amount, iiuc, is > ADDED to the price in items table. Would it be relevant to have 2 > other options: > * the default replacementprice is REPLACING the items.replacementprice > * the default is a % of additionnal fee. > > I'm not sure there's a real case for the 1st, but I'm sure that, for > some libraries, the "overhead" for an overdue document is something > like 20% of the initial price. > Purchase price = 20USD (or CAN ;-) ) > replacementprice = 20 + 4 = 24USD. > The default replacement price will not be added to items.replacementprice value. It's not a value to adjust what we already have. The default replacement price will be used when there is no value in the items.replacementprice column. For example, the default replacement price is 20$. The patron lost the book A. items.replacementprice for book A = 30$. Long overdue cronjob will charge 30$ to the patron. The patron lost book B. items.replacementprice for book B = 0$ Long overdue cronjob will charge 20$ to the patron (the default replacement price). That's the feature we are going to implement. I agree, we could also update the mysql table to replace the 0 value by the default value but it means having access to the database, etc. With this development, librarians will be free to manage these values without having access to the database. I also like the idea of managing the replacement cost with a % of additionnal fee but it's a new feature. We don't have funding for this one so we won't add it to the development. Thanks for the suggestion.
participants (7)
-
Chris Cormack -
Francois Charbonnier -
Jonathan Druart -
Katrin Fischer -
Marc Véron -
Paul Poulain -
Renvoize, Martin