What this category's data looks like
Modern apprenticeship and order class management involves three types of materials: school-enterprise cooperation agreements, order class training plans, and master apprenticeship records. School-enterprise cooperation agreements contain the cooperation period, positions, headcount, and signatures and seals; order class training plans contain courses, credit hours, master arrangements, and dates; master apprenticeship records contain the apprenticeship cycle, positions, assessments, and signed receipts. The materials come from academic affairs, partner enterprises, and apprenticeship masters, and are updated by semester or project milestone. When entering the vector model and indexing feature, agreements and plans serve as terminology sources, and apprenticeship records serve as corroborating evidence; the three types of materials respectively take on the roles of terminology definition, training standards, and process records.
Configuration and implementation checks
This step is executed by the indexing service and vector database, and outputs vectors and indexing status (whether recall is possible, whether data in the same group is merged). The "unified terminology table and comparison draft" is then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| School-enterprise cooperation agreement | Fields include the cooperation period, positions, headcount, and signatures and seals; the name, quantity, and date of the same record in two materials must be consistent | Check the name, headcount, and date of the same order class in the agreement and training plan; check whether signatures and receipts are complete |
| Order class training plan | Fields include courses, credit hours, master arrangements, and dates; versions must be synchronized, and terminology usage must be consistent throughout | Open the data row and check the index fields to confirm that multiple vector identifiers are all present; check whether the plan version and agreement version are synchronized |
| Master apprenticeship record | Fields include the apprenticeship cycle, positions, assessments, and signed receipts; translated names can refer back to the original text | Sample three terms and check whether their usage is consistent throughout; check whether the positions and headcount in the records match those in the agreement and plan |
| Index model | Consistent with the vector model actually used by the knowledge base | Check the index model in the knowledge base settings; view the data scope covered by the rebuild task, and after changing the model, trigger it only for data whose indexing has already been completed |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the same group of data corresponds to multiple vector identifiers, the highest score was not taken during merging, or the data row index fields did not fully record the vector identifiers.
- Symptom: the name, quantity, and date of the same record in two materials do not match. Inspect the following: the agreement and training plan versions are not synchronized, or the apprenticeship record lacks a signed receipt, causing the terminology table and comparison draft to lose their basis for referring back.
- Symptom: recall quality declines after changing the model. Inspect the following: the rebuild task is triggered only for data whose indexing has already been completed and does not cover all data rows; a data row has content but cannot be retrieved, and the index fields are inconsistent with the vector database.
How to verify the setup
Acceptance for this feature: sample one data row and check the index fields to confirm that multiple vector identifiers are all present and the status is indexed; then retrieve once and see whether data in the same group is merged and whether the highest score is taken. If a citation limit is involved, check the tokens of the cited text; the number of array entries is recorded separately, and quoteMaxToken is not compared for equality with the number of entries; limit are checked against the knowledge base settings.
Business test: sample three terms and check whether their usage is consistent throughout, and whether translated names can refer back to the original text.
- Open a data row and check the index fields to confirm that multiple vector identifiers are all present, and the status is indexed, or view the rebuild task record
- Check in the knowledge base settings that the index model is consistent with the vector model actually used by the knowledge base, and view the data scope covered by the rebuild task