What this category's data looks like
In the preliminary review scenario for academic journal submissions, the materials entering the workflow are usually of three types: submitted manuscripts, author information forms, and plagiarism check reports. The submitted manuscript is the primary material, containing the title, authors, affiliations, abstract, main text, and submission date; the author information form records names, order, affiliations, contact information, and signature fields; the plagiarism check report provides the duplication rate, comparison sources, detection date, and receipt. The three types of materials have different sources and different update rhythms: manuscripts change with revised versions, information forms change with author confirmations, and plagiarism check reports change with detection batches. When they enter this feature, the three play different roles: the submitted manuscript serves as the original text basis being queried, the author information form serves as the object for checking authorship and signatures, and the plagiarism check report serves as the object for checking versions and dates. Field characteristics are concentrated in names, quantities, dates, signatures, and receipts, and the same record can easily fail to match across different materials.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. Basis items that can refer back to the original text are completed by subsequent nodes continuing execution according to the branch. When a 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 |
|---|---|---|
| Submitted manuscript | Whether the name, quantity, date, and signature are consistent with the author information form | Check the options and branch connections one by one in the node, trigger it once and then view the node status in the run record, and reference the selection result variable in a subsequent node for a trial run |
| Author information form | Whether the name, order, affiliation, date, and signature field are complete | Check the name and quantity in the author information form and the submitted manuscript, check whether the signature or receipt is missing, and confirm that the version is current |
| Plagiarism check report | Whether the duplication rate, comparison sources, detection date, and receipt match the original text | Check the version and date of the plagiarism check report and the submitted manuscript, confirm that the detection batch is current, and check whether the receipt is complete |
| User selection node | Whether each option corresponds to one branch and correctly records the interaction state | Check the options and branch connections one by one in the node, use nodeId to locate the node, reference the selection result variable in variables, and perform a trial run |
Three common errors
- Symptom: The name and quantity of the same record do not match between the submitted manuscript and the author information form. Cause: The two materials are updated separately, and no field-level comparison has been performed.
- Symptom: The detection date of the plagiarism check report is inconsistent with the manuscript revision date, and the versions are not synchronized. Cause: The detection batch is not bound to the manuscript version, and an old report is treated as the current material.
- Symptom: The author information form lacks a signature or receipt, and the basis item cannot refer back to the original text. Cause: The signature field and receipt have not been included in the material verification checklist.
How to verify the setup
Acceptance of this feature: run a trial for each option one by one, check the branch direction and interaction state in the run record, and use nodeId and variables to confirm that the selection result variable has been passed to subsequent nodes.
Business test: ask a basis question that spans materials and see whether the answer provides a traceable source.
- Check the options and branch connections one by one in the node, trigger it once and then view the node status in the run record.
- Reference the selection result variable in a subsequent node and perform one trial run to confirm that the branch direction is consistent with the recorded interaction state.