What this category's data looks like
This page addresses the initial review stage of academic journal submissions. The materials include three types: submitted manuscripts, author information forms, and plagiarism check reports. Submitted manuscripts come from author submissions, and updates advance with revised versions; fields include title, author, affiliation, date, and signature field. Author information forms are registered by the editorial office; fields include name, order, contribution, contact information, and confirmation signature. Plagiarism check reports are generated by the detection system; fields include check number, similarity rate, check date, and responsible person. When these three types of materials enter the multi-turn dialogue and prompts feature, the submitted manuscript serves as the main text and version baseline, the author information form serves as the correspondence between authorship and responsibility, and the plagiarism check report serves as the compliance basis. Drafting and handover require item-by-item alignment of the name, quantity, and date of the same record across the three materials. Only when versions and dates are consistent, the responsible person is clear, and signatures and receipts are complete can a signable material draft and handover record be formed and handed to the next stage for receipt.
Configuration and implementation checks
This step is executed by the memory turns and prompt configuration in the app settings, and outputs the historical message range and answer constraints to reference. The signable material draft and handover record are then completed by the model. Memory turns control how many previous rounds of dialogue are referenced at most when answering. If the value is too small, prior context cannot be used; if too large, irrelevant content is included and consumption increases.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscript | Title, author, affiliation, version date, and signature field are complete, and are consistent with the name, quantity, and date of the same record in the author information form and plagiarism check report | In the app settings, check the memory turns value, run a trial with two consecutive questions, and check whether the second question inherits the reference from the first; record the number of entries in the messages array separately, and when a citation limit is involved, check the quoteMaxToken budget of the quoted text |
| Author information form | Authorship order, contribution statement, contact information, and confirmation signature can be traced to a specific responsible person, and do not conflict with the dates in the submitted manuscript and plagiarism check report | Draft one according to the template and complete one handover, and check whether missing items are blocked; compare the usage records of two runs to confirm that consumption changes with the turn adjustment |
| Plagiarism check report | Check number, similarity rate, check date, and responsible person fields are complete, and the version is synchronized with the current version of the submitted manuscript | In the app settings, check the memory turns value, and check whether the session corresponding to chatId brings in the opening message as prior context |
| Handover record | Recipient, receipt date, receipt, and version number are complete, and match the name, quantity, and date of the same record in the three materials | Complete one handover, and check whether missing signatures or receipts are blocked; use variables to mark the version and date, and check whether the two materials do not match |
Three common errors
- Phenomenon: The author count or date of the same record does not match between the submitted manuscript and the author information form. Cause: During drafting, items were not checked one by one according to unified fields, and the version was not synchronized.
- Phenomenon: The version of the plagiarism check report is inconsistent with the current version of the submitted manuscript, and the handover record is still signed off according to the old version. Cause: The version number was not updated in sync with the revision.
- Phenomenon: The handover record lacks the recipient's signature or receipt, but the materials still enter the next stage. Cause: Missing-item blocking did not take effect, and the responsible person was not clear.
How to verify the setup
Acceptance of this feature: Use two consecutive follow-up questions to see whether the second question inherits the reference from the first; at the same time, check whether the memory turns value matches the prior context range required by the question
Business test: Draft one according to the template and complete one handover, and see whether missing items are blocked
- In the app settings, check the current memory turns value, and run a trial with two consecutive questions to confirm that the second question can correctly inherit the reference from the first
- Compare the usage records of two runs to confirm that consumption changes with the turn adjustment, and that the opening message is not treated as prior context