What this category's data looks like
This page addresses the scenario of investigating and handling academic misconduct reports, focusing on business basis queries for three types of materials: report materials, investigation reports, and expert appraisal opinions. Report materials come from the original records submitted by the reporter, investigation reports come from the verification process and conclusions formed by the investigation team, and expert appraisal opinions come from external experts' judgments on the disputed content. When the three types of materials enter this function, each plays a different role: report materials provide original facts and clues, investigation reports provide procedural conclusions, and expert appraisal opinions provide the basis for professional judgment. The material update cadence is synchronized with the investigation stage, and field characteristics include record name, quantity, date, signature, and receipt status. The same record may appear with inconsistent name, quantity, or date across different materials, versions may be out of sync, or signatures and receipts may be missing, all of which affect the traceability of basis entries.
Configuration and implementation checks
This step is executed by the index service and the vector database, outputting vectors 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). The index service and vector database are only responsible for vector recall and merging data in the same group; they do not generate glossaries, comparison drafts, or version ledgers.
| Object | Check | Verification action |
|---|---|---|
| Report materials | Whether fields, dates, and signatures are consistent with the investigation report | Open the report materials and the investigation report, check the name, quantity, and date of the same record; check whether signatures and receipts are complete; confirm that the index fields include all vector identifiers |
| Investigation report | Whether the version is current and synchronized with the expert appraisal opinions | Check the investigation report version number against the version cited in the expert appraisal opinions; review the coverage of the rebuild task records; confirm that the data row status is indexed |
| Expert appraisal opinions | Whether entries can be traced back to the original text and correspond to the report materials | Retrieve cross-material basis questions and check whether the returned entries point to the original text; check that the index model is consistent with the vector model actually used by the knowledge base; check the limit citation budgets |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the report materials and the investigation report. Inspect the following: The materials are entered independently, lacking unified field comparison and signature/receipt verification.
- Symptom: The investigation report version is not synchronized, and the expert appraisal opinions cite an old version. Inspect the following: After changing the model, not covering all materials.
- Symptom: Retrieval results contain duplicate entries, or data rows have content but cannot be retrieved. Inspect the following: The index fields do not record all vector identifiers, data in the same group is not merged, or the index models are inconsistent.
How to verify the setup
This function's acceptance check: sample a data row to see whether the index fields record all vector identifiers, then run a retrieval to see whether data in the same group is merged and the highest score is taken; for status values, only indexed and rebuild task records are recognized.
Business test: ask a cross-material basis question, see whether the answer provides traceable sources, and check that the cited text tokens and the number of array entries are recorded separately.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base, and open a data row to check whether the index fields include all vector identifiers.
- Review the data scope covered by the rebuild task records, confirm that after changing the model, rebuilds are triggered only for data that has already been indexed, and check the
limitcitation budgets.