Library Data Platform (LDP) Beta (UXPROD-1128)

[UXPROD-1888] Anonymization of personal data in LDP database Created: 16/Jul/19  Updated: 16/Sep/20  Resolved: 24/Mar/20

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Library Data Platform (LDP) Beta

Type: New Feature Priority: P2
Reporter: Nassib Nassar Assignee: Nassib Nassar
Resolution: Won't Do Votes: 0
Labels: ldp-platform, mandatory, po-mvp, reporting
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by REPTOOLS-113 Prototype anonymization of personal data Closed
is defined by REPTOOLS-123 Anonymize user ID Closed
is defined by REPTOOLS-124 Invert anonymization to operate on "a... Closed
Epic Link: Library Data Platform (LDP) Beta
Back End Estimate: XXL < 30 days
Back End Estimator: Nassib Nassar
Development Team: Reporting
PO Rank: 119
Rank: 5Colleges (Full Jul 2021): R4
Rank: Lehigh (MVP Summer 2020): R2
Rank: U of AL (MVP Oct 2020): R4

 Comments   
Comment by Tom Wilson [ 23/Aug/19 ]

Not exactly clear what this means. I understand the concept of anonymizing personal data, but some times we may want to look at say the historic record of a particular user. Will we be able to do that, or run a report, in FOLIO without going to the LDP?

Comment by Nassib Nassar [ 23/Aug/19 ]

Anonymization will be a configurable option that can be at least turned on or off. It will be needed by libraries that are under GDPR. Some limited support for reporting on historical user data will be possible if they are not anonymized. (Feel free to contact me for details)

Note that issues labeled as "mandatory" or "NFR" need not be ranked, as the rankings are not used.

Comment by Nassib Nassar [ 03/Sep/19 ]

This is a first pass at anonymizing data based on input from the data privacy working group. The LDP loader (by default) currently removes the values of the following attributes in user items, during the process of extracting data from FOLIO modules. I have also asked whether the barcode attribute should be removed as well.

$.username
$.personal.lastName
$.personal.firstName
$.personal.middleName
$.personal.dateOfBirth
$.personal.phone
$.personal.mobilePhone
$.personal.email
$.personal.addresses.description
$.personal.addresses.id
$.personal.addresses.countryId
$.personal.addresses.addressLine1
$.personal.addresses.addressLine2
$.personal.addresses.city
$.personal.addresses.region
$.personal.addresses.postalCode
$.personal.addresses.addressTypeId
$.personal.addresses.primaryAddress
Comment by Nassib Nassar [ 03/Sep/19 ]

An optional configuration parameter "disable_anonymization" is currently provided to allow disabling anonymization if needed.

Comment by Nassib Nassar [ 24/Mar/20 ]

We are investigating full GDPR compliance as an alternative to anonymization.

Generated at Fri Feb 09 00:19:21 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.