What this category's data looks like
This page addresses the scenario of general higher education admissions enrollment and filing. The materials come from provincial admissions and examination institutions and university admissions offices, and the core category materials are enrollment plans, filing rules, and admission rosters. Enrollment plans carry institution-major groups, planned numbers, subject selection requirements, and batch dates; filing rules record filing ratios, tie-breaking sorting, and adjustment scope; admission rosters solidify candidate numbers, major codes, admission conclusions, and signature fields. When these materials enter the deployment and upgrade function, they respectively take on the roles of version comparison, rule verification, and result traceability: enrollment plans are used to check whether the target version and the data row index status are synchronized, filing rules are used to confirm the field scope covered by the migration task records, and admission rosters are used to check names, quantities, and dates item by item on the handover form. The update rhythm advances by batch, and after each round of upgrade the fields and signatures of the three materials must be compared again to avoid the same record failing to match between two materials.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image versions, migration task records, and data row index status. "Handover-ready deployment status and operation records" are then completed by operations handover and business use. Migration scripts do not block service startup, and the latter migration depends on the former completing.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images point to the same target version, and the version identifiers must be consistent with the version notes | Check the version identifiers of the two images in the deployment environment, and record them on the handover form |
| Historical chunk training task migration | Triggered only after the old instance has fully stopped and the old task lease has expired | View the execution record of this task on the administrator version upgrade page, and confirm the status and time |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete, and the times and statuses of the two records must correspond | Compare the times and statuses of the two migration task records, and check the dependency order |
| Data row index status | After migration it is the new index status system, and old markers are no longer retained | Sample one data row to check the status field, and check whether the connection strings MONGODB_URI, PG_URL, and REDIS_URL are consistent with the deployment records |
Three common errors
- Symptom: the service can start but the data row status still shows old markers. Cause: the latter migration was not triggered after the former completed, or the old instance had not fully stopped when it was triggered.
- Symptom: the name, quantity, or date of the same record does not match between the enrollment plan and the admission roster. Cause: the versions are not synchronized, and the two materials are taken from different batches.
- Symptom: the handover form lacks a signature or receipt. Cause: the migration task records were not archived together with the image version identifiers, so the next shift cannot check item by item.
How to verify the setup
This function's acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in order, and confirm that the data row index status has switched; the connection strings MONGODB_URI, PG_URL, and REDIS_URL are consistent with the deployment records.
Business test: check once item by item according to the handover form, see which record is missing, and focus on comparing the fields, dates, and signatures of the enrollment plan, filing rules, and admission roster.
- View the execution records of the two migration tasks on the administrator version upgrade page, and confirm that the time and status order are correct.
- Sample one data row to check the index status field, and check the names, quantities, dates, and signatures of the enrollment plan, filing rules, and admission roster against the handover form.