Re: [Koha] GDPR - Statistics and anonymization

Hello, A bit of fresh news, I have submitted a bunch of patches that is ready to be tested. The main bug report is bug 24151 (Add a pseudonymization process for patrons and transactions) https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24151 I pushed a remote branch with everything

Re: [Koha] GDPR - Statistics and anonymization

Great, thanks! Can You add me to CC of bugs? I'm blac...@gmail.com on Bugzilla. Thank You. Michal út 26. 11. 2019 v 21:22 odesílatel Jonathan Druart < jonathan.dru...@bugs.koha-community.org> napsal: > Hello Michal, > > My next steps are the 3 ones I listed in my first post. > I have already

Re: [Koha] GDPR - Statistics and anonymization

Hello Michal, My next steps are the 3 ones I listed in my first post. I have already started to implement it and will open the bug reports in the next couple of days. Thanks for your interest :) Cheers, Jonathan Please note that Koha is the only ILS known to be powerful ;-) Le ven. 22 nov. 2019

Re: [Koha] GDPR - Statistics and anonymization

Jonathan, First of, wow, thank you SO much for taking on this task! Option 1 looks really good to me. One thing, however: we’re starting to get into demographic analysis, so having a zipcode in the borrowers_anonymized table would be hugely beneficial. We’re generating choropleth maps, and

Re: [Koha] GDPR - Statistics and anonymization

*Honorable Friends * *ABCD Software is a power full Library Automation Software* *FOR PRESENTATION Please Google Search: Rasheed ABCD* *https://www.slideshare.net/Rasheed1976/presentation-by-rasheedahmedmarch2011 *

Re: [Koha] GDPR - Statistics and anonymization

Hello Jonathan, I understand. You're right. So, can we document plan for new GDPR improvements on wiki? Next steps? Michal pá 22. 11. 2019 v 16:53 odesílatel Jonathan Druart < jonathan.dru...@bugs.koha-community.org> napsal: > The anonymized_borrowers table will not contain all data from >

Re: [Koha] GDPR - Statistics and anonymization

The anonymized_borrowers table will not contain all data from borrowers. Only a small part. Also we want to track down the transactions when they happen, it will be much more easier to implement and less error prone. How do you want to retrieve the transactions for a given patron when they are

Re: [Koha] GDPR - Statistics and anonymization

Hello Jonathan, sorry "we want to see them as results from borrower searches" shoub be "we want to hide them (anonymized borrower records) from all results from searches" Really we need to copy every patron into anonymized_borrowers at time of creation of their records? I think that must be done

Re: [Koha] GDPR - Statistics and anonymization

Michal, Redirection the discussion back to the list. What do you mean by "we want to see them as results from borrower searches"? What I understood is that libraries want to collect statistics on transactions even when the patron's records have been deleted. So: 1/ Create a patron (it's copied

Re: [Koha] GDPR - Statistics and anonymization

Thanks for the feedback Aaron, I will try and make it flexible, keeping it mind your need :) Le ven. 22 nov. 2019 à 00:47, asakov...@hmcpl.org a écrit : > > Jonathan, > > First of, wow, thank you SO much for taking on this task! > > Option 1 looks really good to me. One thing, however: we’re

Re: [Koha] GDPR - Statistics and anonymization

Thanks for the help Michal, What about the two options I have? Le jeu. 21 nov. 2019 à 17:58, Mike D. a écrit : > > Hi Jonathan, > I’m volunteer for debate about processes and anon tools and methods. I’m > ready to be tester of bugs. Koha is GDPR ready but some points could be > improved for

Re: [Koha] GDPR - Statistics and anonymization

Hi Jonathan, I’m volunteer for debate about processes and anon tools and methods. I’m ready to be tester of bugs. Koha is GDPR ready but some points could be improved for easier everyday usage in libraries. Because if something is clear and easy everybody do it without fear and stress. Thank You

[Koha] GDPR - Statistics and anonymization

Hello everybody, I have been contracted by KohaLa to work on some GDPR requirements. The main idea is to "anonymize" patron's data but letting the library access the transactions' statistics. I am going to present you what I am planning to implement, in order to collect ideas and answers. There