Instead of resetting the database, separate different data by tenant/event ID.
Allow the management of events based on the IDs.
This introduces possibility to store historical data and use the website for multiple groups of people without needing a separate instance. In essence, implement multi-tenant functionality in the service.
Person who is involved in multiple events should be able to see only the active ones as immediate options.
Historical data should be viewed in a separate page to minimalize the possibility for mistakes.
Instead of resetting the database, separate different data by tenant/event ID. Allow the management of events based on the IDs.
This introduces possibility to store historical data and use the website for multiple groups of people without needing a separate instance. In essence, implement multi-tenant functionality in the service.
Example: Separate IDs for 2023 and 2024 events.