What this category's data looks like
This page addresses the deployment, operations, and application handover scenarios of peer review organizations. The materials come from three types of records: review invitations, expert review comments, and author revision notes, and the update cadence advances with review rounds and version releases. Review invitations carry the invitation time, expert signature, and receipt; expert review comments carry comment items, dates, and signatures; author revision notes carry revision items, corresponding comment numbers, and dates. When these materials enter the deployment and upgrade function, they respectively assume the roles of invitation confirmation, comment traceability, and revision receipt, and need to be aligned item by item with deployment status and operation records, forming a handover-ready deployment status and operation records.
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 |
|---|---|---|
| Image version identifiers | The target version identifiers of the two images, the main service and the commercial edition, must be consistent and correspond to the version notes | In the deployment environment, check the version identifiers of the two images, and verify that MONGODB_URI, PG_URL, and REDIS_URL connections point to the same set of services |
| Historical chunk training task migration | Triggered only after the old instance has been fully stopped and the old task lease has expired; the record includes execution time and status | On the administrator version upgrade page, view this migration task record and compare it item by item with the dates of review invitations and expert review comments |
| Knowledge base rebuild status migration | Triggered only after the previous migration is completed; the time and status of the two records must connect sequentially | Compare the time and status of the two migration task records, and sample one data row to verify the index status field |
| Author revision notes | Revision items, corresponding comment numbers, dates, and signatures must be consistent with the review comments | According to the handover checklist, verify the names, quantities, and dates of the revision notes and expert review comments, and confirm that signatures or receipts are complete |
Three common errors
- Symptom: the service can start but the data row status is still the old marker. Cause: only the image version was updated, the two migration scripts were not executed, and the data row index status was not synchronized.
- Symptom: the names, quantities, and dates of the same record do not match between the review comments and the revision notes. Cause: the two materials were updated separately, and signatures or receipts are missing.
- Symptom: the script execution reports an error or the two image versions are inconsistent. Cause: the old instance was not fully stopped, the old task lease has not expired, or the versions were not synchronized.
How to verify the setup
This function acceptance: verify the two image version identifiers, then verify the execution records of the two migration scripts in order, and confirm that the data row index status field is the new system.
Business test: check item by item once according to the handover checklist to see which record is missing, focusing on verifying the fields, dates, and signatures of review invitations, expert review comments, and author revision notes.
- On the administrator version upgrade page, view the two migration task records and confirm that the second is triggered only after the first is completed.
- Sample one data row to verify the index status field, and verify the two image version identifiers and connection configuration.