*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
Historic Loan Rows Anonymization Process
Still to do: determine the time the weekly process will be run. We have asked for weekends, but the hosting team would prefer during the week. Sharon has asked that we avoid mornings because there are many automated reporting processes that use the Metadb database from 3am to 8am.
Here are the details of the process that was followed to replace the user_id field on historic loan rows with NULL on Friday, May 9:
| Step | Status | |
|---|---|---|
| 1 | The hosting team will keep the backup to Cornell's Metadb reporting database that is taken right before the anonymization process is run. Backups are incremental and are made on a rolling basis by the AWS Managed Service you use for Postgres databases. Backups can be kept for 7 days. | |
| 2 | As specified in the Metadb documentation, the hosting team will stop the server to prevent it from operating with an out-of-date cache. | |
| 3 | The hosting team will run the 2 anonymization scripts on the loan tables in the Metadb reporting database. | |
| 4 | As specified in the Metadb documentation, the hosting team will restart the server | |
| 5 | The hosting team will inform Sharon when the Steps 2 and 3 are complete. | |
| 6 | Sharon and Joanne will verify that the loan anonymization process has been successful and that normal data synchronization is continuing through test scripts that capture data stamps in loan_id rows. |
...
-Tom plans to put in a ticket to request patron identifiers be anonymized in fines and fees
-need to
Patron Notices
-need to review tables that keep patron data in this area
...