Currently, everything in the project relates to a single event.
As a consequence, when the event repeats we need to clean out the database and insert new values. This is an administrative task and should be exposed to users.
The proper way to do this is to add a new concept: "Event", with a start and end-date.
With this, all other resources (routes, teams, stations, audit-logs, scores, etc.) can be bound to that event.
We can allow users to create new events and they should be able to administer those events.
Warning: Currently we use temporary local user-accounts to manage the stations. Those user-accounts should also be bound to the event. We can add a "event-id" column to the users table or create a new "local-users" table to properly separate those local "staff-accounts" from the main application user-accounts. To be discussed...
Currently, everything in the project relates to a single event.
As a consequence, when the event repeats we need to clean out the database and insert new values. This is an administrative task and should be exposed to users.
The proper way to do this is to add a new concept: "Event", with a start and end-date.
With this, all other resources (routes, teams, stations, audit-logs, scores, etc.) can be bound to that event.
We can allow users to create new events and they should be able to administer those events.
Warning: Currently we use temporary local user-accounts to manage the stations. Those user-accounts should also be bound to the event. We can add a "event-id" column to the users table or create a new "local-users" table to properly separate those local "staff-accounts" from the main application user-accounts. To be discussed...