What this category's data looks like
In the initial review stage of academic journal submissions, materials include three types: submitted manuscripts, author information forms, and plagiarism check reports. Manuscripts come from the author submission system, author information forms are filled out by the corresponding author, and plagiarism check reports are generated by plagiarism check tools. The update rhythm changes with submission batches, and each submission forms a set of materials. Field characteristics center on names, quantities, dates, and signatures: the manuscript title and the author information form title must be consistent, the number of authors and the order of authorship must correspond, the submission date and the plagiarism check date must fall within the same period, the author information form must have the corresponding author's signature, and the plagiarism check report must have a receipt number. When the three types of materials enter the tool calling and plugin function, the manuscript serves as the main record, the author information form serves as the basis for identity verification, and the plagiarism check report serves as supporting evidence, jointly supporting the generation of the subsequent discrepancy list.
Configuration and implementation checks
This step is executed by the tool calling node in the workflow (the model decides whether to call, and the node executes), outputting the tool call result (the input parameters and return in the call record). The "discrepancy list" is then completed by a subsequent AI node or manual verification. The model determines whether to call based on the tool description, parameter descriptions, and whether parameters are required.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | Whether the title, number of authors, and submission date are consistent with the author information form and plagiarism check report | Open the tool node description field and verify the manuscript title against the author information form title; run a test query missing the number of authors to see whether it asks a follow-up question first; check the values of toolChoice and functionCall in the call record |
| Author information form | Whether author names, order of authorship, signature, and receipt are complete | Open each parameter configuration and verify the description and required status of the name and signature fields; verify the diamond-shaped connections and node status on the canvas; confirm that the returned result does not contain values that do not exist in the materials |
| Plagiarism check report | Whether the plagiarism check date and receipt number match the manuscript and author information form | Check whether the plagiarism check date and receipt number are in the same period as the manuscript submission date; run a test query missing the receipt number to see whether it asks a follow-up question first; verify the input parameters and return of toolChoice in the call record |
Three common errors
- Symptom: The number of authors for the same record does not match between the manuscript and the author information form. Cause: The two material versions were not synchronized, and the tool call returned fields from an old version.
- Symptom: The plagiarism check report is missing the receipt number or the author information form is missing a signature. Cause: Items were omitted during material collection, and the tool call did not trigger a follow-up question.
- Symptom: After multiple tools are chained, results cross over each other, and dates and names are misaligned. Cause: The tool description did not specify the return result, and the model misused parameters.
How to verify the setup
Acceptance of this feature: run a test query missing a required parameter, check the input parameters and return in the call record, and confirm whether it asks a follow-up question or calls according to the description; also check whether toolChoice and functionCall appear in the call record.
Business test: use a real record to find fields inconsistent with the ledger, focusing on verifying whether the name, quantity, and date of the same record match across the two materials.
- Open the tool node description field, check whether this description can be understood when read on its own, and confirm that the diamond-shaped interface is connected to the target tool.
- Open each parameter configuration, verify the description and required status, run a test query missing that field to see whether it asks a follow-up question first rather than directly fabricating.