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, often circulated in the form of multilingual parallel drafts. The material sources are daily inspections of the kindergarten, drill organization, and security handovers, and the update cadence advances weekly or per drill. Field characteristics center on hazard items and rectification deadlines, drill headcount and sign-in, access control and school bus inspection items, and responsible person signatures. When materials enter parsing and training tasks, they are first stored as data rows as files to be parsed, and then split into retrievable content by parsing chunks; the finished glossary and parallel drafts are generated by retrieval and subsequent processing after indexing is complete, and the materials themselves are only responsible for providing stable fields and multilingual text.
Configuration and implementation checks
This stage is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The unified glossary and parallel drafts are then completed by retrieval and subsequent processing. After parsing is complete, parsing chunks are immediately stored as visible data rows and bound to a unique data identifier, and indexing flows through the three states parsed / indexing / indexed.
| Object | Check | Verification action |
|---|---|---|
| Hazard rectification ledger | Hazard items and rectification deadlines must be closed item by item, and the same term must be written consistently in the parallel draft | Open the data row to check whether the status is indexed, and use chunkSize and chunkSplitter to check whether the chunk boundary cuts off the deadline field |
| Drill plan and sign-in sheet | The drill headcount and sign-in records must be consistent with the plan, and responsible person signatures must not be missing | Check the file records and data rows separately, confirm that trainingType corresponds to the three index states, and sample three terms to check whether their writing is consistent throughout the document |
| Access control and school bus inspection records | Inspection items must not be omitted, and multilingual translated names must be able to refer back to the source text | Check whether the data rows covered by the rebuild task contain only data whose indexing has been completed, and check whether the inspection items and signature columns are complete |
Three common errors
- Symptom: hazards are not closed, and rectification deadlines are written inconsistently in the multilingual parallel draft. Cause: parsing chunks cut off the deadline field, and the index status is retrieved before reaching indexed.
- Symptom: drill records do not match the plan, and headcount and sign-in do not correspond. Cause: the source data and split items are not bound to the same data identifier, and the rebuild scope covers data awaiting indexing.
- Symptom: access control and school bus inspection items are omitted, and translated names cannot refer back to the source text. Cause: the chunk boundary does not cover the full inspection item table, and the glossary is referenced before indexing is complete.
How to verify the setup
Acceptance for this feature: upload one material, observe the status transitions of the data rows and the coverage scope of the rebuild task, confirm that the three states parsed / indexing / indexed are consistent with the interface display, and that the rebuild covers only data whose indexing has been completed.
Business test: sample three terms to check whether their writing is consistent throughout the document, and whether the translated names can refer back to the source text.
- Open the data row to check whether the status is indexed, 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 been completed is covered, and that data awaiting indexing does not participate in the rebuild