What this category's data looks like
Materials for 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. Notices contain the activity name, date, subject, location, participants, and sign-in receipt; lesson observation records contain the instructor, class, topic, observation dimensions, time, and observer signature; lesson evaluation minutes contain review points, improvement suggestions, host, recorder, date, and signature. The material sources are submissions from each school and archiving by teaching research institutions. The update rhythm advances by activity batch, and the same activity often has multiple materials in parallel. When entering the vector model and indexing stage, notices, records, and minutes each serve as independent data rows. Their text and image descriptions generate vector identifiers, the original data is stored in the business database, and the index field records multiple vector identifiers for recall during retrieval and merging of data in the same group.
Configuration and implementation checks
This stage is executed by the indexing service and vector database, outputting vectors and index status (whether recall is possible and whether data in the same group is merged). The version ledger and change records are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials).
| Object | Check | Verification action |
|---|---|---|
| Lesson observation record | The name, quantity, and date of the same record in the notice and minutes must be consistent, and signatures and receipts must be complete | Open one lesson observation record data row, check whether multiple vector identifiers in the index field are complete, and check the defaultToken and maxToken settings |
| Lesson evaluation minutes | When versions are not synchronized, the minutes cite content from an old version of the record, and it is necessary to check that the current version is unique | View the data range covered by the rebuild task record, and confirm whether the data that has completed indexing after changing the model triggers a rebuild |
| Teaching research activity notice | The date, participants, and receipt signature in the notice must correspond to the lesson observation record and lesson evaluation minutes | In the knowledge base settings, check whether the indexing model and the vector model actually used by the knowledge base are consistent, and perform one retrieval to see whether data in the same group is merged |
| Data row index status | A data row has content but cannot be retrieved, or duplicate entries appear in retrieval results | Sample one data row to inspect the index field, check whether limit affects the tokens of the cited text, and record the number of array entries separately |
Three common errors
- Symptom: The name, quantity, and date of the same lesson observation record do not match between the notice and the lesson evaluation minutes. Inspect the following: Multiple materials were imported separately, and they could not be merged during retrieval.
- Symptom: Versions are not synchronized, and old content is still recalled. Inspect the following: After changing the model, the rebuild task only covers completed data. Data rows whose indexing is not completed do not participate in recall, so indexing must be completed before rebuilding.
- Symptom: Lesson evaluation minutes lack signatures or receipts, and the participants in the notice are inconsistent with the record. Inspect the following: The signature field was not checked when archiving materials.
How to verify the setup
Acceptance for this feature: sample one data row to inspect the index field and confirm that multiple vector identifiers are all present; then perform one retrieval to see whether data in the same group is merged, with the vector score taking the highest score.
Business test: change one piece of content and see whether the version number and citation are updated synchronously; check the tokens of the cited text and the number of array entries and record them separately; limit are only budget references.
- In the knowledge base settings, check whether the indexing model and the vector model actually used by the knowledge base are consistent, and view the data range covered by the rebuild task record.
- Open one data row to check the index field and confirm that multiple vector identifiers are complete; perform one retrieval to see whether data in the same group is merged; for status values, only recognize indexed and the rebuild task record.