General overview of what information is shown in each subview of the new scheduler.
Key goal of the scheduler is to provide relevant context to schedulers so that they can make the best decisions for when to schedule games and optimize their limited ice time as much as possible without automatically scheduling their games for them
Day | Week | Month | Season | |
---|---|---|---|---|
Context questions/goals | What’s going on at each surface on that day? When exactly can a game be scheduled? | What are both teams doing on each day? What days are available to be scheduled? | Where can games be most optimally scheduled? | Similar to the month view, but on the scale of a whole season Birds eye view to comparatively show when teams have available time and when they’re not available |
Design | Single day with surfaces as each column and time along the y-axis to show a side-by-side view of what’s going on at each surface | Days of the week as each column, time along the y-axis. Could show surfaces as repeated time along y-axis (third dimension) | Traditional month calendar view that shows events as a list on each day | Teams (of the schedule) as columns, days (with available time slots) as rows Able to click on a time slot and select the opposing team (based on unscheduled games). Team will be based on if it’s a home or away time slot |
No game selected Schedule page | N/A (not enough context about which arenas to show) | N/A (too much data) | N/A (too much data) | Each cell shows the available time slots for a home or away game (marked distinctly), along with any other event slots (game, draft game, practice, activity) or scheduled tournament |
No game selected Office page |
| ? | N/A | N/A |
Game selected |
|
|
| No changes compared to selected state. Allows drag and drop into a time slot |