What this category's data looks like
This category's data for district and county teaching research activities and lesson observation and evaluation materials includes three types: teaching research activity notices, lesson observation records, and lesson evaluation minutes. Sources are submissions from each school and on-site entries by teaching researchers, and the update cadence advances by activity batch and semester milestone. When the three types of materials enter the conversation logs and auditing feature, their roles differ: notices provide the activity name, date, and participation scope; lesson observation records provide classroom observation fields and teaching information; lesson evaluation minutes provide review comments, signatures, and receipts. Field characteristics center on whether the name, quantity, date, signature, and receipt are complete. The same record often has mismatched name, quantity, and date across two materials, versions are not synchronized, and signatures or receipts are missing. Conversation records are pulled by pagination along the application and session dimensions, and the returned results distinguish two roles, question and answer, and carry citation and elapsed-time fields. After materials enter this feature, notices and minutes are used to check whether the session evidence covers the activity batch, and lesson observation records are used to check whether a single record shows citations and elapsed time. Together, the three support a handover-ready deployment state and operation records.
Configuration and implementation checks
This step is executed by the conversation records interface (along the application and session dimensions), outputting a session message list and the total record count, including role and citation information. The handover-ready deployment state and operation records are then completed manually or by an external system. The message list is not a version ledger of business materials; it only takes session evidence and does not write to a business ledger.
| Object | Check | Verification action |
|---|---|---|
| Application and session identifiers | Consistent with the actual application and actual session; name and date match | Check the source of the two identifiers in the request parameters, and confirm that chatId and dataId point to the same session |
| Pagination parameters | Record count matches the total, and quantity and date do not conflict | Pull two consecutive pages and check the total record count and advance the offset by the number of records retrieved, confirming response code of 200 and that the total is not duplicated |
| Role field | message roles correspond to the original conversation, and signatures and receipts are not missing | Look at the order of the two roles in the returned list, and sample one record to check whether the value field is complete |
| Citation and elapsed-time fields | A single record shows citations and elapsed time, and the version is synchronized | Open one record to check citations and elapsed time; record the citation count separately by array length |
Three common errors
- Symptom: the same lesson observation record has mismatched name, quantity, and date in the notice and the minutes. Cause: the two materials are registered separately and are not checked against the same activity batch.
- Symptom: the lesson evaluation minutes lack a signature or receipt, and items are missing when the handover form is checked item by item. Cause: the signature step is not confirmed in sync with the total record count.
- Symptom: the interface returns empty but sessions exist in the UI, or only the first page is retrieved. Cause: the sources of the application and session identifiers are inconsistent, and pagination offsets are not pulled consecutively.
How to verify the setup
This feature's acceptance: page through by total record count to retrieve everything, sample one record to check the role, citation information, and time, and confirm that the message identifiers and content fields _id, dataId and value are consistent with response code of 200 and the total record count total.
Business testing: check once item by item against the handover form, see which record item is missing, and focus on checking the name, quantity, date, and signature receipt of teaching research activity notices, lesson observation records, and lesson evaluation minutes.
- Pull two consecutive pages and check the total record count and advance the offset by the number of records retrieved, confirming response
codeof 200 and that records are not duplicated. - Open one record to check the role, citations, and elapsed time; record the citation count separately by array length.