What this category's data looks like
This category's data looks like this: Kindergarten home-school co-education communication category materials include commitment items and response times, child performance descriptions, parent request classifications, notification delivery, etc. Sources are class notices, home-school contact books, parent meeting records, and daily observation records. The update cadence follows communication progress on a daily or weekly basis. Field characteristics: commitment items include response time and responsible person; child performance descriptions must correspond to observation records; parent requests are grouped by category; notification delivery requires confirmation of receipt status. During multilingual materials and terminology handling, these materials serve respectively as terminology extraction sources, reference draft bases, and indexing source data. After entering the vector model and indexing function, materials are first split into data rows, then vector identifiers are generated for retrieval recall and merging.
Configuration and implementation checks
This stage is executed by the indexing service and vector database, outputting vectors and indexing status (whether recall is possible, whether data in the same group is merged). The unified terminology table and reference draft are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials). Indexing status and merge results only serve as retrieval support and do not directly generate terminology tables or reference drafts.
| Object | Check | Verification action |
|---|---|---|
| Unified terminology table and reference draft | The same terminology is consistent throughout the entire text, and the translated name can refer back to the original text; the four dimensions of commitment items and response times, child performance descriptions, parent request classifications, and notification delivery all need to reflect consistent wording in the reference draft | Sample three terms and check whether their wording is consistent throughout the entire text; verify whether the translated name can refer back to the original text; check whether commitment items are responded to, whether child performance descriptions match observation records, whether parent requests are classified, and whether notification delivery is recorded |
| Data row index fields | Multiple vector identifiers for one data row are all present, and the status is indexed; after changing models, the rebuild task record covers data whose indexing has already been completed | Open a data row and check whether the index field array is complete; view the rebuild task record to confirm the coverage scope; check whether limit affects the citation text budget |
| Index model | Consistent with the vector model actually used by the knowledge base; the number of citations is the array length, citation text tokens are recorded separately, and quoteMaxToken is the citation content budget | Check the index model in the knowledge base settings; perform one retrieval to see whether data in the same group is merged; check that the number of citations and quoteMaxToken are not compared for equality |
Three common errors
- Symptom: a commitment has been sent but remains unanswered. Compare the responsible person, response time and acknowledgment in the notice and contact book, then check which version retrieval actually matched.
- Symptom: a description of a child’s performance differs from the observation record. Compare the original wording, translation and terminology table for the same observation item, then inspect the cited data row.
- Symptom: feedback on a parent request has no category. Check the category field and downstream classification result. If retrieval entries are duplicated, compare data identifiers, group identifiers and merge results.
How to verify the setup
This function's acceptance: sample one data row to inspect the index fields, then perform one retrieval to see whether the same group is merged; check whether the status is indexed, and view the coverage scope of the rebuild task record.
Business test: sample three terms and check whether their wording is consistent throughout the entire text; verify whether the translated name can refer back to the original text, whether commitment items are responded to, whether child performance descriptions match observation records, whether parent requests are classified, and whether notification delivery is recorded.
- Open a data row and check whether the index field array contains multiple vector identifiers and whether the status is indexed.
- Check the index model in the knowledge base settings, and view whether the rebuild task record covers data whose indexing has already been completed.