What this category's data looks like
This page addresses progress records and statistical reconciliation for journal publishing licenses and annual verification. Materials include journal publishing license, annual verification form, and rectification report. The license provides the entity name and scope of permission; the annual verification form provides annual records and quantities; the rectification report provides exceptions and receipts. When these three types of materials enter the database and operations functions, they respectively serve as the source of basic fields, the source of periodic records, and the source of exception explanations. The update cadence is summarized weekly or monthly, and field characteristics center on names, quantities, dates, signatures, and receipts. The progress table and statistical scope description need to align the record count with the statistical count, with the scope written in the header, and exceptions listed separately, to facilitate inclusion in weekly or monthly reports.
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. The output is whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is completed subsequently by deployment handover and follow-up business processing.
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | Fields, dates, and signatures must be consistent with the annual verification form | Compare the license with the annual verification form, check names, quantities, dates, and signatures, and confirm no missing items |
| Annual verification form | The names, quantities, and dates of the same record in the two materials must match | Compare the annual verification form with the rectification report item by item, mark inconsistencies, and record exceptions |
| Rectification report | The version must be synchronized and signatures or receipts must be complete | Check the rectification report version number and receipt, and confirm that the signature date is consistent with the license |
| Main business database connection variable | Points to the main business database actually in use and is connectable | In the deployment environment, check that the variable value matches the database address, and review the connection result in the startup logs |
Three common errors
- Symptom: The names, quantities, and dates of the same record in the license and the annual verification form do not match. Cause: The two materials were entered separately, without field-level comparison and scope unification.
- Symptom: The rectification report version is not synchronized, and the old version is still referenced. Cause: After the version update, the progress table was not written back, and the statistical scope is still calculated according to the old version.
- Symptom: The annual verification form lacks signatures or receipts, and the statistical total does not match the record count. Cause: Signatures and receipts were not included in the check items, and exceptions were not listed separately.
How to verify the setup
This feature acceptance: Connect once to the main business database, log database, cache, and vector database item by item, and check the connection results in the startup logs; check that the values of MONGODB_URI, REDIS_URL, and PG_URL are consistent with the deployment instructions.
Business test: Use one week of records to check the total, and see whether the scope and exceptions are clearly written; the number of quoted items is the array length, and quoteMaxToken is the budget for quoted content. The two are not compared for equality. If a quote upper limit is involved, check the tokens of the quoted text, and record the array item count separately.
- In the deployment environment, check the connection variable values of the main business database, log database, cache, and vector database, and review the connection results in the startup logs
- Use one week of records to check the total, verify whether the statistical scope and exceptions are written in the header, and confirm that the record count matches the statistical count