What this category's data looks like
This page is intended for primary and secondary school admissions organizations and, centered on three types of materials—admission plans, application material checklists, and admission lists—outlines their business basis lookup scenarios. An admission plan contains the school district scope, application conditions, time nodes, and signature fields; an application material checklist lists fields such as household registration, property, and residence permit, as well as receipt requirements; an admission list records student names, admission batches, publicity dates, and review signatures. The three types of materials are updated by academic year or batch, and the version is determined by the document date and seal. When entering this function, the admission plan serves as the primary basis text, the application material checklist serves as the field verification worksheet, and the admission list serves as the result comparison object; together, the three support cross-material basis lookup and item output that points back to the original text.
Configuration and implementation checks
This step is executed by the index service and the vector database, outputting vectors and index status (whether recall is possible and whether data in the same group is merged). The basis items that can point back to the original text are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials). The index model must be consistent with the vector model actually used by the knowledge base, and the index field of a data row must record multiple vector identifiers for that piece of data.
| Object | Check | Verification action |
|---|---|---|
| Admission plan | The fields include the school district scope, application conditions, time nodes, and signature fields, and the date and batch version must be current | Check the index model in the knowledge base settings, open an admission plan data row, and verify whether the index field records multiple vector identifiers |
| Application material checklist | The fields include items such as household registration, property, and residence permit, as well as receipt requirements, and the quantity and names must be consistent with the admission plan | Open an application material checklist data row and check the index field, then run a retrieval to see whether data in the same group is merged |
| Admission list | The fields include student names, admission batches, publicity dates, and review signatures, and signatures and receipts must not be missing | View the data scope covered by the rebuild task, and confirm that after changing the model, rebuilds are triggered only for data that has already been indexed |
| Data row | Multiple vector identifiers for one piece of data are all present, and the status is indexed or is in the rebuild task record | Open a data row and check the index field, and also check limit, and the tokens of the cited text |
Three common errors
- Symptom: the name, quantity, or date of the same record does not match between the admission plan and the admission list. Inspect the following: the versions of the two materials are not synchronized, and old batch fields were not updated with the new plan.
- Symptom: the application material checklist is missing a signature or receipt, but retrieval can still recall that item. Inspect the following: the index only records vector identifiers and does not verify whether the signature and receipt fields are complete.
- Symptom: after changing the model, recall quality decreases, and a data row has content but cannot be retrieved. Inspect the following: the rebuild task is triggered only for data that has already been indexed, and the index field of data rows not covered is empty.
How to verify the setup
This function's acceptance check: sample a data row and look at the index field to confirm that multiple vector identifiers are all present and the status is indexed or is in the rebuild task record; then run a retrieval once to see whether data in the same group is merged and whether the vector score takes the highest score.
Business test: ask a cross-material basis question, for example whether a student's application conditions and admission batch are consistent, and see whether the answer gives a citation that can be pointed back to, and check that the number of cited items is the array length and the tokens of the cited text under the constraints of limit.
- Check in the knowledge base settings whether 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.
- Open a data row and check the index field to confirm that multiple vector identifiers are all present and the status is indexed or is in the rebuild task record.