What this category's data looks like
This page addresses the deployment, operations, and application handover stages of self-funded study abroad application services, involving three types of materials: study abroad service contracts, school application forms, and personal statements. Study abroad service contracts record the scope of services, fees, and signing dates; school application forms carry institution, program, and deadline information; personal statements reflect the applicant's background and version iterations. After deployment and upgrade, the three types of materials enter the handover process: contracts are used to confirm service boundaries, application forms are used to verify institution information, and personal statements are used to compare versions and signatures. Material sources are business system exports and manual uploads, and the update rhythm is triggered by application progress and version upgrades. Field characteristics include name, quantity, date, signature, and receipt; the same record must remain consistent across different materials, versions must be synchronized, and signatures and receipts must not be missing.
Configuration and implementation checks
This step is performed 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. Rebuild state migration depends on completion of historical chunk training task migration; both tasks are triggered manually.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images have the same target version identifier | Check the version identifiers of both images against the version description, and check whether the MONGODB_URI, PG_URL, and REDIS_URL connection configurations are consistent with the migration task records |
| Historical chunk training task migration | Triggered only after the old instance has completely stopped and the old task lease has expired | View the execution record of this task on the administrator's version upgrade page, and check the task status and time |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete | Compare the time and status of the two migration task records to confirm that the latter migration was executed after the former completed |
| Data row index status | After migration, it is the new index status system | Sample one data row and check the status field to confirm that it has switched from the old marker to the new index status |
Three common errors
- Symptom: The service can start but the data row status is still the old marker. Cause: The migration script was not executed or the execution order was incorrect, and the latter migration was not triggered after the former completed.
- Symptom: The name, quantity, and date of the same record do not match between the study abroad service contract and the school application form. Cause: Versions were not synchronized, and fields were not re-checked after the materials were updated.
- Symptom: The personal statement lacks a signature or receipt. Cause: The handover form was not checked item by item, and the signature and receipt steps were omitted.
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 order, and confirm that the MONGODB_URI, PG_URL, and REDIS_URL connection configurations are consistent with the migration task records.
Business test: check item by item once according to the handover form to see which record is missing, focusing on checking the fields, dates, and signatures of the study abroad service contract, school application form, and personal statement.
- On the administrator's version upgrade page, view the execution records of the two migration scripts and check the time and status order.
- Sample one data row and check the index status field to confirm that it has switched to the new index status system.