Sure. The purpose of this big set of patches was to make it possible for koha to send notifications to borrowers upon checkout and check-in.
Next, you might be wondering why this seemingly simple task took 17 patches to accomplish. ;-) First, the high number of patches reflects the back and forth process of showing Dan and Galen what I had done and then going back to fix the flaws that they found in my work. Second, the specs required a high degree of configurability for this feature, so it wasn't just a matter of sending a notification when a check-in or checkout event happened. I also had to implement ways to allow administrators to define the conditions for when alerts could be sent out. (The UI for this is in admin/item_circulation_alerts.pl .) I also had to make it possible for users to set whether they wanted to receive their notifications via email or sms. Third, the spec required that multiple checkout or check-in events should be aggregated together. For example, if you checked out 10 books, you should only get 1 notification that lists the 10 books you checked out. You should NOT get 10 separate notifications, because that would be annoying. Anyway, to make this possible, I had to extend the messaging system so that I could find pending messages in the message_queue table and add more text to them. (The code for most of this work is in C4/Message.pm .) Hopefully, this clarifies the overall intent of this patch set. --beppu On Wed, Feb 4, 2009 at 1:42 AM, LAURENT Henri-Damien < [email protected]> wrote: > Hi John > Thanks for clarification. > It would be great to have a summary or a link to RFC in your patches, so > that we can better catch the general purpose of and the general architecture > implied by the handfull of patches sent. > Cheers. > -- > Henri-Damien LAURENT > >
_______________________________________________ Koha-devel mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-devel
