What this category's data looks like
This page addresses the scenario of student status establishment and changes in primary and secondary schools. The materials come from three categories: student status archives, transfer applications, and suspension/resumption materials. Student status archives are created by schools and follow the student as they move; transfer applications are confirmed by both the transferring-out and transferring-in schools and the parents; suspension/resumption materials are submitted by guardians and reviewed by schools. When these materials enter the deployment, operations, and application handover stage, they respectively serve as identity basis, change credentials, and status change credentials. The fields center on name, student status number, grade and class, change date, approval signature, and receipt. The update rhythm follows three periods: archive creation at the start of the semester, changes during the semester, and verification at the end of the semester. The field characteristic is that multiple materials appear crosswise around the same student record; names, quantities, dates, and signatures need to be aligned item by item during handover.
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" are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Student status archive | Name, student status number, grade and class, archive creation date, and signature must be aligned item by item with the transfer application and suspension/resumption materials | Sample one archive and compare it with the corresponding change materials for name, quantity, and date, and check whether signatures or receipts are complete |
| Transfer application | The school names of both the transferring-out and transferring-in schools, the change date, and the approval signature must be consistent | Check the school names, dates, and signatures in the application and archive against the handover form, and check whether the instances corresponding to the connection strings MONGODB_URI and PG_URL are from the same source |
| Suspension/resumption materials | The start and end dates of suspension and resumption, the guardian's signature, and the receipt must be consistent with the archive status | Compare the dates and signatures in the materials and archive; register those missing receipts as pending supplementation |
| Image version and migration task records | The two images are the same target version, and the two migration scripts are executed in sequence | Check the version identifiers of the two images against the version description, view the time and status of the two migration task records on the administrator version upgrade page, and check the instance corresponding to REDIS_URL |
Three common errors
- Symptom: The name or student status number of the same student does not match between the student status archive and the transfer application. Cause: The two materials were filled in by different handlers, no item-by-item comparison was made during handover, and missing signatures or receipts were not registered.
- Symptom: The service can start, but the data row status is still the old marker. Cause: Consistent image versions do not mean the business data migration is complete; the migration scripts were not triggered in sequence or did not wait for the old instance to fully stop.
- Symptom: The time and status of the two migration task records do not match, and script execution reports an error. Cause: The latter migration depends on the former being completed, but it was triggered before the former completed, or the old task lease had not expired.
How to verify the setup
This feature acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in sequence, and confirm that the data row index status field has been switched.
Business test: check item by item against the handover form once, and see which record is missing.
- Check against the version description whether the version identifiers of the main service and commercial edition images are consistent.
- On the administrator version upgrade page, view the time and status of the two records for historical chunk training task migration and knowledge base rebuild status migration, and confirm that the former is completed before triggering the latter.