What this category's data looks like
Materials for district and county teaching research activities and lesson observation and evaluation include three categories: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices carry the activity name, date, location, participation scope, and receipt requirements; lesson observation records note the class, subject, instructor, observation points, and signature by period; lesson evaluation minutes record review opinions, improvement items, and signatures. The materials are submitted separately by subject teaching researchers, school academic affairs offices, and observing teachers, summarized weekly and archived monthly. When entering this function, notices are used to verify the activity name and date, lesson observation records are used to verify periods and quantities, and lesson evaluation minutes are used to verify signatures and receipts; the three types of materials are read as fields in the tool call node and do not directly generate a ledger.
Configuration and implementation checks
This step is executed by the tool call node in the workflow (the model decides whether to call it, and the node executes it), outputting the tool call result (the inputs and returns in the call record). The "progress table and statistical scope description" is then completed by a subsequent AI node or manual verification.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Check whether the activity name, date, participation scope, and receipt requirements are consistent with the lesson observation records and lesson evaluation minutes | Open the tool node introduction fields, confirm the purpose, when it should be used, and what it returns; then compare the notice date with the lesson observation record date one by one |
| Lesson observation record | Check the period, class, subject, instructor, and signature, and see whether the quantity matches the statistical count | Open each parameter configuration, check the parameter introduction and whether it is required; run a test with a question missing a required field to see whether it asks a follow-up question first |
| Lesson evaluation minutes | Check whether the review opinions, improvement items, and signatures or receipts are complete, and whether the version is synchronized | Check the diamond-shaped interface connections and node status on the canvas, and confirm the call path corresponding to toolChoice and functionCall |
| Statistical scope description | Check whether the header states the scope of the record count and statistical count, exceptions, and date range | Use one week of records to verify the total, check whether the scope and exceptions are clearly stated, and record the number of array items and the referenced text tokens separately |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the notice and the lesson observation record. Cause: The two materials were entered separately and were not checked against the same scope.
- Symptom: The lesson evaluation minutes version is not synchronized, the old version lacks a signature, or the receipt is not attached. Cause: The materials were not resubmitted after updating, and the signature item was not checked during archiving.
- Symptom: Values that do not exist in the business materials appear in the returned result. Cause: When there are no required parameters, the model may fabricate parameter values on its own without asking a follow-up question first.
How to verify the setup
Acceptance for this function: run a test with a question missing a required parameter, check the inputs and returns in the call record, and confirm whether it asks a follow-up question or calls according to the introduction; at the same time, check toolChoice, functionCall, and the diamond-shaped connection status.
Business test: use one week of records to verify the total, see whether the scope and exceptions are clearly stated, and whether the record count and statistical count match.
- Open the tool node introduction fields, check whether this description can be understood when taken out on its own, and confirm the purpose, when it should be used, and what result it returns.
- Open each parameter configuration, check the introduction and whether it is required; run a test with a question missing that field to see whether it asks a follow-up question first instead of directly fabricating.