Page History

...

It’s crucial to approach deletions cautiously—starting with a deep analysis of the schema, understanding dependencies, and always backing up the data. Deletions should ideally be tested in non-production environments and wrapped in transactions to prevent irreversible mistakes.Recommendations

Tables in Metadb with Patron Identifiers

For reporting, folio_circulation, folio_audit, folio_feesfines, folio_derived, folio_email, folio_orders, and folio_patron_blocks have lots of tables and transformed tables that contain user_ids, requester IDs, recipient IDs or free text indicators of users associated with specific loans, requests, circ “events” or library materials. Most of the tables are very complex in their density of data and links to other data. Here is a list of table sets preliminarily identified – this list may not be complete (a ‘table set’ is the full table, plus the various extracted tables with current and/or archive states):

• Folio_audit.circulation_logs
• Folio_circulation.audit_loan
• Folio_circulation.check_in (can be linked by item_id and date/time to audit_loan table, which has user_id)
• Folio_circulation.patron_action_session
• Folio_circulation.loan
• Folio_circulation.request
• Folio_circulation.scheduled_notice
• Folio_email.email_statistics
• Folio_feesfines.accounts
• Folio_feesfines.feefineactions
• Folio_orders.po_line__
• Folio_patron_blocks.fee_fine_balance_changed_event
• Folio_patron_blocks.item_aged_to_lost_event
• Folio_patron_blocks.item_checked_in_event
• Folio_patron_blocks.item_checked_out_event
• Folio_patron_blocks.item_claimed_return_event
• Folio_patron_blocks.item_declared_lost_event
• Folio_patron_blocks.loan_closed_event
• Folio_patron_blocks.loan_due_date_changed_event
• Folio_patron_blocks.user_summary

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

...