What this category's data looks like
This page addresses the scenarios of district and county teaching research activities and lesson observation and evaluation. The materials include teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices are mostly issued by district and county teaching research departments, updated with activity batches, and their fields include activity name, date, location, participants, and signature field; lesson observation records are filled in by observers and include class, subject, topic, observation points, and signature; lesson evaluation minutes are compiled by the organizing party and include review opinions, conclusions, and receipt. After these materials enter the workflow, the notice undertakes initiation and scope definition, the lesson observation record provides process evidence, and the lesson evaluation minutes form conclusions and receipts. The names, quantities, and dates of the same record often do not match across the two materials, versions are not synchronized, signatures or receipts are missing, and multilingual materials and terminology handling require first unifying the terminology table and the comparison draft, then submitting them for external release.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. Unifying the terminology table and the comparison draft is continued and completed by subsequent nodes according to the branches. When a node is triggered, the conversation enters an interaction state and records the workflow state. After the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| User selection node | Each option corresponds to one branch; the options and branch connections are checked one by one in the node | Check the options and branch connections one by one in the node, and after a trial run, verify nodeId and the branch direction |
| Teaching research activity notice | The activity name, date, location, participants, and signature field are consistent with the lesson observation record and lesson evaluation minutes | Sample three terms and check whether their spelling is consistent throughout the whole text; verify the dates, quantities, signatures, or receipts of the notice and the minutes |
| Lesson observation record | The class, subject, topic, and observation points correspond to the conclusions and receipt of the lesson evaluation minutes | Reference the selection result variables in subsequent nodes and run a trial; verify that the record names and quantities are consistent across the two materials |
| Lesson evaluation minutes | The review opinions, conclusions, and receipt are synchronized with the versions of the notice and the lesson observation record | Check where versions are not synchronized, look for missing signatures or receipts, and confirm that the terminology table and the comparison draft can refer back to the original text |
Three common errors
- Phenomenon: The names, quantities, and dates of the same record do not match between the notice and the lesson evaluation minutes. Cause: The two materials are filled in separately, and the terminology table and the comparison draft were not unified first.
- Phenomenon: The versions of the lesson observation record and the lesson evaluation minutes are not synchronized, and old drafts are mixed in. Cause: The update rhythms differ, and versions and dates were not checked in the branches.
- Phenomenon: The lesson evaluation minutes lack signatures or receipts, blocking external release. Cause: After the interaction is completed, the process stops and does not continue executing subsequent nodes according to the branches.
How to verify the setup
This feature's acceptance: run trials option by option, check the branch directions and interaction states in the run records, confirm that each option corresponds to one branch, and that the selection result variables has been passed to subsequent nodes.
Business test: sample three terms and check whether their spelling is consistent throughout the whole text, confirm that the translated names can refer back to the original text, and that the same term is consistent throughout the whole text.
- Check the options and branch connections one by one in the node, run a trial once, and view the node status and
nodeIdin the run records. - Reference the selection result
variablesin subsequent nodes and run a trial, check the branch directions and interaction state records, and confirm that the unified terminology table and the comparison draft are completed by subsequent nodes.