Patrons who have claimed returns items continue to receive overdue notices. This is problematic especially if the claim is they really did return the item or never had it. These patrons should not continue to receive overdue notices. There is currently not a way to exclude claimed returns from overdue notices. It would be nice to have a system setting or some other way to prevent overdue notices from going out on those items.
We would absolutely, 100% like to see this function. Staff have told us that they spend a lot of time discussing this with patrons, who are sometimes irate for having us contact them regarding an item that they've already told us they've RETURNED. We search our locations several times for these items, and receiving these notices creates extra work for everyone.
I'd rather see the ability to decide on a claims-returned-by-claims-returned basis whether or not an overdue notice is sent regarding claims returned items. I'd like to see a checkbox in the claims returned table that staff can check on or off to determine whether or not a notice is sent. That would be far more flexible than an all-on or all-off feature.
I agree with George that some flexibility (similar to ClaimReturnedChargeFee) where we could set it to "Ask if OD notices should trigger" "Always trigger OD notices" "Never trigger OD notices" Lisette
Testing this on master, overdue notices are not generated for items marked Claimed. I followed this test plan: 1 - create a LOST value for claims, put it in the ClaimReturnedLostValue 2 - make sure MarkLostItemsAsReturned is set to not mark claimed items as returned 3 - set your overdue notice triggers to send the first overdue notice at 1 day overdue 4 - check out 1 item to Patron A, manually setting the due date to 1 day ago 5 - mark Patron A's item claimed returned 6 - check out 1 item to Patron B, manually setting the due date to 1 day ago 7 - DO NOT mark Patron B's item claimed returned 8 - run the overdue cron (perl misc/cronjobs/overdue_notices.pl -v -t) 9 - Patron A did not get an overdue, but Patron B did Please comment and reopen if this is not the case in older versions. If so, I'd call that a bug rather than an enhancement.