Request anonymization - thin thread

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

• API endpoint to start the anonymization process.

• requesterId, firstName, lastName and barcode would be removed from the request’s app data.

• User data would be removed from corresponding entries in the circulation log data.

Out of scope

• UI interface to start the anonymization process.

• Automated or timed process to start the anonymization process.

• Detailed settings.

• Adding additional data to the request object for reporting purposes.

Use case(s)

Proposed solution/stories

Create a POST api endpoint similar to ** /loan-anonymization {}that 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

• Referencing UXPROD-1041, what extra fields should be added to the request’s data for reporting purposes? (New feature request)

• Would additional data need to be added to the request object before this feature could be implemented?

• Should all requests with a status of ‘CLOSED - %’ be anonymized our should users have to submit individual anonymization requests for each status they wish to anonymize.