School timetables (Advanced): first day must have first period, otherwise timetable schema is generated wrong
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SchoolTool |
Confirmed
|
Low
|
Unassigned |
Bug Description
Alternative bug title: timetable schema model doesn't match what is displayed to
the user (for assigning schedules to course sections).
Create a School Timetable like this:
Day 1 Day 2
Period 1 08:00-08:45
Period 2 09:00-09:45 09:00-09:45
Summary description (long description to follow): Period 1 for Day 1 should be
unavailable for booking. Unfortunately, when the 'manager' user assigns a
schedule to a course section, Period 1 still appears as an option for Day 1. You
can assign it, and you will see your course "nicely" scheduled in for the Period
1 on Day 1 (even though this was an invalid selection) in the response page. The
user has no warning that something has gone wrong up to this point! The falsely
selected period simply (i.e. quietly) doesn't show up in the calendar... :-(
Changed in schooltool: | |
assignee: | nobody → tom-hoffman |
Changed in schooltool: | |
assignee: | tom-hoffman → nobody |
importance: | Medium → Low |
status: | In Progress → Confirmed |
Here is the XML of the Timetable Schema:
<timetable xmlns="http:// schooltool. org/ns/ timetable/ 0.1"> testing_ select_ invalid_ periods_ 3</title> "WeeklyTimetabl eModel" >
<title>
<model factory=
<daytemplate>
<used when="Monday"/>
<period duration="45" id="Period 2" tstart="09:00"/>
</daytemplate>
<daytemplate>
<used when="Tuesday"/>
<period duration="45" id="Period 1" tstart="08:00"/>
<period duration="45" id="Period 2" tstart="09:00"/>
</daytemplate>
<daytemplate>
<used when="default"/>
</daytemplate>
</model>
<day id="Day 1">
<period id="Period 1"/>
<period id="Period 2"/>
</day>
<day id="Day 2">
<period id="Period 1"/>
</day>
</timetable>
You should be able to clearly see that there is something amiss here.