Deployment and Upgrades for Vocational College Program Registration: Coordinate Operations and Application Handover

Vocational Programs: review upgrades for operational handover. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

Filing materials for specialty setup in vocational colleges mainly consist of the Specialty Setup Filing Form, the Talent Demand Justification, and the List of Faculty and Equipment. They come from the academic affairs and human resources departments of the institutions and are updated by academic year or batch. Fields include specialty name, planned enrollment number, justification date, equipment quantity, and signature field. When entering the deployment and upgrade stage, the filing form serves as the main record to locate the version, the talent demand justification is used to check dates and conclusions, and the faculty and equipment list is used to check quantities and seals; the three often show the same record with mismatched names, quantities, and dates across two materials, unsynchronized versions, and missing signatures or receipts, requiring item-by-item verification against the handover form.

Configuration and implementation checks

This step is executed 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.

ObjectCheckVerification action
Specialty Setup Filing FormSpecialty name, planned enrollment number, filing date, and signature field correspond item by item with the Talent Demand Justification and the List of Faculty and EquipmentSample one filing record, check the name, quantity, date, and signature against the other two materials, and register missing items in the operation records
Talent Demand JustificationThe justification date and conclusion are consistent in the filing form and the faculty and equipment list, with no two sets of dates appearingCheck the date fields against the filing form and the list, and verify item by item whether receipts and signatures are complete
List of Faculty and EquipmentEquipment quantity and faculty headcount are consistent across materials, and seals are completeCheck quantities and seals against the handover form, and verify whether the connection records corresponding to MONGODB_URI, PG_URL, and REDIS_URL are synchronized with the material version
Deployment status and operation recordsThe image version identifier, migration task records, and data row index status are consistent with one anotherOn the administrator version upgrade page, check the two image version identifiers, then check the execution records of the two migration scripts in order

Three common errors

  • Symptom: The same specialty name is written differently in the filing form and the talent demand justification, and the quantity and date do not match. Cause: The two materials were entered separately and were not proofread in sync under the same version.
  • Symptom: The service can start, but the data row status still shows the old marker, and there is no corresponding record on the handover form. Cause: The migration task records were not checked together with the image version identifier.
  • Symptom: Materials are missing signatures or receipts, making responsibility impossible to confirm at handover. Cause: The signature field and receipts were not completed along with the version update, and the handover form was not checked item by item.

How to verify the setup

This feature'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: check item by item once against the handover form to see which record is missing.

  • On the administrator version upgrade page, view the execution records of the historical chunk training task migration and the knowledge base rebuild status migration, and compare the time and status.
  • Sample one data row to check the index status field, and verify whether the connection records corresponding to MONGODB_URI, PG_URL, and DB_MAX_LINK are synchronized with the material version.