What this category's data looks like
This category's data for compulsory education dropout prevention and control includes dropout risk ledgers, return-to-school persuasion records, and home visit records. The ledgers come from school and township surveys, updated weekly, with fields including student name, risk level, date, and signature; the persuasion records come from the persons responsible for persuasion, updated per instance, with fields including persuasion time, method, result, and receipt; the home visit records come from teachers, updated per instance, with fields including home visit date, subject, content, and signature. When these three types of materials enter the progress records and statistical verification function, the ledger plays the role of the baseline, the persuasion records play the role of the process, and the home visit records play the role of supporting evidence, jointly supporting the generation of the progress table and the statistical scope statement.
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 statement" is then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Fields include student name, risk level, date, and signature; check whether the number of ledger records is consistent with the statistical baseline | In the deployment environment, check the ledger records in the main business database pointed to by MONGODB_URI, and check whether the date and signature are complete |
| Return-to-school persuasion records | Fields include persuasion time, method, result, and receipt; check whether the name, quantity, and date of the same record match between the ledger and the persuasion records | Use a client to connect to REDIS_URL once to check the cached return, then compare the persuasion quantity and receipts of the two materials |
| Home visit records | Fields include home visit date, subject, content, and signature; check whether the versions of the home visit records and the ledger are in sync, and whether signatures or receipts are missing | Check the selected vector database and the PG_URL address against the deployment instructions, and check the signatures and receipts of the home visit records |
Three common errors
- Symptom: The name and date of the same student do not match between the ledger and the persuasion records. Cause: The two materials are entered separately, without field alignment and version synchronization.
- Symptom: Home visit records are missing signatures or receipts, yet the statistical totals still include them. Cause: The scope is not written into the header, and exceptional cases are not marked separately.
- Symptom: After startup, the logs continuously report connection timeouts. Cause: The connection variables are inconsistent with the actual database addresses, and the cache or vector database instance is unreachable.
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, and check the connection results in the startup logs; check whether the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses.
Business test: use one week of records to check the totals, and see whether the scope and exceptions are clearly written.
- In the deployment environment, check whether the value of this variable is consistent with the database address, and check whether the log database variable is set and verify the database to which logs are written.
- Use a client to connect to the cache instance once and check the return, and check the selected vector database and address against the deployment instructions.