What this category's data looks like
Materials produced by district and county teaching research activities and lesson observation and evaluation include three categories: teaching research activity notices, lesson observation records, and lesson evaluation minutes. The sources are teaching research groups, school academic affairs offices, and subject teaching researchers. The update cadence advances by activity batch: usually a notice is issued first, then lesson observation records are collected, and finally lesson evaluation minutes are produced. Field characteristics center on activity name, subject, grade, instructor, observer, time, location, lesson period, evaluation points, improvement suggestions, responsible person, version number, and date. When materials enter the model access and configuration stage, the notice serves as the entry point for activity information, the lesson observation record serves as process evidence, and the lesson evaluation minutes serve as the basis for conclusions and handover. The three types of materials need to correspond to one another in name, quantity, date, and signature; the lesson title, number of observers, and activity date for the same lesson must be consistent across different materials. The configuration stage is only responsible for model binding relationships and channel responses; it does not replace the business side in completing material drafting and handover sign-off.
Configuration and implementation checks
This step is executed by the server-side model channel configuration and outputs model binding relationships and channel responses. The material drafts and handover records that can be issued are 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.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Check whether the activity name, subject, grade, instructor, time, location, responsible person, version, and date are complete, and whether the number of lesson periods in the notice is consistent with the subsequent lesson observation records | In the model configuration, check the language model binding, run one conversation and one retrieval, and see whether the model identifier in the response is consistent with the model name returned by the channel |
| Lesson observation record | Check whether the observer, observation time, lesson period, class, evaluation points, and signature receipt are complete, and whether the name and date of the same lesson match across the two materials | Check the indexing model binding, and inspect whether retrieval errors related to the indexing model are caused by a mismatch in type annotation; use quoteMaxToken to check the tokens of quoted text, and record the number of array entries separately |
| Lesson evaluation minutes | Check whether the conclusion, improvement suggestions, responsible person, version, and date are complete, whether they are consistent with the number of lesson periods and dates in the notice and lesson observation records, and whether signatures or receipts are missing | Check the reranking model binding, adjust maxContext, maxTokens, and toolChoice, then run one retrieval to confirm that the model identifier in the response has not changed |
| Channel and key | Check whether the channel configuration and key source are consistent with the connected service, and whether the model identifier is consistent with the name listed in the documentation | Verify the model identifier against the model name returned by the channel, confirm that when authentication fails you should first check the channel and key, and check material permissions separately |
Three common errors
- Symptom: The lesson title and number of lesson periods for the same lesson do not match between the notice and the lesson evaluation minutes. Cause: During drafting, items were not checked one by one according to the template, the version was not synchronized, and the responsible person did not review before handover.
- Symptom: The lesson observation record has evaluation points but lacks a signature or receipt, and the date of the lesson evaluation minutes is inconsistent with the activity date. Cause: In the handover step, judgment was not made according to complete fields, a clear responsible person, and consistent version and date, and missing items were not stopped when the next step signed off.
- Symptom: Retrieval reports an indexing model-related error, or the answer style changes abruptly after switching models. Cause: The model type does not correspond to the stage in which it is to be used, the model identifier is inconsistent with the model name returned by the channel, or authentication fails.
How to verify the setup
Acceptance for this feature: run one conversation and one retrieval, check the model identifier in the response, confirm that the language, indexing, and reranking model bindings are consistent with the model name returned by the channel, and check that the values of maxContext, maxTokens, quoteMaxToken, and toolChoice in the configuration are consistent with the documentation.
Business test: draft one copy according to the template and complete one handover, see whether missing items are stopped, check whether the fields, dates, and signatures of the notice, lesson observation record, and lesson evaluation minutes are complete, whether the responsible person is clear, and whether the version and date are consistent.
- In the model configuration, check item by item that the model type corresponds to the stage in which it is to be used, check the channel configuration and key source, and verify the model identifier against the model name returned by the channel.
- Draft one material according to the template and complete one handover, check whether the names, quantities, dates, and signatures of the notice, lesson observation record, and lesson evaluation minutes are consistent, and ensure missing items are stopped by the next step during sign-off.