What this category's data looks like
District and county teaching research activity and lesson observation and evaluation materials include teaching research activity notices, lesson observation records, and lesson evaluation minutes. Their sources are teaching research offices, schools, and subject groups, and their update cadence accumulates activity by activity with the activity cycle. When these three types of materials enter this feature, their roles differ: notices provide the activity theme, time, and participation scope; lesson observation records provide classroom observation fields and signatures; lesson evaluation minutes provide conclusions and improvement suggestions. Multilingual materials and terminology handling require that the same term be written consistently in notices, records, and minutes, and that translated names can refer back to the source text. Field characteristics include date, subject, instructor, observation items, signature, and receipt. The indexing service and vector database are responsible for making these materials retrievable, and subsequent nodes then generate a unified terminology table and comparison draft.
Configuration and implementation checks
This step is executed by the indexing service and vector database, outputting vectors and index status (whether retrieval is possible and whether data in the same group is merged). The unified terminology table and comparison draft are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Date, subject, and participation scope fields are complete, and signatures or receipts are not missing | Open the notice data row and check the index fields, confirming that multiple vector identifiers are all present |
| Lesson observation record | The name, quantity, and date of the same record match between the notice and the record | Retrieve once to see whether data in the same group is merged, and check the status value against indexed and the rebuild task record |
| Lesson evaluation minutes | The version has been synchronized, and the terminology wording and comparison draft can refer back to the source text | Check the index model in the knowledge base settings, confirming it is consistent with the vector model actually used by the knowledge base |
| Data row | After changing models, only data that has already completed indexing is triggered for rebuild, and the coverage scope is checkable | View the data scope covered by the rebuild task, and check the reference budget of limit |
Three common errors
- Symptom: duplicate entries appear in retrieval results. Inspect the following: the same group of data corresponds to multiple vector identifiers, and after retrieval it is not merged back to the original data by identifier.
- Symptom: the name, quantity, and date of the same record do not match between the notice and the minutes. Inspect the following: versions are not synchronized, and materials are updated separately.
- Symptom: retrieval quality declines after changing models. Inspect the following: rebuild is triggered only for data that has already completed indexing, and data rows not covered have content but cannot be retrieved.
How to verify the setup
Feature acceptance: sample one data row and look at the index fields, confirming that multiple vector identifiers are all present, then retrieve once to see whether data in the same group is merged, and check the status value against indexed and the rebuild task record.
Business test: sample three terms and check whether their wording is consistent throughout the entire text, and whether translated names can refer back to the source text.
- Check the index model in the knowledge base settings, confirming it is consistent with the vector model actually used by the knowledge base.
- View the data scope covered by the rebuild task, check the reference budget of
limit, and record the number of array entries separately.