CUL Requirements for Access to Metadb Data

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

-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

-how does this process run?

-folio_circulation.loans_t_? The process does not remove user id on loans with the item_status available and the action of checked_in from this table?

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

-folio_circulation.loans 

-currently checked out user ids are not deleted

Current and Historical Request data to be purged

-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

-need to 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?

Fines and Fees

Patron Notices

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

-folio_email... etc.

------------------------------

What is in the zzz_ tables in Metadb?

 e.g., zzz___loan__t___

Is there a way to turn off the collection of historical data that is sensitive in Metadb?

What processes currently anonymize FOLIO data before it is synchronized with the Metadb reporting database?

Fine and fees data (from Ken via Simeon)

If we choose to forgive a fine or fee (without any collection attempt) then there is no financial record, and we are not subject to any retention requirement. The “without collection attempt” means that if we sent it to the bursar, even if we later forgave it, we should keep the record.

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.