Page History

...

Current Loans are already purged of patron data, but Historical Loans are not

-need to research connection between loans and fine/fee transactions

-fines/fees need to be kept with loan data

-a job runs on a schedule to delete the user id on loans checked in (discharged) on the loan__t table. The user id is reset to NULL, which anonymizes the data

...

-folio_circulation.loans_t_ ? The FOLIO process does not remove user id on loans with the item_status available and the action of checked_in from this tablehistorical loan rows; we just need to replace user_id with NULL on all historical rows

-user patron group is retained and is used for reports about collection usage; no sensitve data is included in those reports

-script will be run manually initially, then library systems will run it as a chron job on Jenkins

-good to ask Alexander Kurash, lead developer for loans

-What about turning off historical data for loans

-our anonymization should be equal to FOLIO's anonymization

-need to determine whether or not removing userid from historical loan rows would negatively impact fine/fee data

-loan id stays the same throughout all loan trans

Current and Historical Request data to be purged

-not attached to fines, fees, or loans

-Request anonymization cannot currently be configured in FOLIO; Should we put in a Jira for this? Who from CUL works on Requests?  

-need to purge requester_id from folio_circulation.request__t when status is Closed, and not delete rows on this table for any other status

...

-how does this impact My Account on catalog, where I can look at my current requests? Data coming from FOLIO, not Metadb

-script will be run manually initially, then library systems will run it as a chron job on Jenkins

...

When a bill is sent to collections, what status is it given in FOLIO. This is data that we need to keep. We need to ask Michelle about this. 

-need to determine what we need to anonymize

Patron Notices

-need to review tables that keep patron data in this area

...