Whenever positions change due to changes in our governing documents, we have to manually ensure these changes are reflected in our application. For instance, to add a new position we have to connect directly to the database and add a new row in the Positions table.
Additionally, these positions are assigned an id which needs to correspond to a group in Keycloak. If a new position is created in our application database, a corresponding new group needs to be created in Keycloak.
Describe the solution you'd like
Add an admin interface somewhere over on /committees/:slug to make it possible for normal users to manage positions in a committee, instead of just DWWW-developers with database access.
Describe alternatives you've considered
The current solution of connecting to the database is workable, but changes happen more often than you'd think and it's somewhat time consuming to make changes directly to the database.
Description
Whenever positions change due to changes in our governing documents, we have to manually ensure these changes are reflected in our application. For instance, to add a new position we have to connect directly to the database and add a new row in the
Positionstable.Additionally, these positions are assigned an id which needs to correspond to a group in Keycloak. If a new position is created in our application database, a corresponding new group needs to be created in Keycloak.
Describe the solution you'd like
Add an admin interface somewhere over on
/committees/:slugto make it possible for normal users to manage positions in a committee, instead of just DWWW-developers with database access.Describe alternatives you've considered
The current solution of connecting to the database is workable, but changes happen more often than you'd think and it's somewhat time consuming to make changes directly to the database.