What this category's data looks like
This page focuses on the category of primary and secondary school teacher training credit management. Material sources include training notices, credit recognition forms, participant lists, receipts, and signature pages. The training notice determines the project name, class hours, and start and end dates; the credit recognition form carries the teacher's name, subject, credit amount, and recognition conclusion; the participant list records attendance and sign-in information; the receipt and signature page serve as evidence that the materials are complete. These materials enter the knowledge base by semester or project batch, and the update rhythm is synchronized with the training cycle. When entering the document parsing and chunking stage, the notice and recognition form provide the field structure, the list provides personnel and date rows, and the receipt provides signature status. After chunking, searchable data rows are formed for reference by the version ledger and change records.
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). "Version ledger and change records" are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Whether the project name, class hours, and start and end dates are consistent with the credit recognition form | Check the date fields of the notice and the recognition form, and confirm that the data row status after chunking is parsed, indexing, or indexed |
| Credit recognition form | Whether the teacher's name, subject, credit amount, and signature column are complete | Check the names and amounts in the recognition form and the participant list row by row, and check whether the receipt signature is missing |
| Participant list | Whether the attendance dates and sign-in records correspond to the notice batch | Compare the list dates with the notice start and end dates, and confirm that the name and amount of the same record are consistent in both materials |
| Data rows and file records | Whether the identities of file records and data rows are kept separate | Check the file records and data rows separately, confirm that the unique data identifier is consistent with the interface display, and use trainingType to distinguish processing modes |
Three common errors
- Symptom: The name or credit amount of the same teacher does not match between the recognition form and the participant list. Cause: The two materials are entered separately, lacking cross-material field verification and a closed loop for signature receipts.
- Symptom: The notice has been updated, but the knowledge base still recalls the old version content. Cause: The version was not synchronized, the old version was not marked invalid, and references were not updated with the version number.
- Symptom: After a training failure, empty data rows are left, and the just-uploaded material cannot be found. Cause: Successful parsing does not equal completed indexing; data pending indexing does not participate in recall, and the index status must be checked.
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, and confirm that the status only changes among parsed, indexing, and indexed, and that the rebuild only covers data that has completed indexing.
Business test: Change one piece of content and see whether the version number and references are updated synchronously.
- Open the data rows to check the status, confirm that it is consistent with the interface display, and record the separate identities of the file records and data rows.
- Check the data rows covered by the rebuild task, confirm that it only targets data that has completed indexing, and use
chunkSize,chunkSplitter, andtrainingTypeto check the chunking and training modes.