GDPR Support (Later) (UXPROD-1641)

[UXPROD-287] GDPR User Consent Created: 03/Mar/18  Updated: 12/Apr/23

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
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to UXPROD-304 UX Rendering of statement of intent a... Open
relates to UXPROD-305 UX Rendering of user form to collect ... Open
relates to UXPROD-306 Authentication Hooks for User Consent Open
relates to UXPROD-308 User Loan Hooks for User Consent Open
relates to UXPROD-309 Patron Portal Hooks for User Consent Open
relates to UXPROD-310 Configuration UX for User Consent Open
Potential Workaround: HK - Workaround, Either the university system gathers consent for all services provided by the university (including the library) or the library has the patron sign a form either on paper or electronically that is kept on file.
Epic Link: GDPR Support (Later)
Front End Estimate: XL < 15 days
Front End Estimator: VBar
Back End Estimate: XXL < 30 days
Back End Estimator: VBar
PO Rank: 104
PO Ranking Note: CB: Ranking same as calculated
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): R4
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   

This feature concerns itself with how Folio can help support the GDPR requirement for gathering User Consent for Processing.

Consent is intended to be recorded in systems external to the User domain, and quite likely outside of Folio itself. This feature provides the hooks to the user workflow that will trigger the interaction with the consent system.

Estimates from stories:
UXPROD-310 Open Configuration UX for User Consent FE: Medium < 5 days BE: Medium < 5 days
UXPROD-309 Open Patron Portal Hooks for User Consent FE: None BE: Medium < 5 days
UXPROD-308 Open User Loan Hooks for User Consent FE: None BE: Small < 3 days
UXPROD-306 Open Authentication Hooks for User Consent FE: None BE: Small < 3 days
UXPROD-305 Open UX Rendering of user form to collect consent. FE: Medium < 5 days BE: Small < 3 days
UXPROD-304 Open UX Rendering of statement of intent and retention policies FE: Medium < 5 days BE: Small < 3 days

Note:
For most personal data GDPR libraries cannot base processing on consent and must not collect user consent: https://edpb.europa.eu/sites/default/files/files/file1/edpb_guidelines_202005_consent_en.pdf



 Comments   
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:05 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.