What this category's data looks like
This page focuses on vocational school student internship management materials, including three types: internship agreements, internship plans, and internship logs. Agreements contain the organization name, position, start and end dates, signatures, and receipts; plans contain batch, week number, supervising instructor, and dates; logs contain daily records, position name, quantity, and signatures. Materials are archived by batch and updated on a rolling basis with the internship cycle, with versions anchored by signature dates and receipts. When entering knowledge base retrieval and recall, agreements serve as the authorization and responsibility source document, plans serve as the time and task framework, and logs serve as process evidence; each of the three material types provides traceable fields for locating original records during exception tracing and manual review.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate chunks and similarity scores (after pattern, merge, rerank, filter, and limit trimming). The exception list and review conclusions are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | Whether fields, dates, and signatures are consistent with the plan and logs | In the search test, search by organization name and position, verify the start and end dates, signatures, and receipts in the agreement, and record the number of candidates and scores |
| Internship plan | Whether batch, week number, and supervising instructor match the logs | Switch searchMode to hybrid, verify the batch and week number in the plan, and check whether the name, quantity, and date of the same record are consistent across the two materials |
| Internship log | Whether daily records, position name, and quantity are supported by original records | Compare the top few rankings before and after enabling usingReRank, check whether the log chunks contain signatures and dates, and record the similarity score |
| Exception list | Whether each exception is supported by original records and whether the reviewer has signed | For each candidate chunk, link back to the original text of the agreement, plan, or log one by one, confirm that the cited text tokens and array count are recorded separately, and after the reviewer signs, hand it over to the responsible person for handling |
Three common errors
- Phenomenon: The position name, quantity, and date of the same record do not match between the agreement and the log. Cause: The two materials are entered separately, and field-level back-linking verification was not performed.
- Phenomenon: The plan version is not synchronized, and old week numbers are still recalled. Cause: After updating, re-archiving was not performed according to signature dates and receipts.
- Phenomenon: The log lacks signatures or receipts, and the exception cannot be closed. Cause: Process materials were not collected completely by batch, and the reviewer cannot sign for confirmation.
How to verify the setup
Acceptance of this feature: Test once each with synonym-rewritten questions, compare candidates and similarity scores, then toggle usingReRank on and off to observe the top few rankings, and record the number of candidates separately.
Business test: Create an exception record, see whether it can be traced to the source material, and confirm that the original text of the agreement, plan, or log can be linked back.
- In the knowledge base search test, switch
searchModeand compare the candidate results of the three modes: semantic, full-text, and hybrid. - Verify the cited text tokens and array count, and check whether key original text chunks are still retained after
limittrimming.