What this category's data looks like
Materials for general college entrance examination registration qualification review usually include the college entrance examination registration form, household registration and student status proof, and materials for children accompanying migrant workers. The registration form carries the candidate's basic information and examination subjects; the household registration and student status proof carries the household registration address, the school where the student status is held, and the years of attendance; the materials for children accompanying migrant workers carry supporting evidence such as the parents' residence and social insurance. The materials come from candidate submissions, school preliminary review, and re-review by the examination and enrollment agency, and are updated intensively during the registration season, with supplementary submissions and corrections occurring during this period. Field characteristics center on name, ID number, household registration address, student status school, attendance start and end dates, signature, and receipt. When entering the progress record and statistical reconciliation function, the registration form is the main record, while the household registration and student status proof and the materials for children accompanying migrant workers are attachments and supporting evidence; the progress table records status by review stage, and the statistical scope description clearly states the inclusion and exclusion rules. Together they support the reconciliation of totals for weekly or monthly reports.
Configuration and implementation checks
This part 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). The "progress table and statistical scope description" is then completed by deployment handover and subsequent business processing. The connection address is configured by environment variables: the main business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it will reuse the main database.
| Object | Check | Verification action |
|---|---|---|
| Main business database connection variable | Points to the main business database actually in use and is connectable; the registration form and review progress records are written to this database | In the deployment environment, check that the variable value is consistent with the database address, and connect once with a client to verify the return |
| Log database connection variable | Configured separately, or left empty as instructed to reuse the main database; the database to which logs are written can be distinguished from the business database | Check whether the variable is set, and verify the database to which logs are written; when left empty, confirm that the main database is reused |
| Cache connection variable | The cache instance is connectable and is used for temporary storage of streaming recovery images | Connect once with a client and verify the return; check that the connection address is consistent with the deployment instructions |
| Vector database connection variable | Consistent with the vector database actually in use; retrieval goes through the selected vector database | Check the selected vector database and address against the deployment instructions, and verify whether retrieval errors come from the vector database |
Three common errors
- Symptom: the same candidate's name or household registration address does not match between the registration form and the household registration and student status proof. Cause: the two materials are entered separately, without field-level comparison and receipt verification.
- Symptom: the attendance start and end dates in the materials for children accompanying migrant workers are inconsistent with the dates filled in the registration form. Cause: versions were not synchronized; after supplementary submission, only one place was changed, while the other still retained the old value.
- Symptom: the review record lacks a signature or receipt, but the progress table still shows received. Cause: receipt and signature are registered separately, and the statistical scope does not list missing signatures as an exception.
How to verify the setup
This function's acceptance: connect once item by item to the main business database, log database, cache, and vector database, and verify the connection results in the startup logs; for the main business database check MONGODB_URI, for the cache check REDIS_URL, for the vector database check PG_URL, and for the log database check according to whether the variable is set.
Business test: use one week of records to reconcile the totals, see whether the scope and exceptions are clearly stated, and confirm that the number of records matches the statistical count and that the scope is written in the table header.
- In the deployment environment, check that the connection variable values of the main business database, log database, cache, and vector database are consistent with the database addresses, and save the connection logs.
- Use one week of records to reconcile the totals, compare item by item the names, quantities, dates, and signatures in the registration form, household registration and student status proof, and materials for children accompanying migrant workers, and write exceptions into the scope description.