What this category's data looks like
District and county teaching research activity and lesson observation and evaluation materials usually include three types: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices are published by the organizing party before the activity and contain the activity name, time, location, participants, and agenda; lesson observation records are filled in by the observer at the classroom site and contain the instructor, class, topic, observation dimensions, and timestamps; lesson evaluation minutes are summarized by the evaluator and contain evaluation points, improvement suggestions, and a signature field. Materials are updated weekly or monthly, and the same activity often produces multiple documents. After entering this feature, the notice serves as the activity background and date baseline, the lesson observation record serves as the source of classroom facts, and the lesson evaluation minutes serve as the basis for conclusions and responsibility, and the three together support anomaly tracing. Field characteristics are concentrated in names, quantities, dates, signatures, and receipts, version synchronization depends on the publishing service and file permissions, and the model is only responsible for answering based on the historical message range and answer constraints.
Configuration and implementation checks
This part is executed by the memory turns and prompt configuration in the application settings, and outputs the referenced historical message range and answer constraints. The anomaly list and review conclusions are then completed by the model. Memory turns control how many previous rounds of dialogue can be referenced at most when answering; if the value is too small, the preceding text cannot be used, and if the value is too large, irrelevant content is brought in and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | The activity name, date, participants, and agenda fields must be aligned item by item with the lesson observation record and lesson evaluation minutes | Check the memory turns value in the application settings, run a trial with two consecutive rounds of questions, and check whether the second round can carry forward the references from the first round |
| Lesson observation record | The instructor, class, topic, and timestamps are consistent with the number of conclusion items in the lesson evaluation minutes; missing signatures or receipts must be marked | Compare the usage records of two runs to confirm that after adjusting the turns, the run consumption changes accordingly |
| Lesson evaluation minutes | The evaluation points, improvement suggestions, and signature field are complete; when the version is not synchronized, it is necessary to trace back to the original record | Carry chatId and messages in the dialogue, and check whether the historical message range covers the required preceding text |
| Anomaly list and review conclusions | Each anomaly is supported by an original record, and after the reviewer signs, it is handed to the person in charge for handling | Use variables to mark the source material of the anomaly, and verify whether the source material can be traced |
Three common errors
- Phenomenon: The name and quantity of the same record do not match between the notice and the lesson evaluation minutes. Cause: The version is not synchronized, old and new drafts are mixed, and receipt confirmation is missing.
- Phenomenon: The date of the lesson observation record is inconsistent with the date of the lesson evaluation minutes. Cause: The material update rhythms differ, signatures or receipts are missing, and correction has not been made according to the original record.
- Phenomenon: The second question answers off-topic when using references. Cause: The memory turns value does not match the preceding text range required by the question, and the opening message is treated as preceding text.
How to verify the setup
Feature acceptance: ask two consecutive follow-up questions and see whether the second question carries forward the references from the first question; check whether the three identifiers chatId, messages, and variables appear in the historical message range and answer constraints.
Business test: create an anomaly record, see whether the source material can be traced, and confirm that the anomaly list and review conclusions are supported by original records and signed by the reviewer.
- Check the current memory turns value in the application settings, and confirm that it matches the preceding text range required by the question.
- Run a trial with two consecutive rounds of questions, compare the usage records of the two runs, and confirm that after adjusting the turns, the run consumption changes accordingly.