What this category's data looks like
For district and county teaching research activities and classroom observation and evaluation, materials fall into three categories: teaching research activity notices, classroom observation records, and classroom evaluation minutes. Notices are issued by the teaching research department and include the activity name, date, location, participating schools, and subject; classroom observation records come from the classroom site and include the instructor, class, lesson topic, time, and observation points; classroom evaluation minutes come from the evaluation session and include the evaluator, opinions, signature, and receipt. The update rhythm advances weekly: notices arrive first, classroom observation records are generated during class, and classroom evaluation minutes are added after class. When the three types of materials enter the workflow, the notice serves as the activity master record, the classroom observation record serves as process detail, and the classroom evaluation minutes serve as the basis for conclusions and signatures; field characteristics are concentrated in name, quantity, date, signature, and receipt, and must be aligned item by item in the progress table and statistical scope description.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The "progress table and statistical scope description" is completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | The activity name, date, and participating schools in the notice must be aligned item by item with the classroom observation records and classroom evaluation minutes | Check the options and branch connections one by one in the node, and confirm that the notice fields enter the corresponding branch |
| Classroom observation record | The instructor, class, lesson topic, and time in the classroom observation record must be consistent with the name, quantity, and date in the notice and classroom evaluation minutes | Reference the selection result variable in subsequent nodes and run a trial once, and check whether the record enters the statistical detail |
| Classroom evaluation minutes | The evaluator, opinions, signature, and receipt in the classroom evaluation minutes must correspond to the classroom observation records and notice | Trigger the user selection node once, and view the node status and branch direction in the run record |
| Progress table and statistical scope description | The number of records and the statistical count must match, the scope must be written in the header, and exceptions must be clearly stated | Reference variables and nodeId in subsequent nodes, and run a one-week record check against the totals |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the notice and the classroom observation record. Cause: The two materials are entered separately and the fields are not aligned according to the same scope.
- Phenomenon: The version of the classroom evaluation minutes is not synchronized, and the old version's signature and the new version's opinions coexist. Cause: The update rhythm is inconsistent, and subsequent nodes do not use the latest materials according to the branch.
- Phenomenon: Signatures or receipts are missing, but the statistical totals are still included. Cause: The scope does not write exceptions in the header, and verification does not distinguish valid records from records pending supplementation.
How to verify the setup
This feature's acceptance: run trials option by option, check the branch direction and interaction status in the run record, confirm that the options and branch connections are consistent, that the selection result variable has been passed to subsequent nodes, and that variables and nodeId are each trial-run once.
Business test: use one week of records to check the totals, see whether the scope and exceptions are clearly stated, whether the number of records and the statistical count match, and whether the scope is written in the header.
- Check the options and branch connections one by one in the node, trigger the user selection node once, and view the node status and branch direction in the run record.
- Reference the selection result variable in subsequent nodes and run a trial once, check the one-week record totals and the statistical scope description, and confirm that exceptions are clearly stated.