[Koha-devel] RFC for overdue notice enhancements

[Francois Charbonnier]

Salut Jonathan, Hi all,

My answers bellow.

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?

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/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...

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 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/20140825/917b062f/attachment.html>