What this category's data looks like
Journal three-stage review, three-proofread, and editorial quality materials mainly include three-stage review forms, proofs, and proofreading records. Their sources are the editorial office's initial review, re-review, and final review stages as well as files returned by the proofreading company, and their update cadence follows each issue's manuscript circulation and version iteration. After these materials enter the workflow, the three-stage review form takes on the role of process node confirmation and signed receipt, the proof takes on the role of content comparison and version identification, and the proofreading record takes on the role of error registration and revision traceability. Field characteristics center on manuscript number, review stage, proofreading stage, date, signature, receipt status, version number, and citation location. If the name, quantity, or date of the same record does not match across two materials, or if the version is not synchronized, or a signature or receipt is missing, this will directly affect the uniqueness of the current version and the traceability of old versions.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction status records. The "version ledger and change records" are completed by subsequent nodes continuing execution according to the branch. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; 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 review stage, date, and signature are consistent with the proof and proofreading record | Check the options and branch connections one by one in the node, and confirm that the review stage and signature receipt correspond to the same manuscript number |
| Proof | Whether the version number and citation location are updated synchronously | Trigger one user selection and check the node status and variables reference values in the run record |
| Proofreading record | Whether the error name, quantity, and date match the three-stage review form and proof | Reference the selection result variable in a subsequent node and run a test once, and check the branch corresponding to nodeId |
| Version ledger | The current version is unique, old versions are traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and record the number of array entries and the reference text tokens |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the three-stage review form and the proofreading record. Cause: The materials come from different stages, versions are not synchronized, and a unified manuscript number is missing.
- Symptom: The proof has been updated, but the version ledger still points to the old version, and the citation location is not synchronized. Cause: Change maintenance did not trigger the workflow branch; the old version is traceable, but the current version is not unique.
- Symptom: The three-stage review form lacks a signature or receipt, and the proofreading record has no corresponding confirmation. Cause: The interaction status was not fully recorded, and subsequent nodes continued execution along the default branch.
How to verify the setup
Acceptance for this feature: run tests option by option, check the branch direction and interaction status in the run record, and confirm that variables have been passed to subsequent nodes and that nodeId corresponds to the correct branch.
Business test: change one piece of content, see whether the version number and references are updated synchronously, and check the dates and signature receipts of the three-stage review form, proof, and proofreading record.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and check whether the interaction status is recorded.
- Reference the selection result variable in a subsequent node and run a test once, and check whether the version ledger and change records are updated synchronously and whether old versions are traceable.