[Koha-devel] RFC for overdue notice enhancements

[Francois Charbonnier]

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 at inLibro.com <mailto:francois.charbonnier at 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/4f1ca08d13876439ef035af26e8f47833a90bc3a
> 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 at 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 at 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 at inLibro.com
>>
>> inLibro | pour esprit libre | www.inLibro.com
>>
>>
>> _______________________________________________
>> Koha-devel mailing list
>> Koha-devel at 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 at 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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20140827/81b29cca/attachment.html>