[UXPROD-4302] Request anonymization - thin thread Created: 12/May/23 Updated: 05/Feb/24 |
|
| Status: | Open |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Thomas Trutt | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cornell-access-services, support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Development Team: | None | ||||||||
| PO Rank: | 0 | ||||||||
| Description |
|
Current situation or problem: As an institution we have a need to anonymize closed requests in the request’s app as well as corresponding data in the circulation log, breaking the link to the patron record. Some data should be retained for reporting purposes. In scope
Out of scope
Use case(s) Proposed solution/stories Create a POST api endpoint similar to ** /loan-anonymization {*}t*hat would allow library staff to kick off an anonymization process. This process could be based on the loan anonymization process already implemented.
Links to additional info This a thin thread of: https://folio-org.atlassian.net/browse/UXPROD-1041 until a full implementation of the anonymization process can be added. Questions
|