What this category's data looks like
In the district and county teaching research activity and classroom observation and evaluation scenario, materials usually include three types: teaching research activity notices, classroom observation records, and classroom evaluation minutes, which respectively carry activity arrangements, classroom observations, and evaluation conclusions. Notices are issued by the organizing party and include the activity theme, time, location, participating kindergartens, and receipt requirements; classroom observation records are filled in by the observer and include the class, teacher, activity name, observation dimensions, and signature; classroom evaluation minutes are compiled by the evaluation group and include evaluation points, improvement suggestions, and signatures/seals. Materials are continuously updated by activity batch, and the name, quantity, date, and signature status of the same activity in the notice, record, and minutes must remain consistent. After materials enter parsing and training tasks, the notice, record, and minutes are each stored as independent data rows, making it easy to trace back to the original text by material type and activity batch during subsequent retrieval.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The basis entries that can be traced back to the original text are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Teaching research activity notice | Contains the activity theme, date, participating kindergartens, and receipt requirements; fields and signature must correspond to the classroom observation record and classroom evaluation minutes | Check the notice date and receipt status, and confirm that the activity name is consistent with that in the record and minutes |
| Classroom observation record | Contains the class, teacher, activity name, observation dimensions, and signature; must align with the dates and quantities in the notice and minutes | Check the activity name and date in the record, and confirm that the signature is complete and corresponds to the notice batch |
| Classroom evaluation minutes | Contains evaluation points, improvement suggestions, and signatures/seals; must be consistent with the names and quantities in the notice and record | Check the signatures/seals and evaluation points in the minutes, and confirm that they are consistent with the activity name and date in the classroom observation record |
| Data rows and index status | Is in one of the three states and consistent with the interface display; data pending indexing does not participate in recall | View the status transitions of data rows, and check chunkSize, chunkSplitter, trainingType, and the coverage scope of the rebuild task |
Three common errors
- Symptom: The name and date of the same activity in the notice and classroom observation record do not match. Cause: The two materials were entered separately, and fields were not checked uniformly by activity batch.
- Symptom: The classroom evaluation minutes lack a signature or receipt, and the basis entries cannot be traced back to the original text. Cause: The signature/seal status was not synchronized during material circulation, and the version was not synchronized.
- Symptom: Newly uploaded materials cannot be found, and rebuilding after changing the model takes abnormally long. Cause: Data pending indexing does not participate in recall, and rebuilding only covers data that has already completed indexing.
How to verify the setup
Acceptance for this feature: Upload one material, observe the status transitions of data rows and the coverage scope of the rebuild task, and check chunkSize, chunkSplitter and trainingType; separately confirm that the rebuild task covers indexed data.
Business test: Ask a cross-material basis question and see whether the answer provides a traceable source.
- Open the data rows to check the status, confirm that they are parsed, indexing, or indexed, and check that the identifiers of file records and data rows are distinguishable.
- View the data rows covered by the rebuild task, and confirm that it only covers data that has already completed indexing, while data pending indexing does not participate in rebuilding.