What this category's data looks like
Kindergarten home-school co-education communication materials mainly consist of class notices, child observation records, parent request classification tables, and commitment response forms. Their sources are teachers' daily records and the kindergarten's unified templates, and their update cadence is weekly or event-triggered. When entering the knowledge base retrieval and recall function, notices and commitment forms handle current-version uniqueness verification, observation records handle wording consistency comparison, and request classification tables handle feedback categorization checks. Field characteristics include version number, effective date, change description, citation location, and related material number. Old versions must be traceable, citations must be synchronized, and multiple current versions of the same commitment must be avoided.
Configuration and implementation checks
This step is performed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks and similarity scores (after pattern, merge, rerank, filter, and limit trimming). The version ledger and change records are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Notice and commitment item materials | Whether the commitment item and response time are unique and traceable in the current version | In the search test, search with synonymous questions, record the number of candidate items and scores, and check whether the hit chunks under similarity and searchMode point to the current version |
| Child observation records | Whether the description of child performance is consistent with the observation record | Switch searchMode to semantic, full-text, or hybrid, and compare whether the wording in the candidate chunks is consistent with the original observation record |
| Parent request classification table | Whether the parent request classification is consistent with the feedback categorization | Search with request keywords, check whether the candidate chunks are classified into the correct category, and record the citation array length and citation text tokens |
| Version ledger and change records | The current version is unique, old versions are traceable, and citations are synchronized | After changing one piece of content, search again, compare whether the version number and citation location are updated synchronously, and toggle usingReRank to see changes in the ranking of the top few items |
Three common errors
- Symptom: The same commitment cannot be recalled when rephrased. Cause: The commitment has not been responded to or the current version is not unique, and the old version is still being recalled.
- Symptom: The description of child performance does not match the observation record. Cause: Citations were not synchronized after the change, and the candidate chunks still point to the old version.
- Symptom: Parent feedback is not categorized or is categorized incorrectly. Cause: The request classification table was not updated with the change, and retrieval candidates are mixed with old categories.
How to verify the setup
This function's acceptance: test once each with synonymously rewritten questions, compare candidates and scores, then toggle rerank to see the ranking of the top few items.
Business test: change one piece of content and see whether the version number and citations are updated synchronously.
- In the knowledge base search test, switch
searchMode, record the number of candidate items and scores, and check current-version uniqueness. - Check the citation array length and citation text tokens, confirm that old versions are traceable and citations are synchronized, and adjust
limitif necessary.