Summary: | Add new permission related to personal data | ||
---|---|---|---|
Product: | Koha | Reporter: | Michal Denar <black23> |
Component: | System Administration | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | claire.hernandez, george, gmcharlt, josef.moravec, lisette, magnus, paul.poulain, rbit |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Bug Depends on: | |||
Bug Blocks: | 18081 |
Description
Michal Denar
2018-01-18 10:03:00 UTC
It is probably too hard to detect reports or plugins that expose sensitive personal data. So a sysem for manually flagging reports and plugins that do, and then have special permissions for accessing them, sounds like a good idea. Reports flagged as containing sensitive data could perhaps also be blocked from being made public. Hi Magnus, I agree with your point of view. Only person who make report can make relevant decision. Semi automatic should come out from database items like: name, surname, date of birht, sex, adress, phone, email. We can say, thats personal data, be careful. |