What this category's data looks like
Kindergarten operation behavior and quality self-assessment are compliance materials submitted by kindergartens on a periodic basis, typically including self-assessment reports, issue lists, and rectification plans; some kindergartens also attach ledgers, receipts, and signature pages. The material sources are kindergarten submissions, summaries from higher-level inspections, and retained historical versions. The update cadence is centralized submission per semester or year, accompanied by supplements and revisions during the period. Field characteristics center on object names, quantities, dates, signatures, and receipt status. The same record often appears repeatedly in the self-assessment report and the issue list, and forms corresponding entries in the rectification plan. After materials enter parsing and training tasks, the self-assessment report, issue list, and rectification plan each become data rows to be parsed. After parsing and chunking are completed, they are immediately persisted as visible data rows and bound to a unique data identifier, for retrieval and subsequent processing to perform field comparison and discrepancy localization.
Configuration and implementation checks
This stage 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 completed, parsing and chunking are immediately persisted as visible data rows and bound to a unique data identifier. The index transitions through the three states parsed, indexing, and indexed. Data pending indexing does not participate in recall. Changing the model only rebuilds data that has completed indexing.
| Object | Check | Verification action |
|---|---|---|
| Self-assessment report | Check whether the name, quantity, and date of the same record are consistent with the issue list | Open the data row to check the status, separately verify the file record and the data row, and compare the name, quantity, and date fields |
| Issue list | Check whether the name, quantity, and date of the same record are consistent with the rectification plan | View the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and check field discrepancies |
| Rectification plan | Check whether signatures and receipts are complete against the self-assessment report | Verify the signature page and receipt records, check whether the versions are synchronized, and record missing items |
| Data row | Is in one of the three states parsed, indexing, indexed and consistent with the interface display | View training progress by processing mode, and check the status corresponding to chunkSize, chunkSplitter, and trainingType |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the self-assessment report and the issue list. Cause: The two materials were submitted separately, without field-level comparison and version synchronization.
- Symptom: The rectification plan lacks signatures or receipts, and the materials cannot be closed-loop. Cause: The signature page and receipt status were not checked at submission, and missing items were not identified.
- Symptom: Newly uploaded materials cannot be found, and failed training leaves empty data rows. Cause: Successful parsing does not equal retrieval hits; the index status must also be checked; data pending indexing does not participate in recall.
How to verify the setup
Acceptance for this feature: Upload one material, observe the data row status transitions and the coverage scope of the rebuild task, and confirm that the three states parsed, indexing, and indexed are consistent with the interface, and that rebuild only covers data with completed indexing.
Business test: Use one real record to find fields inconsistent with the ledger, submit them to the reviewer for confirmation, and write back.
- Separately verify the file record and the data row, confirm that the identifiers of the file and the data row can be distinguished, and record discrepancies in name, quantity, and date.
- View the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and that data pending indexing does not participate in the rebuild chain.