What this category's data looks like
The category materials for initial review of academic journal submissions include submitted manuscripts, author information forms, and plagiarism check reports. The sources are the submission system, author submissions, and the plagiarism check service, and the update cadence changes with each round of submission batches. When the materials enter the deployment, operations, and application handover function, the submitted manuscripts serve as the main text comparison baseline, the author information forms serve for verifying authorship and affiliations, and the plagiarism check reports serve for verifying duplication rates and dates. The field characteristics center on names, quantities, dates, and signatures: the manuscript title and the title in the author information form must be consistent, the number of manuscripts and the number of articles covered by the plagiarism check report must be consistent, the receipt date and the plagiarism check date must be traceable, and the initial review comments and the handover form must have signatures or receipts. The deployment side only handles connection configuration and startup logs, does not read or write the above materials, and does not use them to determine whether materials are mixed up.
Configuration and implementation checks
This step is executed by the connection configuration of the deployment environment (server side), not by the capability of a model node, and outputs whether the connection is available (service startup result and connection logs). The handover-ready deployment status and operation records are then completed by the deployment handover and subsequent business processing. The connection address is configured by environment variables, and the main business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it reuses the main database.
| Object | Check | Verification action |
|---|---|---|
| Submitted manuscripts | The manuscript title, receipt date, and initial review comments are consistent between the manuscript and the handover form. | Compare the submitted manuscript with the handover form, and check whether the title, receipt date, and signature field are complete. |
| Author information form | The author names, affiliations, and manuscript authorship are consistent between the author information form and the manuscript. | Compare the author information form with the manuscript authorship item by item, and check whether the quantities and dates match. |
| Plagiarism check report | The plagiarism check date, duplication rate conclusion, and manuscript batch are consistent between the plagiarism check report and the handover form. | Check the plagiarism check report date and manuscript batch, and inspect whether the receipt or signature is missing. |
| Deployment connection | The main business database, log database, cache, and vector database connections are available and consistent with the deployment instructions. | In the deployment environment, check the values of MONGODB_URI, REDIS_URL, and PG_URL against the instance addresses, and review the connection results in the startup logs. |
Three common errors
- Symptom: The title or number of articles for the same manuscript does not match between the manuscript and the handover form. Cause: The two materials were entered separately, and names and quantities were not checked against the same batch.
- Symptom: The plagiarism check report date is inconsistent with the manuscript receipt date. Cause: The versions were not synchronized, and the manuscript used for the plagiarism check is not the same version as the current manuscript.
- Symptom: After startup, the logs continuously report connection timeouts. Cause: The instance pointed to by the connection variable is unreachable, or the log database and main database addresses are mixed up.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and confirm that MONGODB_URI, REDIS_URL, and PG_URL are consistent with the deployment instructions.
Business test: check item by item once according to the handover form, see which record is missing, and focus on checking the names, quantities, dates, and signatures of the manuscripts, author information forms, and plagiarism check reports.
- In the deployment environment, check the values of the connection variables for the main business database, log database, cache, and vector database, and review the service startup result and connection logs.
- Check the fields, dates, and signatures of the submitted manuscripts, author information forms, and plagiarism check reports item by item according to the handover form, record missing items, and hand over to the next shift.