What this category's data looks like
Vocational school student internship management materials include internship agreements, internship plans, and internship logs; together, the three constitute a verifiable source of deployment status and operation records. The internship agreement contains the organization name, position, start and end dates, and signature fields; the internship plan contains the batch, week number, tasks, and supervising instructor; the internship log contains the date, position, work content, and signed receipt. Materials are updated by batch: before each internship round, the agreement and plan are synchronized, and during the internship, logs are filled in daily. When entering the knowledge base retrieval and recall function, the agreement and plan serve as candidate retrieval sources, while the log serves as item-by-item comparison material. The fields and dates of all three need to be locatable in the candidate snippets, so that subsequent nodes or manual work can generate a handover-ready deployment status and operation records.
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 mode, merge, re-rank, filter, and limit trimming). The "handover-ready deployment status and operation records" are then completed by subsequent nodes or manual work.
| Object | Check | Verification action |
|---|---|---|
| Internship agreement | The organization name, position, start and end dates, and signature fields need to match the internship plan | In the search test, use the organization name and position as the query, check whether the candidate snippets hit both the agreement and the plan, and record the number of candidates and the score |
| Internship plan | The batch, week number, tasks, and supervising instructor need to be consistent with the log dates | Switch searchMode to hybrid, compare semantic and full-text candidates, and see whether the plan week number and log date fall in the same candidate snippet |
| Internship log | The date, position, work content, and signed receipt need to be verifiable item by item | Use the log date and position as the query, compare the ranking of the top few items before and after enabling usingReRank, and confirm that key passages have not been trimmed |
| Retrieval parameters | After similarity filtering and citation limit trimming, key original passages are still retained | Adjust similarity and limit, record the number of candidates and the score, and record the citation text tokens separately; do not compare array length and budget |
Three common errors
- Symptom: For the same record, the organization name, number of positions, and dates in the agreement and plan do not match. Cause: The two material versions were not synchronized, the retrieval candidates hit only one of them, and no field-by-field comparison was performed.
- Symptom: The log dates and plan week numbers are misaligned, and signatures or receipts are missing. Cause: The material update cadence is inconsistent, the old plan version is still among the candidate sources, and filtering and checking for the receipt field are lacking.
- Symptom: The same question cannot be recalled when rephrased, and although there are many candidates, the ones ranked at the top are all irrelevant. Cause: The retrieval mode does not match the material form, re-ranking was not enabled, or the similarity filter threshold is set improperly.
How to verify the setup
Acceptance for this function: test once each with synonym-rewritten queries, compare candidates and scores, then toggle re-ranking on and off to inspect the ranking of the top few items; switch searchMode and usingReRank, record the number of candidates and the score, and check the impact of similarity and limit on the results.
Business test: check item by item against the handover form to see which record is missing; compare whether the version, connection, and task records are consistent, and confirm that the fields, dates, and signatures of the agreement, plan, and log can all be located.
- In the knowledge base search test, switch
searchModeand retrieve the same query in semantic, full-text, and hybrid modes respectively, record the number of candidates and the score, and compare the ranking of the top few items. - Enable and disable
usingReRank, adjustsimilarityandlimit, check the citation text tokens and the number of candidates, and inspect item by item whether the fields, dates, and signatures of the agreement, plan, and log are complete.