What this category's data looks like
This page addresses student disciplinary and appeal handling scenarios, involving three types of business materials: disciplinary fact materials, disciplinary decision documents, and appeal statements. Disciplinary fact materials record the time, place, involved personnel, and specific circumstances of the conduct; disciplinary decision documents state the basis for the disciplinary action, the type of disciplinary action, the effective date, and the delivery signature; appeal statements include the appeal request, factual grounds, submission date, and the appellant's signature. The three types of materials must correspond to one another in fields, dates, and signatures, and the name, quantity, and date of the same record must be consistent. When the materials enter the conversation logs and auditing function, each assumes a different role: disciplinary fact materials serve as the source of facts, disciplinary decision documents serve as the handling conclusion, and appeal statements serve as the record of the relief procedure. The update rhythm advances according to the disciplinary process, from fact determination to decision delivery to appeal acceptance, with each stage producing a new version. Field characteristics are concentrated in the signature column, date column, and number column, and version changes must retain the old version for traceability.
Configuration and implementation checks
This step is executed by the conversation record interface (by application and session dimension), outputting the session message list and the total record count, including role and citation information. The "version ledger and change records" is then completed manually or by an external system. The interface paginates and pulls by chatId, and the returned results distinguish between the two role types of question and answer, and carry citation and elapsed-time fields.
| Object | Check | Verification action |
|---|---|---|
| Disciplinary fact materials | The name, quantity, and date correspond consistently with the disciplinary decision document and appeal statement, and the signature column is complete | In the request parameters, verify the source of the application and session identifiers, and confirm that the material records belong to the same session; open a single record and verify dataId and the citation fields |
| Disciplinary decision document | The type of disciplinary action, effective date, and delivery signature are consistent with the disciplinary fact materials and appeal statement | Pull two consecutive pages and compare the total record count and offset, and confirm that the decision document version number and citation are updated in sync; verify the date and signature information in the value field |
| Appeal statement | The appeal request, factual grounds, submission date, and signature correspond with the disciplinary decision document | Check the order of the two role types of question and answer in the returned list, and confirm that the appeal statement appears as an independent record; verify whether the citation and elapsed-time fields are complete |
| Session message list | The total record count matches the pagination parameters, and roles appear alternately | Page through by the total record count to retrieve all, and sample one record to verify the role, citation information, and time; confirm that response code of 200 is consistent with the total record count total |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the disciplinary fact materials and the disciplinary decision document. Cause: The two materials are maintained separately, versions are not synchronized, and citations are not updated with the content.
- Symptom: The disciplinary decision document lacks a signature or receipt, and the appeal statement submission date conflicts with the decision document effective date. Cause: The signature column and date column were not verified when the materials were registered, and the old version was not archived in time.
- Symptom: The interface returns empty but there is a session in the interface, or only the first page is retrieved. Cause: The sources of the application and session identifiers are inconsistent, and the pagination offset does not advance with the total record count.
How to verify the setup
This feature's acceptance: page through by the total record count to retrieve all, and sample one record to verify the role, citation information, and time; confirm that response code of 200 is consistent with the total record count total, and verify the fields corresponding to the message identifiers and content fields _id, dataId and value.
Business test: change one piece of content and see whether the version number and citation are updated in sync; the citation count is the array length, and the tokens of the citation text are verified separately, and the two are not compared for equality.
- In the request parameters, verify the source of the application and session identifiers, and confirm that they are consistent with the actual application and actual session; pull two consecutive pages and compare the total record count and offset.
- Open a record and verify the citation and elapsed-time fields, and confirm that the role field appears alternately; when exporting records, check whether the citation information is complete.