Events and facilities

Three unrelated things share this page because they are all about physical school life: the dates in the calendar, the laboratory equipment and the sessions booked against it, and the room master that the timetable and exam seating draw on. They do not feed each other automatically - an event does not reserve a room, and a lab session does not appear on the school calendar - so treat each as its own register with its own owner.

Events usage

• Create event at /events - title, start date, optional end date, category, location, and organiser.
• Events are academic calendar entries. The page picks an academic year and reads and writes /api/academic-calendar for that year.
• Choose a type of event, milestone, or other, and flag the ones that matter with the important marker.
• Publishing to the public site is a separate action in /school-website/events - the two stores are not linked.

Who owns each area

Laboratories usage

• /laboratories - maintain equipment (add/edit/deactivate/maintenance).
• Schedule sessions from list or week calendar; empty slot click opens Schedule Session with date/time prefilled.
• From timetable: POST /api/laboratories/sessions/from-timetable-entry books the next matching weekday (or a supplied date).
• Equipment carries a unique serial number and barcode, an operational status of in service, out of service, or maintenance, a custodian, and the last maintenance and next calibration dates.
• Safety incidents are recorded against equipment and can be reported by anyone who can view the module, not only by the people who maintain it.

What blocks a lab booking

• The timetable cell already has a lab session linked to it - one entry books one session.
• The period has no valid start and end time on the timetable structure.
• A date was supplied that does not fall on the weekday of that timetable entry.
• Another session already occupies the same lab room over an overlapping time on that date.
• The chosen equipment is inactive or out of service.

Infrastructure

• /infrastructure is the classroom master: room name, a unique room number, building, floor, desk count, and an optional link to an academic class.
• A utilisation view compares desk counts against the classes assigned to each room.
• Rooms defined here are what the timetable and exam venue screens choose from, so an incomplete room list limits both.
• It is a room register, not a maintenance log. Repairs and servicing are only tracked for laboratory equipment.