What this category's data looks like
Self-taught examination registration records and graduation review materials fall into three categories: registration record files record the candidate's basic information and enrollment status; course pass certificates record single-subject scores and the time they were obtained; and graduation application forms carry the completion status of the professional plan and the review conclusion. The three categories of materials come from different sources: registration record files are generated by the provincial-level registration record system, course pass certificates are produced at the score release stage, and graduation application forms are filled in by candidates and signed level by level by the main examining institution and the provincial examination office. In terms of update cadence, registration record files change with transfer examinations, exemption examinations, and information changes; course pass certificates are updated in batches by examination session; and graduation application forms are submitted in a concentrated manner according to the graduation review cycle. Field characteristics center on names, quantities, dates, and signatures: the same candidate's name, ID number, number of courses, and pass dates must be consistent across the three categories of materials, and the review conclusion must have the handling person's signature or an electronic receipt. When materials enter deployment, operations, and application handover, registration record files and course pass certificates are the basis for checking data row status, and graduation application forms are the objects to be signed off item by item on the handover form.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), outputting the image version, migration task records, and data row index status. "Handover-ready deployment status and operation records" are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | The two images must be the same target version, and the version identifiers must not be one high and one low | Check the version identifiers of the two images against the version description; if either is inconsistent, record it as pending |
| Historical chunk training task migration | It must be triggered after the old instance is completely stopped and the old task lease has expired, and the execution record must include time and status | View the execution record of this task on the administrator version upgrade page, and check the trigger time and completion status |
| Knowledge base rebuild status migration | It must be triggered only after the previous migration is completed, and the time and status of the two records must connect in sequence | Compare the time and status of the two migration records, and confirm that the latter was completed later than the former |
| Data row index status | After migration, the data row status field must be the new index status system, with no residual old markers | Sample one data row to check the status field, and check whether the MONGODB_URI, PG_URL, and REDIS_URL connection configurations are consistent with the current environment |
Three common errors
- Symptom: the service starts normally, but when data rows are spot-checked, the status field still shows old markers. Cause: the two migration scripts were not executed in order, or the data row index status was not checked after execution.
- Symptom: the same candidate's name, number of courses, or pass dates do not match between the registration record file and the course pass certificate. Cause: the records on the two sides were not updated in sync, and the fields were not compared item by item during handover.
- Symptom: the graduation application form lacks the handling person's signature or electronic receipt, and that item cannot be signed off on the handover form. Cause: the review step was not completed before entering handover, and the material circulation record is incomplete.
How to verify the setup
Acceptance of this function: check the two image version identifiers, then check the execution records of the two migration scripts in order, confirm that the latter depends on the completion of the former, and sample one data row to check the index status field.
Business test: check once item by item according to the handover form, see which record is missing, and focus on comparing the names, quantities, dates, and signatures of the registration record files, course pass certificates, and graduation application forms.
- On the administrator version upgrade page, view the migration task records one by one, register the trigger time and completion status, and write them into the handover form together with the image version identifiers.
- Sample one data row to check the index status field, and check whether
MONGODB_URI,PG_URL,REDIS_URL, andDB_MAX_LINKare consistent with the current deployment environment.