Since most values in folio are also represented in metadb, for any anonymization effort to be effective the values must be anonymized in the reporting db as well as in folio. Additionally, for every main table the transform table will also need anonymized. Conveniently, this also allows values in metadb to serve as a shorthand for values in folio itself.

Relevant sources

Tables which may warrant special consideration:

folio_email.email_statistics

There is a lot of info scattered in here, and message delivery and contents could be relevant to fines (requiring a different anonymization period)

folio_users.users

The nature of this table might mean that anonymization requires special handling.

Values which may require anonymization

Relevant sources