Vector Models and Indexes for School Moral Education and Class Teacher Work: Maintain Document Versions and Changes

Pastoral Education: review vector indexes for version tracking. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This category's data covers three types of materials: themed class meeting plans, student comprehensive quality records, and home visit records. Sources include homeroom teacher handbooks, moral education office archives, grade group summaries, and parent receipts. The update rhythm runs in parallel by semester and by month: class meeting plans are revised each round, comprehensive quality records are supplemented monthly, and home visit records are entered as events occur. Field characteristics center on activity name, number of participants, date, signature, and receipt number. The same record often appears in two materials with different names, quantities, or dates. When materials enter this feature, class meeting plans and home visit records serve as the body text to be retrieved, while comprehensive quality records serve as traceable attachments. Together, the three form the comparison draft for the version ledger and change records.

Configuration and implementation checks

This step is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).

ObjectCheckVerification action
Themed class meeting planWhether activity name, number of participants, date, and signature are consistent across versionsOpen the plan data row, check whether the index fields are complete, and whether retrieval of the same group is merged
Student comprehensive quality recordWhether record name, quantity, date, and signature match between the attachment and the summary tableRetrieve by record identifier and check whether the original data in the same group is merged by taking the highest score
Home visit recordWhether home visit date, receipt number, and signature are synchronously updated to the current versionCheck the coverage of the rebuild task record and confirm whether indexed data has been rebuilt after changing models
Data row index fieldsWhether multiple vector identifiers for one piece of data are all present and whether the status is indexedSample one data row to check the index fields, and record the number of citations and the tokens of the cited text

Three common errors

  • Symptom: The same class meeting plan has mismatched names and participant numbers in two materials. Inspect the following: The versions are not synchronized.
  • Symptom: A home visit record has content but cannot be retrieved. Inspect the following: The data row index fields are missing, the vector identifiers were not written, or the rebuild task did not cover it.
  • Symptom: A comprehensive quality record is missing a signature or receipt. Inspect the following: The attachment and summary table have different update rhythms, and the signature and receipt were not synchronized with the body text.

How to verify the setup

This feature's acceptance: sample one data row to inspect the index fields, then retrieve once to see whether the same group is merged. For status values, only indexed and rebuild task records are recognized.

Business test: change one piece of content and see whether the version number and citations are synchronously updated; the number of citations is recorded by array length, and the tokens of the cited text are checked separately.

  • In the knowledge base settings, check whether the indexing model is consistent with the vector model actually used by the knowledge base.
  • Open a data row to check the index fields and confirm that limit, and fields related to defaultToken are not mistakenly changed during citation trimming.