What this category's data looks like
This page focuses on the business basis query for primary and secondary school timetables and after-school service scheduling. The materials include the master timetable, teacher assignment table, and after-school service project table. The sources are the academic affairs office and grade groups, and the update cadence follows semester and monthly adjustments. Field characteristics include class, course name, teacher name, weekly class hours, date, signature, and receipt. When entering the model integration and configuration function, the master timetable is used to answer course arrangements and time slot distribution, the teacher assignment table is used to verify teaching assignments and class hour attribution, and the after-school service project table is used to confirm project names, number of participants, and dates. The three types of materials jointly support cross-material comparison. The model binding relationship determines whether the corresponding capability can be invoked, and the retrieval and dialogue stages complete the traceable output of basis entries.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, which outputs the model binding relationship and channel response. The "basis entries that can be traced back to the original text" are then completed by subsequent AI nodes, code nodes, or manual work. Models are divided into five categories: language, indexing, reranking, speech synthesis, and speech recognition. Different stages bind different model types.
| Object | Check | Verification action |
|---|---|---|
| Master timetable | Fields include class, course name, weekly class hours, date, and signature; the version must be the current one, and entries must match the original text | Check whether the same course name, weekly class hours, and date in the master timetable and teacher assignment table are consistent; check whether signatures and receipts are complete; in the model configuration, confirm that the indexing model type label is consistent with the model name returned by the channel |
| Teacher assignment table | Fields include teacher name, assigned class, class hours, and signature; the name, quantity, and date of the same record in the two materials must match | Compare the teacher names and class hour quantities in the teacher assignment table and the after-school service project table; check whether the versions are synchronized; check the channel configuration and key source, and confirm that the model identifier is consistent with the name listed in the documentation |
| After-school service project table | Fields include project name, number of participants, date, and receipt; missing signature or receipt is regarded as incomplete basis | Compare the project names and dates in the after-school service project table and the master timetable; check whether receipts are complete; in dialogue and retrieval, confirm that the number of quoted entries is recorded by array length, quoteMaxToken is checked separately as the quoted content budget, and maxContext and maxTokens are checked according to the stage labels |
| Model configuration | The model type corresponds to the stage to be used, and the channel and key are consistent with the integrated service | In the model configuration, check the type label; check the channel configuration and key source; compare with the model name returned by the channel; confirm that toolChoice matches the current stage |
Three common errors
- Symptom: The name or weekly class hours of the same course do not match between the master timetable and the teacher assignment table. Cause: The two materials were not updated synchronously, and the versions were not synchronized, so the basis entries cannot be traced back to the same original text.
- Symptom: The date in the after-school service project table is inconsistent with the master timetable, and signatures or receipts are missing. Cause: The materials have different update cadences, receipts were not archived, and the basis entries are incomplete.
- Symptom: Retrieval reports an indexing model-related error or authentication failure. Cause: The model type does not match the stage, or the channel key is inconsistent with the integrated service; after switching models, the answer style changes abruptly.
How to verify the setup
Acceptance for this function: run one dialogue and one retrieval, check the model identifier in the response, and confirm it is consistent with the name listed in the documentation; check that the number of quoted entries is recorded by array length, quoteMaxToken is checked separately as the quoted content budget, and maxContext, maxTokens, and toolChoice are checked according to the stage labels.
Business test: ask a cross-material basis question, see whether the answer provides traceable sources, and check that the sources match the original text of the master timetable, teacher assignment table, or after-school service project table.
- Check the fields, dates, and signatures of the master timetable, teacher assignment table, and after-school service project table, and confirm that the name, quantity, and date of the same record in the two materials match.
- In the model configuration, check that the model type corresponds to the stage to be used, check the channel configuration and key source, and compare with the model name returned by the channel.