What this category's data looks like
This page addresses the deployment, operations, and application handover stages of journal publication license and annual verification materials. The materials include three categories: journal publication licenses, annual verification forms, and rectification reports. Licenses are issued by the competent authority, and their fields include license number, publishing entity name, business scope, validity start and end dates, and issuance date; the update cadence is triggered by license renewal or changes. Annual verification forms are filed annually, and their fields include verification year, publishing entity information, publishing activity details, legal representative signature, and submission date. Rectification reports address issues found during verification, and their fields include rectification items, rectification measures, completion date, and responsible party signature. After these three categories of materials enter the deployment environment, licenses and verification forms are written into the primary business database as primary business data, while rectification reports are retained as process records together with the verification forms; the log database separately handles service runtime records, and the cache and vector database support retrieval and streaming recovery. During handover, consistency among version, connection, and task records is used as the basis for determination, and material fields, dates, and signatures must correspond item by item.
Configuration and implementation checks
This step is executed by the connection configuration of the deployment environment (server side), not by the capability of a model node, and outputs whether the connection is available (service startup result and connection logs). "Handover-ready deployment status and operation records" are then completed by deployment handover and subsequent business processing. The primary business database, log database, cache, and vector database can point to different instances respectively; if the log database is not configured separately, it reuses the primary database.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | The license number, publishing entity name, business scope, validity start and end dates, and issuance date must be consistent with the corresponding fields in the annual verification form | Check the number, name, and dates item by item against the original license and the verification form, and check whether signatures and receipts are complete |
| Annual verification form | The verification year, publishing entity information, publishing activity details, legal representative signature, and submission date must be consistent with the corresponding records in the rectification report | Check the year, name, quantity, and dates page by page, and check whether the signature field and receipt are missing items |
| Rectification report | The rectification items, rectification measures, completion date, and responsible party signature must correspond one-to-one with the issues listed in the verification form | Compare rectification items and completion dates one by one according to the issue list, and check the responsible party signature and receipt |
| Primary business database connection variable | It points to the primary business database actually in use and can be connected, and its value is consistent with the database address | In the deployment environment, check that the variable value is consistent with the database address, and check the connection result in the startup logs |
Three common errors
- Symptom: The publishing entity name and validity dates of the same record do not match between the license and the verification form. Cause: The two materials were filed at different points in time and were not updated synchronously under the same version.
- Symptom: The quantity and completion dates are inconsistent between the annual verification form and the rectification report. Cause: The rectification report was finalized before the verification form, and the corresponding fields in the verification form were not backfilled afterward.
- Symptom: The handover form is missing the legal representative signature or receipt. Cause: The signature pages were not fully collected during the material circulation stage, and the checklist was not checked item by item during handover.
How to verify the setup
Acceptance for this function: connect once each to the primary business database, log database, cache, and vector database, check the connection results in the startup logs, and check that the values of the three connection variables MONGODB_URI, REDIS_URL, and PG_URL are consistent with the instance addresses.
Business test: check once item by item according to the handover form, see which record is missing, and focus on checking whether the fields, dates, and signatures of the license, verification form, and rectification report are complete.
- In the deployment environment, check that the value of the primary business database connection variable is consistent with the database address, and check the connection result in the startup logs and the database to which logs are written.
- Use a client to connect once to the cache instance and check the response, check the selected vector database and address against the deployment instructions, and check whether the handover form signatures and receipts are complete.