What this category's data looks like
In the initial review stage of academic journal submissions, the materials include three types: submitted manuscripts, author information forms, and plagiarism check reports. Manuscripts come from the author submission system, author information forms are exported by editors from the submission system or submitted separately by authors, and plagiarism check reports are generated by plagiarism check tools and sent back. The update rhythm advances manuscript by manuscript, and a single manuscript's materials may have their versions replaced multiple times within the initial review cycle. Field characteristics are concentrated in the title, author name, affiliation, manuscript number, plagiarism check date, signature and receipt columns. When entering the model access and configuration function, the three types of materials serve respectively as retrieval corpus and dialogue context: manuscripts provide the basis for the main text, author information forms provide identity and affiliation fields, and plagiarism check reports provide duplication rate and detection date. The model binding relationship determines which type of model is used for dialogue and retrieval, and the channel response determines whether the call can succeed.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting the model binding relationship and channel response. "Basis entries that can be traced back to the original text" are completed subsequently by AI nodes, code nodes, or manual work. Models are divided into five types: language, indexing, reranking, speech synthesis, and speech recognition, and different steps bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | The title, author name, manuscript number, and signature column must match the author information form item by item, and the date must fall within the current version | Check the title and manuscript number against the author information form, check whether the signature column and receipt are complete, and confirm that the version used is the current version |
| Author information form | The name, affiliation, manuscript number, and date must be consistent with the submitted manuscript and plagiarism check report, and there must not be any mismatch in the name or quantity of the same record | Compare field by field with the manuscript and plagiarism check report, record inconsistent items, and check the version number and signature column |
| Plagiarism check report | The plagiarism check date, duplication rate, and manuscript number must correspond to the manuscript and author information form, and the detection date must not be earlier than the submission date | Check the plagiarism check date and manuscript number, compare the name and affiliation in the author information form, and confirm that the report is the current version |
| Model binding relationship | The language model, indexing model, and reranking model must correspond to the step to be used, and the model identifiers must be consistent with the names listed in the documentation | Check the type labels in the model configuration, compare them with the model names returned by the channel, and check whether maxContext, maxTokens, and quoteMaxToken match the step |
Three common errors
- Symptom: The title or manuscript number of the same manuscript does not match between two materials. Cause: The author information form and the manuscript were submitted separately, and no field-by-field comparison and version synchronization were performed.
- Symptom: The detection date of the plagiarism check report is inconsistent with the manuscript version date. Cause: After the plagiarism check report was sent back, it was not updated with the manuscript version change, and the signature or receipt is missing.
- Symptom: Retrieval reports an indexing model-related error or authentication failure. Cause: The model type does not match the step, or the channel key is inconsistent with the connected service, and the answer style changes abruptly after switching models.
How to verify the setup
Acceptance of this function: run one dialogue and one retrieval, check whether the model identifiers in the response are consistent with the names listed in the documentation, and check whether maxContext, maxTokens, and quoteMaxToken match the step.
Business test: ask a basis question across materials, and see whether the answer gives a traceable source, whether the basis comes from the materials in this category, whether the version is the current one, and whether the entries can be matched to the original text.
- In the model configuration, check the type labels of the language, indexing, and reranking models and their correspondence to the steps, and compare them with the model names returned by the channel.
- Compare field by field the title, name, manuscript number, date, and signature of the submitted manuscript, author information form, and plagiarism check report, record inconsistent items, and trace them back to the original text.