-
Notifications
You must be signed in to change notification settings - Fork 34
Activity option calendar v2
As a result of the recent discussion with members of the board and candidate board, this is brief overview of the required changes in the activity option calendar.
The board would like to have most features implemented before 24 June. Their complete wishes for that date may not be feasible, but also not strictly nessecary.
Organs will no longer create individual options, but instead plan an activity and set a limited number of options for that activity. These options will be referred to as tentative options or 'blue' options.
This part will most likely be the most work, both for front-end and backend (although this is mostly backend), but is pretty much required for most other features.
Each planned activity will be associated with 1. a number of options 2. a title 3. an optional text field for comments and 4. the preferred 'type' of the activity. 5. If the type is 'multiple days', a start and end date (both days). 6. The creator (the Organ).
The 'type' roughly corresponds to the time of day an activity is planned and is intended to provide information to the board to schedule the activities. The different types are 'lunch', 'afternoon', 'evening', 'day', 'multiple days'. The board will provide a description of these types to clarify what type should go on an activity.
Implementation of this feature should takes very little back-end work, and a bit front-end work. Should not take much time to implement in total.
Admins will be able to select one option from tentative options of an activity and mark it as the planned option ('green' option). This green option can later be removed, and will be replaced in the calendar by the actual activity, if the activity is approved. (So for the option calendar, all that is needed is that green options can be selected and removed). Once a planned option is selected, all tentative options for that activity should be removed.
Implementing this feature takes a little back-end time, but mostly front-end. Should not be too much work.
There will be the option to 'lock' the option calendar, which can be toggled by admin. Whenever the option calendar is lock, non-admins should not be able to add or update the dates of their options. (They should be able to change the title and comment field for an activity, however.)
Implementing this is just a simple permission check on the backend and a single button on the frontend. Should be easy.
Admins will be able to add/remove activities and options from activities on their own or on behalf of another Organ, but without any limits that the Organ would normally have, at any time (so also when the planning period is closed) and on any date. (This is mostly already implemented, but has to be modified a bit to work with the new data model.)
Implementation wise, this is not really a seperate feature, but something we have to keep in mind when developing the other features.
Organs can only create options for within a limited time frame, configurable by the board. For example, options can be planned only for the next quarter. The proposed system for this is that the admins can set a date range for the timeslots to plan the options in.
There will be a limit on the number of activities an organ/member per period.
The limits on the number of activities is configurable by the board for each organ.
- Improved admin interface: a list of all options, ordered by date.
- Possibility to set a time when planning options will be opened automatically.
- Contributing
- Architecture
- Components
- View helpers
- Sub-projects
- Archive