What this category's data looks like
The revision of undergraduate programs involves three types of materials: program plans, course syllabi, and credit structure tables. Fields include course name, credit count, semester offered, revision date, and signature field. The materials come from academic affairs system exports, departmental revision notes, and meeting minutes. The update cadence advances by academic year or semester, with revised drafts and final drafts coexisting. When entering this function, the program plan serves as the main record carrying the version number and effective date, the course syllabus serves as a sub-record linked to the course identifier and credits, and the credit structure table serves as a summary record for checking total credits and module proportions. Each of the three types of materials leaves traces of questions and answers in the conversation records, used to trace the discussion basis and citation sources of a given revision.
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. The "version ledger and change records" are then completed manually or by an external system.
| Object | Check | Verification action |
|---|---|---|
| Program plan | Name, credit count, revision date, and signature field are consistent across the three types of materials | Pull records by application and session identifier, verify that chatId matches the actual session, and compare course names and credit counts one by one |
| Course syllabus | Course name, credit count, and semester offered match between the program plan and the syllabus | Open a single record to verify the role field and citation information, and confirm the answer citation source corresponding to dataId |
| Credit structure table | Total credits and module proportions are consistent across the two materials, and signatures and receipts are complete | Pull two pages consecutively to compare the total record count total and the offset, confirm response code of 200, then export the records to review signatures and receipts |
| Conversation records | The total record count matches the number of paginated entries, and message roles correspond to the original conversation | Use value to view a single record, verify the citation and elapsed time fields, and confirm that old versions are traceable and citations are synchronized |
Three common errors
- Symptom: The name and credit count of the same course do not match between the program plan and the course syllabus. Cause: Revised drafts and final drafts coexist, the current version was not locked by version number, and citations were not updated synchronously.
- Symptom: The total credits in the credit structure table are inconsistent with the program plan, and dates and signatures are missing. Cause: The summary table was not synchronized with the revised draft, receipts were not archived, and the version ledger did not register change records.
- Symptom: The conversation records return empty although sessions exist in the interface, or only the first page is retrieved. Cause: The sources of the application and session identifiers are inconsistent, pagination offsets were not pulled continuously, and exported records lack citations.
How to verify the setup
Acceptance of this function: page through by total record count to retrieve all records, sample one record to verify role, citation information, and time, confirm response code of 200 and that the total record count total matches the number of paginated entries, and that a single record shows the citation and elapsed time fields.
Business test: change one piece of content and see whether the version number and citations are updated synchronously.
- Verify the sources of the application and session identifiers, confirm that
chatIdmatches the actual session, and pull two pages consecutively to compare the total record count and offset. - Open one record to verify the role field and citation information, and confirm that the citation and elapsed time fields corresponding to
dataIdandvalueare queryable.