What this category's data looks like
This page is for the scheduling and class cancellation scenarios of training institution academic affairs. The materials include three types: class schedules, class cancellation records, and schedule change requests. The class schedule provides the week number, class, teacher, classroom, and time slot; class cancellation records reflect actual attendance, leave, make-up classes, and class hour deductions; schedule change requests carry the reason for the change, the original time slot and the new time slot, and approval signatures. When these three types of materials enter the database and operations functions, the class schedule is the scheduling baseline, class cancellation records are the original evidence for progress and statistics, and schedule change requests are the source for scope adjustments and exception explanations. Materials are updated weekly, and reconciled in a monthly summary. Field characteristics are date, class name, course name, quantity, signature or receipt. The progress table and statistical scope explanation are completed by business processing after deployment handover.
Configuration and implementation checks
This part is executed by the connection configuration of the deployment environment (server side), not by the capability of the model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope explanation" is completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Class schedule | Fields include date, class, teacher, classroom, and time slot; compare item by item with the original time slot and new time slot of the schedule change request; signatures or receipts are complete | Take one week's class schedule and schedule change requests and check them side by side, verify whether the same class and same course are consistent in date and time slot, and separately record entries missing signatures or receipts |
| Class cancellation records | Fields include attendance, leave, make-up classes, and class hour deduction quantity; compare item by item with the class schedule's date, class name, and course name; the version is based on the latest approval | Use one week's class cancellation records to summarize by class and course, verify whether the record count and statistical count match, and write the scope and exceptions in the header |
| Schedule change requests | Fields include original time slot, new time slot, reason, and approval signature; compare with the time slot after the class schedule change; for versions not synchronized, the approval receipt prevails | Extract one week's schedule change requests, verify whether the same record's name, quantity, and date are consistent in the class schedule and class cancellation records, and mark those not synchronized |
| Deployment environment connection configuration | The connection addresses of the main business database, log database, cache, and vector database are pointed to different instances by environment variables; when the log database is not configured separately, the main database is reused | Connect once to the main business database, log database, cache, and vector database item by item, verify that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses, and check the connection results in the startup logs |
Three common errors
- Symptom: The class name or class hour quantity of the same class cancellation record does not match between the class schedule and the statistical table. Cause: The two materials are maintained separately, names are not unified, and the quantity scope is not written in the header.
- Symptom: The schedule change request has been approved, but the class schedule and class cancellation records still show the old time slot. Cause: The version is not synchronized, and subsequent materials are not updated according to the latest approval receipt.
- Symptom: Class cancellation records lack signatures or receipts, and the weekly report total is inconsistent with the sum of individual entries. Cause: Exceptions are not clearly stated, and unconfirmed records are included in the total during statistics.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and verify that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses.
Business test: use one week's records to check the total, see whether the scope and exceptions are clearly written, and verify whether the record count and statistical count match.
- Take one week's class schedule, class cancellation records, and schedule change requests, summarize by class and course, verify the record count and statistical count, and write the scope and exceptions in the header.
- Check whether the deployment environment variables point to the main business database, log database, cache, and vector database respectively, and when the log database is not configured separately, verify whether the main database is reused.