What this category's data looks like
This page is for the course selection, scheduling, and classroom resource allocation category, covering three types of materials: course offering plans, scheduling tables, and course selection rules. The sources are tables and approval documents exported from the academic affairs system, with an update cadence of centralized release before the semester and incremental revision during the semester based on course change forms. When the materials enter the vector model and index feature, the course offering plan serves as the original basis for course and class fields, the scheduling table serves as the original basis for time, classroom, and teacher fields, and the course selection rules serve as the original basis for course selection conditions, capacity, and priority fields. Each of the three types of materials enters the business database in the form of data rows, and the index field records its corresponding vector identifier. During retrieval, vectors are first recalled and then merged back with the original data, and the highest score is taken for the same group of data, thereby providing traceable original-text support for cross-material basis queries.
Configuration and implementation checks
This part is executed by the index service and the vector database, outputting vectors and index status (whether recall is possible and whether the same group of data is merged). "Basis entries that can be traced 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).
| Object | Check | Verification action |
|---|---|---|
| Course offering plan | Fields, dates, and signatures must match the scheduling table and course selection rules; the version must be the current version | Open a data row and check the index field to confirm that multiple vector identifiers are all present; check the course name, class count, release date, and approval signature in the course offering plan, and compare them item by item with the scheduling table; for status values, only indexed and rebuild task records are recognized |
| Scheduling table | Time, classroom, and teacher fields must be consistent with the course offering plan; course change forms must have receipts | View the data scope covered by the rebuild task and confirm that after changing the model, only data that has completed indexing is triggered; check the scheduling table dates and signatures, and compare them with the course change form receipts; check the budget of limit in the cited text |
| Course selection rules | Course selection conditions, capacity, and priority fields must be consistent with the course offering plan; when the version is not synchronized, they must not be used as a basis | Check the capacity and priority fields in the course selection rules and compare them with the corresponding records in the course offering plan; check whether the rule version number and release date are consistent with the current version; the number of citations is the array length, and quoteMaxToken is the citation content budget; the two are not compared for equality |
| Data row index field | Multiple vector identifiers for one piece of data are all present, and the same group of data can be merged | In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base; retrieve once to see whether the same group is merged; for status values, only indexed and rebuild task records are recognized |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the name, quantity, and date of the same record do not match across the two materials, and the index field has not merged the same group of data.
- Symptom: recall quality drops after changing the model. Inspect the following: the version is not the same, and data rows that have not completed indexing do not participate in recall; indexing must be completed first, then rebuild.
- Symptom: a data row has content but cannot be retrieved. Inspect the following: materials lacking signatures or receipts have not entered the current version, and the index field is missing the corresponding vector identifier.
How to verify the setup
This feature's acceptance check: sample a data row and look at the index field to confirm that multiple vector identifiers are all present; then retrieve once to see whether the same group is merged; for status values, only indexed and rebuild task records are recognized; check that the index model is consistent with the vector model actually used by the knowledge base.
Business test: ask a cross-material basis question and see whether the answer gives a traceable source; the number of citations is the array length, and quoteMaxToken is the citation content budget; the two are not compared for equality; when citation limits are involved, check the tokens of the cited text, and record the array count separately; limit are used for checking the cited text budget.
- In the knowledge base settings, check the index model and confirm that it is consistent with the vector model actually used by the knowledge base; open a data row and check the index field to confirm that multiple vector identifiers are all present.
- View the data scope covered by the rebuild task and confirm that after changing the model, only data that has completed indexing is triggered; check the fields, dates, and signatures of the course offering plan, scheduling table, and course selection rules, and compare whether the name, quantity, and date of the same record are consistent.