We wondered if you would consider implementing a retention period? We at imin think this would be beneficial to you and also the users of your data.
Retention periods are discussed in the OpenActive Developer Docs (here), which suggest setting the state of "old" items (i.e. items with a startDate that is in the past) to "deleted" and then deleting them "at least 7 days from the point in time at which it transitioned to a "deleted" state".
This would help us immensely as we sometimes need to re-ingest your feed and it takes a while to get through it as it includes runs from 2016 onwards. Hopefully the ability to delete old sessions from the database (or move them to an archive) would also help you with cutting costs/increasing performance.
Hi,
We wondered if you would consider implementing a retention period? We at imin think this would be beneficial to you and also the users of your data.
Retention periods are discussed in the OpenActive Developer Docs (here), which suggest setting the state of "old" items (i.e. items with a
startDatethat is in the past) to"deleted"and then deleting them "at least 7 days from the point in time at which it transitioned to a"deleted"state".This would help us immensely as we sometimes need to re-ingest your feed and it takes a while to get through it as it includes runs from 2016 onwards. Hopefully the ability to delete old sessions from the database (or move them to an archive) would also help you with cutting costs/increasing performance.
Very best,
Dom