What this category's data looks like
In the student disciplinary and appeal processing scenario, material sources include three types: disciplinary fact materials, disciplinary decision documents, and appeal letters. They are usually produced separately by student affairs, academic affairs, and the appeal acceptance stage at different points in time, and their update cadence enters in batches as the disciplinary process advances. Disciplinary fact materials carry behavior descriptions, time and location, and witness information; disciplinary decision documents carry the type of disciplinary action, the cited provisions, and the effective date; appeal letters carry the appeal request, reasons, and receipt signature. When the three types of materials enter the document parsing and chunking function, each is stored as an independent data row and bound to a unique data identifier. At the field level, attention is paid to whether names, quantities, dates, and signatures can be traced back to the original text, providing a searchable draft for the subsequent unified terminology table and comparison draft.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), outputting data rows and index status (parsed, indexing, indexed). The "unified terminology table and comparison draft" is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | The names, quantities, and dates of the same record in the fact materials and the decision document must match, and signatures and receipts must not be missing | Check the material fields against the corresponding items in the decision document, and check whether the date and signature paragraphs are retained after chunking by chunkSize and chunkSplitter |
| Disciplinary decision document | The type of disciplinary action, cited provisions, and effective date must be consistent with the fact materials, and versions must be synchronized | Compare the provisions cited in the decision document and the appeal letter, and check whether the data row status is parsed, indexing, or indexed |
| Appeal letter | The appeal request and reasons must be traceable back to the original text, and the receipt signature must not be missing | Check the dates and names in the appeal letter and the decision document, and confirm that the index status is completed under the processing mode corresponding to trainingType |
| Data row | It is in one of the three states and consistent with the interface display, and the file record and the data row identity can be distinguished | Open the data row to check the status, check the file record and the data row separately, and view the coverage scope of the rebuild task |
Three common errors
- Symptom: The names, quantities, or dates of the same disciplinary record do not match between the fact materials and the decision document. Cause: Multilingual materials and terminology handling are not unified, and fields after chunking are not traced back to the original text.
- Symptom: The appeal letter lacks a signature or receipt, and versions are not synchronized. Cause: Materials enter in batches, the old version is stored first, and the new version does not overwrite the same data identifier.
- Symptom: Newly uploaded materials cannot be found, and failed training leaves empty data rows. Cause: Successful parsing does not equal a retrieval hit, and the index status has not reached completed.
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, confirm that the three states parsed, indexing, and indexed are consistent with the interface, and that rebuild only covers data whose indexing is completed.
Business test: Sample three terms and check whether their spelling is consistent throughout the entire text, confirm that translated names can be traced back to the original text, and record cited text tokens and array item counts separately.
- Open the data row to check the status, check the file record and the data row separately, and confirm that the unique data identifier is bound correctly.
- View the data rows covered by the rebuild task, confirm that it targets only data whose indexing is completed, and that data pending indexing does not participate in the rebuild.