What this category's data looks like
This page addresses primary and secondary school timetable and after-school service scheduling scenarios. Material sources include the master timetable, teacher assignment table, after-school service project table, and accompanying receipts and signature pages. The master timetable is updated by semester and week, with fields including class, period, course name, assigned teacher, and venue; the teacher assignment table summarizes classes and class hours by teacher dimension; the after-school service project table records project name, participating students, time slot, and responsible teacher. When these three materials enter the multilingual materials and terminology processing stage, the master timetable serves as the baseline for course name and period terminology, the teacher assignment table is used to check whether the translated name of the same course is consistent with the master timetable's back-reference, and the after-school service project table provides a comparison source for project names and time slot expressions. The update rhythm is mainly centralized release at the beginning of the semester, with rolling revisions during the semester based on schedule change receipts. There is a characteristic that names, quantities, and dates across fields need to be aligned across tables, and the terminology glossary and comparison draft are accumulated item by item accordingly.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "Unified Terminology Glossary and Comparison Draft" is continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters an interactive 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 |
|---|---|---|
| Master timetable | The terminology for course names, periods, and dates is written consistently throughout, and the translated names can back-reference the source text | Check the options and branch connections one by one in the node to confirm the course name branch direction; use variables to reference the selection result, and sample three course names to check their writing throughout |
| Teacher assignment table | The names, class hour quantities, and dates for the same teacher and same course match the master timetable | Trigger a user selection once and check the node status in the run record; reference the selection result variable corresponding to nodeId in a subsequent node and run a trial |
| After-school service project table | Project names, time slots, participant counts, and receipt signatures are consistent across the three materials | Check whether the project name branch and the default branch are separated; sample three project names and compare the names, quantities, and dates across the master timetable, teacher assignment table, and project table |
| Receipts and signature pages | When signatures or receipts are missing, the terminology glossary and comparison draft do not enter the external release branch | Check in the node whether the options and branch connections cover the missing receipt case, and record the interaction state |
Three common errors
- Symptom: The names and class hour quantities of the same course do not match between the master timetable and the teacher assignment table. Cause: The two materials are revised separately, and the terminology glossary has not been synchronized to back-reference the source text.
- Symptom: The dates in the after-school service project table are inconsistent with the dates on the receipt signature pages. Cause: Versions are not synchronized, and the old version receipt is still attached to the current branch.
- Symptom: After selecting an option, the default branch is still taken, and the process stops after the interaction is completed. Cause: The options and branch connections were not checked one by one, and the selection result variable was not passed to subsequent nodes.
How to verify the setup
Acceptance for this feature: Run trials for each option one by one, check the branch direction and interaction state in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: Sample three terms to check whether their writing is consistent throughout, and confirm that the translated names can back-reference the source text.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and avoid taking the default branch after selecting an option.
- Reference the selection result variable in a subsequent node and run a trial once to confirm that the process continues downward after the interaction is completed.