What this category's data looks like
This page addresses district and county teaching research activities and lesson observation and evaluation scenarios. Material sources include three types: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Notices contain activity theme, time, location, participating subjects, and personnel scope; lesson observation records contain the teaching teacher, class, lesson topic, observation points, and classroom transcript; lesson evaluation minutes contain speaking points, improvement suggestions, signatures, and receipts. When these three types of materials enter the model access and configuration stage, notices and minutes serve as terminology sources, lesson observation records serve as the context in which terminology appears, and the unified terminology table and comparison draft are completed in the subsequent dialogue and retrieval stages. The material update rhythm advances with the semester's teaching research schedule. The same activity may produce multiple records, and dates, names, and quantities need to be aligned across materials. In terms of field characteristics, notices are mainly based on dates and personnel scope, lesson observation records are mainly based on lesson topics and observation items, and lesson evaluation minutes are mainly based on suggestion items and signature receipts. Multilingual materials and terminology handling need to keep translated names traceable back to the original text after model binding.
Configuration and implementation checks
This step is executed by the server-side model channel configuration, outputting model binding relationships and channel responses. The "unified terminology table and comparison draft" is completed subsequently by 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. During configuration, it is necessary to verify that the channel and key source, model identifier, and the name listed in the documentation are consistent.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Dates and participating personnel scope need to correspond to lesson observation records and lesson evaluation minutes; the same activity name must be consistent throughout | Verify whether the notice date and minutes date come from the same source, verify the writing of the activity name, and verify whether the participating personnel scope corresponds to the class and subject in the lesson observation records |
| Lesson observation record | Lesson topic name, teaching teacher, and class need to be traceably consistent with the lesson evaluation minutes; translated names must be traceable back to the original text | Compare the lesson topic and teacher writing in the lesson observation records and lesson evaluation minutes, verify whether multilingual translated names can be traced back to the original text, and verify whether record versions are synchronized |
| Lesson evaluation minutes | Signatures and receipts are complete; suggestion items correspond to the observation items in the lesson observation records, with consistent quantities | Verify whether signatures and receipts are complete, verify whether the number of suggestion items is consistent with the number of observation items in the lesson observation records, and verify whether the minutes version is synchronized with the notice |
| Model configuration | Model type corresponds to the stage in which it will be used; model identifier is consistent with the name listed in the documentation | In the model configuration, verify the type label, verify the channel configuration and key source, compare the model name returned by the channel, and when citation budget is involved, verify quoteMaxToken and the tokens of the quoted text, recording the array length separately |
Three common errors
- Symptom: The same lesson observation record has different lesson topic name writings in the notice and the minutes. Cause: Multilingual translated names are not unified, and the terminology table is not synchronized across materials.
- Symptom: The lesson evaluation minutes lack signatures or receipts, and the dates in the notice and minutes do not match. Cause: Versions are not synchronized, and signatures and receipts are not verified during material circulation.
- Symptom: Retrieval reports indexing model-related errors or authentication failures. Cause: The model type does not match the stage, and the channel key is inconsistent with the accessed service.
How to verify the setup
Acceptance for this feature: run one dialogue and one retrieval, verify the model identifier in the response, and verify that the binding relationships of maxContext, maxTokens, and toolChoice in the configuration are consistent with the channel response.
Business testing: sample three terms and check whether their writing is consistent throughout, verify that translated names can be traced back to the original text, and verify whether the dates, names, quantities, and signature receipts of notices, lesson observation records, and lesson evaluation minutes are aligned.
- In the model configuration, verify that the model type label corresponds to the stage in which it will be used, verify the channel configuration and key source, and compare the model name returned by the channel with the name listed in the documentation for consistency.
- Sample three terms and check whether their writing is consistent throughout, verify whether the name, quantity, and date of the same record match across two materials, and verify whether versions are synchronized and signatures and receipts are complete.