What this category's data looks like
This page focuses on journal three-stage review and three-proof checking and editing quality, handling three types of materials: three-stage review forms, proofs, and proofreading records. The three-stage review form carries the dates and signatures of the initial review, re-review, and final review; the proof records the changes and receipts of each round of proofing; the proofreading record summarizes error types, quantities, and responsible persons. The materials come from each stage of the editorial process and enter the progress table and statistical scope description on a weekly or monthly basis. The three types of materials play different roles in the function: the three-stage review form defines process nodes, the proof defines version status, and the proofreading record defines quality statistics. Field characteristics are concentrated in record name, quantity, date, signature, and version number. Progress records and statistical verification require that the record count and statistical count match, the scope is written into the table header, and the destination goes into the weekly or monthly report.
Configuration and implementation checks
This link is executed by the connection configuration of the deployment environment (server side), not by the capability of the model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is then completed by the deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Three-stage review form | The fields, dates, and signatures of the three-stage review form must be aligned item by item with the proofs and proofreading records; the same record name, quantity, and date must not fail to match across the two materials | In the deployment environment, verify that the main business database pointed to by MONGODB_URI is connectable, then sample one week of three-stage review forms to compare the names, dates, and signatures in the proofs and proofreading records |
| Proof | The proof version number and proofing round must be synchronized with the proofreading records; proofs missing signatures or receipts must not be counted in the progress total | Use a client to connect once to REDIS_URL to confirm the cache instance is connectable, then check whether the proof version and the proofreading record version are synchronized |
| Proofreading record | The error quantity and total scope of the proofreading record must be written into the table header, exceptions must be marked separately, and the record count and statistical count must match | Against the deployment instructions, verify that the vector database pointed to by PG_URL is consistent with the one actually in use, then verify the proofreading record totals and exception notes on a weekly basis |
| Progress table and statistical scope description | The table header must state the statistical scope and exception rules, the record count and statistical count must match, and the destination goes into the weekly or monthly report | Check whether the log database connection variable is set or left empty to reuse the main database according to the instructions, and verify that the progress table totals are consistent with the weekly and monthly report data |
Three common errors
- Symptom: the name, quantity, and date of the same three-stage review form fail to match across the two materials. Cause: the record identifier was not unified at entry, the progress table and statistical table each took data separately, and no item-by-item comparison was made.
- Symptom: the proof version is not synchronized, and the proofreading record still references the old version. Cause: after the version update, the proofreading record was not written back, and proofs missing signatures or receipts were mixed into the total.
- Symptom: after startup, the logs continuously report connection timeouts. Cause: the connection variable value is inconsistent with the database address, or when the log database and the main database are shared, it was not left empty to reuse according to the instructions.
How to verify the setup
This function's acceptance: connect once item by item to the main 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 connectable.
Business test: use one week of records to verify the totals, see whether the scope and exceptions are clearly written, and whether the record count and statistical count match.
- In the deployment environment, verify that the main business database connection variable value is consistent with the database address, and check whether the log database connection variable is set or left empty to reuse the main database according to the instructions.
- Use a client to connect once to the cache instance, check the selected vector database and address against the deployment instructions, and confirm that the startup logs show no connection timeouts.