What this category's data looks like
This page addresses the graduate admissions re-examination and admission scenario, with materials consisting of re-examination plans, candidate score sheets, and adjustment lists. Re-examination plans are issued by admissions units and updated by batch, containing procedures, dates, and signature fields; candidate score sheets come from the scoring and score entry process and are organized by subject, date, and score fields; adjustment lists are exported from the adjustment system and contain candidate identifiers, adjustment directions, and receipt status. When these three enter the deployment, operations, and application handover function, each plays a different role: re-examination plans are used to check whether procedures and signatures are complete, candidate score sheets are used to check whether subjects, quantities, and dates are consistent, and adjustment lists are used to check whether list versions and receipts are complete. Materials are updated on a rolling basis by batch, with fields mainly consisting of names, quantities, dates, and signatures, and each item must be compared one by one during handover.
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 handover-capable deployment status and operation records are then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Re-examination plan | Whether the batch, procedure dates, and signature fields in the plan are consistent with the handover form, and whether the name and date of the same record match across the two materials | Check the plan version, dates, and signatures item by item against the handover form, and record missing items when signatures or receipts are absent |
| Candidate score sheet | Whether the subjects, quantities, and dates in the score sheet are consistent with the re-examination plan and adjustment list, and whether the name and quantity of the same record match | Check subjects and quantities against the re-examination plan and adjustment list, and record items with inconsistent dates |
| Adjustment list | Whether the candidate identifiers, adjustment directions, and receipt status in the list are complete, and whether the version is synchronized with the current batch | Check the list version and receipts, and record discrepancies when receipts are missing or the version is not synchronized |
| Main business database connection variable | MONGODB_URI points to the main business database actually in use and can be connected | Check in the deployment environment that the variable value is consistent with the database address, and view the connection result in the startup logs |
Three common errors
- Symptom: The name, quantity, or date of the same candidate does not match between the score sheet and the adjustment list. Cause: The two materials are registered separately, no item-by-item comparison is made against the handover form, and discrepancies are not recorded.
- Symptom: The versions of the re-examination plan and adjustment list are not synchronized, and the old batch is still used during handover. Cause: Materials are updated on a rolling basis by batch, and the version and date are not checked before handover.
- Symptom: The adjustment list lacks signatures or receipts, and the handover form cannot be closed. Cause: Receipts are not archived together with the list, and only the list is checked during verification, not the receipts.
How to verify the setup
Acceptance of this function: 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; verify that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the actual instances.
Business test: check once item by item against the handover form to see which record is missing.
- In the deployment environment, check that the values of
MONGODB_URI,REDIS_URL, andPG_URLare consistent with the instance addresses, and view the connection results in the startup logs. - Check the names, quantities, dates, and signatures of the re-examination plan, candidate score sheet, and adjustment list item by item against the handover form, and record missing items.