Skip to content

SmartClass Dispatch HubTimetable-driven classroom recording

Imports course timetables, binds rooms to smartclass-webcam-server devices, starts and stops each lesson's recording automatically, and keeps every stream id and photo id addressable in PostgreSQL.

What it is ​

smartclass-dispatchub owns the classroom recording schedule. It is the service between the academic timetable and the camera fleet:

  • Timetables in. A term plus its 节次 time table, then a CSV of course/teacher/room rows per teaching week. dispatchub validates every row and materializes concrete sessions.
  • Recordings out. For each session the scheduler asks smartclass-webcam-server to start recording before the lesson and stop it at the end, and stores the returned stream_id.
  • Artifacts on demand. Segments and photos are never mirrored: given a stored stream_id, dispatchub asks webcam-server for fresh download URLs (15-minute TTL) when a client asks for them.
  • Authorization delegated. All access is authenticated and authorized by teamusers; dispatchub keeps no local accounts.
  • Getting Started - run it locally against PostgreSQL.
  • Deployment - the fleet compose file and the full DISPATCH_* reference.
  • Permissions - the nine dispatch:* keys and the any > team > own ladder.
  • API Usage - import, schedule, record, fetch artifacts.
  • Operations - scheduler semantics, triage and outage behaviour.
  • API Reference - the generated reference and the OpenAPI document.