What this category's data looks like
The materials in the compulsory education dropout prevention and control category mainly include three types: dropout risk ledgers, persuasion-to-return records, and home visit records. The dropout risk ledger records students' basic information, risk level, determination date, and responsible person's signature; the persuasion-to-return record records the persuasion time, method, participating personnel, and parent receipt; the home visit record registers the home visit date, visit target, communication content, and signatures of both parties. When these materials enter the knowledge base retrieval node, each plays a different role: the risk ledger provides student identity and the basis for risk determination, the persuasion-to-return record provides process evidence and receipt status, and the home visit record supplements family communication details and the signature chain. In terms of update rhythm, ledgers are created centrally at the beginning of the semester, dynamically appended during the semester along with persuasion-to-return and home visits, and versions are uniformly reviewed at the end of the semester. Field characteristics are concentrated in four categories: name, quantity, date, and signature. For the same student across different materials, inconsistencies are likely to appear in name spelling, number of persuasion-to-return instances, home visit dates, and signature completeness. A version ledger and change records are needed to lock the current version, retain old versions for traceability, and keep citation sources updated in sync.
Configuration and implementation checks
This link is executed by the citation output of the knowledge base retrieval node, which outputs an array of citation content, each containing an original text snippet and a source identifier, and the length can be 0. The "version ledger and change records" are completed subsequently by AI nodes, code nodes, or manual work.
| Object | Check | Verification action |
|---|---|---|
| Dropout risk ledger | Whether the risk level, determination date, and responsible person's signature are consistent with the persuasion-to-return record and home visit record | Check the same student's name spelling, risk level, determination date, and signature field, compare the three materials, and then register the version number |
| Persuasion-to-return record | Whether the number of persuasion-to-return instances, persuasion dates, and parent receipt match the home visit record | Compare the persuasion time, participating personnel, and receipt signature item by item, and confirm that the old version is traceable and citations are synchronized |
| Home visit record | Whether the home visit date, visit target, and signatures of both parties are consistent with the risk ledger and persuasion-to-return record | Check the date order, signature completeness, and missing receipt items, record changes, and update the knowledge base |
| Citation content array | Whether each citation can point back to the original paragraph, and whether the array length matches the hit materials | Open the citation superscript to compare against the source document, and check quoteMaxToken and the quoteList field in responseData (non-streaming module results returned with detailed output enabled) |
Three common errors
- Phenomenon: The same student's name spelling and number of persuasion-to-return instances do not match between the risk ledger and the persuasion-to-return record. Cause: The two materials were entered separately, without field-level comparison and version synchronization.
- Phenomenon: The home visit record date contradicts the persuasion-to-return record date, and the old version is still cited. Cause: The knowledge base was not updated after the change, and the version ledger did not lock the current version.
- Phenomenon: The persuasion-to-return record lacks a parent receipt or the signature field is blank, yet the citation snippet appears complete. Cause: The material was stored before signatures were completed, and the correspondence between the citation and the original text was not verified.
How to verify the setup
This feature's acceptance: ask a question with an original-text basis, and check whether the citation array and superscript can point back to the original text; then ask a question with no matching material, confirm that the array is empty while the pipeline runs through, and check quoteMaxToken and the quoteList in responseData.
Business test: change one piece of content, see whether the version number and citations are updated in sync, and confirm that the current version is unique, the old version is traceable, and citations are synchronized.
- Open the citation superscript, compare item by item against the source document, check whether the original text snippet and source identifier are consistent, and record the array length.
- Check whether the vector models of the selected knowledge bases are the same, and check whether the search parameter values are consistent with the knowledge base retrieval section.