*** This version of Confluence is for testing only and contains a copy of content from June 29th 2026. No changes will be preserved. ***
...
| 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. |
Data Anonymization Processes on the Metadb Database
Backups to Metadb Database
How often are backups made, how are they made, are the historical data backups overwritten with each new backup, are backups incremental or full?
Backups are incremental and are made on a rolling basis - they are made by the AWS Managed Service that the hosting team uses for Postgres databases.
Is it possible to keep the backup taken right before the anonymization process is run?
YES. This has been requested as part of the historic loan data anonymization procedure.
How long can the backups be saved?
The backups can be saved for 7 days.
Loan Anonymization Scripts
...
-need to review tables that keep patron data in this area
-folio_email... etc.
Cornell University Library Data Privacy
Policies pertaining to data privacy for Cornell Library patrons are described here:
- Commitment to Privacy: https://www.library.cornell.edu/about/commitment-to-privacy/
Cornell University Data Privacy Policy
Below are links to general information and policies regarding personal data use at Cornell University.
...
Data Anonymization Processes on the Metadb Database
Backups to Metadb Database
How often are backups made, how are they made, are the historical data backups overwritten with each new backup, are backups incremental or full?
Backups are incremental and are made on a rolling basis - they are made by the AWS Managed Service that the hosting team uses for Postgres databases.
Is it possible to keep the backup taken right before the anonymization process is run?
YES. This has been requested as part of the historic loan data anonymization procedure.
How long can the backups be saved?
The backups can be saved for 7 days.
Questions for Nassib
- Given increasing concerns about data privacy, is data anonymization on the roadmap and how will it work
- There is some loan anonymization functionality in FOLIO settings and there are plans to do the same for Requests
- Is metadb anonymization being developed with that interdependence in mind, or is it going to be an independent feature
- Will there be a feature to turn off the historical row creation for Metadb (as you do for LDP)
- Will there be a feature to make patron identifiers (e.g., user_id, requester_id) NULL in historical rows?
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?
Nassib says this has not yet been developed
...