What this category's data looks like
This category covers three types of materials involved in undergraduate program planning: program plans, course syllabi, and credit structure tables. Fields include course name, credits, credit hours, semester offered, revision date, and signature field. The program plan defines total credits and course modules; course syllabi correspond to the objectives and assessments of each course; the credit structure table summarizes the credits of each module. Materials are updated according to the academic-year revision cadence, and versions are determined by date and signature. When entering the conversation logs and auditing feature, each of the three types of materials is referenced as a citation source in conversation records, used to check whether the name, credits, and date of the same course are consistent between the program plan and the syllabus, and whether signatures and receipts are complete.
Configuration and implementation checks
This step is performed by the conversation record interface (by application and session dimension), outputting a session message list and total record count, including role and citation information. "Handover-ready deployment status and operation records" are then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Course name, credits, revision date, and signature field match between the program plan and the syllabus | Pull records by application and session identifier, check whether the course name and credits in the citation fields are consistent with the program plan; check whether signatures and receipts are complete |
| Course syllabus | The name, quantity, and date of the same course are consistent between the two materials, and the version is synchronized | Pull two consecutive pages and compare the total record count and offset; sample one record to inspect the role field and citation information, and confirm that the syllabus version date is consistent with the program plan |
| Credit structure table | The total credits match the quantity of each module, and there are no missing dates or signatures | Open one record to check the citation and elapsed-time fields, locate the session by chatId and dataId, and use value to view the details of a single record |
| Deployment status and operation records | Version, connection, and task records are consistent and can be handed over to the next shift | Check the version number, connection status, and task records item by item according to the handover sheet, and confirm that the total record count matches the accumulated pagination rows; check the response code separately |
Three common errors
- Symptom: The credits and dates of the same course do not match between the program plan and the course syllabus. Cause: The two materials are revised separately, versions are not synchronized, and there is no unified receipt.
- Symptom: The summarized quantity in the credit structure table is inconsistent with the item-by-item sum of the course syllabi. Cause: Different naming conventions, so the same record's name does not match between the two materials.
- Symptom: The handover sheet lacks a signature or receipt, and the next shift cannot confirm the version. Cause: Operation records were not registered together with the deployment status, and task records are incomplete.
How to verify the setup
Feature acceptance: page through to retrieve all records by total record count, sample one record to check the role, citation information, and time; check the message identifiers and content fields _id, dataId and value; for status values, only the total record count total and response code of 200 are recognized.
Business test: check once item by item according to the handover sheet to see which record item is missing.
- Pull pages by application and session identifier, pull two consecutive pages and compare the total record count and offset, and confirm that the number of records matches the total.
- Open one record to check the citation and elapsed-time fields, confirm that the number of citations equals the array length, and that the tokens of the citation text are recorded separately.