What this category's data looks like
This page addresses the category of foreign teacher appointment and course scheduling. The materials come from three types of documents: appointment contracts, work permit materials, and course schedules. The update cadence is once after each batch of appointments and course scheduling is completed. Field characteristics include teacher name, ID number, contract start and end dates, permit number, course name, number of class hours, signature and receipt. When entering the progress records and statistical verification function, appointment contracts provide personnel and term fields, work permit materials provide compliance numbers and validity periods, and course schedules provide course and class hour fields. Together, the three support the generation of the progress table and the statistical scope description. Materials are stored in the database as records, the progress table is summarized weekly or monthly, and the statistical scope must state the counting rules and exception handling in the header, ensuring that the number of records matches the statistical count.
Configuration and implementation checks
This step is handled by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Appointment contract | Check whether fields, dates, and signatures are complete, and whether teacher name and ID number are consistent with the work permit materials | Compare contract start and end dates and signature fields one by one, check name and ID number, and reference MONGODB_URI to confirm records in the primary business database |
| Work permit materials | Check whether permit number, validity period, and receipt connect with the contract term | Compare permit number and validity period, check whether the receipt is missing, and reference PG_URL to confirm vector database retrieval results |
| Course schedule | Check whether course name, number of class hours, and dates correspond to the contract and permit materials | Compare course names and class hour counts item by item, check whether dates fall within the contract period, and reference REDIS_URL to confirm the cache connection |
| Progress table and statistical scope description | Check whether the number of records matches the statistical count and whether the scope is written in the header | Use one week of records to verify the total, check whether exceptions are clearly stated, and confirm that the header includes the counting rules |
Three common errors
- Phenomenon: the same teacher name is written inconsistently in the contract and permit materials. Cause: field formats were not unified during entry, and the versions of the two materials were not synchronized.
- Phenomenon: the number of class hours in the course schedule does not match the number agreed in the contract. Cause: after scheduling adjustments, the contract fields were not written back, and signature or receipt confirmation is missing.
- Phenomenon: after startup, the logs continuously report connection timeouts. Cause: the primary business database or cache connection address is configured incorrectly, and the service cannot establish a connection.
How to verify the setup
This feature acceptance: connect once to the primary business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and confirm that the instances corresponding to MONGODB_URI, PG_URL, and REDIS_URL are reachable.
Business test: use one week of records to verify the total, see whether the scope and exceptions are clearly stated, and confirm that the number of records matches the statistical count.
- In the deployment environment, check that the variable value is consistent with the database address, and check whether the database written to by the logs is configured separately or reuses the primary database.
- Use a client to connect once to the cache instance, check the return, and compare the selected vector database and address against the deployment instructions.