Slots - what do we want/need? #17
Description
The current slot system is a bit of a mess. EMS creates slots that are not used - and the clients have to try to group sessions into meaningful periods.
We're also assuming that the system is for all day conferences - as it stands it doesn't really fit feks javaBins meetings.
What do we actually present?
Well - as far as I can see - JZ has three levels.
- Day
- Main Period Group
- Slot time
A slot is part of a group happens on a day.
Right now the apps/web team extract group and day based on logic that is JZ specific and happens in the client.
If we supported
- Outer
- Inner
- Slot
And then said that outer and inner were conference specific and defined manually then we could have day and the groupings defined as data rather than logic - and then for javaBin we could define oh - I don't know - month and week or whatever suits. We could even make the inner and outer non-time based (Outer could be oslo, bergen, sørlandet feks) if we had the correct parent/child relationships.
This is meant to be the start of a discussion - hope that others can join in before we actually decide what to make EMS do :)