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—need to enter the multilingual materials and terminology processing workflow simultaneously. The question-setting two-way specification table carries the distribution of assessment points and cognitive levels, the exam paper carries the wording of question stems and options, and the grading rubric carries scoring points and translated-name cross-references. The three types of materials come from different sources and have different update rhythms: the specification table is often finalized when question setting begins, the exam paper is finalized after question review, and the grading rubric is finalized before grading. In terms of field characteristics, the specification table contains assessment point numbers, question types, and scores; the exam paper contains question numbers, question stems, options, and answers; the grading rubric contains question numbers, scoring points, translated names, signatures, and dates. When materials enter this function, the specification table provides terminology anchors, the exam paper provides wording to be unified, and the grading rubric provides the basis for translated names that can be traced back to the source text. Together, the three support the generation of a unified terminology list and a comparison draft.
Configuration and implementation checks
This step is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible and whether data in the same group is merged). The "unified terminology list and comparison draft" is then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Question-setting two-way specification table | Assessment point numbers, question types, and scores must correspond item by item with the exam paper and grading rubric, and dates and signatures must be complete | Check whether the question numbers, scores, and dates in the specification table and exam paper are consistent, inspect the signature field; confirm that the data row status is indexed or that a rebuild task record exists |
| Exam paper | The terminology wording in question stems and options must be consistent with the specification table and grading rubric, and versions must be synchronized | Extract three terms and check whether their wording is consistent throughout the entire document, verify the version number and date; check whether the citation budgets of limit cover the terminology entries |
| Grading rubric | Scoring points and translated names must be traceable back to the source text, and signatures and receipts must be complete | Check the question numbers, scoring points, and translated names in the grading rubric and exam paper, inspect signatures and receipts; confirm that the number of citations and the quoteMaxToken budget are recorded separately |
| Data row index fields | Multiple vector identifiers for one data row are all present, and the status is indexed or a rebuild task record exists | Open a data row and check the index fields to confirm that the vector identifiers are complete; in the knowledge base settings, check that the index model is consistent with the vector model actually used |
Three common errors
- Phenomenon: the same term is written differently in the specification table and the exam paper. Inspect the following: versions are not synchronized, and the two materials were finalized at different times.
- Phenomenon: the question numbers, scores, and dates for the same record do not match between the exam paper and the grading rubric. Inspect the following: manual transcription did not trace back to the source text.
- Phenomenon: the grading rubric lacks signatures or receipts. Inspect the following: compare the relevant source fields, document versions and downstream processing records.
How to verify the setup
Acceptance for this function: extract one data row and inspect the index fields to confirm that multiple vector identifiers are all present and the status is indexed or a rebuild task record exists; then perform a retrieval once and see whether data in the same group is merged, with the vector score taking the highest score.
Business test: extract three terms and check whether their wording is consistent throughout the entire document, and confirm that translated names can be traced back to the source text.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used, and view the data scope covered by the rebuild task.
- Check the index fields of the data row to confirm that the multiple vector identifiers for one data row are complete, and trigger a rebuild if necessary.