What this category's data looks like
This page focuses on the student awards, grants, loans, and hardship determination scenario, organizing three types of materials: the family financial hardship determination form, the scholarship and grant application form, and the loan receipt. These materials are usually updated by academic year or batch, and their fields involve student name, student ID, family size, income, determination level, application amount, loan amount, date, and signature. The family financial hardship determination form is used to determine the hardship level, the scholarship and grant application form is used for application and review, and the loan receipt is used to confirm loan disbursement and signature. After these three types of materials enter the knowledge base, each plays a different role: the determination form provides the basis for determination, the application form provides application information, and the receipt provides proof of disbursement and signature. The update rhythm of the materials is tied to batches, old versions must be traceable, and citations must be synchronized.
Configuration and implementation checks
This part is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible and whether data in the same group is merged). The "version ledger and change records" are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Family financial hardship determination form | Fields, date, and signature need to be verified; the determination level corresponds to family size and income | Check the name, student ID, determination level, signature, and date in the determination form, and confirm they are consistent with the application form |
| Scholarship and grant application form | Fields, date, and signature need to be verified; the application amount corresponds to the determination level | Check the name, student ID, application amount, signature, and date in the application form, and confirm they are consistent with the determination form |
| Loan receipt | Fields, date, and signature need to be verified; the loan amount corresponds to the receipt date | Check the name, student ID, loan amount, signature, and date in the receipt, and confirm they are consistent with the application form |
| Data row index fields | Multiple vector identifiers for one data row are all present; the index model is consistent with the vector model actually used by the knowledge base | Open a data row and check the index fields, view defaultToken, maxToken, and the index model, and confirm the status is indexed |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match across two materials. Inspect the following: the family financial hardship determination form and the scholarship and grant application form are updated separately, and the fields are not checked in sync.
- Symptom: versions are not synchronized, and the old version is still recalled. Inspect the following: after changing the model, rebuild is triggered only for data that has already been indexed, the old version data is not covered, and citations still point to the old version.
- Symptom: signature or receipt is missing. Inspect the following: the loan receipt is not updated with the batch, signature and date are missing.
How to verify the setup
Feature acceptance: sample one data row and look at the index fields, confirm that multiple vector identifiers are all present and the status is indexed; then retrieve once and see whether data in the same group is merged, with the vector score taking the highest score.
Business test: change one piece of content and see whether the version number and citations are updated in sync; if a citation limit is involved, check the tokens of the cited text, record the number of array entries separately, quoteMaxToken is the citation content budget and is not compared for equality with the number of array entries.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base, and view the data scope covered by the rebuild task and the rebuild task records.
- Open a data row and check the index fields, confirm
defaultToken,maxToken, and the status value indexed, and check whether data in the same group is merged.