Currently, the membership expiry cron runs and can be limited by branchcode, to exclude specific branches. However, it can not limit by patron category. It would be extremely helpful for libraries to be able to utilize a different way of using this cron by allowing the limiting by patron category.
Created attachment 107367 [details] [review] Bug 26062: Add --category option to membership_expiry.pl This patch adds a new option switch to the script, allowing to restrict the query for upcoming expirying patrons to a specific category. To test: 1. Apply this patch 2. Have upcoming expirying patrons with a certain category, and some others matching the expiry params (before/after), but with a different category 3. Run the script passing --category CAT (CAT being the chosen category) => SUCCESS: Only those on the specified category are picked 4. Sign off :-D Sponsored-by: ByWater Solutions
The delay for sending the notice is already a system preference - can we have the limit as a system preference too please? This would make it much easier for installations with multiple instances.
I agree with Katrin here - from a sysadmin standpoint it's much better for libraries to be able to configure these from the interface (it's easier for package maintenance/upgrades too, since users won't be inclined to modify the default cron files and then have to resolve those differences at upgrade time in apt)
I think comment 2 and comment 3 indicate that this should be Failed QA.
I think this is obsolete since Bug 28456 added --where arg.
Our library has patrons who we would like to exclude from notices to renew their accounts. It would make more sense to have this be something we could control from the staff interface, since we do not have control of the crons as a supported library.
On command line you can already achieve the limit on patron category using the --where parameter. I believe we should really move this into the GUI.