https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23260
--- Comment #91 from AgustÃn Moyano <[email protected]> --- (In reply to Katrin Fischer from comment #78) > Hi George, > > I think an option to clean it is not in question, I just think we should not > tie it to the same 'switch' - so libraries can make the decision to delete > both tables after a different number of days. > > This change as proposed currently would not only affect the cronjob. The > method changed is used in different areas: > > - batch_anonymise.pl cronjob > - When using the batch anonymize feature tool in the staff interface > - When a patron decides to delete their reading history from the OPAC > (OpacPrivacy etc.) > > So if I know I just returned a damaged book via the self check... I could > delete my reading history from the OPAC. Info might still be retrievable > somewhere, but I feel StoreLastPatron should be covering that use case. Hi Katrin, I've added a series of follow-ups that separates anonymization of checkouts from item's last borrower. I added a new cron job just for this, that's controlled by two sysprefs.. one to say if anonymizing item's last borrower is allowed and another to set how old it must be before it get's anonymized. Hope this is the one! -- 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/
