What this category's data looks like
Graduate training process management centers on the training plan, the proposal report, and the mid-term assessment form. These three types of materials play different roles in material verification and discrepancy location: the training plan carries course and credit arrangements, the proposal report carries topic selection and argumentation, and the mid-term assessment form carries stage progress and conclusions. Material sources are mentor submission, training unit aggregation, and academic affairs archiving, with an update cadence that advances along semester milestones, and one concentrated round each for the proposal and the mid-term. Field characteristics center on name, quantity, date, and signature: the name, quantity, and date of the same record in two materials must be aligned item by item, and unsynchronized versions plus missing signatures or receipts often cause discrepancies. When materials enter this feature, the visible scope is first determined by member identity, then field comparison is performed within the visible file set to form a discrepancy list for the reviewer to confirm and write back to the ledger.
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 then completed by subsequent AI nodes, code nodes, or manual work; the file list and retrieval only return the readable set filtered by member, and team administrators do not bypass file-level permissions either.
| Object | Check | Verification action |
|---|---|---|
| Training plan | Name, quantity, date, and signature must be aligned item by item with the proposal report | Use a restricted member account under the same teamId to view the file list and details, and check the visible scope |
| Proposal report | Name, quantity, and date must be aligned item by item with the mid-term assessment form; a missing signature or receipt is listed as a discrepancy | Use the member account corresponding to tmbId to search the same question, and check whether unauthorized files are recalled |
| Mid-term assessment form | When versions are not synchronized, the latest written-back version prevails; inconsistent names and dates are marked separately | Use a collaborator account to try deleting a file, and check whether non-creators are filtered out and prompted |
| Discrepancy list | Only when the name, quantity, and date of the same record in two materials are consistent can it be submitted for review | Export the field comparison results according to the visible file set, and mark inconsistent fields |
Three common errors
- Symptom: a restricted member saw files they should not see. Cause: file-level permissions were not filtered item by item by member, and the list was not returned according to the current member's readable scope.
- Symptom: retrieval recalled unauthorized files. Cause: retrieval was not filtered by the current member's readable files, or authentication was not performed by member identity.
- Symptom: the name, quantity, and date of the same record in two materials do not match. Cause: versions were not synchronized, signatures or receipts were missing, and discrepancies were not written back to the ledger.
How to verify the setup
Feature acceptance: use a restricted account to view the list and perform one retrieval, check the visible scope, and confirm that unauthorized files do not occupy a place and are not recalled.
Business test: use one real record to find fields inconsistent with the ledger, and mark discrepancies in name, quantity, date, or signature.
- Check the member's readable file set by
teamIdandtmbId, and confirm that the list and retrieval results are consistent. - Write back the discrepancy list to the ledger item by item, and proceed to the next round of material verification only after the reviewer confirms.