What this category's data looks like
This page focuses on the three-review-three-proof and editorial quality scenario for journals, with materials drawn from three types of editorial materials: three-review forms, proofs, and proofreading records. The three-review form carries the fields, dates, and signatures for initial review, re-review, and final review; the proof carries the version identifier and revision traces; the proofreading record carries the proofreading rounds, counts, and receipts. When these materials enter the deployment and upgrade function, each plays a different role: the three-review form is used to check whether the version and signatures are synchronized, the proof is used to check whether the name, count, and date of the same record are consistent across the two materials, and the proofreading record is used to check for missing signatures or receipts. The update rhythm advances with the editorial process, and a new record is generated after each round of three-review or proofreading is completed. Field characteristics include record name, count, date, signature, and receipt. When the version is not synchronized or the fields do not match, the deployment status and operation records cannot be handed over.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), outputting the image version, migration task records, and data row index status. "Handover-ready deployment status and operation records" are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Main service and commercial edition image versions | Both images are the same target version; check the version identifiers of the two images against the version notes | On the version upgrade page, check the version identifiers of the two images and confirm they are consistent |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired; view the execution record of this task on the administrator's version upgrade page | View the execution record of this task and check the trigger time and status |
| Knowledge base rebuild status migration | Triggered after the previous migration is completed; compare the time and status of the two records | Compare the time and status of the two migration records and confirm the order |
| Data row index status | After migration, it is the new index status system; sample one data row and check the status field | Sample one data row and check the status field to confirm it has been migrated |
Three common errors
- Symptom: The name, count, and date of the same record do not match between the three-review form and the proof. Cause: The two materials were not updated in sync, and the versions were not synchronized.
- Symptom: The service can start, but the data row status is still the old marker. Cause: The migration script was not executed or execution reported an error; consistent image versions do not mean the business data migration has been completed.
- Symptom: The proofreading record is missing a signature or receipt. Cause: During handover, items were not checked one by one against the handover list, so the record is incomplete.
How to verify the setup
This function's acceptance: check the two image version identifiers, then check the execution records of the two migration scripts in order; check the connection status of MONGODB_URI, PG_URL, and REDIS_URL; the migration task records and data row index status must be consistent.
Business test: check once item by item against the handover list and see which record is missing.
- On the version upgrade page, view the execution records of the two migration scripts and check the time and status.
- Sample one data row to check the status field, and check whether
MONGODB_URI,PG_URL, andREDIS_URLconnections are normal.