http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11642 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gmcharlt@gmail.com |kyle@bywatersolutions.com -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11642 --- Comment #1 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 24891 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=24891&action=edit Bug 11642 - Batch patron deletion/anonymization should not allow permanent destruction of patron data The Batch patron deletion/anonymization tool gives the option of destroying patron data or moving it to the "trash". I see know reason why we allow deletion of patrons without moving them to deletedborrowers first. We don't allow this kind of behavior for records or items, so why patrons? Furthermore it seems far to easy to mis-use this tool by accident, further exacerbating the situation. Test Plan: 1) Apply this patch 2) Verify you can no longer permanently delete patrons with the batch patron deletion/anonymization tool, instead they will always be moved to deletedborrowers. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11642 Chris Cormack <chris@bigballofwax.co.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |In Discussion CC| |chris@bigballofwax.co.nz --- Comment #2 from Chris Cormack <chris@bigballofwax.co.nz> --- Records and items aren't interesting to the FBI in the same way patron data is. I can see that as a valid reason for deleting them completely. Perhaps a better response is to do a "Are you sure you want to delete permanently .. there is no way to get them back?" Confirmation prompt is a better way than disabling this. -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11642 Jacek Ablewicz <abl@biblos.pk.edu.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abl@biblos.pk.edu.pl --- Comment #4 from Jacek Ablewicz <abl@biblos.pk.edu.pl> --- Additionally, in EU countries - ability to permanently remove patron personal data from computer systems may be actually required by law, as mandated by EU Data Protection Directive 95/46/EC (to be replaced in 2016 by even more strict version). Aka: "Right to be Forgotten" (= personal data has to be deleted when the individual withdraws consent or the data is no longer necessary and there is no legitimate reason for an organization to keep it). AFAIK, interpretations, implementations and practical enforcement of this directive widely varies by country, but still - it will be better to have such functionality in the system, just to be on the safe side ;). But I agree it's perhaps too easy to destroy patron data by mistake using this tool. Maybe "Move these patrons to the trash" should be default option instead of "Permanently delete these patrons"? -- You are receiving this mail because: You are watching all bug changes.

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11642 --- Comment #5 from Kyle M Hall <kyle@bywatersolutions.com> --- I've seen serious data loss because of bugs/misuse in the batch patron tools. I think it would be much better for all interactive Koha patron deletes to move them to deleted, and then have cleanup_database.pl delete them permanently. That way we have the most flexibility and safety possible. (In reply to Chris Cormack from comment #2)

Records and items aren't interesting to the FBI in the same way patron data is. I can see that as a valid reason for deleting them completely.

Perhaps a better response is to do a "Are you sure you want to delete permanently .. there is no way to get them back?"

Confirmation prompt is a better way than disabling this.

-- You are receiving this mail because: You are watching all bug changes.