What this category's data looks like
The category materials for initial review of academic journal submissions consist of three parts: submitted manuscripts, author information tables, and plagiarism check reports. Submitted manuscripts come from the author submission system, and their update cadence rolls with submission batches; author information tables are generated synchronously with manuscripts and include names, affiliations, authorship order, and dates; plagiarism check reports are produced by the plagiarism check step and are attached with detection time and receipt. When the materials enter the workflow orchestration function, submitted manuscripts take the role of the main record, author information tables take the role of verifying authorship and affiliations, and plagiarism check reports take the role of verifying duplication rates and detection dates. The field characteristics of the three are concentrated in names, quantities, dates, and signed receipts; any mismatch in one place will affect the initial review handover. During the deployment, operations, and application handover stage, the three—version, connection, and task records—need to be aligned to form a handover-ready deployment state and operation records, so that operations or the next shift can check them item by item according to the handover sheet.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction state records. The "handover-ready deployment state and operation records" are completed by subsequent nodes continuing execution 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 |
|---|---|---|
| Submitted manuscripts | Whether the name, quantity, date, and signed receipt are consistent in the author information table and plagiarism check report | Compare item by item the manuscript number, title, author count, receipt date, and signature field, and check whether the manuscript identifier referenced by variables points to the same record |
| Author information table | Whether the authorship order, affiliation names, dates, and receipts match the manuscript and plagiarism check report | Check names, affiliations, authorship order, and dates according to the handover sheet, inspect entries missing signatures or receipts, and reference nodeId in a subsequent node to run a trial once |
| Plagiarism check report | Whether the detection date, duplication rate range, and receipt are synchronized with the manuscript and author information table | Check the detection date and receipt number, confirm entries whose versions are not synchronized, and trigger an interaction state once to view the node status in the run records |
| Deployment state and operation records | Whether version, connection, and task records are consistent | Check the version number, connection items, and task records item by item according to the handover sheet, and check whether variables and nodeId correspond to the same branch in the records |
Three common errors
- Symptom: For the same manuscript, the title, author count, and date do not match between the author information table and the plagiarism check report. Cause: The two materials are entered separately, lacking unified verification and receipts.
- Symptom: The manuscript version has been updated, but the author information table and plagiarism check report still remain at the old version. Cause: The version was not synchronized, and the handover sheet did not note the change time and signature.
- Symptom: After the interaction is completed, the process stops, or after selecting an option it still follows the default branch. Cause: The options and branch connections were not checked item by item, and the selection result variable was not passed to subsequent nodes.
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 records, confirm that the selection result variable has been passed to subsequent nodes, and check the correspondence between variables, nodeId, and the option branches.
Business test: check once item by item according to the handover sheet, see which record is missing, and focus on checking the names, quantities, dates, and signed receipts of the submitted manuscripts, author information tables, and plagiarism check reports.
- In the nodes, check the options and branch connections one by one, trigger an interaction state once, and view the node status and branch direction in the run records.
- In a subsequent node, reference the selection result variable and run a trial once, and check according to the handover sheet whether version, connection, and task records are consistent.