What this category's data looks like
This page focuses on three types of materials in the social evaluation scenario of vocational skill level certification: the evaluation implementation plan, the candidate registration form, and the assessor dispatch form. The evaluation implementation plan is prepared by the evaluation institution and is updated as occupational standards and assessment arrangements change; it contains the occupation name, level, subjects, test sites, dates, and signature/seal fields. The candidate registration form is filled in by the candidate and reviewed by the institution; it contains name, ID number, declared level, subjects, photo, and signature field. The assessor dispatch form is generated by the institution after scheduling assessments; it contains assessor name, ID number, assessment occupation, session, date, and receipt field. When these three types of materials enter the multilingual materials and terminology processing workflow, the implementation plan serves as the terminology source and reference baseline, while the registration form and dispatch form serve as the data carriers to be checked and translated. Fields, dates, and signatures must be compared item by item to avoid the same record having mismatched names, quantities, or dates across the two materials, as well as versions not being synchronized, missing signatures, or missing receipts.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Unified terminology glossary and comparison draft" is continued and completed by subsequent nodes according to the branch.
| Object | Check | Verification action |
|---|---|---|
| Evaluation implementation plan | The occupation name, level, subjects, test sites, dates, and signature/seal fields must correspond item by item with the registration form and dispatch form, and terminology usage must be consistent throughout | Check options and branch connections one by one in the node, reference variables for parameter passing and run a trial, and view node status in the run records |
| Candidate registration form | Name, ID number, declared level, subjects, dates, and signature field must match the implementation plan and dispatch form, and translated names must be traceable back to the source text | Reference the selection result variable in subsequent nodes and run a trial once, and check the branch direction and interaction state corresponding to nodeId |
| Assessor dispatch form | Assessor name, ID number, assessment occupation, session, dates, and receipt field must be consistent with the implementation plan and registration form, and versions must be synchronized | Trigger a user selection once, check whether variables have been passed to subsequent nodes, and check whether the receipt and signature are complete |
| Unified terminology glossary and comparison draft | The same term must be consistent throughout, translated names must be traceable back to the source text, and three terms should be sampled to check usage throughout | Reference this variable in subsequent nodes and run a trial once, and check the nodeId branch direction and interaction state records |
Three common errors
- Phenomenon: The same candidate name or assessor name is written differently in the registration form and dispatch form. Cause: multilingual materials have not unified terminology, and node branches do not follow the corresponding processing path according to the option.
- Phenomenon: The same session date or number of people does not match across the two materials. Cause: versions are not synchronized, the old implementation plan and the new registration form are mixed, and the process stops after the interaction is completed.
- Phenomenon: The dispatch form lacks an assessor signature or the receipt field is blank. Cause: the interaction state is not recorded, a default branch is still followed even after an option is selected, and subsequent nodes do not continue execution according to the branch.
How to verify the setup
Acceptance of this feature: run trials for each option one by one, check the branch direction and interaction state in the run records, and confirm that variables have been passed to subsequent nodes and that the branch corresponding to nodeId is correct.
Business testing: sample three terms to check whether usage is consistent throughout, check whether translated names can be traced back to the source text, and compare the fields, dates, and signatures of the implementation plan, registration form, and dispatch form.
- Check options and branch connections one by one in the node, trigger a user selection once, and view the node status and selection result variables in the run records.
- Reference this variable in subsequent nodes and run a trial once, check
variables,nodeId, and branch direction, and confirm that the same session does not repeatedly enter the interaction.