What this category's data looks like
Materials for the deployment, operations, and application handover of vocational college skills competition organization come from three types of documents: competition regulations, registration forms, and training plans, which enter the knowledge base as versioned files and signed scanned copies. Competition regulation fields include event name, group, date, scoring criteria, and signature/seal; registration form fields include contestant name, student ID, event, advisor, and receipt signature; training plan fields include phase tasks, week number, venue, and responsible person's signature. The update cadence rolls forward across three nodes: pre-competition release, registration deadline, and weekly training reports. When the three types of materials enter the retrieval function, their roles differ: regulations provide the rule basis, registration forms provide clues for verifying personnel and quantities, and training plans provide process records. For the same record, the name, quantity, and date between the regulations and the registration form must be compared item by item; when versions are not synchronized or the signed receipt is missing, retrieval candidates can only serve as verification clues and cannot replace the handover form.
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 handover-ready deployment status and operation records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Competition regulations | Event name, group, date, and signature fields are complete and consistent with the corresponding items in the registration form | Search by event name in the search test, verify the name and date in the candidate snippets, and record the number of candidates and scores |
| Registration form | Contestant name, student ID, event, advisor, and receipt signature have consistent names and quantities across the regulations and training plan | Search once each using different phrasings of the same event name, compare whether the returned candidates include both semantic and full-text results, and check whether the signed receipt is missing any items |
| Training plan | Phase tasks, week number, venue, and responsible person's signature do not conflict with the regulation dates, and the version is synchronized | Switch searchMode to hybrid, enable usingReRank to compare the order of the top few results, and adjust similarity to see whether key snippets are retained after filtering |
| Deployment status record | Version, connection, and task records are consistent, and the handover form can be verified item by item | Verify once item by item against the handover form to see which record is missing; record the citation count separately, and count the tokens of the cited text separately |
Three common errors
- Symptom: the name or quantity of the same event does not match between the regulations and the registration form. Cause: the two materials are maintained by different personnel, versions are not synchronized, and retrieval candidates can only serve as verification clues.
- Symptom: the training plan lacks the responsible person's signature or receipt. Cause: process records were not archived in time, it cannot be confirmed at handover that the version has taken effect, and candidate snippets cannot replace the signed document.
- Symptom: key paragraphs cannot be recalled when the question is phrased differently. Cause: the retrieval mode does not match the material form, or key snippets are truncated after similarity filtering and citation upper-limit trimming.
How to verify the setup
This feature'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 results; at the same time switch searchMode, adjust similarity and limit, and record changes in the number of candidates and scores.
Business test: verify once item by item against the handover form to see which record is missing; record the citation count by array length, verify the tokens of the cited text separately, and do not compare them as equal to the count.
- In the search test, search once each for the same event name using two phrasings, record the number of candidates, scores, and returned snippets, and confirm whether both semantic and full-text results are included.
- Verify version, connection, and task records item by item against the handover form, list items missing signatures or receipts separately, and complete them before handing over to operations or the next shift.