What this category's data looks like
Kindergarten safety protection and emergency drill materials include hazard rectification ledgers, drill plans and sign-in sheets, access control and school bus inspection records, and responsible person signature pages. Sources are daily kindergarten inspections, drill execution, and security handovers. The update cadence changes with monthly inspections, quarterly drills, and semester checks. Materials are mainly tables, scanned documents, and photo attachments, with fields including hazard item, rectification deadline, number of drill participants, sign-in list, inspection item, responsible person signature, and date. After entering this function, the original materials are first parsed and chunked into the database as visible data rows and bound to a unique data identifier, then flow through the three index states for retrieval and subsequent processing to complete the discrepancy list.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index states (parsed, indexing, indexed). The "discrepancy list" is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Hazard rectification ledger | Whether the hazard item and rectification deadline form a closed loop, and whether the name, quantity, and date of the same hazard are consistent across the two materials | Check the file records and data rows separately, view whether the data row status is parsed / indexing / indexed, and check whether the chunkSize and chunkSplitter splitting of table rows preserves the hazard item and deadline fields |
| Drill plan and sign-in sheet | Whether the number of drill participants corresponds to the sign-ins, and whether the drill record matches the plan | Check the data row status transitions, confirm that the sign-in list and the plan participant count fall under the same data identifier, and use trainingType to distinguish vector and QA processing modes to view training progress |
| Access control and school bus inspection records | Whether access control and school bus inspection items are missing, and whether the responsible person signature and date are complete | Open the data rows to check status, check whether the inspection item fields are fully stored in the database, mark items that are not closed-loop, hand them to the reviewer for confirmation, and write back |
| Responsible person signature page | Whether the responsible person signature and date are consistent with the ledger | Check the file records and data rows separately, confirm that the signature page is not misaligned with the main table after parsing, and enter retrieval only after the index status is indexed |
Three common errors
- Symptom: newly uploaded materials cannot be found. Cause: the data rows are still in parsed or indexing, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Symptom: the drill record does not match the plan. Cause: the sign-in sheet and the plan are not bound to the same data identifier after chunking, and the participant count and date fields are split apart during retrieval.
- Symptom: inspection items are missing or hazards are not closed-loop. Cause: access control and school bus inspection items are truncated during parsing and chunking, and the rectification deadline field is not stored in the database together with the hazard item.
How to verify the setup
This function's acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the transitions from parsed to indexing to indexed are consistent with the interface display, and when changing models only rebuild data whose indexing has already been completed.
Business test: use one real record to find a field inconsistent with the ledger, hand it to the reviewer for confirmation, and write back.
- Open the data rows to check status, confirm that the three states are consistent with the interface display, and check the file records and data rows separately.
- Look at the data rows covered by the rebuild task, confirm that only data whose indexing has already been completed is covered, and that data pending indexing does not participate in the rebuild.