What this category's data looks like
For the pre-departure training and overseas safety reminders category, materials include pre-departure training courseware, safety reminder checklists, and accommodation contact forms. Courseware fields include topic, class hours, and terminology definitions; checklist fields include risk items, handling steps, and contacts; contact form fields include accommodation name, address, check-in date, signature, and receipt. Sources are the international offices and program offices of each school, with updates rolling by semester and batch, and versions often running in parallel. The same record having mismatched names, quantities, and dates across two materials, versions not being synchronized, and missing signatures or receipts are common inconsistencies. When materials enter this feature, the courseware and checklists provide terminology source sentences, and the contact forms provide entity fields; together the three form the input for multilingual materials and terminology processing, for use by the vector model and the indexing step.
Configuration and implementation checks
This step is executed by the indexing service and the vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). The "unified terminology glossary and comparison draft" is then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | The same term is consistent throughout, and the translated name can refer back to the source text | Sample three terms and check whether their written form is consistent throughout the courseware, and verify the terminology definitions and whether the translated names refer back |
| Safety reminder checklist | The same record has mismatched names, quantities, and dates across two materials | Compare the checklist with the courseware, verify whether risk item names, quantities, and dates are consistent, and verify signatures and receipts |
| Accommodation contact form | Versions are not synchronized, signatures or receipts are missing | Verify the contact form version number and batch, and verify whether the check-in date, signature, and receipt fields are complete |
| Data row index fields | Multiple vector identifiers for one data item are all present | Open a data row and verify the index fields, and verify the values of defaultToken and maxToken |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the same group of source data corresponds to multiple vectors, and after recall they are not merged by identifier, and the highest score is not taken.
- Symptom: recall quality drops after changing models. Inspect the following: rebuilding is triggered only for data that has already been indexed, does not cover all data rows, and the indexing model is inconsistent.
- Symptom: the same record has mismatched names, quantities, and dates across two materials. Inspect the following: versions are not synchronized, signatures or receipts are missing, and the terminology glossary and comparison draft are not unified.
How to verify the setup
Acceptance for this feature: sample one data row and inspect the index fields, then run a retrieval once to see whether the same group is merged; verify the status value indexed and the rebuild task records, and verify limit, and the tokens of the cited text, recording the array count separately.
Business test: sample three terms and check whether their written form is consistent throughout, verify that translated names can refer back to the source text, and verify whether signatures and receipts are complete.
- In the knowledge base settings, verify that the indexing model is consistent with the vector model actually used by the knowledge base, and check the data scope covered by the rebuild task.
- Open a data row and verify the index fields, confirm that multiple vector identifiers are all present, and after retrieval verify whether data in the same group is merged and whether the highest score is taken.