What this category's data looks like
This category's data covers the deployment, operations, and application handover for undergraduate program setup and dynamic adjustment, and involves three types of materials: program setup application forms, talent cultivation plans, and expert review opinions. The program setup application form provides the program name, code, degree-granting category, and application date, and is the starting point for version identification; the talent cultivation plan carries the curriculum system, credit counts, and study requirements, and its fields must be aligned item by item with the application form; the expert review opinions record the review date, expert signatures, and conclusions, and are the evidence for receipts and signatures. Materials are updated by academic year or batch, and the name, quantity, and date of the same program in two materials are often inconsistent; when versions are not synchronized or signatures are missing, gaps appear in the handover form. When the three types of materials enter the deployment and upgrade function, they respectively serve as the version basis, the field verification draft, and the source of signature receipts, and operations handover and business use verify them item by item accordingly.
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 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 |
|---|---|---|
| Program setup application form | The name, code, degree-granting category, and application date must be consistent item by item with the talent cultivation plan | Compare the name, quantity, and date in the two materials, and check whether signatures and receipts are complete |
| Talent cultivation plan | The curriculum system, credit counts, and study requirements must correspond to the conclusions of the expert review opinions | Compare course names, credit counts, and review dates item by item, and check whether version identifiers are synchronized |
| Expert review opinions | The review date, expert signatures, and conclusions must be complete; missing signatures or receipts are regarded as not closed-loop | Check the signature column and receipt date against the handover form, and confirm consistency with the application form version |
| Image version and migration task records | The two images are the same target version, and the two migration scripts leave execution records in order | On the version upgrade page, check the image version identifiers, and view the two migration task records and data row index status in order |
Three common errors
- Symptom: the service can start but the data row status is still the old marker. Cause: only the image version was updated, the two migration scripts were not executed in order, and the old task lease was triggered before it expired.
- Symptom: the name, credit counts, and date of the same program do not match between the application form and the cultivation plan. Cause: versions were not synchronized, the two materials were updated separately, and the handover form lacks corresponding records.
- Symptom: the expert review opinions lack signatures or receipts, and one record is missing during item-by-item verification of the handover form. Cause: the signature page was not collected during material circulation, and the receipt date was not aligned with the review date.
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 sample one data row to check the index status field.
Business test: verify once item by item against the handover form to see which record is missing; when connection parameters are involved, check whether the entries and version records of MONGODB_URI, PG_URL, and REDIS_URL are consistent.
- On the administrator version upgrade page, view the execution records of the two migration scripts, compare the time and status, and confirm that the second is triggered only after the first is completed.
- Verify the name, quantity, date, and signatures of the program setup application form, talent cultivation plan, and expert review opinions item by item against the handover form, and record the missing items.