What this category's data looks like
For the deployment, operations, and application handover of primary and secondary school admissions organizations, the core materials are the admissions plan, the application materials checklist, and the admission list. The admissions plan comes from the education authorities and the school admissions committee, and is updated by academic year or batch; its fields include plan name, applicable school level, application start and end dates, and approval signature. The application materials checklist is maintained by the admissions execution team and is updated by application batch; its fields include material name, number of copies, submission date, and receipt acknowledgment. The admission list is reviewed and approved by the admissions leadership group and is updated by admission batch; its fields include student name, admission category, publicity date, and responsible person's signature. When these three types of materials enter the deployment and upgrade function, they respectively serve as the basis for the plan version, the baseline for checking the materials checklist, and the data source for admission results; their fields, dates, and signatures must correspond item by item in the handover form.
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 version, migration task records, and data row index status. "Handover-ready deployment status and operation records" is then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images are the same target version; check the version identifiers of the two images against the version notes | View the image tag on the administrator version upgrade page, and confirm that both the main service and the commercial edition point to the same version identifier |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired; view the execution record of this task on the administrator version upgrade page | Check the old instance stop time and the task lease expiration time, then view the execution record and status of this migration task |
| Knowledge base rebuild status migration | Triggered only after the previous migration is completed; check the time and status of the two records against each other | First confirm that the historical chunk training task migration is completed, then view the execution record time and status of this migration task |
| Data row index status | After migration, it is the new index status system; sample one data row to check the status field | Sample one data row, check whether the status field is the new index status system, and record the data row index status |
Three common errors
- Symptom: the service can start, but the data row status is still the old marker. Cause: the knowledge base rebuild status migration was not triggered after the previous migration was completed, or the migration record is missing.
- Symptom: the name, quantity, and date of the same record do not match between the admissions plan and the admission list. Cause: the two material versions were not synchronized, and signatures or acknowledgments are missing.
- Symptom: the script execution reports an error. Cause: the old instance was not fully stopped or the old task lease has not expired, the migration task record is interrupted, and the two image versions are inconsistent.
How to verify the setup
This function's acceptance check: verify the two image version identifiers, then verify the execution records of the two migration scripts in order; at the same time, check whether the connection status of MONGODB_URI, PG_URL, and REDIS_URL is consistent with the migration task records.
Business test: check item by item once according to the handover form to see which record is missing; check whether the fields, dates, and signatures of the admissions plan, application materials checklist, and admission list are consistent.
- On the administrator version upgrade page, view the version identifiers of the two images and the execution records of the two migration tasks, and confirm the time and status order.
- Sample one data row to check the index status field, and check whether the connection records of
MONGODB_URI,PG_URL, andREDIS_URLand the migration task records are complete.