What this category's data looks like
Modern apprenticeship and order class management materials include three categories: school-enterprise cooperation agreements, order class training plans, and mentor apprenticeship records. Agreements come from signatures by both the school and enterprise, training plans come from academic affairs and order class management positions, and apprenticeship records come from daily entries by mentors and apprentices. Agreements are updated by academic year or cooperation cycle, training plans are adjusted by semester, and apprenticeship records are updated weekly or by batch. Field characteristics are: agreements contain cooperation entities, majors, headcount, term, and signatures/seals; training plans contain course modules, class hours, rotation arrangements, assessment methods, and approval signatures; apprenticeship records contain mentor and apprentice names, positions, apprenticeship dates, work hours or task volume, and signatures and receipts from both parties. When materials enter the deployment and upgrade function, agreements and training plans are referenced as business baselines, and apprenticeship records are referenced as process data; the three are not automatically rewritten with image upgrades and must be checked item by item for names, quantities, dates, and signatures during migration and handover.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), outputting image versions, migration task records, and data row index status. The handover-ready deployment status and operation records are then completed by operations handover and business use. The script does not block service startup, and the latter migration depends on the former completing.
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Cooperation entities, majors, headcount, term, and signatures/seals must be consistent between the agreement and the training plan | Check the names, quantities, dates, and signatures of the agreement and training plan; compare connection parameters such as MONGODB_URI, PG_URL, and REDIS_URL item by item in the deployment records |
| Order class training plan | Course modules, class hours, rotation arrangements, assessment methods, and approval signatures must be complete | Check names and dates item by item against the agreement and training plan, and check whether approval signatures and receipts are missing |
| Mentor apprenticeship record | Mentor and apprentice names, positions, apprenticeship dates, task volume, and signatures from both parties must correspond to the training plan | Sample one apprenticeship record to check the date and signatures, and compare it with the rotation arrangements in the training plan |
| Image versions and migration task records | The two images are the same target version, and the two migration scripts are executed in sequence | Check the version identifiers of the two images against the version description, and check the execution records of the two migration scripts and the data row index status on the version upgrade page |
Three common errors
- Symptom: The names, quantities, and dates of the same apprenticeship record do not match between the agreement and the training plan. Cause: The two materials are maintained separately by the school and enterprise, with different update rhythms, and were not compared item by item on the handover form.
- Symptom: The image version identifiers are consistent, but the data row status still shows the old marker. Cause: Version consistency was mistaken for migration completion, and the execution records and index status of the two migration scripts were not checked.
- Symptom: The training plan or apprenticeship record lacks signatures or receipts. Cause: The approval and receipt steps were not included as check items on the handover form, and the signature fields were left blank when archived.
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 sequence.
Business test: check item by item once according to the handover form to see which record is missing.
- Check the version identifiers of the main service and commercial edition images against the version description, and view the execution records and time sequence of the historical chunk training task migration and knowledge base rebuild status migration on the version upgrade page.
- Sample one data row to check the index status field, and check whether
MONGODB_URI,PG_URL,REDIS_URL, andDB_MAX_LINKin the deployment records are consistent with the current environment.