What this category's data looks like
In the journal publication license and annual verification scenario, materials fall into three categories: the original and copy of the journal publication license, the annual verification form, and the rectification report. The sources are issuance by the publishing administrative department and filing by the publishing unit, and the update cadence rolls forward according to the annual verification cycle and rectification deadlines. Field characteristics center on journal name, journal number, sponsoring unit, publishing unit, legal representative, verification year, signature, and receipt date. The license plays the role of subject qualification and licensed scope, the annual verification form plays the role of annual operating and publishing data declaration, and the rectification report plays the role of explaining problem items and completion status. After the three material categories enter the file-level permission system, the visible scope is filtered member by member, and the discrepancy list is generated by comparison within the visible set, used to locate fields whose names, quantities, or dates do not match for the same record across two materials.
Configuration and implementation checks
Enable commercial file permissions and give the member read access to the knowledge base.
This step is executed by member permissions and file-level permissions (server-side authentication), outputting the visible file set filtered by member. The "discrepancy list" is completed afterward by subsequent AI nodes, code nodes, or manual work; the file list and retrieval only return the readable set filtered by member.
| Object | Check | Verification action |
|---|---|---|
| Journal publication license | Fields, dates, and signatures: journal name, journal number, sponsoring unit, legal representative, validity period, and issuance date must match the corresponding items in the annual verification form | Use a restricted member account to view the list and details, check the license fields against the ledger registration items, mark inconsistent fields, and record teamId |
| Annual verification form | Fields, dates, and signatures: verification year, publishing unit, quantity metrics, and signature receipt must match the corresponding items in the license and rectification report | Search the same journal name with authentication by member identity, check the annual verification form quantities and dates, compare the rectification report receipt, and record tmbId |
| Rectification report | Fields, dates, and signatures: problem items, rectification completion date, and signature receipt must match the conclusion of the annual verification form | Use the creator account to confirm the deletion permission boundary, use a collaborator account to attempt deletion, which should be filtered and prompted, and check whether the report signature and receipt are complete |
| File-level permission | Filtered item by item by member: viewing the list and details requires knowledge base read permission plus file read permission, and retrieval is filtered by the files readable by the current member | Use a restricted member account to search the same issue, check that unauthorized files are not recalled, and check the authentication configuration of the workflow and nodes |
Three common errors
- Symptom: the name, quantity, or date of the same record does not match between the license and the annual verification form. Cause: the two materials are filed separately, no field-level comparison is performed, and discrepancies are not exposed before write-back.
- Symptom: the rectification report version is not synchronized, and the receipt date is inconsistent with the conclusion of the verification form. Cause: under file-level permissions the visible sets differ, members each hold an old version, and retrieval is not uniformly filtered by member identity.
- Symptom: the annual verification form lacks a signature or receipt but still enters the discrepancy list. Cause: material verification does not cover the signature and receipt fields, and deletion and modification permissions are not validated according to the creator and collaborator boundaries.
How to verify the setup
This feature's acceptance: use a restricted account to view the list and perform one retrieval, check that the visible scope contains only files for which that member has read permission, that unauthorized files do not occupy a place and are not recalled, and that paginated results are correct.
Business test: use one real record to find fields inconsistent with the ledger, check names, quantities, dates, and signature receipts, record the discrepancies, and write back after confirmation by the reviewer.
- Use a restricted member account to view the file list and details, check whether the returned set is filtered item by item by member, and confirm that unreadable files do not occupy a place.
- Use a collaborator account to attempt to delete a file, check that only the creator can delete, and that non-creator items are filtered and prompted.