What this category's data looks like
This category covers the preliminary screening of academic journal submissions. Materials include submitted manuscripts, author information forms, and plagiarism check reports. Manuscripts are submitted by authors, author information forms are registered along with the manuscripts, and plagiarism check reports are generated by the plagiarism check step and returned. The update cadence rolls by submission batch, and a single manuscript may produce new versions during the preliminary screening cycle due to corrections. Field characteristics center on four types: name, quantity, date, and signature: the manuscript byline and the name on the author information form must match, the number of figures and tables must match the number registered on the information form, the receipt date and the issue date of the plagiarism check report must be traceable, and the review conclusion must have a reviewer signature or receipt. Once the three types of materials enter workflow orchestration, each takes on a role: the manuscript is the source material for exception tracing, the author information form is the baseline for name and quantity comparison, and the plagiarism check report is the reference for date and version synchronization.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch direction and interaction state records. The "exception list and review conclusion" is completed by subsequent nodes continuing execution along the branch. When the user selection node is triggered, the conversation enters an interaction state and the workflow state is recorded; after the user completes the selection, execution continues along the branch corresponding to the chosen option.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | Byline, receipt date, and version number must match the author information form and plagiarism check report | Check the manuscript name, quantity, date, and signature one by one, compare whether the same record in the two materials is consistent, record discrepancies, and reference variables and nodeId in subsequent nodes, running each once |
| Author information form | Name, affiliation, and quantity registration must match the manuscript; missing signatures or receipts must be flagged | Check the information form fields against the manuscript byline and figure/table quantities, check whether the signature field and receipt are complete, and flag inconsistent items |
| Plagiarism check report | Issue date and version must be synchronized with the current manuscript, and the duplication rate field must be traceable | Check the report date against the manuscript version, check whether the report corresponds to the latest manuscript, and record cases where the version is not synchronized |
| Workflow node (user selection and branching) | Each option corresponds to one branch, and the interaction state and selection result variable must be recorded | Run each option once, check the branch direction and interaction state in the run record, reference variables in subsequent nodes, and run once |
Three common errors
- Symptom: the name or quantity of the same manuscript does not match between the author information form and the plagiarism check report. Cause: registration and the plagiarism check step each enter data separately, without using the manuscript source material as the baseline for field comparison.
- Symptom: after the manuscript is corrected, the version is not synchronized, and the plagiarism check report still points to the old version. Cause: version updates do not trigger re-verification, and the date and version fields are not linked for validation.
- Symptom: the review conclusion lacks a signature or receipt, and the exception list cannot be handed to the person in charge for handling. Cause: the review step does not enforce signature collection, and the receipt is not archived together with the conclusion.
How to verify the setup
Feature acceptance: run each option once, check the branch direction and interaction state in the run record, confirm that each option corresponds to one branch and that the selection result variable has been passed to subsequent nodes, and reference variables and nodeId, running each once.
Business test: create an exception record, see whether it can be traced to the source material, confirm that the exception is supported by original records and that the reviewer signature is complete, then hand it to the person in charge for handling.
- In the node, check the options and branch connections one by one to ensure that each option corresponds to one branch and that no default branch is mistakenly taken.
- Trigger the user selection node once, view the node state and interaction state in the run record, and confirm that the selection result variable has been passed to subsequent nodes.