What this category's data looks like
This page addresses the compulsory education dropout prevention and retention scenario, and the materials are dropout risk ledgers, persuasion-to-return records, and home visit records. The ledger is updated by semester and school stage, and its fields include student name, class, risk level, determination date, and responsible person's signature; persuasion-to-return records are generated per instance and include persuasion time, method, result, and parent or guardian receipt; home visit records are registered per household visit and include home visit date, teacher signature, and parent signature. When the three types of materials enter the deployment, operations, and application handover function, their roles differ: the ledger is the primary business data, while persuasion-to-return records and home visit records are process traces, and all are stored in the primary business database; the log database separately carries service operation records. During handover, consistency among version, connection, and task records is the criterion, and items are checked one by one according to the handover form; a missing signature or receipt is deemed an incomplete record.
Configuration and implementation checks
This step is executed by the connection configuration of the deployment environment (server side), not by the capability of a model node, and outputs whether the connection is available (service startup result and connection logs). "Handover-ready deployment status and operation records" are then completed by deployment handover and subsequent business processing. The connection address is configured by environment variables: the primary business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it reuses the primary database.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Whether fields, dates, and signatures are complete, and whether the name, quantity, and date of the same record match across the two materials | Check against the database pointed to by the primary business database connection variable MONGODB_URI, verify ledger fields and signatures one by one, then cross-compare names, dates, and quantities with persuasion-to-return records and home visit records |
| Persuasion-to-return record | Whether persuasion time, method, result, and receipt are complete, and whether the version is synchronized | Use a client to connect to the cache once and check the return of REDIS_URL; then check whether the persuasion-to-return record receipt is consistent with the ledger determination date |
| Home visit record | Whether the home visit date, teacher signature, and parent signature are missing, and whether the same household visit matches between the ledger and the home visit record | Check the selected vector database and address against the deployment instructions, inspect the vector database pointed to by PG_URL; then check household by household whether the home visit record signatures match the ledger household visits |
Three common errors
- Symptom: the name or date of the same student does not match between the ledger and the persuasion-to-return record. Cause: the two materials are registered separately, without cross-checking by the same student identifier and date criteria, and only a single material was reviewed during handover.
- Symptom: the persuasion-to-return record lacks a parent receipt, and the home visit record lacks a teacher signature. Cause: process traces were not archived in sync with the task, the handover form did not list signatures and receipts as mandatory check items, and missing items were not discovered.
- Symptom: after startup, the logs continuously report connection timeouts, and retrieval reports a vector database error. Cause: the connection variables are inconsistent with the actual instances, or the log database and primary database were shared without checking the write location, and the version was not synchronized.
How to verify the setup
This function's 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; check whether the values of the three variables MONGODB_URI, REDIS_URL, and PG_URL are consistent with the database addresses, and record the connection logs.
Business test: check item by item once according to the handover form to see which record is missing; check whether version, connection, and task records are consistent; a missing signature or receipt is recorded as incomplete.
- In the deployment environment, check that the value of the primary business database connection variable is consistent with the database address, check whether the log database connection variable is set, and check the database to which logs are written.
- Use a client to connect to the cache once and check the return, check the selected vector database and address against the deployment instructions, and check the fields, dates, and signatures of the ledger, persuasion-to-return records, and home visit records item by item according to the handover form.