What this category's data looks like
This page centers on the business basis query for journal three-review-three-proof and editorial quality. The materials include three types: three-review forms, proofs, and proofreading records. Three-review forms record the fields, dates, and signatures of initial review, re-review, and final review; proofs carry the revision traces and layout confirmations of each proof round; proofreading records register the proof round, error type, quantity, and receipt. The materials are updated on a rolling basis by issue and proof round, and the same manuscript appears repeatedly across the three types of materials, with fields mainly consisting of names, quantities, dates, and signatures. When entering workflow orchestration, three-review forms provide the basis for review rounds and responsible persons, proofs provide the basis for layout and textual changes, and proofreading records provide the basis for error counts and receipts. The three must be compared one by one to form basis entries that can be traced back to the original text.
Configuration and implementation checks
This link is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. "Basis entries that can be traced back to the original text" are 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-review form | Whether the review round fields, dates, and signatures are complete, and whether it can be traced back to the original manuscript text | Check the options and branch connections one by one in the node, confirm that the review round options correspond to branches; reference variables and nodeId to locate the node state in the run record |
| Proof | Whether the proof round name, change quantity, and date are consistent across the three-review form and the proofreading record | Trigger a user selection once, view the node state in the run record, and compare the names, quantities, and dates of the proof with the other two materials |
| Proofreading record | Whether the proof round, error quantity, receipt, and signature match the proof | Reference the selection result variable in a subsequent node and run a trial once to confirm that the error entries can be traced back to the original proof text |
| Version and receipt | Whether the three materials are the current version, and whether missing signatures or receipts are flagged | Run trials on each option one by one, check the branch direction and interaction state, and check whether the branch points to the material to be supplemented when the version is not synchronized or the receipt is missing |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the three-review form and the proofreading record. Cause: The two materials are entered separately, and no field-level comparison has been performed.
- Symptom: The proof has been updated, but the three-review form still remains at the old version. Cause: The version is not synchronized, and the material update rhythms are inconsistent.
- Symptom: The proofreading record lacks a signature or receipt, and the basis entry cannot be traced back to the original text. Cause: The receipt step is not closed-loop, and the signature field is empty.
How to verify the setup
This feature's acceptance: run trials on each option one by one, check the branch direction and interaction state in the run record, and confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes.
Business test: ask a basis question that spans materials, see whether the answer gives a traceable source, and check that the tokens of the quoted text and the number of array entries are recorded separately.
- Check the options and branch connections one by one in the node, confirm that each option corresponds to one branch, and check whether the
variablesreference takes effect. - Trigger a user selection once, view the node state in the run record, and confirm that the interaction state is recorded and that subsequent nodes continue execution according to the branch.