What this category's data looks like
This page focuses on the business basis query for school moral education and homeroom teacher work. The materials come from three categories: this kindergarten's thematic class meeting plans, student comprehensive quality records, and home visit records. Thematic class meeting plans provide activity objective and process fields; comprehensive quality records carry student performance and evaluation fields; home visit records retain communication time, object, and receipt fields. The three are updated by semester and by month, and dates, signatures, quantities, and names must be aligned item by item. After the materials enter document parsing and chunking, each becomes an independent data row bound to a unique data identifier, for the retrieval layer to decide whether to recall based on index status. Thematic class meeting plans focus on process nodes, comprehensive quality records focus on field completeness, and home visit records focus on signatures and receipts. Together, the three support basis entries that can be traced back to the original text.
Configuration and implementation checks
Parsing and training tasks (server-side tasks) only output data rows and index status (parsed, indexing, indexed); basis entries that can be traced back to the original text must be handled next by retrieval and subsequent processing. After parsing is completed, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier; the index flows through three states, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Thematic class meeting plan | Fields include activity objective, process, date, and signature, and must be aligned with the name, quantity, and date in the student comprehensive quality records | Open the data row to check that the status is consistent with the interface display, and confirm that entries split by chunkSize and chunkSplitter can be traced back to the original text |
| Student comprehensive quality record | Fields include evaluation items, date, and signature, and must match the student name and date in the home visit records | Check the file records and data rows separately, and confirm that trainingType and the three index states parsed / indexing / indexed flow correctly |
| Home visit record | Fields include communication time, object, receipt, and signature, and must be consistent with the date and quantity in the thematic class meeting plans | View the data rows covered by the rebuild task, and confirm that only data with completed indexing is covered, and data pending indexing does not participate in the rebuild |
| Data row and index status | Is in one of the three states parsed / indexing / indexed and is consistent with the interface display | Open the data row to check the status, confirm that data pending indexing does not participate in recall, and that changing the model only rebuilds data with completed indexing |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match across two materials. Cause: the materials are parsed and persisted independently, fields are not aligned across materials, and disagreements appear when tracing back to the original text.
- Symptom: versions are not synchronized, and an old plan is still recalled. Cause: the rebuild only targets data with completed indexing, data pending indexing does not participate in the rebuild chain, and the old version's index status is not updated in time.
- Symptom: a signature or receipt is missing, and the basis entry cannot be closed. Cause: parsing and chunking only output data rows and index status; when signature and receipt fields are missing, the retrieval layer may still hit them.
How to verify the setup
This feature's acceptance: upload a thematic class meeting plan, watch the data row status flow from parsed to indexing and then to indexed, and check that the rebuild task only covers data with completed indexing, confirming that chunkSize, chunkSplitter, and trainingType are recorded in the data row.
Business test: ask a cross-material basis question, for example whether the date in a certain home visit record is consistent with that in the comprehensive quality record, and see whether the answer gives a traceable source.
- Open the data row to check that the status is consistent with the interface display, and confirm that the identities of the file record and the data row are distinguishable from each other.
- View the data rows covered by the rebuild task, and confirm that only data with completed indexing is covered, and data pending indexing does not participate in the rebuild.