What this category's data looks like
This page addresses the scenario of student disciplinary actions and appeal handling. The materials include three types: factual materials on disciplinary violations, disciplinary decision documents, and appeal statements. Factual materials on disciplinary violations record the course of conduct, time and place, and witness statements; disciplinary decision documents state the basis clauses, type of disciplinary action, effective date, and signatures/seals; appeal statements contain the appeal request, reasons, submission date, and receipt. The three types of materials each have different emphases in their fields: factual materials emphasize description and witnessing, decision documents emphasize clause citations and approval signatures, and appeal statements emphasize demands and acceptance receipts. The source of the materials is the institution's routine management archiving, and they enter in batches as the incident handling progresses. The update rhythm is driven by the nodes of the disciplinary process, and the same incident produces multiple texts at different stages. When the materials enter this function, each participates in parsing and chunking as an independent data row, for subsequent retrieval positioning and basis comparison.
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 basis entries that can be traced back to the original text are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Factual materials on disciplinary violations | The name, quantity, date, and witness signature must be consistent with the facts cited in the disciplinary decision document | Check whether the behavior descriptions in the factual materials correspond item by item with the cited passages in the decision document, check whether the date and signature fields are complete, and confirm that the data row status is parsed or indexed |
| Disciplinary decision document | The basis clauses, type of disciplinary action, effective date, and approval signature must be complete and the version must be current | Compare whether the clause numbers in the decision document match the circumstances described in the factual materials, check the signature/seal and effective date, and pay attention to the impact of the chunkSize and chunkSplitter settings on clause splitting |
| Appeal statement | The appeal request, reasons, submission date, and acceptance receipt must be consistent with the delivery record of the decision document | Check whether the date of the appeal statement connects with the delivery date of the decision document, confirm the receipt signature, and check whether the data row is in indexing or indexed |
| Data rows and file records | The identity of file records and data rows can be distinguished, and the status is consistent with the interface display | Verify the file records and data rows separately, confirm the processing mode corresponding to trainingType, and check whether the rebuild task only covers indexed data |
Three common errors
- Symptom: The name or quantity of the same disciplinary record does not match between the factual materials and the decision document. Cause: The two materials are filled in at different stages, no field-level comparison is made, and after parsing they each become rows without cross-verification.
- Symptom: The version of the disciplinary decision document cited in the appeal statement is outdated. Cause: After the decision document is revised, the archive is not updated synchronously, the old version is still in a retrievable state, and the version is not synchronized.
- Symptom: The disciplinary decision document lacks an approval signature or the appeal statement lacks an acceptance receipt. Cause: The process nodes were not completed before archiving, the incomplete materials still entered parsing and chunking, and retrieval cannot trace back to valid original text.
How to verify the setup
This function's acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, and confirm that the status passes through parsed, indexing, and indexed in sequence, and that model-switch rebuilds only target indexed data.
Business test: ask a basis question that spans materials, see whether the answer provides traceable sources, and verify that the number of citations and the quoteMaxToken budget are recorded separately.
- Open the data rows to verify the status, confirm that the identity of file records and data rows is separate, and check that the settings corresponding to
chunkSize,chunkSplitter, andtrainingTypeare consistent with the three-state index display. - Compare the names, quantities, dates, and signatures of the factual materials on disciplinary violations, disciplinary decision documents, and appeal statements, and mark and correct entries with unsynchronized versions or missing receipts.