What this category's data looks like
This page addresses the deployment, operations, and application handover stage in the school safety hazard inspection and campus incident reporting scenario, centering on three types of materials: safety inspection checklists, hazard rectification ledgers, and emergency incident reports. Safety inspection checklists are recorded item by item by area and inspection item, with fields including inspection date, inspector, hazard description, and signature; hazard rectification ledgers use the hazard number as the thread, recording the rectification responsible person, rectification deadline, completion date, and receipt; emergency incident reports contain the incident name, occurrence time, number of people involved, handling process, and reporting signature. The three types of materials have different update rhythms: checklists are generated weekly or monthly, rectification ledgers are updated on a rolling basis as hazard status changes, and incident reports are submitted immediately when an incident occurs. When the materials enter the knowledge base retrieval and recall function, checklists and ledgers are mainly recalled as historical inspection evidence, while incident reports are recalled as reporting wording and handling references; together the three support item-by-item verification of the handover form.
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, re-rank, filter, and limit trimming). The handover-ready deployment status and operation records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Safety inspection checklist | Whether the inspection date, inspector, hazard description, and signature are complete, and whether the name and quantity of the same hazard match across the two materials | In the search test, test the same inspection item once with each of different phrasings, record the number of candidates and the score, and check the values of searchMode and similarity |
| Hazard rectification ledger | Whether the rectification deadline, completion date, and receipt signature are complete, and whether the version is in sync with the checklist | Compare the order of the top few results before and after enabling re-rank, record the usingReRank status, and check the reference text tokens and array count after limit trimming |
| Emergency incident report | Whether the incident name, occurrence time, number of people involved, and reporting signature are consistent, and mark any missing signature or receipt | Verify the report and ledger item by item against the handover form for date, name, and quantity, and record the candidate chunks and scores |
Three common errors
- Symptom: The name, quantity, and date of the same hazard do not match between the checklist and the rectification ledger. Cause: The two materials were entered separately, no cross-check was done by hazard number, and only a single material was checked during handover.
- Symptom: The knowledge base material versions are not in sync, and the old checklist is still recalled. Cause: Indexing was not re-triggered after the update, the retrieval side still returns old candidates, and the handover form does not record the version change time.
- Symptom: The emergency incident report lacks a signature or receipt, but the handover form marks it as verified. Cause: Only the body of the report was checked during verification, and the signature field and receipt attachment were not checked item by item, so missing items were omitted from the record.
How to verify the setup
This function's acceptance: test once with each synonym-rewritten question, compare candidates and scores, then toggle re-rank on and off to see the ordering of the top few results; check the values of the three identifiers searchMode, similarity, and usingReRank, record the number of candidates and the score, and record the reference text tokens and array count separately.
Business test: verify once item by item against the handover form and see which item is missing from the record; compare against the fields, dates, and signatures of the safety inspection checklist, hazard rectification ledger, and emergency incident report, and confirm that the version, connections, and task records are consistent.
- In the knowledge base search test, switch between semantic, full-text, and hybrid modes, retrieve the same inspection item with different phrasings, record the number of candidates and the score, and check the reference text tokens after
limittrimming. - Verify the dates, names, quantities, signatures, and receipts of the checklist, rectification ledger, and incident report item by item against the handover form, mark missing items, and record the version sync status.