https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34498
--- Comment #5 from Aleisha Amohia <[email protected]> --- (In reply to Emily Lamancusa (emlam) from comment #4) > 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. Hey Emily, thanks for your thoughts here. The particular use case for our patch was that the library is using the ItemsDeniedRenewal system preference to exclude items from renewal based on collectioncode. So it's more permanent than a lost status, and I'm sure they had a reason for not using an item type which would've allowed them to use the circulation rules. It means that patrons are getting empty autorenewal notices if they have items from this collection checked out, which aren't eligible for auto-renew. Does that explain the purpose of this better? -- 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/
