What this category's data looks like
Materials for exam organization and violation handling include exam administration manuals, examination room record sheets, and violation fact records. Their sources are the exam administration department and test site receipts, and their update cadence changes with exam batches and institutional revisions. The exam administration manual defines processes and field conventions; the examination room record sheet carries on-site time, headcount, and signatures; the violation fact record locks down facts, dates, and receipts. When these three types of materials enter document parsing and chunking, the exam administration manual serves as the rule source and participates in chunking and indexing, while the examination room record sheet and violation fact record serve as evidence rows. After being split by field, they are bound to a unique data identifier for subsequent retrieval and version ledger reference. Field characteristics center on names, quantities, dates, signatures, and receipts, and records with the same name must maintain consistent conventions across different materials.
Configuration and implementation checks
Parsing and training tasks (server-side tasks) only output data rows and index status (parsed, indexing, indexed); the version ledger and change records must be handled next by retrieval and subsequent processing. After parsing is complete, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier. Indexing flows through the three states parsed, indexing, and indexed, and data pending indexing does not participate in recall. Changing models only rebuilds data that has already completed indexing.
| Object | Check | Verification action |
|---|---|---|
| Exam administration manual | Whether the field conventions and date version are unique, and whether signature and receipt requirements are synchronized with the batch | Check the parsed, indexing, and indexed status of each chapter after chunking by chunkSize and chunkSplitter |
| Examination room record sheet | Whether the name, quantity, and date of the same record match across the two materials, and whether signatures are complete | Check the file record and the data row separately, and confirm that the examination room record sheet and the exam administration manual reference the same data identifier |
| Violation fact record | Whether the violation facts, date, and receipt are consistent with the record sheet, and whether the old version is traceable | View the data row status under the training mode corresponding to trainingType, and confirm that rebuilding only covers indexed data |
| Version ledger | Whether the current version is unique, whether the old version is traceable, and whether references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and inspect the number of array entries and the reference text tokens |
Three common errors
- Symptom: A material that was just uploaded cannot be found. Cause: The data row is in parsed or indexing, and data pending indexing is naturally isolated at the retrieval layer and is not recalled, so you must wait for indexing to complete.
- Symptom: The name, quantity, and date of the same record do not match between the exam administration manual and the examination room record sheet. Cause: After chunking, the two materials were not bound to the same data identifier, and the versions were not synchronized.
- Symptom: After a training failure, empty data rows remain, or signatures and receipts are missing. Cause: The initial training overwrote data pending indexing, the failed data was not edited or deleted, and the material itself has incomplete fields.
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 transitions from parsed to indexing to indexed are consistent with the interface display, and that rebuilding only covers indexed data.
Business test: Change one piece of content and check whether the version number and references are updated synchronously
- Open the data row to check the status, and confirm that it is in one of the three states parsed, indexing, or indexed and is consistent with the interface display
- Check the file record and the data row separately, confirm that the identities of the file record and the data row are distinguishable, and record the number of reference array entries and the reference text tokens