What this category's data looks like
This page addresses the journal publishing license and annual verification scenario; materials include journal publishing licenses, annual verification forms, rectification reports, and multilingual attachments. The license contains the permitted scope, validity period, and the issuing authority's seal; the annual verification form contains annual data, personnel, and publishing information; the rectification report contains the problem description, rectification measures, and receipt signature. Materials are a mix of scanned copies and spreadsheets, updated by year and batch, with fields covering names, quantities, dates, signatures, and receipts. After multilingual materials enter parsing and chunking, each takes on a different role: the license and verification form serve as the primary record sources, the rectification report serves as supplementary and back-reference evidence, and the terminology glossary and comparison draft are generated by subsequent retrieval and processing steps.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), outputting data rows and index status (parsed, indexing, indexed). "Unified terminology glossary and comparison draft" is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | Whether the fields, dates, and signatures are consistent with the annual verification form | Check the license name, quantity, validity period, and issuing authority's seal against the same items in the annual verification form; check whether the data row status is parsed or indexed, and confirm that the terminology context remains complete after chunkSize splitting |
| Annual verification form | Whether the name, quantity, and date of the same record match across the two materials | Compare item by item the name, quantity, and date in the annual verification form against the license and rectification report; check whether signatures and receipts are complete; check whether the data row status transitions from indexing to indexed |
| Rectification report | Whether versions are synchronized and missing signatures or receipts are completed | Check the rectification report version number and receipt signature, and confirm consistency with the annual verification form record; check whether terminology can be traced back to the source text after chunkSplitter chunking; check whether the rebuild task covers only indexed data |
| Multilingual terminology comparison draft | Whether the same term is written consistently throughout and whether the translated name can be traced back to the source text | Extract three terms and check their spelling throughout; check the data rows under the processing mode corresponding to trainingType; confirm that data pending indexing does not participate in recall, that the tokens of cited text are recorded separately, and that the number of citations is checked by array length |
Three common errors
- Symptom: newly uploaded materials cannot be found. Cause: the data row is in parsed or indexing, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Symptom: the name, quantity, and date of the same record do not match across the two materials. Cause: versions are not synchronized, and the license and annual verification form are updated in different batches.
- Symptom: empty data rows remain after a training failure. Cause: missing signatures or receipts interrupt parsing, and the data row does not complete the index transition.
How to verify the setup
This feature's acceptance: upload one material and observe the data row status transitions and the coverage scope of the rebuild task. Check whether the three states parsed to indexing to indexed are consistent with the interface, whether rebuilding with a different model covers only indexed data, and whether data pending indexing does not participate in recall.
Business test: extract three terms and check whether their spelling is consistent throughout. Check whether the translated name can be traced back to the source text, that the tokens of cited text are recorded separately, and that the number of citations is checked by array length.
- Open the data rows to check the status, confirm that the three states are consistent with the interface display, and check the file records and data row identifiers separately.
- View the data rows covered by the rebuild task, confirm that it covers only data whose indexing is completed, and that the initial training covers data pending indexing and data being indexed.