What this category's data looks like
In the scenario of exam question setting and grading in primary and secondary schools, three types of materials—the question-setting two-way specification table, the exam paper, and the grading rubric—often circulate in parallel, with sources covering the teaching and research group's final draft, the school's issuance, and the district/county filing receipt. The update cadence is driven by the exam cycle: concentrated revisions before the exam, and patches based on feedback after the exam. Field characteristics are concentrated in four categories: name, quantity, date, and signature, and the same record is prone to mismatches across two materials. When the materials enter the document parsing and chunking function, the specification table plays the role of mapping assessment points to question numbers, the exam paper plays the role of carrying question stems and score values, and the grading rubric plays the role of scoring points and grade descriptions; together, the three form the comparison source for 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). The version ledger and change records are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | Assessment point names, question number quantities, and signature dates must be consistent with the exam paper, and the signature field must not be blank | Compare the assessment point names, question number quantities, dates, and signatures of the specification table and the exam paper row by row, and check whether the chunking of table rows by chunkSize and chunkSplitter is complete |
| Exam paper | The total score of question stems matches the number of scoring points in the grading rubric, and the version number and references are in sync | Open the data row to check whether the status is parsed / indexing / indexed, then check whether the identities of the file record and the data row are distinguishable |
| Grading rubric | Grade descriptions and the number of scoring points are consistent with the exam paper, and the receipt or signature is complete | Check the file record and the data row separately, and confirm the processing mode corresponding to trainingType and the data rows covered by the rebuild task |
| Version ledger and change records | The current version is unique, old versions are traceable, and references are in sync | After changing one piece of content, check whether the version number and references are updated in sync, and confirm that the rebuild only covers data that has completed indexing |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the specification table and the exam paper. Cause: the two materials were finalized separately, and no field-level comparison was performed.
- Symptom: an old version of the exam paper is still referenced, and the version is not in sync. Cause: the change record was not written back to the ledger, and the reference chain was not updated with the version number.
- Symptom: the grading rubric lacks a signature or receipt. Cause: the issuance step was not checked in linkage with the parsing and database persistence status.
How to verify the setup
Upload one material, observe the status transitions of the data rows and the coverage scope of the rebuild task, confirm that data pending indexing does not participate in recall, and that changing the model only rebuilds data that has completed indexing.
Business test: change one piece of content, and check whether the version number and references are updated in sync.
- Open the data row to check whether the status is parsed / indexing / indexed, and keep it consistent with what the interface displays.
- Check the file record and the data row separately, and confirm that the rebuild task only covers data rows that have completed indexing.