What this category's data looks like
In the scenario of district and county teaching research activities and lesson observation and evaluation, the draftable materials and handover records mainly come from teaching research activity notices, lesson observation records, and lesson evaluation minutes. These materials are updated according to the activity cycle; usually there is a notice first, then lesson observation records, and finally lesson evaluation minutes and handover receipts. Notice fields include activity name, time, location, participating schools, agenda, and issuer; lesson observation record fields include instructor, class, subject, topic, observation dimensions, time, and recorder; lesson evaluation minutes fields include review points, improvement suggestions, responsible person, version, date, and signature. When materials enter the multi-turn dialogue and prompt feature, the notice serves as the upstream basis, lesson observation records serve as process evidence, lesson evaluation minutes serve as the conclusion carrier, and handover records connect the responsible person and the receipt step. Complete fields, a clear responsible person, and consistent version and date are the prerequisites for entering the next step of receipt.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and outputs the historical message range and answer constraints for reference. The draftable materials and handover records are then completed by the model. Memory turns control how many previous dialogue turns can be referenced at most when answering. If the value is too small, the previous text cannot be used; if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Category check dimensions: whether activity name, time, location, participating schools, agenda, and issuer are complete, and whether date and signature are consistent | Check the memory turns value in the application settings, run a trial with two consecutive follow-up questions, and check whether the second round inherits the references from the first round; check whether the historical range in messages covers the notice fields |
| Lesson observation record | Category check dimensions: whether instructor, class, subject, topic, observation dimensions, time, and recorder are complete, and whether the names, quantities, and dates of the same record match across the notice and minutes | Draft a lesson observation record according to the template, go through one handover, and see whether missing items are blocked; check the field consistency between the notice and the record in the session corresponding to chatId |
| Lesson evaluation minutes | Category check dimensions: whether review points, improvement suggestions, responsible person, version, date, and signature are complete, whether the version is synchronized, and whether the receipt is complete | Compare the usage records of two runs to confirm the consumption change after adjusting the turns; check whether the version and date fields in variables are consistent with the notice and record |
| Handover record | Category check dimensions: whether both handover parties, material list, version, date, signature or receipt are complete, and whether the responsible person is clear | Draft one according to the template and complete one handover, and see whether missing items are blocked; check whether the version and date of the handover record and the lesson evaluation minutes are consistent |
Three common errors
- Phenomenon: The topic name, number of participants, and date of the same lesson observation record do not match between the notice and the lesson evaluation minutes. Cause: During drafting, fields were not checked one by one according to the template, and the version was not synchronized.
- Phenomenon: The lesson evaluation minutes lack a signature or receipt, so the next step cannot be received. Cause: The handover record did not specify the responsible person, and the signature field was omitted.
- Phenomenon: When references are used in the second question, the answer does not address the question, and the response becomes slower with increased consumption. Cause: The memory turns value does not match the previous text range required by the question, and the opening message is treated as previous text.
How to verify the setup
Acceptance of this feature: ask two consecutive follow-up questions and see whether the second question inherits the references from the first question; check the memory turns value in the application settings, confirm that the historical range in messages is consistent with the session corresponding to chatId, and that the version and date fields in variables are traceable.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- Check the current memory turns value in the application settings, run a trial with two consecutive follow-up questions, and confirm that the second round can correctly inherit the references from the first round.
- Compare the usage records of two runs, confirm that usage changes accordingly after adjusting the turns, and check that the fields of the material draft and handover record are complete, the responsible person is clear, and the version and date are consistent.