Automated expiry #6

Open
opened 2024年10月14日 15:45:56 +02:00 by fnetX · 0 comments
Owner
Copy link

Data stored on the platform (especially recordings, but also associated metadata like submitted noted and email addresses) should automatically expire.

  • content that has no related database entry should be pruned regularly to avoid inconsistencies (e.g. leftover files that were not removed due to spurious errors)
  • uploaded recordings that were not submitted explicitly (originating from connection loss, browser crash and similar) should be pruned after at most some hours (probably one hour, maybe even less?)
  • submissions should be removed after the configured period (e.g. three days, one week)
Data stored on the platform (especially recordings, but also associated metadata like submitted noted and email addresses) should automatically expire. - content that has no related database entry should be pruned regularly to avoid inconsistencies (e.g. leftover files that were not removed due to spurious errors) - uploaded recordings that were not submitted explicitly (originating from connection loss, browser crash and similar) should be pruned after at most some hours (probably one hour, maybe even less?) - submissions should be removed after the configured period (e.g. three days, one week)
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/usertesting#6
Reference in a new issue
Codeberg/usertesting
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?