We should start archiving records older than a certain date for PII security.
Notes from George:
For V1, I think we can create a new base that we selectively give access to, and archive records to that base. In the future, we can revisit whether we trust airtable enough to keep historical data on their servers.
We need to take care to consider how deleting inbound and intake records will affect other records that link to those tables. I'd suggest keeping around "stubs" of archived records. When we archive a record, instead of deleting it, we could change the status to Archived and deleting any PII from the record. I'm not sure what if any metadata we'll need to keep in the records to ensure that automation can continue to process them.
We should start archiving records older than a certain date for PII security.
Notes from George:
For V1, I think we can create a new base that we selectively give access to, and archive records to that base. In the future, we can revisit whether we trust airtable enough to keep historical data on their servers.
We need to take care to consider how deleting inbound and intake records will affect other records that link to those tables. I'd suggest keeping around "stubs" of archived records. When we archive a record, instead of deleting it, we could change the status to
Archivedand deleting any PII from the record. I'm not sure what if any metadata we'll need to keep in the records to ensure that automation can continue to process them.