When you have a Borrower A, who makes n Checkouts from Branches 1,2,3.
overdue_notifications.pl generates one message_queue-table -entry for each Branch containing all the Items n.
Thus the same Items' overdue notifications are generated for Branches 1,2,3, regardless of the checkout-events branch of origin.
The Borrower ends up receiving 3 overdue notifications each having the same Items.
This is a fringe case and it is hard to imagine someone checking out from more than one branch during the same day, and that such a hardcore library addict would forget to return his books.
Not expecting anyone to fix this but reporting it because identified it during testing.
We are a multi-college library with 6 libraries spread around central London. There is some course overlap and it is NOT unusual for users to visit more than one library in a day. Whether these users are hardcore library addicts is debatable. But we did send out three ODUE emails to one user the other day, each listing the same 9 items as overdue, one email from each of the three libraries this dedicated library user had visited and borrowed items from. Ideally, in multi-library Koha sites the digest emails would become a digest of digests.
University of the Arts London
Hi Ray, I think what you describe might have been solved by 17470 - the item list now should only include items from the right branch.
I believe the original issue was fixed by bug 17470. There is also another bug for sending only one centralized message now:
Bug 17649 - Create only one message per borrower and overdue level
I am closing this as RESOLVED MOVED - please reopen if I am missing something.