What this category's data looks like
This page addresses kindergarten safety protection and emergency drill scenarios. The materials come from the kindergarten's safety management system, hazard inspection ledger, emergency drill plans and sign-in records, access control and school bus inspection forms, responsible person signature pages, etc. After these materials enter the knowledge base, the vector model and index play a recall support role, while the original data remains in the business database data tables for later stages to trim and reference. The update rhythm changes with semester inspections, drill organization, and rectification backfilling. Field characteristics include hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus inspection items, and responsible person signatures. When the materials enter this function, each serves as a recallable support fragment and does not directly generate conclusions.
Configuration and implementation checks
This step is executed by the index service and vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). The 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).
| Object | Check | Verification action |
|---|---|---|
| Index model | Consistent with the vector model actually used by the knowledge base; otherwise recall quality decreases | Check the index model in the knowledge base settings, and view the data range covered by the rebuild task |
| Index fields of the data row | Multiple vector identifiers for one data item are all present; during retrieval, data in the same group is merged by taking the highest score | Open a data row to check the index fields, and run a retrieval to see whether duplicate entries appear |
| Hazard inspection ledger | Hazard items match the original text with rectification deadlines and responsible person signatures, and the hazard has been closed-loop | Extract hazard entries and trace them back to the original text, checking whether the rectification deadline and signature are complete |
| Emergency drill plans and sign-in records | Drill headcount and sign-in, and drill records and plans, are consistent, with no missing inspection items | Compare the drill plan with the sign-in headcount, and check whether access control and school bus inspection items are missing |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the same group of data corresponds to multiple vector identifiers, and the merge step does not consolidate by the highest score, causing duplicate returns of content from the same group.
- Symptom: the hazard is not closed-loop. Inspect the following: hazard items in the ledger are not updated synchronously with rectification deadlines and responsible person signatures, and the basis is incomplete when replying to parents.
- Symptom: drill records do not match the plan. Inspect the following: drill headcount and sign-in, and missing inspection items, are not backfilled, material versions are inconsistent.
How to verify the setup
This function's acceptance: extract one data row to check the index fields, then run a retrieval to see whether the same group is merged; status values only recognize indexed and rebuild task records, check limit, and the tokens of the referenced text, and record the number of array items separately.
Business test: ask a basis question that spans materials, and see whether the answer gives a traceable source.
- Open a data row to check the index fields, confirm that multiple vector identifiers are all present, and view the data range covered by the rebuild task
- Check the index model in the knowledge base settings, run a retrieval to observe whether data in the same group is merged, and record the reference budget of
limit