What this category's data looks like
In the kindergarten home-school co-education communication category, materials come from class notices, parent feedback records, child observation records, commitment item ledgers, and kindergarten plans. The update rhythm rolls forward with daily communication and weekly/monthly reviews. Field characteristics include commitment items and response times, descriptions of child performance, classification of parent requests, and notice delivery status. When materials enter parsing and training tasks, notices and ledgers handle commitment and delivery verification, observation records handle performance description comparison, feedback records handle request classification, and plans handle basis tracing. Each material retains its original text position in the data rows for the retrieval layer to refer back to.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The basis entries that can refer back to the original text are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Commitment items and response times | Commitment entries can be matched to the original text and response times are traceable | Open the data row to check whether the status is parsed, indexing, or indexed, and review the original commitment and response time |
| Child performance descriptions | The wording is consistent with the observation records | Check the file records and data rows separately, and compare the performance descriptions with the original observation records |
| Parent request classification | Feedback has been classified and can refer back to the original text | Check the training mode by trainingType, and verify the request classification entries and original text positions |
| Notice delivery | Notice delivery status can refer back to the original text | Check the notice data row status and the original delivery records, and confirm that entries can be referred back to after chunking by chunkSize and chunkSplitter |
Three common errors
- Symptom: A parent asks about a commitment item but no response record can be found. Cause: The commitment item was not grouped with the response time into the same traceable basis, so the original text cannot be located during retrieval.
- Symptom: The child performance description does not match the observation record. Cause: The performance description entry does not refer back to the original observation record, or the context is truncated after chunking.
- Symptom: Parent request feedback is not classified. Cause: The feedback records were not stored by request category, so the retrieval layer cannot recall the corresponding basis entries by category.
How to verify the setup
This feature acceptance: upload one material and observe the data row status transitions and the coverage scope of the rebuild task.
Business test: ask a cross-material basis question and see whether the answer provides traceable sources.
- Open the data row to check whether the status is parsed, indexing, or indexed, and confirm it is consistent with the interface display.
- Check the file records and data rows separately, and confirm that the rebuild task only covers data whose indexing has been completed.