What this category's data looks like
This page addresses the international student admissions and enrollment management category. The core materials include international student admission brochures, admission letters, and visa application forms. Brochures are published by the admissions department, and their update cadence varies with the academic year and program batches; admission letters are generated by the admissions system by batch and contain name, student ID, major, registration date, and a signature field for the issuer; visa application forms are filled out by students and returned, and contain passport number, program name, start and end dates, and a receipt acknowledgment. When these three types of materials enter the deployment and upgrade function, their roles differ: brochures and admission letters are used to check whether the name, quantity, and date of the same record are consistent, while visa application forms are used to check whether signatures and receipts are complete. Field characteristics center on name, student ID, passport number, program name, date, and signature. Common inconsistencies are that the name, quantity, or date of the same record does not match across two materials, versions are not synchronized, or signatures or receipts are missing.
Configuration and implementation checks
This step is performed 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.
| Object | Check | Verification action |
|---|---|---|
| Primary service and commercial edition image versions | Both images are the same target version | Check the version identifiers of both images against the version notes, and check whether the connection parameters MONGODB_URI, PG_URL, and REDIS_URL are consistent with the deployment environment |
| 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 trigger time and status |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete | Compare the time and status of the two records, and confirm that the latter migration is executed after the former is complete |
| Data row index status | After migration, it is the new index status system | Sample one data row and check the status field to confirm it is no longer the old marker |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the brochure and the admission letter. Cause: The versions of the two materials are not synchronized, the field sources differ, and no cross-check was performed.
- Symptom: The visa application form is missing a signature or receipt, and this cannot be confirmed during handover. Cause: The signature field and receipt status were not checked item by item during the material return step.
- Symptom: The service can start, but the data row status is still the old marker. Cause: The two migration scripts were not executed in order, or the latter migration was not triggered after the former was complete.
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; at the same time, check whether the MONGODB_URI, PG_URL, and REDIS_URL connections are consistent with the task records.
Business test: check once item by item according to the handover form, and see which record is missing.
- On the administrator version upgrade page, check the two image version identifiers and the execution records of the two migration tasks, and confirm that the latter migration is triggered after the former is complete.
- Sample one data row to check the index status field, and check whether the
DB_MAX_LINKconnection parameter corresponds to the task records.