What this category's data looks like
This category's data looks like this: The journal publishing license and annual verification scenario involves three types of materials: the journal publishing license, the annual verification form, and the rectification report. Sources are scanned originals of qualification documents, verification filing forms, and rectification statement receipts, with updates maintained on a rolling basis according to license renewal, annual verification cycles, and rectification deadlines. Field characteristics center on license number, publication period, sponsoring organization, verification year, verification conclusion, rectification items, signatures, and receipt dates. After materials enter parsing and chunking, the license and verification form assume the role of the current version for qualifications and annual conclusions, while the rectification report assumes the role of change explanation and receipt; the same record may show inconsistencies in name, quantity, and dates between the license and verification form, and when versions are not synchronized or signature receipts are missing, the differences need to be located to specific materials through data rows and index status.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The version ledger and change records are then completed by retrieval and subsequent processing; successful parsing does not equal a retrieval hit, and it is also necessary to see whether the index status has reached completed.
| Object | Check | Verification action |
|---|---|---|
| Journal publishing license | Check whether the license number, publication period, sponsoring organization, signature, and date are consistent with the verification form | Open the data row to check the status and confirm it is in one of parsed / indexing / indexed |
| Annual verification form | Check whether the verification year, verification conclusion, quantity, and date match the license and rectification report | Separately check the identity identifiers of the file record and the data row, and check the processing mode corresponding to trainingType |
| Rectification report | Check whether the rectification items, signature, and receipt date are complete and synchronized with the verification form conclusion | View the data rows covered by the rebuild task and confirm that only data with completed indexing is covered |
| File record and data row | The identities of the file record and the data row are kept separate, and the version number and references are updated synchronously | After changing one piece of content, check whether the chunks and references related to chunkSize and chunkSplitter are synchronized |
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 materials are maintained independently, versions are not synchronized, and there is no unified ledger for comparison.
- Symptom: The rectification report lacks a signature or receipt, and the annual verification conclusion cannot be closed. Cause: The pace of material collection and verification filing is disconnected, and signature receipts are not updated with the version.
- Symptom: Newly uploaded materials cannot be found. Cause: The data row is still in a pending-indexing state and does not participate in recall; the retrieval layer is naturally isolated, and it is necessary to wait for the index flow to complete.
How to verify the setup
How to verify the setup: Acceptance for this feature: upload one material, observe the status flow of the data row and the coverage scope of the rebuild task, and confirm that changing the model only rebuilds data with completed indexing.
Business test: change one piece of content, check whether the version number and references are updated synchronously, and confirm that the old version is traceable and the current version is unique.
- Open the data row to check the status, confirm it is consistent with the interface display, and separately check the identity identifiers of the file record and the data row.
- View the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and that pending-indexing data does not participate in the rebuild chain.