Deployment and Upgrades for School Timetables and After-School Scheduling: Coordinate Operations and Application Handover

School Timetables: review upgrades for operational handover. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This category covers primary and secondary school timetables and after-school service scheduling. Materials include the master timetable, teacher assignment table, and after-school service project table. Sources are the academic scheduling system and the after-school service management ledger. The update cadence rolls forward at the start of each semester, at month-end, and at class-adjustment nodes. Field characteristics are course name, assigned teacher, class, week number, date, project name, class-hour quantity, and signature column. When the master timetable enters deployment and operations, it takes on the role of global class-hour distribution and class week-number verification; the teacher assignment table takes on the role of verifying teacher class hours, class, and subject consistency; the after-school service project table takes on the role of verifying project name, number of participants, date, and receipt. After deployment and upgrade, the three types of materials must correspond item by item with the migration task records and data row index status, forming a handover-ready deployment status and operation record to hand over to operations or the next shift.

Configuration and implementation checks

This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image versions, migration task records, and data row index status. The "handover-ready deployment status and operation record" is then completed by operations handover and business use.

ObjectCheckVerification action
Main service and commercial edition image versionsBoth images are the same target version; check the version identifiers of the two images against the version notesOn the administrator version upgrade page, view the version identifiers of the two images and confirm both are the same target version
Historical chunk training task migrationTriggered only after the old instance has fully stopped and the old task lease has expired; view the execution record of this task on the administrator version upgrade pageCheck the stop status of the old instance in the cluster and the expiration time of the old task lease, then view the execution record of this migration task
Knowledge base rebuild status migrationTriggered only after the previous migration is complete; check the time and status of the two records against each otherFirst check the status of the historical chunk training task migration record, then check the time and status of the knowledge base rebuild status migration record
Data row index statusAfter migration it is the new index status system; sample one data row and check the status fieldSample one data row and check whether the status field is the new index status system

Three common errors

  • Symptom: the service starts but the data row status is still the old marker. Cause: the migration task was not executed or the data row status field was not checked after execution; version consistency does not equal data migration.
  • Symptom: the name, quantity, and date of the same record do not match between the master timetable and the teacher assignment table. Cause: the two materials were not synchronized to the same version, and signatures or receipts are missing.
  • Symptom: the script reports an error or the two image versions are inconsistent. Cause: the old instance was not fully stopped, the old task lease has not expired, or the latter migration did not wait for the previous one to complete.

How to verify the setup

This feature's acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in order; check the data row index status field; when connection parameters are involved, check the configuration records of MONGODB_URI, PG_URL, and REDIS_URL.

Business test: check item by item once against the handover sheet to see which record is missing; compare the master timetable, teacher assignment table, and after-school service project table item by item for name, quantity, date, and signature.

  • On the administrator version upgrade page, check the version identifiers of the two images and the execution records of the two migration tasks, and confirm the order and time.
  • Sample one data row to check the index status field, and check whether the connection records of MONGODB_URI, PG_URL, and REDIS_URL are consistent with the handover sheet.