[Koha-bugs] [Bug 32907] New: Add a field for personal ID
bugzilla-daemon at bugs.koha-community.org
bugzilla-daemon at bugs.koha-community.org
Wed Feb 8 09:26:25 CET 2023
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32907
Bug ID: 32907
Summary: Add a field for personal ID
Change sponsored?: ---
Product: Koha
Version: master
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: Patrons
Assignee: koha-bugs at lists.koha-community.org
Reporter: magnus at libriotech.no
QA Contact: testopia at bugs.koha-community.org
CC: gmcharlt at gmail.com, kyle.m.hall at gmail.com
I know storing social security numbers are a big no-no in some countries, but
in others it is perfectly fine and legal. At least libraries in Norway and
Sweden expect an ILS to store and handle these numbers. They are not considered
"top secret", but are used "everywhere" to identify people. In these countries
it looks like a strange omission that "personal IDs" are not handled properly
by the system, but have to be shoe-horned in as an extended patron attribute.
This also makes it harder than necessary to write reports, sync data from
external sources etc.
I propose that we
- add a database column like borrowers.personalid
- add a syspref called something like UsePersonalID
- set UsePersonalID to false as the default
- make all display and handling of personalid dependent on UsePersonalID
This way handling personal IDs will be opt-in only, and something that can be a
choice for libraries that want/need to use it.
Personal IDs could not only be social security numbers either, in an academic
library it could be used for e.g. ORCIDs: https://orcid.org/
A further enhancement to this would be to use personalid for logins, as a third
alternative to cardnumber and userid. This could also be governed by a syspref.
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
More information about the Koha-bugs
mailing list