https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39879 Steve, OSLRI, USA <sspohn@oslri.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bywater@oslri.net -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39879 Lisette Scheer <lisette@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lisette@bywatersolutions.co | |m --- Comment #1 from Lisette Scheer <lisette@bywatersolutions.com> --- (In reply to Steve, OSLRI, USA from comment #0)

Currently, it appears that pseudonymization only captures checkouts, renewals and returns. I'd like to suggest that 'localuse' transactions be captured as well.

Since pseudonymization is a pathway to retaining anonymized data on a journey to patron privacy which would include using the clean-up cron, we'd want to be sure not to lose this data.

Hi Steve, With Bug 32440 cleanup_database can be used to selectively delete transactions based on type, so local use can be left while other statistics are deleted after pseudonymization. Since local use doesn't include patron information, it seems to me that leaving them in the statistics table with the new setting for cleanup database should work. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32440 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39879 Thibault Keromnès <thibault.keromnes@univ-paris8.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE CC| |thibault.keromnes@univ-pari | |s8.fr --- Comment #3 from Thibault Keromnès <thibault.keromnes@univ-paris8.fr> --- I believe it's the same issue as bug32441, let me know if I'm wrong about marking it a duplicate. *** This bug has been marked as a duplicate of bug 32441 *** -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39879 --- Comment #5 from Pedro Amorim <pedro.amorim@openfifth.co.uk> --- Created attachment 197203 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=197203&action=edit Bug 39789: Add ability to specify an alternative header to X-Forwarded-For for finding the real ip address Some services ( such as CloudFlare ) use alternative heads to X-Forwarded-For. Koha should be able to use a custom header instead of X-Forwarded-For if needed. This patch updates the feature to allow both the custom header and X-Forwarded-For to work harmoniously For example, CloudFlare has it's own custom header. This patch allows a site to be configured for Cloudflare's proxy before the proxy is enabled. Test Plan: 1) prove t/Koha/Middleware/RealIP.t Signed-off-by: Lin Wei Li <lin-wei.li@inLibro.com> Signed-off-by: Pedro Amorim <pedro.amorim@openfifth.co.uk> -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.