Knowledge Base Retrieval for Kindergarten Operations and Quality Self-Assessment: Maintain Document Versions and Changes

Kindergarten Quality: review retrieval for version tracking. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

Kindergarten operation behavior and quality self-assessment materials usually come from the kindergarten's self-assessment report, issue list, rectification plan, as well as superior evaluation feedback and receipts. Materials are updated by semester or year, and fields include kindergarten name, class and child counts, item name, occurrence date, responsible person, rectification deadline, signature and receipt status. When entering the knowledge base retrieval service, the self-assessment report provides overall conclusions and descriptions of indicator achievement, the issue list provides item-by-item facts and responsibility assignments, the rectification plan provides time nodes and acceptance methods, and the receipt and signature pages provide closure evidence. The update rhythm is mainly replacement by revised versions, and old versions need to be archived and traceable. During retrieval, the three types of materials each become sources of candidate chunks, and the similarity score determines the presentation order, for subsequent nodes or humans to generate a version ledger and change records accordingly.

Configuration and implementation checks

This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks and similarity scores (after mode, merge, rerank, filter, and limit trimming). The "version ledger and change records" are then completed by subsequent nodes or humans.

ObjectCheckVerification action
Self-assessment reportThe kindergarten name, class and child counts, item name, date, and signature in the report must correspond item by item with the issue listIn the search test, use synonymous rewritten questions to retrieve once each, record the number of candidates and scores, and check whether the report fields and list fields are consistent
Issue listThe item name, quantity, date, and responsible person of the same record in the list and rectification plan must be consistent; missing signatures or receipts must be markedSwitch searchMode to compare semantic, full-text, and hybrid candidates, check whether the same item is recalled at the same time, and verify the date and signature status
Rectification planThe rectification deadline, acceptance method, and receipt in the plan must close with the issue list, and old versions must be traceableAdjust similarity and limit to observe candidate trimming, record the cited text tokens and array count, and confirm that old versions can still be retrieved
Version ledgerThe current version is unique, old versions are traceable, citations are synchronized, and change records include revision date and revision descriptionCompare the ranking of the first few items before and after enabling usingReRank, and check whether the version number and citations of the same item are updated synchronously

Three common errors

  • Phenomenon: The name, quantity, or date of the same item in the self-assessment report and issue list do not match. Cause: The two materials were revised separately, without field-level comparison and version synchronization.
  • Phenomenon: The rectification plan has been updated, but retrieval still returns old-version chunks, and citations are not synchronized. Cause: The old version was not marked as invalid, and the version ledger did not record the replacement relationship.
  • Phenomenon: The issue list lacks signatures or receipts, and the rectification closure cannot be confirmed. Cause: The signature pages did not enter the knowledge base with the materials, or the receipt status is not reflected in the fields.

How to verify the setup

Acceptance of this feature: test once each with synonymous rewritten questions, compare the number of candidates and similarity scores, then toggle usingReRank to see changes in the ranking of the first few items; switch searchMode to compare semantic, full-text, and hybrid candidates.

Business test: change one piece of content and see whether the version number and citations are updated synchronously.

  • In the search test, retrieve the same item using two question formulations, record the number of candidates and scores, and check whether the name, quantity, date, and signature of the self-assessment report, issue list, and rectification plan are consistent.
  • After adjusting similarity and limit, retrieve again, separately record the cited text tokens and array count, and confirm that the current version is unique, old versions are traceable, and citations are synchronized.