What this category's data looks like
Vocational college program setup filing materials usually include three types: the program setup filing form, the talent demand justification, and the faculty and equipment list. The filing form contains the program name, code, program length, enrollment number, signature, and date; the talent demand justification contains industry positions, research data, justification conclusion, and signature; the faculty and equipment list contains the number of teachers, professional titles, equipment names and quantities, and date. Materials are updated by academic year or application batch, and the same record should be consistent across the three materials. When entering the vector model and index stage, the filing form serves as the main record, while the talent demand justification and the faculty and equipment list serve as supporting materials. They are split separately to generate vectors, the original data is stored in the business database data table, and the index field records multiple vector identifiers for subsequent retrieval and citation trimming to take supporting materials.
Configuration and implementation checks
This step is executed by the index service and vector database, and outputs vectors and index status (whether recall is possible and whether data in the same group is merged). "Basis entries that can be traced back to the original text" are completed next by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials). The index service and vector database are only responsible for recall and merging, and do not generate glossaries, comparison drafts, or version ledgers.
| Object | Check | Verification action |
|---|---|---|
| Program setup filing form | The fields include program name, code, program length, enrollment number, signature, and date, and the date is the current version | Open the data row and check whether the index field records multiple vector identifiers, search the program name to see whether data in the same group is merged, and check whether the status is indexed |
| Talent demand justification | The fields include industry positions, research data, justification conclusion, and signature, and the program name and date match the filing form | Check that the program name in the justification conclusion is consistent with the filing form, search the position name to see whether it can be recalled, and check the values of defaultToken and maxToken |
| Faculty and equipment list | The fields include the number of teachers, professional titles, equipment names and quantities, and date, and the quantities match the filing form | Check that the equipment quantities are consistent with the filing form, search the equipment name to see whether the same group is merged, and view the coverage scope of the rebuild task record |
| Index model | It is consistent with the vector model actually used by the knowledge base | Check the index model in the knowledge base settings, and after changing the model, view the data scope covered by the rebuild task record to confirm that it is triggered only for data that has already been indexed |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: for the same record, the name and date in the filing form and the talent demand justification do not match, and the index field does not merge data in the same group.
- Symptom: recall quality drops after changing the model. Inspect the following: the version is not synchronized, and data rows whose indexing has not been completed do not participate in recall, so indexing must be completed before rebuilding.
- Symptom: a data row has content but cannot be retrieved. Inspect the following: the faculty and equipment list lacks a signature or receipt, the material has not entered the index, and the status has not reached indexed.
How to verify the setup
Acceptance of this feature: sample one data row and look at the index field to confirm that multiple vector identifiers are all present and the status is indexed; then retrieve once to see whether data in the same group is merged, and view the coverage scope of the rebuild task record, checking the values of defaultToken and maxToken.
Business test: ask a basis question that spans materials, and see whether the answer gives a traceable source, and whether the source comes from the institution’s materials, the version is current, and the entries match the original text.
- Check the index field of the data row to confirm that multiple vector identifiers for one piece of data are all present and the status is indexed.
- After changing the model, view the rebuild task record to confirm that it is triggered only for data that has already been indexed, and check that the tokens and array count of the cited text are recorded separately, while also checking the values of
limit.