What this category's data looks like
The materials for progress records and statistical verification in the organization of college admissions physical examinations come from three types of forms returned by each examination site and the re-examination stage: physical examination forms, re-examination applications, and restricted-major notifications. The physical examination form serves as the carrier of the initial examination conclusion and date signature; the re-examination application records the reason for re-examination and the acceptance time; the restricted-major notification carries the notification and the receipt signature. Materials are summarized weekly into the progress table, whose fields include name, number, examination date, item, conclusion, signature, and receipt status. When entering this function, the three types of materials serve respectively as the source of record counts, the source of the re-examination criteria, and the source of notification receipts; the progress table and the statistical criteria description are formed accordingly, for reference in weekly or monthly reports.
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). The "progress table and statistical criteria description" are then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Main business database connection | Points to the main business database actually in use and is connectable, consistent with the database address | In the deployment environment, check whether the MONGODB_URI value is consistent with the database address, and view the connection result in the startup logs |
| Log database connection | Configured separately, or left empty per the instructions to reuse the main database | Check whether the log database variable is set, and verify the database to which logs are written; when it is not set, confirm that the main database is reused |
| Cache connection | The cache instance is connectable | Connect once to REDIS_URL with a client and verify the response; verify that the vector database pointed to by PG_URL is consistent with the deployment instructions |
| Physical examination forms and restricted-major notifications | Fields, dates, and signatures are complete, and notifications include receipts | Verify name, number, examination date, and signature one by one; list separately any that lack a signature or receipt |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the physical examination form and the re-examination application. Cause: the two are registered separately, without same-source verification and unified numbering.
- Symptom: the version of the restricted-major notification and the version referenced by the progress table are not synchronized. Cause: after the notification was revised, it was not written back to the progress table, and the criteria description still follows the old version.
- Symptom: after startup, the logs continuously report connection timeouts. Cause: the connection address is inconsistent with the actual instance, or the cache and vector database addresses were not filled in according to the deployment instructions.
How to verify the setup
This function's acceptance: connect once each to the main business database, log database, cache, and vector database, and verify the connection results in the startup logs; verify the values of the three variables MONGODB_URI, REDIS_URL, and PG_URL.
Business test: use one week of records to verify the totals, and see whether the criteria and exceptions are clearly stated.
- Check the selected vector database and address against the deployment instructions, and confirm that the main database is reused when the log database variable is left empty.
- Align one week of physical examination forms, re-examination applications, and restricted-major notifications by number, and verify name, quantity, date, and signature receipt one by one.