What this category's data looks like
This page focuses on material drafting and handover of responsibility in the scenario of journal three-stage review and three-proofreading and editorial quality. Category materials include three types: three-stage review forms, proofs, and proofreading records. The three-stage review form carries the fields and signatures for initial review, re-review, and final review; the proof carries layout, text changes, and dates; the proofreading record carries the names, quantities, and dates of the first proofreading, second proofreading, and third proofreading. When these three types of materials enter workflow orchestration, each has a different role: the three-stage review form serves as the prerequisite basis, the proof serves as the process evidence, and the proofreading record serves as the result receipt. Material sources are internal circulation within the editorial department and returns from external proofreading companies. The update rhythm advances with each issue's manuscript batch, and field characteristics are concentrated on responsible persons and version dates.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branches), outputting branch directions and interaction state records. "Draft materials that can be issued and handover records" are then completed by subsequent nodes continuing execution according to the 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 |
|---|---|---|
| Three-stage review form | Fields are complete and responsible persons are clear; the signatures and dates of initial review, re-review, and final review are consistent | Check the options and branch connections one by one in the node, and check whether the signatures and dates of the three-stage review form correspond to the proofreading records |
| Proof | Version and date are synchronized; the names and quantities in the same record match across the two materials | Trigger a user selection once, view the node status in the run record, and check the proof version number and date |
| Proofreading record | Missing signatures or receipts are blocked; the selection result variable has been passed to subsequent nodes | Reference variables in a subsequent node and run a trial once, and check the names, quantities, and dates of the proofreading record and the three-stage review form |
| Handover record | Responsible persons are clear and version and date are consistent; receipts are complete | Check the branch direction corresponding to nodeId, and confirm that there are no missing fields in the handover record |
Three common errors
- Phenomenon: The names, quantities, and dates of the same record do not match between the three-stage review form and the proofreading record. Cause: During drafting, checks were not performed against the same field template, and cross-comparison was missing before handover.
- Phenomenon: The proof version is not synchronized, and subsequent nodes still reference the old version. Cause: After user selection, the referenced variable was not updated, and the branch direction became disconnected from the version.
- Phenomenon: The three-stage review form lacks signatures or the proofreading record lacks receipts. Cause: The handover record did not set required fields, and the receipt step did not block missing items.
How to verify the setup
Acceptance of this function: Run trials option by option, check the branch direction and interaction state in the run record, and confirm that variables and nodeId are correctly referenced in subsequent nodes.
Business test: Draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the options and branch connections one by one in the node, and confirm that each option corresponds to one branch.
- Trigger a user selection once, and view the node status and selection result variable in the run record.