What this category's data looks like
This category's data covers three types of materials: program setup application forms, talent cultivation plans, and expert demonstration opinions. The program setup application form contains fields such as program name, code, length of schooling, degree-granting category, faculty and conditions, along with the signing date and the signature of the person in charge; the talent cultivation plan contains cultivation objectives, curriculum system, credits and class hours, practical components, and the revision date; the expert demonstration opinions contain the demonstration conclusion, list of experts, signatures, and demonstration date. The three types of materials are updated by year or revision batch, and field names and record granularity are not uniform: the same program may be named differently in the application form and the cultivation plan, the number of courses or credit figures may be inconsistent, version dates may not be synchronized, or signatures or receipts may be missing. When the materials enter this feature, the application form and the cultivation plan serve as the primary source of basis, while the expert demonstration opinions serve as conclusive supporting evidence; each is stored as documents or data rows, and the index service and vector database establish vector and index status for subsequent retrieval and citation trimming to draw supporting materials.
Configuration and implementation checks
This step is executed by the index service and vector database, outputting vector and index status (whether recall is possible, whether data in the same group is merged). Basis entries that can be traced back to the original text are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Program setup application form | Fields include program name, code, length of schooling, degree-granting category, and faculty conditions; the signing date and the signature of the person in charge are complete, and the name, quantity, and date can be matched with the same record in the talent cultivation plan | Open the data row to check whether the index field records multiple vector identifiers; compare the name, course quantity, and date of the same program in the application form and the cultivation plan; check whether signatures and receipts are complete |
| Talent cultivation plan | The fields for cultivation objectives, curriculum system, credits and class hours, and practical components are complete; the revision date is the current version and does not conflict with the conclusion date of the expert demonstration opinions | Check the version date and current status; check whether the name and credits of the same course are consistent in the two materials; confirm that the index status is indexed, and if necessary, check the rebuild task records |
| Expert demonstration opinions | The demonstration conclusion, list of experts, signatures, and demonstration date are complete; the conclusion can correspond to the program direction and curriculum setup in the application form and cultivation plan | Check signatures and receipts; compare the demonstration date with the plan revision date; when retrieving this material, confirm whether data in the same group is merged, and the vector score takes the highest score |
| Index field of the data row | Multiple vector identifiers of one piece of data are all present; limit, and the citation content budget are checked against the knowledge base settings, and the number of citations is recorded separately | Open a data row to check the index field; retrieve once to see whether the same group is merged; after changing models, only trigger rebuild for data that has already completed indexing, and check the coverage scope of the rebuild task records |
Three common errors
- Phenomenon: the name, course quantity, or date of the same program do not match between the application form and the cultivation plan. Inspect the following: the two materials are maintained separately, and the field definitions and revision batches are not aligned.
- Phenomenon: the cultivation plan has been revised, but the expert demonstration opinions are still the previous version, and retrieval gives the old conclusion. Inspect the following: versions are not synchronized, and the current version identifier is missing.
- Phenomenon: a data row has content but cannot be retrieved, or duplicate entries appear in retrieval results. Inspect the following: the index field does not record all vector identifiers, or after changing models, rebuild was not triggered for data that has already completed indexing.
How to verify the setup
Acceptance of this feature: sample one data row to see whether the index field records multiple vector identifiers, then retrieve once to see whether data in the same group is merged and whether the vector score takes the highest score; check that the index status is indexed, and check the data scope covered by the rebuild task records.
Business test: ask a basis question across materials and see whether the answer gives traceable sources, and whether the sources can be matched to the original text of the program setup application form, talent cultivation plan, or expert demonstration opinions.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used, open the data row to check the index field, and confirm that
limit, and the citation content budget take effect according to the settings. - After changing models, only trigger rebuild for data that has already completed indexing, and check the coverage scope of the rebuild task records; for the same record, compare the name, quantity, date, and signature receipts of the two materials, and record the number of citations and the tokens of the cited text separately.