What this category's data looks like
This page addresses the category of school safety hazard inspection and campus incident reporting. Materials include safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are filled in weekly or monthly by the teacher on duty and the homeroom teacher, with fields including inspection item, location, date, and inspector signature; hazard rectification ledgers are updated on a rolling basis by the safety officer or logistics lead, item by item, with fields including hazard name, quantity, rectification deadline, responsible person, and re-inspection signature; emergency incident reports are submitted on the day of the incident by the on-site teacher or school doctor, with fields including incident name, number of people involved, time, handling process, and reporting receipt. When the three types of materials enter the knowledge base retrieval service, each is split and recalled as an independent source, used to answer hazard queries and incident tracing within the authorized scope, and does not replace the original ledgers and reports. In terms of update cadence, the rectification ledger is the most frequent, followed by the checklists, while incident reports are generated as incidents occur.
Configuration and implementation checks
The knowledge base retrieval service (retrieval node and search test) only outputs candidate chunks and similarity scores (after pattern, merge, re-rank, filter, and upper-limit truncation); the externally facing entry point and authorized scope must be handled by subsequent nodes or manually. A single retrieval consists of question optimization, semantic or full-text or hybrid recall, multi-path merging, re-rank secondary sorting, similarity filtering, and reference upper-limit truncation, and only then is the reference content handed to the model obtained.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Inspection item, location, date, and inspector signature must correspond one by one with the hazard rectification ledger; the name and quantity of the same item must not be inconsistent between the two materials | In the search test, test once each with synonym-rewritten questions, record the number of candidates and scores, and check whether the returned chunks cover the inspection item and signature fields |
| Hazard rectification ledger | Hazard name, quantity, rectification deadline, responsible person, and re-inspection signature must be consistent with the safety inspection checklist and emergency incident reports, and versions must be synchronized | Switch searchMode to semantic, full-text, and hybrid once each, compare whether candidates contain both semantic and full-text results, and check the rectification deadline and quantity fields |
| Emergency incident report | Incident name, number of people involved, time, handling process, and reporting receipt must be consistent with the ledger records; entries missing signatures or receipts should not be externally visible content | Turn usingReRank on and off to compare the ranking of the top few results, adjust similarity and limit to observe changes in the number of candidates and scores, and separately record the number of items in the reference array |
| External entry point and authorized scope | Visitor identity matches the visible scope; unauthorized content is not visible; parents or superiors see only their corresponding scope | Access once with a restricted identity, see whether the visible scope matches the setting, and check the tokens budget of the reference text rather than comparing it for equality with the number of array items |
Three common errors
- Symptom: the name, quantity, and date of the same hazard do not match between the two materials. Cause: the checklist and the rectification ledger are entered separately, without backfilling and checking against the same record.
- Symptom: an emergency incident report missing a signature or receipt is still recalled by retrieval. Cause: material versions are not synchronized, and the old draft and the new draft are both stored in the knowledge base without filtering.
- Symptom: there are many candidates, but the ones ranked at the front are all irrelevant, and the answer lacks key passages. Cause: the retrieval mode does not match the material form, re-rank is not enabled, or similarity filtering is too loose.
How to verify the setup
Acceptance of this feature: test once each with synonym-rewritten questions, compare candidates and scores, then turn re-rank on and off to see the ranking of the top few results, and check the number of candidates and scores under searchMode, similarity, and limit.
Business test: access once with a restricted identity, see whether the visible scope matches the setting, and unauthorized content should not appear in candidates or references.
- In the knowledge base search test, switch retrieval modes, record the number of candidates and scores item by item, and check whether the name, quantity, date, and signature fields of the safety inspection checklist, hazard rectification ledger, and emergency incident report are consistent.
- Adjust similarity filtering and the reference upper limit, separately record the number of items in the reference array and the reference text tokens, confirm that key passages of the original text are still retained after truncation, and then check the authorized scope of the external entry point.