What this category's data looks like
This category's data involves three types of materials: internship agreements, internship plans, and internship logs. Sources are the academic affairs system, the internship management platform, and paper-signed receipts. The update cadence is batch-based and monthly aggregation. Fields include student name, position name, start and end dates, mentor signature, and parent receipt. When entering the knowledge base retrieval and recall function, the internship agreement serves as the authorization basis and the draft for determining the externally visible scope, the internship plan serves as the reference for batch and position matching, and the internship log serves as the process record and anomaly clue. The three types of materials respectively assume the roles of authorization boundary, batch verification, and process traceability. During retrieval, candidate snippets are recalled by material type and field combinations, for subsequent nodes or manual generation of external entry points and authorization scope.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate snippets and similarity scores (after pattern, merge, rerank, filter, and upper-limit trimming). The externally available entry points and authorization scope are then completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Check the student name, position name, start and end dates, and signature receipt in the agreement, and compare them item by item with the same-named fields in the internship plan | In the knowledge base search test, search by name plus position as conditions, record the number of candidates and scores, and check whether the candidates cover the key snippets of the agreement after switching searchMode |
| Internship plan | Check the batch, number of positions, start and end dates, and mentor signature in the plan, and keep them consistent with the dates and position names in the internship log | Search by batch number or position name, check whether the candidates include both plan and log snippets, record the number of candidates and scores, and confirm that snippets without signatures or receipts are not recalled |
| Internship log | Check the date, position name, mentor signature, and parent receipt in the log, and mark inconsistencies when the dates, names, or quantities do not match the agreement and plan | Search by date range plus position name, compare the order of the top few items before and after enabling rerank, record the number of candidates and scores, and check the impact of usingReRank and similarity on the results |
Three common errors
- Symptom: The position name and start and end dates for the same student do not match between the agreement and the plan. Cause: The two materials were entered in different batches, versions were not synchronized, and the snippets recalled during retrieval were not compared at the field level.
- Symptom: The internship log lacks a mentor signature or parent receipt but still appears in the candidate snippets. Cause: The signature and receipt fields were not validated during material aggregation, and retrieval filtering only trims by similarity without checking signature status.
- Symptom: The quantity or dates of the same record are inconsistent across the agreement, plan, and log, and the externally visible scope shifts accordingly. Cause: The authorization basis is taken from the agreement, while the plan and log are not updated in sync, and the sources of recalled snippets are mixed.
How to verify the setup
This function's acceptance: test once each with synonym-rewritten questions, compare candidates and scores, then toggle rerank on and off to observe the ordering of the top few items; record the number of candidates and scores, record the tokens of the cited text separately, and do not compare the number of array items with the citation budget as equal.
Business test: access once with a restricted identity, check whether the visible scope matches the setting, and that unauthorized content is not visible; verify the actual behavior of searchMode, usingReRank, similarity, and limit in the retrieval node and search test.
- In the knowledge base search test, switch
searchMode, compare the number of candidates and scores across the semantic, full-text, and hybrid modes, and confirm that the material form matches the mode. - Enable and disable
usingReRank, compare the order of the top few candidates, and adjustsimilarityandlimitto check whether key snippets are retained after similarity filtering and citation upper-limit trimming.