What this category's data looks like
This category's data covers three types of materials: talent cultivation programs, course standards, and job competency analysis tables. It is usually led by the academic affairs office, with collaboration from secondary colleges and professional teaching and research offices, and is updated by academic year or professional accreditation cycle. The fields of the three types of materials include program name, course code, competency indicator, class hours and credits, development date, and approval signature, and versions are identified by revision number and effective date. In the deployment, operations, and application handover stage, the talent cultivation program serves as the master outline that determines the curriculum system, the course standards take over from the program to break down teaching units, and the job competency analysis table provides the basis for competency mapping. When the materials enter the deployment and upgrade function, each plays the role of version verification and handover evidence, and it is necessary to ensure that the name, quantity, and date of the same record are consistent across the three materials, that signatures and receipts are complete, and that handover items are not missing due to unsynchronized versions.
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-capable deployment status and operation records" are then completed by operations handover and business use. Consistent image versions do not mean that business data migration has been completed; the migration script does not block service startup, nor is it a prerequisite for enabling the interface.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition images | Both images are the same target version, and the version identifier matches the version description | Check the version identifiers of the two images against the version description, and record the image tag |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired; the task record status is executed | View the execution record of this task on the administrator version upgrade page, and check the trigger time against the old instance stop time |
| Knowledge base rebuild status migration | Triggered only after the previous migration is complete; the time and status of the two records connect in sequence | Compare the time and status of the two records to confirm the dependency order |
| Data row index status | After migration, it is the new index status system, no longer the old marker | Sample one data row to check the status field and confirm that the status value has switched |
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 reversed, and the latter migration was triggered before the previous migration was complete.
- Symptom: the name, quantity, and date of the same record do not match between the talent cultivation program and the course standards. Cause: versions were not synchronized, and items were not checked one by one against the handover form during handover.
- Symptom: the job competency analysis table lacks a signature or receipt. Cause: the material circulation step was not closed-loop, the handover evidence is incomplete, and the next shift cannot confirm responsibility.
How to verify the setup
This function acceptance: check the version identifiers of the two images, then check the execution records of the two migration scripts in order; check the connection status corresponding to MONGODB_URI, PG_URL, and REDIS_URL, and confirm that after DB_MAX_LINK is set, the task records and data row index status are consistent.
Business test: check once item by item against the handover form to see which record is missing, focusing on checking the fields, dates, and signatures of the talent cultivation program, course standards, and job competency analysis table.
- 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 latter is triggered only after the former is complete.
- Sample one data row to check the index status field, and check against the version description whether the version identifiers of the main service and commercial edition images are consistent.