What this category's data looks like
The materials for progress records and statistical verification of graduate admissions re-examination and enrollment come from the re-examination plan, the candidate score sheet, and the transfer list, updated weekly and monthly. The re-examination plan provides process nodes and dates, the candidate score sheet provides scores and rankings, and the transfer list provides transfer destinations and statuses. When these three types of materials enter the database and operations functions, each plays its own role in record writing and statistical scope description: the re-examination plan defines the nodes, the score sheet defines the scores, and the transfer list defines the destinations. Field characteristics include candidate ID, name, department, major, preliminary examination score, re-examination score, total score, date, signature, and receipt. If the name, quantity, or date of the same record does not match across two materials, if versions are not synchronized, or if a signature or receipt is missing, the progress table and the statistical scope description will not match. Only when the record count and the statistical count match and the scope is written in the header can it enter the weekly or monthly report.
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 log). The "progress table and statistical scope description" is then completed by the 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 |
|---|---|---|
| Re-examination plan | Fields include process nodes, dates, and signatures, and the name, quantity, and date must be consistent with the score sheet and transfer list | Check the dates and signatures item by item against the plan, score sheet, and transfer list, and see whether the receipts are complete |
| Candidate score sheet | Fields include candidate ID, preliminary examination score, re-examination score, and total score, and the record count must match the plan and transfer list | Use one week of records to check the totals, see whether the scope and exceptions are clearly written, and check the main business database pointed to by MONGODB_URI |
| Transfer list | Fields include transfer destination, status, and date, and the name, quantity, and date must be consistent with the plan and score sheet | Check the candidate IDs and total counts in the transfer list and score sheet, and see whether the cache instance at REDIS_URL is connectable |
| Vector database connection variable | Consistent with the vector database actually used, and check the selected vector database and address against the deployment instructions | Check PG_URL and the selected vector database address against the deployment instructions, and view the connection result in the startup log |
Three common errors
- Symptom: The name, quantity, or date of the same candidate does not match between the score sheet and the transfer list. Cause: The two materials are updated separately and are not checked against the same record.
- Symptom: The versions of the re-examination plan and the score sheet are not synchronized, and the progress table totals do not match the statistical scope description. Cause: After the materials are updated, they are not synchronized to the same version.
- Symptom: The transfer list lacks a signature or receipt, and it cannot be confirmed during statistical verification. Cause: Signatures and receipts were not fully collected during the material circulation step.
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, check the connection results in the startup log, and check that 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 that the variable value is consistent with the database address, see whether the variable is set, and check the database to which the logs are written.
- Use a client to connect once to the cache instance and check the return; check the selected vector database and address against the deployment instructions.