...
Discussion Items:
Time | Item | Who | Description | Goals/Info/notes | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
5min | Administrivia | |||||||||||
30Min | Request Anonymization | Thomas Trutt | Ticket:
Questions i have:
| We cannot use API for request anonymization – has to do with Circ Log. Loan anonymization is editing the Circ Log directly – no API exists that allows us to go in and remove patron barcode. Thomas' questions for the team:
Jana Freytag – hopes the anonymization doesn’t clear out the number of requests (for the library, for the item) – Julie Bickle – each request will have a UUID, there’s probably a way to pull reports, we need to make sure this count data isn’t lost – Cheryl Malmborg – we do need to add patron statistical data to the request app (patron type) so we don’t lose that Amelia Sutton - It looks like requests save the following patron information: requester__barcode requester__last_name requester__first_name requester__middle_name proxy_user_id proxy__barcode proxy__last_name proxy__first_name proxy__middle_name Thomas Trutt – instead of request creation writing metadata at time of request, can do it at time of anonymization, David Bottorff – no we purposely did it at the time of creation because patrons can change patron type and we want to capture that initial information. Amelia Sutton - I am looking through the requests data and I'm not seeing a direct connection between a request and its associated loan – Thomas Trutt – not all requests result in a loan Thomas Trutt – will work on writing this up more, will ping Stephanie Buck to see if they can wrap this into their work |