What this category's data looks like
This page addresses kindergarten childcare daily life management; the materials include the daily life schedule, morning and afternoon health check records, and child health observation records. The sources are daily filling and handover circulation at the kindergarten, and the update cadence advances by day and by week. Field characteristics include date, time period, activity name, number of children, physical signs, signature, and receipt. During multilingual materials and terminology processing, the daily life schedule provides the backbone of time periods and activity names, the morning and afternoon health check records provide physical signs and number of children, and the child health observation records provide individual observation entries. After the three enter the workflow, terminology extraction and comparison are performed first, and then subsequent nodes orchestrate them into a unified terminology table and comparison draft for consistent wording before external release.
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 table and 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 |
|---|---|---|
| Daily life schedule | Whether the translated names of time periods and activity names in the comparison draft can refer back to the source text, and whether dates and signatures are complete | Check the options and branch connections one by one in the node, and reference variables and nodeId to record branch directions |
| Morning and afternoon health check records | Whether the names, quantities, and dates of the same record match across the schedule and the observation records | Trigger once, view the node status in the run records, and check whether the interaction state is recorded |
| Child health observation records | Whether the translated names of individual observation entries are consistent throughout, whether versions are synchronized, and whether any receipt items are missing | Reference the selection result variable in subsequent nodes and run a trial once to check whether the selection result has been passed to subsequent nodes |
| Unified terminology table and comparison draft | Whether the wording of the same term is consistent throughout, and whether translated names can refer back to the source text | Sample three terms to check whether the wording is consistent throughout, and check that the tokens and array item counts of the referenced text are recorded separately |
Three common errors
- Phenomenon: The names, quantities, and dates of the same record do not match across the schedule and the morning and afternoon health check records. Cause: The two materials extracted terminology separately and entered orchestration without first performing comparison.
- Phenomenon: Versions are not synchronized, and old translated names remain in the comparison draft. Cause: After the materials were updated, the interaction was not triggered again, and the branch still followed the old path.
- Phenomenon: Signatures or receipts are missing and are only discovered before external release. Cause: Field checks were not included in branch judgment, and interaction state records were not reviewed.
How to verify the setup
Feature acceptance: Run trials option by option, check the branch directions and interaction states in the run records, and confirm that variables and nodeId are traceable in the records.
Business testing: Sample three terms to check whether the wording is consistent throughout.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Reference the selection result variable in subsequent nodes and run a trial once to check whether the selection result has been passed to subsequent nodes.