Created attachment 81489 [details] [review]
Bug 21712: Report anonymized patron records

The solution is rather limited but effective on itself.
It only needs an enabled pref BorrowersLog.
We log a specific ANONYMIZE action in Koha::Patron::anonymize.

Now we only need to add a SQL report like:
    select object AS borrowernumber, timestamp AS date_anonymized from action_logs where module='MEMBERS' and action='ANONYMIZE'
Depending on your needs, you could give this report a date parameter to
show all actions from a given date onwards.

Test plan:
[1] Add a patron.
[2] Enable BorrowersLog
[3] Run in perl this line:
    use Koha::Patrons; Koha::Patrons->find(BORROWERNUMBER)->anonymize;

    Or (much more work): enable GDPR, unsubscribe, set reflection delay to
    zero and anonymize delay to zero and run cleanup_database.pl.
[4] Check if the log contains a ANONYMIZE action for this patron.

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>

Hi Marcel,

can you explain how this will help with destroying the paper records? What kind of information is logged?

(In reply to Katrin Fischer from comment #2)
> Hi Marcel,
> 
> can you explain how this will help with destroying the paper records? What
> kind of information is logged?

It is a rather simple solution just based on logging the borrowernumber. If we need more information to find back a paper record, we could extend it. Perhaps with surname, firstname or so?
Perhaps Michal Denar could respond here too?

I think we'd need the name as they are often filed alphabetically and wihout the borrowernumber. Maybe the cardnumber too.

Hi,
if librarian use anonymisation tool, list of relevant users could be feature of this tool.

If library prefer use automatic way of anonymisation, would be nice to generate some kind report for identify paper contracts. 
Useful informations to find right contract are:
- surname
- name
- home branch

optional:
- date of birth
- adress
- barcode from library card

I prefer report as part of auto anonymisation workflow. List will be generate before anonymisation on based on same select query.

But this is my point of view. 

Mike

(In reply to Michal Denar from comment #5)
> I prefer report as part of auto anonymisation workflow. List will be
> generate before anonymisation on based on same select query.

This actually has my preference too. But I am waiting now first on some moving of the code on 21336 before spending more time.

(In reply to Marcel de Rooy from comment #6)
> (In reply to Michal Denar from comment #5)
> > I prefer report as part of auto anonymisation workflow. List will be
> > generate before anonymisation on based on same select query.
> 
> This actually has my preference too. But I am waiting now first on some
> moving of the code on 21336 before spending more time.

Note that if we add more fields to the log, we actually have a privacy issue there.

I want to take this back to movement. If we want to make anon process automatic and need to destroy paper contracts too, procees should be:
- automatic anon
- some kind of log with relevant info for search of paper contracts
- some trigger that destroy log if all papers contracts from bach was destroyed.

Any ideas how to handle it?

Thanks

21336 is moving again, so i am coming back here soon hopefully