What this category's data looks like
Journal publication licenses and annual verification involve three types of materials: the journal publication license, the annual verification form, and the rectification report. The license records the journal name, publication number, sponsoring unit, and validity period; the annual verification form summarizes publication status, personnel, and asset fields by year; the rectification report explains item by item the issues found during verification. The material sources are license decisions, annual submissions, and rectification receipts, and the update cadence is immediate for license changes, periodic for annual verification, and subject to the notification deadline for rectification. When entering the model access and configuration stage, the license and verification form serve as the baseline for field comparison, and the rectification report serves as the explanation of differences; together the three form a signable material draft and handover record, and dialogue and retrieval use this model to complete subsequent drafting and retrieval.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, which outputs the model binding relationships and channel responses. The signable material draft and handover record are then completed by dialogue and retrieval using this model. Models are divided into five categories: language, indexing, reranking, speech synthesis, and speech recognition, and different steps bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Fields, dates, and signatures must be consistent with the license decision; journal name, publication number, sponsoring unit, and validity period must correspond item by item | Compare the model name returned by the channel with the name listed in the document, and verify the type label, channel configuration, and key source |
| Annual verification form | The name, quantity, and date of the same record in the two materials must match; the version and date must be consistent | Compare the verification form and license fields item by item by year, record the number of array entries and the tokens of the referenced text, and do not compare the two as equal |
| Rectification report | If a signature or receipt is missing, it must not proceed to the next step; rectification items must correspond one by one to the issues in the verification form | Verify whether the signature and receipt are complete, and check the quoteMaxToken reference content budget and the maxContext context range |
| Model binding relationship | Must correspond to the step to be used; the retrieval step binds the indexing model, and the dialogue step binds the language model | Check the type label in the model configuration, and check whether the values of maxTokens and toolChoice meet the requirements of the step |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the license and the verification form. Cause: The two materials were drafted separately, and the fields were not compared against the same baseline.
- Symptom: The material versions are not synchronized, and the handover record and draft dates are inconsistent. Cause: The version number and issuance date were not unified after modification, and the receipt was not updated with the version.
- Symptom: Retrieval reports an indexing model-related error or authentication failure. Cause: The channel key is inconsistent with the connected service, and the model identifier does not match the name listed in the document.
How to verify the setup
This feature acceptance: run one dialogue and one retrieval, check the model identifier in the response, and confirm it is consistent with the name listed in the document; check whether the values of maxContext, maxTokens, quoteMaxToken, and toolChoice meet the requirements of the step.
Business test: draft one copy according to the template and complete one handover, and see whether missing items are blocked.
- Check the channel configuration and key source, confirm that the model identifier is consistent with the name listed in the document, and that the model type corresponds to the step to be used.
- Check the fields, dates, and signatures of the license, verification form, and rectification report, confirm that the version and date are consistent and the receipt is complete, and then hand it over to the next step for signing and acceptance.