What this category's data looks like
This page focuses on kindergarten home-school co-education communication materials. Sources include teacher commitment records, child observation logs, parent request registrations, and notification delivery receipts, with an update cadence that advances daily or weekly along with class activities. After materials enter parsing and training tasks, each plays a different role: commitment records are used to verify items and response times, observation logs are used to compare descriptions of child performance, request registrations are used to check feedback categorization, and notification receipts are used to confirm delivery status. Field characteristics are mainly object names, quantities, and dates, and the same object must remain consistent across two materials. The discrepancy list is generated by retrieval and subsequent processing, handed to the reviewer for confirmation, and written back.
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 "discrepancy list" is then completed by retrieval and subsequent processing. After parsing is complete, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier; the index transitions through three states, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Commitment record | Whether the commitment item and response time are consistent | Check the response date and item name of the same commitment in the two materials, and inspect the processing mode corresponding to trainingType |
| Observation log | Whether the description of child performance matches the ledger | Compare the description field with the ledger record, and confirm that the text is not truncated after chunkSize chunking |
| Request registration | Whether the categorization of parent requests is consistent | Check the feedback categorization field, and verify whether the category label is complete after chunkSplitter splitting |
| Notification receipt | Whether the notification delivery status is consistent | Check the delivery date and object name, and confirm that the data row status is parsed, indexing, or indexed |
Three common errors
- Symptom: The response time is filled in the commitment record, but there is no corresponding response in the ledger. Cause: The commitment was not responded to, the two materials were not updated in sync, and the discrepancy list was not marked.
- Symptom: The observation log says the child napped peacefully, while the ledger records difficulty falling asleep. Cause: The wording does not match the observation record, and the description field is not aligned.
- Symptom: After a parent request is registered, there is no category label, and the reviewer cannot assign it. Cause: The feedback was not categorized, and the missing category field causes discrepancy localization to fail.
How to verify the setup
This feature acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the status transitions among parsed, indexing, and indexed, and that the rebuild covers only data whose indexing is completed.
Business test: use one real record to find the field inconsistent with the ledger, record the discrepancy list, and hand it to the reviewer for confirmation.
- Open the data row to check the status, confirm it is consistent with the interface display, and separately verify the file record and the data row identifier.
- View the data rows covered by the rebuild task, confirm that it targets only data whose indexing is completed, and that data pending indexing does not participate in the rebuild.