What this category's data looks like
Self-taught examination registration records and graduation review materials fall into three categories: registration archives (including basic candidate information, exemption records, and transfer records), course qualification certificates (including course codes, qualification dates, and scores), and graduation application forms (including major names, main examining institutions, signatures, and receipts). These materials are submitted in batches by provincial examination offices, main examining institutions, and study assistance centers according to examination periods, and the update cadence is synchronized with registration record changes. The field characteristics are multiple sources and multiple versions, and the names and dates of the same record in different materials need to be cross-compared. When entering the deployment, operations, and application handover function, registration archives serve as the main business data verification object, course qualification certificates serve as the basis for quantity and date comparison, and graduation application forms serve as the object for completeness checks of signatures and receipts.
Configuration and implementation checks
This step is performed by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and it 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.
| Object | Check | Verification action |
|---|---|---|
| Registration archives | Fields, dates, and signatures are consistent between the registration database and the handover form | In the deployment environment, verify that the main business database connection variable MONGODB_URI points to the actual registration database, and spot-check archive fields and dates |
| Course qualification certificates | Course codes, quantities, and qualification dates match between the two materials | Compare the qualification certificate list with the registration archives, verify course codes, quantities, and dates one by one, and record discrepancies |
| Graduation application forms | Major names, signatures, and receipts are complete and versions are synchronized | Check whether the application form signatures and receipts are complete, and verify whether the version number is consistent with the current review batch |
| Cache and vector database | The cache is connectable, and the vector database address is consistent with the actual retrieval database | Use a client to connect to REDIS_URL once, and verify that PG_URL is consistent with the vector database address selected in the deployment instructions |
Three common errors
- Symptom: The same candidate's name is written differently in the registration archives and the graduation application form. Cause: Multi-source entry has not been field-aligned, so names and dates do not match.
- Symptom: The number of course qualification certificates is inconsistent with the number recorded in the registration archives. Cause: Versions are not synchronized, and old batch materials have not been replaced.
- Symptom: The graduation application form is missing signatures or receipts. Cause: During handover, the signature fields and receipt attachments were not checked item by item.
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 logs, and confirm that the instances corresponding to MONGODB_URI, REDIS_URL, and PG_URL are connectable.
Business test: verify once item by item according to the handover form, see which record is missing, and compare the fields, dates, and signatures of the registration archives, course qualification certificates, and graduation application forms.
- In the deployment environment, verify the values of the main business database and log database connection variables, and confirm whether the log database is configured separately or reuses the main database as described in the instructions.
- Use a client to connect to the cache and vector database, and verify that the returned results are consistent with the vector database address selected in the deployment instructions.