What this category's data looks like
This category's data covers three core types of materials: daily life schedules, morning and afternoon check records, and child health observation records. Daily life schedules come from the kindergarten's childcare and education plan and are updated by semester or season; their fields include time period, activity segment, teacher and childcare worker division of duties, and venue. Morning and afternoon check records are filled in daily by health personnel; their fields include date, child's name, body temperature, oral and skin condition, and parent signature. Child health observation records are filled in by class teachers as needed; their fields include observation time, description of behavior, handling measures, and health personnel receipt. After these three types of materials enter the document parsing and chunking function, each plays a different role: the schedule serves as the institutional basis and is split into time-period and responsibility chunks; morning and afternoon check records serve as daily logs and are split into entry chunks by date and child; health observation records serve as case tracking and are split into observation event chunks. In terms of update rhythm, schedules are adjusted by semester or season, morning and afternoon check records are added daily, and health observation records are supplemented whenever events occur. In terms of field characteristics, date, child's name, body temperature value, signature, and receipt are the key anchors for cross-material alignment; once names, quantities, or dates do not match, the version ledger and change records lose their unique current version.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), which outputs data rows and index status (parsed, indexing, indexed). The version ledger and change records are then completed by retrieval and subsequent processing. After parsing is completed, parsing 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 |
|---|---|---|
| Daily life schedule | The time period, activity segment, teacher and childcare worker division of duties, and venue fields are complete, and consistent with the current version number | After checking the chunkSize and chunkSplitter settings of the schedule data row, confirm that the time-period and responsibility chunks are complete; open the data row to see whether the status is parsed, indexing, or indexed |
| Morning and afternoon check records | Date, child's name, body temperature, oral and skin condition, and parent signature align item by item, and the names and quantities in the two materials are consistent | Check the file records and data rows separately to confirm that dates and child names are not misaligned; check whether the signature field is empty, and if a signature is missing, mark it as pending supplementation |
| Child health observation records | Observation time, description of behavior, handling measures, and health personnel receipt are complete, and the dates match the morning and afternoon check records | Check the data rows covered by trainingType and the rebuild task, and confirm that only data with completed indexing is covered; compare whether the receipt is missing |
| Version ledger and change records | The current version is unique, old versions are traceable, references are synchronized, and after changing one piece of content, the version number and references are updated at the same time | After changing one piece of content, check whether the version number and references are updated synchronously; confirm that the rebuild scope targets only data with completed indexing |
Three common errors
- Symptom: The child's name, body temperature quantity, or date in the same morning and afternoon check record does not match between the daily life schedule and the health observation record. Cause: The material sources are not synchronized, and after parsing and chunking, alignment was not performed by date and name anchors.
- Symptom: The schedule has been updated to the new semester, but the knowledge base or external documents still reference the old version's time periods and responsibilities. Cause: The version was not synchronized, and the old data rows are still in completed indexing status and are being recalled.
- Symptom: Morning and afternoon check records or health observation records lack a parent signature or health personnel receipt, and the ledger cannot determine the current version. Cause: The signature field was empty when parsing was persisted, and subsequent processing did not intercept it.
How to verify the setup
This function's acceptance: upload one material and observe the data row status transitions and the coverage scope of the rebuild task. Check whether data rows transition through the three states parsed, indexing, and indexed and are consistent with the interface; check that file records and data rows each have distinguishable identities; check that the rebuild task covers only data with completed indexing, and that data pending indexing does not participate in recall.
Business test: change one piece of content and see whether the version number and references are updated synchronously. Change a time period in the daily life schedule or a body temperature entry in the morning and afternoon check records, confirm that the version ledger generates a new version number, that the old version is traceable, and that external documents referencing that content synchronously point to the new version.
- Open the data row to check the status, and confirm that it is in one of parsed, indexing, or indexed and consistent with the interface display; check the file records and data rows separately, and confirm that file records and data rows each have distinguishable identities.
- View the data rows covered by the rebuild task, and confirm that only data with completed indexing is covered; after changing one piece of content, check whether the version number and references are updated synchronously, and check whether signatures and receipts are complete.