What this category's data looks like
Materials for district and county teaching and research activities and classroom observation and evaluation usually fall into three categories: teaching and research activity notices (activity name, time, location, participants, sign-off column), classroom observation records (instructor, class, subject, date, observation points), and evaluation meeting minutes (evaluators, conclusions, improvement suggestions, signatures). Sources are mostly archives from kindergartens and district and county teaching and research institutions, updated by activity batch and centrally reviewed at the end of the semester. When entering this function, the notice serves as the activity scope and time anchor, the classroom observation record serves as the classroom facts and date, and the evaluation meeting minutes serve as the conclusions and signature receipt; the three types of materials each retain their fields and versions for subsequent nodes to use by branch.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Evidence items that can refer back to the original text" are completed by subsequent nodes continuing execution according to the branch. After triggering, the conversation enters the interaction 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 and research activity notice | Whether the name, time, location, participants, and sign-off column are consistent with the same batch of activities, and whether the version is current | Check the options and branch connections one by one in the node, confirm the branch direction corresponding to the notice, and view the node status in the run record |
| Classroom observation record | Whether the instructor, class, subject, date, and observation points match the notice and minutes, and whether missing signatures or receipts are marked | Reference the selection result variable in subsequent nodes and run a trial once, checking whether the record dates and quantities are consistent across materials |
| Evaluation meeting minutes | Whether the evaluators, conclusions, improvement suggestions, and signatures are complete, and whether the name, quantity, and date of the same record are consistent in the two materials | Use nodeId to locate the node, check the branch direction and interaction status records, and confirm that the minutes items can refer back to the original text |
| Workflow node | Each option corresponds to one branch, whether execution continues after the interaction is completed, and whether the same session repeatedly enters the interaction | Check variables and nodeId in the run record, run trials for each option, and record the branch direction |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the notice and the minutes. Cause: The two were entered separately and no cross-material check was performed.
- Symptom: Material versions are not synchronized, and an old notice is still referenced. Cause: The update rhythm is not unified, and the current version is not marked.
- Symptom: The classroom observation record lacks a signature or receipt, and the evaluation conclusion cannot refer back to the original text. Cause: The signature column and receipt were not checked item by item during archiving.
How to verify the setup
Acceptance of this function: run trials for each option, check the branch direction and interaction status in the run record, confirm that the selection result variable has been passed to subsequent nodes, and check whether the references to variables and nodeId correspond.
Business test: ask a cross-material evidence question, see whether the answer gives a traceable source, and check whether the items can refer back to the original text and whether the version is current.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a node once, view the node status in the run record, and confirm that execution continues after the interaction is completed.