What this category's data looks like
In the course selection, scheduling, and classroom resource allocation scenario, drafting materials and handing over responsibility involve three core types of materials: the course offering plan, the scheduling table, and the course selection rules. The course offering plan comes from the academic affairs department and includes course name, course code, credits, weekly class hours, offering term, instructor, and planned enrollment; the scheduling table is generated by the scheduling system and includes course code, class time, classroom number, capacity, and week range; the course selection rules are jointly drafted by academic affairs and the departments and include selection batch, priority, capacity cap, and add/drop deadline. The material update rhythm is centralized release before the term, adjustment during the term based on changes, and archiving at the end of the term. When entering the context and token feature, the course offering plan serves as the source of basic fields, the scheduling table serves as the source of time and space constraints, and the course selection rules serve as the source of boundary conditions; together, the three form the issuable material draft and handover record.
Configuration and implementation checks
This part is executed by application settings (reply limit, etc.), which output the length of a single answer and the range of context that can be accommodated. The "issuable material draft and handover record" is then completed by the model. The reply limit uses a slider to control the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Fields complete: course name, course code, credits, weekly class hours, offering term, instructor, and planned enrollment are checked item by item; dates and signatures: the offering term is consistent with the department signature date | In the application settings, check the switch and slider positions, and confirm the values of maxResponse and maxContext; compare the course offering plan fields item by item with the fields referenced in the scheduling table |
| Scheduling table | Fields complete: course code, class time, classroom number, capacity, and week range are checked item by item; dates and signatures: the week range corresponds to the offering term, and the scheduling responsible person's signature is complete | Ask a question that requires a long answer and look at the ending to confirm the truncation behavior of maxResponse; check whether the capacity for the same course code is consistent between the scheduling table and the course selection rules |
| Course selection rules | Fields complete: selection batch, priority, capacity cap, and add/drop deadline are checked item by item; dates and signatures: the deadline is consistent with the academic affairs receipt date | Compare the usage of two runs to confirm the change in single-run usage after adjusting the limit; check whether the same course name, quantity, and date match between the course selection rules and the course offering plan |
Three common errors
- Symptom: the name, quantity, and date of the same course do not match between the course offering plan and the scheduling table. Cause: the two materials were drafted separately, and fields were not cross-checked item by item according to the template.
- Symptom: the version of the course selection rules was not synchronized, and the old batch priority is still referenced. Cause: the version number and date were not updated with the changes, and the receipt was not checked during handover.
- Symptom: the scheduling table lacks the signature of the scheduling responsible person, or the course selection rules lack the academic affairs receipt. Cause: the handover record did not list signature items, and the next stage did not block missing items at sign-off.
How to verify the setup
Feature acceptance: ask a question that requires a long answer and see whether the ending is complete; at the same time, check whether the values of the three identifiers maxResponse, maxContext, and quoteMaxToken in the application settings match the page requirements; the tokens of the quoted text are recorded separately, and the number of array entries is not compared for equality.
Business test: draft one copy according to the template and complete one handover to see whether missing items are blocked.
- In the application settings, check the reply limit switch and slider position, confirm the values of
maxResponseandmaxContext, and compare the usage of two runs. - Check the name, quantity, date, and signature of the course offering plan, scheduling table, and course selection rules item by item according to the template, confirm that the version number and date are consistent, and then hand it to the next stage for sign-off.