What this category's data looks like
This category's data typically includes course filing forms, study certificates, and credit hour recognition forms. The course filing form records the course name, course number, filing date, and responsible person's signature; the study certificate records the learner's name, course name, study start and end dates, number of credit hours, and the issuing unit's seal; the credit hour recognition form records the recognition conclusion, recognition date, and the signatures of the handler and reviewer. The three types of materials are updated by batch or year, and fields must be cross-consistent: the name and number of the same course in the filing form and the study certificate should be the same, the number of credit hours in the study certificate should correspond to the conclusion in the recognition form, and the date chain should be traceable from the study start and end dates to the recognition date. When the materials enter the knowledge base retrieval and recall function, each serves as a candidate fragment source, used for subsequent nodes or manual drafting of signable material drafts and handover records, and to support verification of responsible persons, versions, and dates.
Configuration and implementation checks
This step is executed by the knowledge base retrieval service (retrieval node and search test), outputting candidate fragments and similarity scores (after pattern, merge, rerank, filter, and limit trimming). The signable material drafts and handover records are completed by subsequent nodes or manually.
| Object | Check | Verification action |
|---|---|---|
| Course filing form | Fields complete: course name, course number, filing date, responsible person's signature; dates and signatures must be consistent with the study certificate and credit hour recognition form | In the knowledge base search test, switch searchMode to semantic, full-text, or hybrid, search the same course name separately, record the number of candidates and the similarity score, and check whether the filing date and signature fields appear in the candidate fragments |
| Study certificate | Fields complete: learner's name, course name, study start and end dates, number of credit hours, issuing unit's seal; name and quantity must be consistent with the course filing form and credit hour recognition form | Search once each with synonym-rewritten questions, compare the number of candidates and scores; compare the order of the first few results before and after enabling usingReRank, and check whether the number of credit hours and study start and end dates are returned completely |
| Credit hour recognition form | Fields complete: recognition conclusion, recognition date, handler's and reviewer's signatures; version and date must be synchronized with the course filing form and study certificate | Search the recognition conclusion and recognition date, check whether the candidate fragments contain the handler's and reviewer's signature fields; adjust limit to observe changes in the number of citations, separately record the array length and citation text tokens, and check version and date consistency |
| Handover record | Fields complete: handover material name, handover date, signatures of the handover person and receiver, receipt; missing signatures or receipts must be blocked | Draft a handover record according to the template, search relevant material fragments to check the name, quantity, and date; complete one handover and confirm whether the process blocks when signatures or receipts are missing |
Three common errors
- Symptom: The name and number of the same course do not match between the course filing form and the study certificate. Cause: When drafting, the same record was not used as the anchor, and the retrieved candidate fragments were not cross-checked by field.
- Symptom: The number of credit hours in the study certificate is inconsistent with the conclusion in the credit hour recognition form. Cause: The two materials were drafted separately, versions were not synchronized, and the quantity and date were not checked during handover.
- Symptom: The handover record lacks the signature of the handover person or receiver, or lacks a receipt. Cause: The handover step did not check item by item according to the template, and the candidate fragments returned by retrieval did not cover the signature and receipt fields.
How to verify the setup
This function's acceptance: test once each with synonym-rewritten questions, compare the number of candidates and similarity scores, then toggle usingReRank on and off to see whether the order of the first few results changes; switch searchMode to observe differences in candidate sources.
Business test: draft one according to the template and complete one handover, and see whether missing items are blocked.
- In the knowledge base search test, search the same course name in semantic, full-text, and hybrid modes respectively, record the number of candidates and scores, and check whether the returned fragments contain the course name, number, date, and signature fields.
- Search once each with rerank enabled and disabled, compare the order of the first few results; after adjusting the citation limit, separately record the array length and citation text tokens, and check whether the key fragments are still complete.