What this category's data looks like
This category's data covers student registration forms, teaching plans, and skills training records. Multilingual materials and terminology handling require that the same term be consistent throughout the whole text and that translated names can refer back to the source text. Material sources include student registration forms exported from the academic affairs system, teaching plans prepared by teaching and research groups, and skills training records filled in by training workshops; the update rhythm advances with semester registration, course adjustments, and skills assessment batches. Field characteristics center on names, quantities, dates, and signatures: student registration forms contain student names, registration dates, and homeroom teacher signatures; teaching plans contain course names, class hours, preparation dates, and teaching and research supervisor signatures; skills training records contain training items, consumable quantities, training dates, instructor technician signatures, and receipts. When these materials enter the vector model and indexing function, student registration forms and teaching plans serve as the benchmark text for terminology comparison, while skills training records serve as supplementary material to be verified, each playing a supporting role in terminology consistency checks and in translated names referring back to the source text.
Configuration and implementation checks
This step is executed by the indexing service and the vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). "Unified terminology glossary 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 |
|---|---|---|
| Student registration form | Whether the same student's name, registration date, and homeroom teacher signature are consistent between the student registration form and the skills training record, and whether the translated name can refer back to the source text | Open one student registration form data row, check whether the index field contains multiple vector identifiers, then search the student name to see whether data in the same group is merged |
| Teaching plan | Whether the same course's course name, class hours, preparation date, and teaching and research supervisor signature match between the teaching plan and the skills training record | In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base, and check the reference text budget corresponding to limit |
| Skills training record | Whether the same training item's item name, consumable quantity, training date, instructor technician signature, and receipt are complete between the skills training record and the teaching plan | View the data scope covered by the rebuild task, confirm that after changing the model it is triggered only for data that has already been indexed, and check the status values indexed and the rebuild task record |
Three common errors
- Symptom: the same student's name and registration date do not match between the student registration form and the skills training record. Inspect the following: the two materials are entered separately, versions are not synchronized, and receipt verification is missing.
- Symptom: the same course's course name, class hours, and preparation date are inconsistent between the teaching plan and the skills training record. Inspect the following: the teaching and research group and the training workshop each maintain their own version, and no terminology comparison has been done.
- Symptom: the skills training record has content but cannot be retrieved, or duplicate entries appear in retrieval results. Inspect the following: the data row index field does not record multiple vector identifiers, and data in the same group is not merged.
How to verify the setup
This function's acceptance: sample one data row to look at the index field, then search once to see whether the same group is merged; for status values, only indexed and the rebuild task record are recognized.
Business test: sample three terms to check whether their spelling is consistent throughout the whole text, whether translated names can refer back to the source text, whether the citation count is recorded by array length, and whether quoteMaxToken is checked separately against the citation content budget.
- Open one data row to check the index field, confirm that multiple vector identifiers for one piece of data are all present and consistent with the vector model actually used by the knowledge base.
- View the data scope covered by the rebuild task, confirm that after changing the model it is triggered only for data that has already been indexed, and check the reference text budget corresponding to
limit.