What this category's data looks like
This category's data involves three types of materials: submitted manuscripts, author information forms, and plagiarism check reports. Manuscripts come from the author submission system and enter the initial review queue in batches, with an update cadence synchronized with the call-for-papers cycle; author information forms are submitted along with the manuscript, with fields including name, affiliation, authorship order, date, and signature; plagiarism check reports are generated by detection tools and include similarity rate, comparison sources, and generation date. When these three types of materials enter the authorized access and external services feature, the manuscript is the main record, the author information form serves as the basis for identity and authorization, and the plagiarism check report serves as supporting judgment material. External services are open to parents or superiors and must limit the visible scope according to the visitor's identity. Field characteristics center on names, quantities, dates, and signatures; the same record often has mismatched names, quantities, and dates across the two materials, versions are not synchronized, and signatures or receipts are missing.
Configuration and implementation checks
This step is executed by the form input node (interaction node) in the workflow, which outputs the field values filled in by the user (passed to subsequent nodes after submission). The externally available entry point and authorization scope are then completed by subsequent nodes or manually. After the form input node is triggered, the conversation enters an interactive state and records the workflow state; after the user fills in the required items and submits, the form information is passed to subsequent nodes for use.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | Whether the names, quantities, and dates are consistent with the author information form and plagiarism check report, and whether signatures and receipts are complete | Check the manuscript title, authorship order, and submission date one by one, and reference the fields in subsequent nodes for a trial run |
| Author information form | Whether the authorship order, affiliation, date, and signature correspond to the manuscript and plagiarism check report, and whether the versions are synchronized | Check the field names and required markers one by one, and verify the field names and required settings in the formInput node configuration |
| Plagiarism check report | Whether the similarity rate, comparison sources, and generation date correspond to the manuscript version, and whether signatures or receipts are missing | Check the report generation date against the manuscript submission date, limit the visible scope in userSelect, and run a trial |
| External service entry point | Whether the visitor's identity matches the visible scope, and whether unauthorized access is invisible | Access once with a restricted identity and check whether the field values obtained by subsequent nodes match the settings |
Three common errors
- Symptom: The names, quantities, and dates of the same manuscript do not match between the author information form and the plagiarism check report. Cause: The two materials were entered separately, and no consistency check of field names and dates was performed.
- Symptom: The manuscript version is not synchronized, and the plagiarism check report corresponds to an old version. Cause: The report was not updated after submission, and the field values obtained by subsequent nodes are still the old version.
- Symptom: The author information form lacks a signature or receipt but still enters external services. Cause: The required markers do not cover the signature field, and subsequent nodes cannot obtain the value after submission.
How to verify the setup
Feature acceptance: Fill in and submit once, check the field values obtained by subsequent nodes, and confirm that the corresponding fields of formInputResult and selectResult are passed correctly.
Business test: Access once with a restricted identity, see whether the visible scope matches the settings, and confirm that unauthorized content is invisible.
- In the
formInputnode configuration, check the field names and required markers one by one to ensure that key material fields are marked as required. - Reference the
selectResultoutputs in subsequent nodes and run a trial to confirm that the corresponding field values can be obtained after submission and that the conversation does not remain in the interactive state.