What this category's data looks like
This page handles the status records of journal publication license and annual verification materials entering the deployment, operations, and application handover stage. The materials include journal publication licenses, annual verification forms, and rectification reports, sourced from issuance by publication administrative departments and submission receipts. The update cadence advances according to the annual verification cycle and rectification deadlines, and the field characteristics center on journal name, journal number, sponsoring organization, verification year, rectification items, signatures, and receipt dates. When entering this function, the license and verification form assume the role of version and entity verification, while the rectification report assumes the role of discrepancy explanation and closure; together, the three constitute a handover-ready deployment status and operation record.
Configuration and implementation checks
The deployment environment and administrator version upgrade page (server-side operation) only output the image version, migration task records, and data row index status; the handover-ready deployment status and operation records must be continued by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Check whether the journal name, journal number, sponsoring organization, and signature date are consistent with the annual verification form | Compare the name, quantity, and date item by item against the license and verification form, and check the records in the database corresponding to MONGODB_URI |
| Annual verification form | Check whether the verification year, verification conclusion, and receipt date are complete | View the migration task records on the administrator version upgrade page, and confirm that the verification form fields are consistent with the license |
| Rectification report | Check whether the rectification items, rectification deadline, and signature receipt form a closed loop | Sample one data row to check the status field, and confirm that the rectification report dates match the verification form |
| Main service and commercial edition image versions | Both images are the same target version | Compare the version identifiers of the two images against the version description, and check the connection status of PG_URL and REDIS_URL |
Three common errors
- Symptom: the service starts but the data row status is still the old marker. Cause: the two migration scripts were not executed in order, and the latter depends on the former completing.
- Symptom: the name, quantity, and date of the same record do not match between the license and the verification form. Cause: the versions are not synchronized, 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, and the old task lease had not expired before triggering.
How to verify the setup
This function's 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 is the new system.
Business test: check item by item once according to the handover form, see which record is missing, and confirm that the fields, dates, and signatures of the license, verification form, and rectification report are complete.
- On the administrator version upgrade page, view the execution records of the historical chunk training task migration and knowledge base rebuild status migration, and compare the time and status.
- Sample one data row to check the status field, and check whether the
DB_MAX_LINKconnection and the two image version identifiers are consistent.