What this category's data looks like
This page addresses the scenario of journal three-stage review and three-proof correction and editorial quality. The material sources are the three-stage review forms, proofs, and proofreading records that circulate in the editorial office daily, and the update rhythm advances round by round with manuscript circulation. The three-stage review form carries the fields, dates, and signatures of the initial review, re-review, and final review, and serves as the draft of the acceptance questions when entering the workflow; the proof carries layout and text modification traces, and is used to compare the name, quantity, and date of the same record when entering the workflow; the proofreading record carries the responsible person and receipt for each round of proofreading, and is used to verify whether signatures are complete and whether versions are synchronized when entering the workflow. The field characteristics of the three types of materials are: manuscript number, responsible person, round, date, signature, receipt, modification description. When the materials enter this function, each assumes a different role: the three-stage review form provides the skeleton of the questions, the proof provides the basis for factual comparison, and the proofreading record provides clues for missing items and receipts. Together they support the generation of acceptance records and completed questions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Acceptance records and completed questions" are continued and completed by subsequent nodes according to the branch. When the user selection node is triggered, the conversation enters the 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 | Check whether the fields, dates, and signatures of the initial review, re-review, and final review are complete, and whether the name, quantity, and date of the same record match across the two materials | Check the options and branch connections one by one in the node, and after a trial run, view the node status in the run record |
| Proof | Check whether the versions are synchronized, whether the modification description is consistent with the name, quantity, and date in the proofreading record, and whether missing signatures or receipts are identified | Reference the selection result variable variables in a subsequent node and run a trial once to confirm the branch direction |
| Proofreading record | Check whether the responsible person and receipt for each round of proofreading are complete, and whether the name, quantity, and date of the same record fail to match across the two materials | Trigger an interaction once, view the nodeId and node status in the run record, and confirm that the process continues after the interaction is completed |
| Acceptance question | Missing items are identified and followed up on, the answer has a material basis, and the questions correspond one by one to the three-stage review form, proof, and proofreading record | Reference the selection result variable in a subsequent node and run a trial to confirm that the follow-up precedes the answer, then transfer to the responsible person for handling |
Three common errors
- Phenomenon: The name, quantity, and date of the same record fail to match between the three-stage review form and the proof. Cause: The versions of the two materials are not synchronized, and the acceptance question answers before first following up on missing items.
- Phenomenon: The proofreading record is missing a signature or receipt, but the process still continues. Cause: The options and branch connections were not checked one by one, and after selecting an option, the default branch is still taken.
- Phenomenon: After the interaction is completed, the process stops, and the same session repeatedly enters the interaction. Cause: The selection result variable is not passed to subsequent nodes, and the workflow state is not correctly recorded.
How to verify the setup
This function's acceptance: run trials for each option one by one, check the branch direction and interaction state in the run record, confirm that options and branches correspond one to one, and that the selection result variable has been passed to subsequent nodes.
Business test: submit a question missing key information and see whether it first follows up before answering; the follow-up items must correspond to the fields of the three-stage review form, proof, and proofreading record, and after the answer has a material basis, transfer to the responsible person for handling.
- Check the options and branch connections one by one in the node, trigger an interaction once, and view the
nodeIdand node status in the run record. - Reference the selection result variable
variablesin a subsequent node and run a trial once to confirm that the process continues after the interaction is completed and that missing items are identified and followed up on.