GDPR Support (Later) (UXPROD-1641)

[UXPROD-288] GDPR User-centric Anonymisation Created: 03/Mar/18  Updated: 10/Dec/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: GDPR Support (Later)

Type: New Feature Priority: P3
Reporter: VBar Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: gdpr, privacy, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to RMB-366 Anonymizing/Scrubbing Metadata (creat... Draft
relates to RMB-373 Enable/disable logging date and user ... Open
relates to UXPROD-311 Add user alias storage Open
relates to UXPROD-312 Configuration settings for User pre-a... Open
relates to UXPROD-313 Rewire endpoints to expose alias userids Open
relates to UXPROD-314 User anonymization endpoint (clears a... Open
relates to UXPROD-315 Check-in Checkout changes to alias us... Open
relates to UXPROD-316 Loans to expose multi-userid interface Open
Potential Workaround: HK- See workaround for UXPROD-291
Epic Link: GDPR Support (Later)
Front End Estimate: Large < 10 days
Front End Estimator: VBar
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: VBar
Estimation Notes and Assumptions: CB: Vince's story estimates totalled more than was allowed for back-end estimate, so I just picked the largest we had and marked the confidence factor low. @vince, this probably should be broken up into smaller features so it doesn't have an estimate of > 30 days on the backend.
Kiwi Planning Points (DO NOT CHANGE): 12
PO Rank: 113
PO Ranking Note: https://docs.google.com/document/d/1bj058saKO-Kux7HI0vK5acfe-P6Lo62a6udcLDbtcRE/edit
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R2
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R5
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

In support of GDPR's Right of Erasure, this feature implements the ability to anonymise user personal data within the system, without compromising the integrity of other components such as circulation or requests.

The basic premise is that user personal data does not leave the user domain. The user personal data is pre-anonymised and only the anonynised version of user data are provided to other domains. The relationship between the anonymous versions and the personal version is mantained entirely within the user domain. When it comes time to anonymise specific user data. This can be done entirely within the user domain by breaking that connection.

Note that anonymising user data may be triggered by user created requests (Right to Erasure). But it can also be triggered by system processes that enforce the data retention policies that have been put forth, against which User Consent has been requested and obtained.

Estimates from stories
UXPROD-316 Open Loans to expose multi-userid interface None Medium < 5 days
UXPROD-315 Open Check-in Checkout changes to alias userids None Large < 10 days
UXPROD-314 Open User anonymization endpoint (clears aliases) None Medium < 5 days
UXPROD-313 Open Rewire endpoints to expose alias userids None Medium < 5 days
UXPROD-312 Open Configuration setttings for User pre-anonymization Large < 10 days Large < 10 days
UXPROD-311 Open Add user alias storage None Large < 10 days



 Comments   
Comment by Cate Boerema (Inactive) [ 25/May/18 ]

Vince, your story estimates totaled more than was allowed for back-end estimate, so I just picked the largest we had and marked the confidence factor low. VBar, this probably should be broken up into smaller features so it doesn't have an estimate of > 30 days on the backend.

Comment by Cate Boerema (Inactive) [ 05/Sep/18 ]

Removing the Q3 2018 fix version as this feature will not make that release.

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