What this category's data looks like
This page centers on kindergarten operation behavior and quality self-assessment, placing three types of materials—self-assessment reports, problem lists, and rectification plans—into the same basis query pipeline. Self-assessment reports provide statements of indicator achievement and supporting descriptions, problem lists record items to be improved and responsibility assignments, and rectification plans carry measures, deadlines, and receipts. Materials are mostly updated by semester or special-topic milestone, fields include record name, quantity, date, signature, and receipt, and version relationships are complex. After entering this feature, the three types of materials are first parsed into retrievable data rows, each retaining its original text location and identity identifier, for later reference back to the original text by basis item, to support replying to parents or writing into proposals.
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). "Basis items that can be traced back to the original text" are then completed by retrieval and subsequent processing. After parsing is completed, parsing and chunking 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 |
|---|---|---|
| Self-assessment report | The record name, quantity, date, and signature must match those in the problem list and rectification plan, and the version must be the current one | Open the data row to check whether the status is parsed, indexing, or indexed, and separately verify the identity identifiers of the file record and the data row |
| Problem list | When the name, quantity, and date of the same record are inconsistent across the two materials, it must not be used directly as a basis item | Verify the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and check whether the chunkSize chunking splits items apart |
| Rectification plan | Items lacking a signature or receipt cannot serve as closed-loop basis, and versions that are not synchronized must be aligned first | Verify the respective identities of the file record and the data row, confirm that after setting trainingType and chunkSplitter, the index status is consistent with the interface display |
Three common errors
- Symptom: newly uploaded materials cannot be found. Cause: the data row is in a pending-indexing state, and the retrieval layer naturally isolates it from recall, so you must wait for indexing to complete.
- Symptom: the name, quantity, and date of the same record do not match across the two materials. Cause: versions are not synchronized, the old-version material still participates in parsing and chunking, and the item refers back to the old original text.
- Symptom: empty data rows are left after training fails. Cause: successful parsing does not equal a retrieval hit, the index status is not completed, and items lacking a signature or receipt are also mixed into the basis.
How to verify the setup
This feature's acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that it is in one of the three states parsed, indexing, or indexed and is consistent with the interface; changing the model only rebuilds data with completed indexing, and the initial training covers data pending indexing.
Business test: ask a basis question that spans materials, see whether the answer gives a traceable source, and verify that the tokens of the cited text and the number of array entries are recorded separately.
- Open the data row to check the status, separately verify the file record and the data row, confirm that the three states are consistent with the interface display, and that data pending indexing does not participate in recall.
- View the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and check
chunkSize,chunkSplitter,trainingType, and the index status.