What this category's data looks like
Journal three-stage review and three-proof correction and editorial quality materials include three categories: three-stage review forms, proofs, and proofreading records. Their sources are the editorial department's initial review, re-review, and final review stages and proofreading position circulation, and the update rhythm is submitted in batches according to each issue's manuscript progress. Three-stage review forms record the fields, dates, and signatures of initial review, re-review, and final review; proofs carry the revision traces and receipts of each proofreading round after typesetting; proofreading records summarize the number, type, and responsible person of errors in each proofreading round. When these three categories of materials enter workflow orchestration, their roles differ: three-stage review forms serve as the basis for process initiation and branching, proofs serve as intermediate verification objects, and proofreading records serve as handover archives. Field characteristics are concentrated in three places: version number, connection relationships, and task records. Handover is only allowed when version, connection, and task records are consistent.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. "Handover-ready deployment status and operation records" are then completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation 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 | Whether the fields, dates, and signatures of 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, trigger once to view the node status in the run records, and reference variables to confirm that the selection result variable has been passed to subsequent nodes |
| Proof | Whether the revision traces, receipts, and version number of each proofreading round are synchronized, and whether proofreading rounds missing signatures or receipts are marked | Reference the variable corresponding to nodeId in subsequent nodes and run a trial once, and check whether the proof version is consistent with the version number in the task records |
| Proofreading record | Whether the number, type, and responsible person of errors in each proofreading round are consistent with the three-stage review form and proof, and whether the dates match | Check item by item once according to the handover form, see which record is missing, and confirm that the selection result recorded in variables corresponds to the proofreading record entries |
| Deployment status and operation records | Whether version, connection, and task records are consistent, and whether branch direction and interaction state leave traces | Check the branch direction and interaction state in the run records, and confirm that the node status corresponding to nodeId has been recorded |
Three common errors
- Phenomenon: The name, quantity, and date of the same record do not match between the three-stage review form and the proofreading record. Cause: The two materials are entered separately, and cross-checking by version number and task records is not performed.
- Phenomenon: The proof version is not synchronized, and subsequent nodes still reference the old proof version to continue execution. Cause: The version number is not written into the connection relationships, and task records are not updated with the proof.
- Phenomenon: Proofreading rounds missing signatures or receipts are directly released, and there is no corresponding record on the handover form. Cause: Interaction state records are not compared item by item with proofreading records, and branch direction leaves no trace.
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 records, and confirm that the selection result variable corresponding to variables and nodeId has been passed to subsequent nodes.
Business test: check item by item once according to the handover form, see which record is missing, and check whether the fields, dates, and signatures of the three-stage review form, proof, and proofreading record are consistent.
- Check the options and branch connections one by one in the node, trigger once to view the node status in the run records, and confirm that the selection result variable has been passed to subsequent nodes.
- Check the fields, dates, and signatures of the three-stage review form, proof, and proofreading record item by item according to the handover form, and after confirming that version, connection, and task records are consistent, hand over to operations or the next shift.