What this category's data looks like
Materials for journal publication licenses and annual verification mainly consist of journal publication licenses, annual verification forms, and rectification reports. They come from submissions by publishing units and receipts from competent authorities, and the update cadence advances with license changes, annual verification cycles, and rectification milestones. Field characteristics center on license number, journal name, publication period, sponsoring unit, legal representative, verification year, rectification items, dates, and signature fields. After multilingual materials enter the workflow, the license and verification form serve as the terminology source, the rectification report serves as the comparison draft, and the terminology list is continuously executed and summarized by subsequent nodes according to branches. The three materials must cross-reference each other item by item in names, quantities, dates, and signatures.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Unified terminology list and comparison draft" is then completed by subsequent nodes continuing execution according to branches. When the user selection node is triggered, the dialogue 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 |
|---|---|---|
| Journal publication license | Fields, dates, and signatures: whether license number, journal name, publication period, sponsoring unit, legal representative, issue date, and seal are consistent with the verification form | In the node, check the options and branch connections one by one, reference variables to record the selection result, and run a trial to see the branch direction |
| Annual verification form | Fields, dates, and signatures: whether verification year, journal name, publication period, sponsoring unit, quantity, filing date, signature, and receipt are consistent with the license | In the run record, view the node status corresponding to nodeId, confirm that the interaction state is recorded and that the selection result variable has been passed to subsequent nodes |
| Rectification report | Fields, dates, and signatures: whether rectification items, journal name, quantity, rectification date, signature, and receipt match the verification form and license | In subsequent nodes, reference the selection result variable and run a trial, checking whether the names, quantities, and dates in the rectification report and the other two materials cross-reference each other |
| Unified terminology list and comparison draft | The same term is consistent throughout, and the translated name can refer back to the source text; sample three terms to check whether their usage is consistent throughout | In subsequent nodes, reference the selection result in variables, continue execution according to the branch, and check the correspondence between the terminology list and the comparison draft |
Three common errors
- Phenomenon: The journal name, quantity, and date of the same record do not match between the license and the verification form. Cause: The two materials were entered separately, and field cross-reference checking was not performed within the same branch.
- Phenomenon: The rectification report has been updated, but the license and verification form are still the old version. Cause: Versions were not synchronized, and the branch direction did not continue execution according to the latest selection result.
- Phenomenon: The verification form lacks a signature or receipt, but the process still moves forward. Cause: After the interaction was completed, the signature field and receipt were not checked, and the node status did not reflect the missing item.
How to verify the setup
Acceptance of this function: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch, and that the selection result variable has been passed to subsequent nodes.
Business testing: sample three terms to check whether their usage is consistent throughout, and check whether the translated names can refer back to the source text.
- In the node, check the options and branch connections one by one, confirm that each option corresponds to one branch, and avoid still taking the default branch after selecting a certain option.
- In the run record, view the node status and selection result variable, confirm that the process continues downward after the interaction is completed, and that the same session does not enter the interaction repeatedly.