Conversation Records and Traceability for Self-Study Exam Records and Graduation Review: Track Progress and Check Statistics

Self-Study Exams: review chat records for progress tracking. Check source versions, input mappings and the values received by downstream nodes.

What this category's data looks like

This page focuses on progress records and statistical verification in self-taught examination registration and graduation review. The materials include three types: registration files, course qualification certificates, and graduation application forms. Registration files are generated by the provincial examination office during the registration stage and record the candidate's basic information and major plan; course qualification certificates are issued by the host institution after each course ends and carry the course code, score, and date; graduation application forms are submitted by candidates when they meet the conditions and include a signature and receipt. When the materials enter the conversation record interface, they appear as the question and answer roles in the session respectively, and the reference information points to the corresponding file or data entry. The update rhythm is that registration files change by examination session, course qualification certificates are appended by course batch, and graduation application forms are submitted by application cycle. In terms of field characteristics, all three types of materials contain name, quantity, date, and signature, and these must be aligned item by item in the progress table and statistical scope description.

Configuration and implementation checks

This step is performed by the conversation record interface (by application and session dimension), which outputs the session message list and total record count, including role and reference information. The progress table and statistical scope description are then completed manually or by an external system. The interface only retrieves session evidence and does not write to business ledgers.

ObjectCheckVerification action
Registration filesFields, dates, and signatures are complete, and the name, quantity, and date of the same record are consistent between the file and the qualification certificatePull records by application and session identifier, verify chatId and dataId, and compare the field values of the registration file and the course qualification certificate
Course qualification certificatesCourse code, score, date, and signature are complete, and the version is synchronized with the registration filePage through to retrieve all records, use value to view a single reference and elapsed time, and verify the course quantity of the qualification certificate and the graduation application form
Graduation application formsApplication form fields, date, signature, and receipt are complete and consistent with the registration file and course qualification certificatePage through by total record count total to retrieve all, sample one record to verify role, reference information, and time, and check the signature and receipt
Progress table and statistical scope descriptionThe record count and statistical count match, the scope is written in the header, and exceptions are clearly statedUse one week of records to verify the total, compare total with the statistical count, and confirm successful retrieval with response code of 200

Three common errors

  • Symptom: The name, quantity, and date of the same record do not match between the registration file and the course qualification certificate. Cause: The two materials are entered in different stages, and field-level alignment and cross-checking were not performed.
  • Symptom: The graduation application form version is not synchronized, and the signature or receipt is missing. Cause: The materials were modified multiple times during the application cycle, no version records were retained, and the receipt was not archived.
  • Symptom: The interface returns empty but there are sessions in the interface. Cause: The sources of the application and session identifiers are inconsistent, or only the first page was retrieved and paging by total record count was not used to retrieve all.

How to verify the setup

Acceptance for this feature: Page through by total record count total to retrieve all, sample one record to verify role, reference information, and time, and confirm response code of 200.

Business test: Use one week of records to verify the total, check whether the scope and exceptions are clearly stated, and compare the record count with the statistical count.

  • Verify the source of the application and session identifiers in the request parameters, and confirm they are consistent with the actual application and actual session.
  • Pull two pages consecutively and compare the total and offset, and check whether the role field matches the original conversation between question and answer.

References