What this category's data looks like
This page addresses progress records and statistical reconciliation in the initial review stage of academic journal submissions. The materials include submitted manuscripts, author information tables, plagiarism check reports, and the progress table and statistical criteria notes formed on that basis. Manuscripts enter the initial review queue by submission date; the author information table is used to verify authorship, affiliation, and contact details; the plagiarism check report provides the duplication rate and detection time. The three materials each play a different role in progress records: the manuscript is the record subject, the author information table is the basis for identity and attribution, and the plagiarism check report supports the initial review conclusion. The update cadence rolls forward on a weekly basis, and the field characteristics center on manuscript number, author name, receipt date, plagiarism check date, initial review status, and signature column. The name, quantity, and date of the same record in the manuscript and the author information table must be consistent; the receipt and signature of the plagiarism check report are both indispensable; if versions are not synchronized, the statistical criteria and totals will not match.
Configuration and implementation checks
This step is carried out by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical criteria notes" are then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Primary business database connection variable | Points to the primary business database actually in use and can connect | In the deployment environment, check that the variable value matches the database address, and confirm that MONGODB_URI points to the primary business database |
| Log database connection variable | Configured separately, or left empty to reuse the primary database as instructed | Check whether the variable is set, and verify the database to which logs are written; when left empty, confirm that the primary database is reused |
| Cache connection variable | The cache instance can be connected | Connect once with a client, check the response; confirm that REDIS_URL points to the cache instance |
| Vector database connection variable | Consistent with the vector database actually in use | Check the selected vector database and address against the deployment instructions, and confirm that PG_URL is consistent with the deployment instructions |
Three common errors
- Symptom: The name, quantity, and date of the same manuscript in the progress table and the author information table do not match, and totals do not match the details. Cause: The two materials are maintained separately and are not written back under the same manuscript number.
- Symptom: The version of the plagiarism check report is not synchronized, and the detection date referenced in the progress table is inconsistent with the report receipt date. Cause: After the report is updated, it is not synchronized to the progress record, and the versions are not aligned.
- Symptom: Initial review records lack a signature or receipt but are counted as reviewed during statistics. Cause: The signature column and receipt are not archived with the record, and the criteria do not clearly state the exceptions.
How to verify the setup
Acceptance for this feature: connect once to each of the primary business database, log database, cache, and vector database, check the connection results in the startup logs, and confirm that the services corresponding to MONGODB_URI, REDIS_URL, and PG_URL are all available.
Business test: use one week of records to check the totals, see whether the criteria and exceptions are clearly stated, and confirm that the number of records matches the statistical count and that the criteria are written into the table header.
- In the deployment environment, check that the connection variable values for the primary business database, log database, cache, and vector database match the database addresses, and save the startup logs.
- Check the manuscript number, date, and signature receipt in the progress table against the author information table and plagiarism check report on a weekly basis, and write exceptions into the criteria notes.