GDPR
(UXPROD-285)
|
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | GDPR |
| 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: |
|
||||||||||||||||
| Potential Workaround: | HK: See UXPROD-292 for workaround | ||||||||||||||||
| Epic Link: | GDPR | ||||||||||||||||
| Front End Estimate: | Large < 10 days | ||||||||||||||||
| Front End Estimator: | VBar | ||||||||||||||||
| Back End Estimate: | XXL < 30 days | ||||||||||||||||
| Back End Estimator: | VBar | ||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 2 | ||||||||||||||||
| 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): | R2 | ||||||||||||||||
| 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 implements Folio's support for the GDPR Right of Access. This specifies that a user is able to request from the platform, in human readable and understandable format, a report specifying exactly what personal data are currently retained in the Folio instance in their name. The goal of this feature is to gather all the data retained for a given user and from them generate a report. This report can be retrieved from an Edge (externally facing) API. There is currently no need to provide a user experience (or UI) within Folio to display such the report. Estimates from stories: |