What this category's data looks like
This category's data comes from the kindergarten's own observation records, area activity plans, material placement lists, activity objective tables, and reflection-to-next-week plans. Observation records are updated weekly, area plans are adjusted monthly, material lists change with placement, objective tables advance with themes, and reflection-to-next-week plans are generated on weekends. After these materials enter the workflow, user-selected nodes take on the assignment role, giving branches by material type and version status, and subsequent nodes then extract, by branch, basis entries that can be traced back to the original text. Each material has a different role: observation records are used to correspond to area plans, material lists are used to check placement quantities, objective tables are used to judge whether activity objectives have been achieved, and reflection-to-next-week plans are used to confirm whether the plan has been updated. Field characteristics include material name, version number, effective date, entry number, and original text location.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. "Basis entries that can be traced back to the original text" are completed by subsequent nodes continuing execution according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | Entries can be matched to the original text, and observation records correspond to area plans | Check options and branch connections one by one in the node, and after a trial run, view the branch directions and interaction status in the run records |
| Material placement list | Material placement quantities are consistent with the list, and the basis comes from the kindergarten's own materials | Reference the selection result variable variables in subsequent nodes and run once, checking material quantities and original text locations |
| Activity objective table and reflection-to-next-week plan | Activity objective achievement is consistent with observations, and the reflection-to-next-week plan is the current version | Use nodeId to locate the node, and check the objective entries and the version date of the reflection-to-next-week plan |
| Basis entries | Entries can be traced back to the original text, and the version is the current one | Check the tokens of the referenced text; record the array item count separately, and do not compare quoteMaxToken |
Three common errors
- Symptom: insufficient materials lead to missing basis entries. Cause: the material placement list has not been updated, and observation records do not correspond to area plans.
- Symptom: objectives do not match observations. Cause: the activity objective table version has not been synchronized, and observation record entries cannot be matched to the original text.
- Symptom: the plan has not been updated. Cause: the reflection-to-next-week plan is still an old version, and the branch directions and interaction status records have not been refreshed.
How to verify the setup
This feature's acceptance: run each option one by one, check the branch directions and interaction status in the run records, confirm that each option corresponds to one branch, and that the selection result variable variables has been passed to subsequent nodes.
Business test: ask a basis question spanning materials, see whether the answer gives a traceable source, and check whether the entries can be matched to the original text.
- Check options and branch connections one by one in the node, and trigger once to view the node status in the run records.
- Reference the selection result variable
variablesin subsequent nodes and run once, checking the branch directions and interaction status records.