https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34498
Emily Lamancusa (emlam) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |emily.lamancusa@montgomeryc | |ountymd.gov Status|Signed Off |Failed QA --- Comment #4 from Emily Lamancusa (emlam) <[email protected]> --- I don't think skipping the item completely in the auto-renewal cron job is the way to go here. If the item is denied renewal based on a permanent attribute, like item type, then it's either a bug or a configuration issue if that item is getting flagged for auto-renewal in the first place. On the other hand, if it's denied renewal based on a temporary status such as Lost status, that means it was eligible for auto-renewal at some point, and libraries might want to notify patrons rather than have it silently fail to renew. We should adjust the default notice template as the bug title suggests to better handle items_denied_renewal, and leave libraries the choice to make their own revisions based on whether they want to notify of that failure reason or not. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
