Bug 33196 - Terminology: rephrase Pseudonymization system preference to be more general
Summary: Terminology: rephrase Pseudonymization system preference to be more general
Status: RESOLVED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: System Administration (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor (vote)
Assignee: Katrin Fischer
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-03-10 15:43 UTC by Aude Charillon
Modified: 2023-12-28 20:47 UTC (History)
5 users (show)

See Also:
Change sponsored?: ---
Patch complexity: Trivial patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
23.05.00,22.11.06,22.05.14, 21.11.22


Attachments
Bug 33916: Generalize pseudonymization system preference description (2.93 KB, patch)
2023-03-17 22:46 UTC, Katrin Fischer
Details | Diff | Splinter Review
Bug 33196: Generalize pseudonymization system preference description (2.97 KB, patch)
2023-03-22 09:07 UTC, David Nind
Details | Diff | Splinter Review
Bug 33196: Generalize pseudonymization system preference description (3.03 KB, patch)
2023-04-27 18:35 UTC, Lucas Gass
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Aude Charillon 2023-03-10 15:43:17 UTC
The Pseudonymization system preference description in the staff interface is: "Disable/Enable pseudonymization to comply with GDPR for personal information. Patrons and transactions will be copied to a separate table for statistics purpose."

GDPR is a European Union (and, at time of writing, UK) law; it makes the system preference look irrelevant for libraries outside this area. However, this is not correct: pseudonymization may be useful for libraries anywhere.

The system preference description should be changed to reflect this. Instead, it could be something like: "Disable/Enable pseudonymization to help improve security in the way you store personal information. Selected patron and transaction fields will be copied to a separate table for statistics purposes."
Comment 1 Katrin Fischer 2023-03-17 22:46:28 UTC
Created attachment 148390 [details] [review]
Bug 33916: Generalize pseudonymization system preference description

The Pseudonymization system preference description in
the staff interface is: "Disable/Enable pseudonymization
to comply with GDPR for personal information. Patrons and
transactions will be copied to a separate table for
statistics purpose."

GDPR is a European Union (and, at time of writing, UK) law;
it makes the system preference look irrelevant for
libraries outside this area. However, this is not correct:
pseudonymization may be useful for libraries anywhere.

This generalized the system preference description and
only uses GDPR as an example instead of the only purpose.

It also updates the fields listed to more closely reflect
the labels on the patron form.

To test:
* Search for "Pseudonymization" in the systme preferences
* Verify that the description of the system preference is
  very GDPR
* Apply patch
* Verify the system preference description is improved
Comment 2 David Nind 2023-03-22 09:07:02 UTC
Created attachment 148506 [details] [review]
Bug 33196: Generalize pseudonymization system preference description

The Pseudonymization system preference description in
the staff interface is: "Disable/Enable pseudonymization
to comply with GDPR for personal information. Patrons and
transactions will be copied to a separate table for
statistics purpose."

GDPR is a European Union (and, at time of writing, UK) law;
it makes the system preference look irrelevant for
libraries outside this area. However, this is not correct:
pseudonymization may be useful for libraries anywhere.

This generalized the system preference description and
only uses GDPR as an example instead of the only purpose.

It also updates the fields listed to more closely reflect
the labels on the patron form.

To test:
* Search for "Pseudonymization" in the systme preferences
* Verify that the description of the system preference is
  very GDPR
* Apply patch
* Verify the system preference description is improved

Signed-off-by: David Nind <david@davidnind.com>
Comment 3 David Nind 2023-03-22 09:08:58 UTC
Comment on attachment 148390 [details] [review]
Bug 33916: Generalize pseudonymization system preference description

I edited the commit to change the bug number in the title from 33916 to 33196.

A nice improvement 8-).
Comment 4 Lucas Gass 2023-04-27 18:35:24 UTC
Created attachment 150311 [details] [review]
Bug 33196: Generalize pseudonymization system preference description

The Pseudonymization system preference description in
the staff interface is: "Disable/Enable pseudonymization
to comply with GDPR for personal information. Patrons and
transactions will be copied to a separate table for
statistics purpose."

GDPR is a European Union (and, at time of writing, UK) law;
it makes the system preference look irrelevant for
libraries outside this area. However, this is not correct:
pseudonymization may be useful for libraries anywhere.

This generalized the system preference description and
only uses GDPR as an example instead of the only purpose.

It also updates the fields listed to more closely reflect
the labels on the patron form.

To test:
* Search for "Pseudonymization" in the systme preferences
* Verify that the description of the system preference is
  very GDPR
* Apply patch
* Verify the system preference description is improved

https://bugs.koha-community.org/show_bug.cgi?id=33196
Signed-off-by: David Nind <david@davidnind.com>
Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
Comment 5 Lucas Gass 2023-04-27 18:36:12 UTC
The changes all make perfect sense, the QA script doesn't complain. An easy PQA.
Comment 6 Tomás Cohen Arazi 2023-05-05 15:14:50 UTC
Pushed to master for 23.05.

Nice work everyone, thanks!
Comment 7 Martin Renvoize 2023-05-12 15:23:55 UTC
Many hands makes light work, thankyou everyone!

Pushed to 22.11.x for the next release
Comment 8 Lucas Gass 2023-06-13 16:25:14 UTC
Backported to 22.05.x for upcoming 22.05.14
Comment 9 Danyon Sewell 2023-07-21 02:44:51 UTC
Backported to 21.11.x for upcoming 21.11.22.