What this category's data looks like
This category's data involves three types of materials: student registration forms, teaching plans, and skills training records. Student registration forms record student identity, registration date, and enrollment status, and are usually updated centrally at the beginning of each semester; teaching plans specify course names, class hour quantities, and implementation dates, and are revised as professional programs are adjusted; skills training records register training items, completion quantities, and instructor signatures, and are entered on a rolling basis by week or by module. When these three types of materials enter the material verification and discrepancy localization function, the student registration form serves as the enrollment baseline, the teaching plan serves as the course and class hour baseline, and the skills training record serves as the process and signature baseline. For the same student, the name, student ID, course name, class hour quantity, training date, signature, and receipt status in the three materials need to be compared item by item. Field characteristics include text-type names, numeric-type quantities, date-type nodes, and signature and receipt statuses. Different update rhythms make version misalignment likely, so a discrepancy list needs to be established by object and field.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which output the length of a single answer and the range of context that can be accommodated. The discrepancy list is then completed by the model, and entry and authorization are handled by the publishing service and file permissions.
| Object | Check | Verification action |
|---|---|---|
| Student registration form | Student name, student ID, registration date, and enrollment status are consistent in the two materials, and signatures and receipts are complete | Compare against the teaching plan and skills training record, verify name, student ID, and date field by field, and record inconsistent items |
| Teaching plan | Course name, class hour quantity, implementation date, and version number are consistent in the two materials; missing signatures or receipts must be marked | Compare against the student registration form and skills training record, verify course name, quantity, and date, and check whether versions are synchronized |
| Skills training record | Training item, completion quantity, training date, and instructor signature are consistent in the two materials | Compare against the teaching plan and student registration form, verify item name, quantity, date, and signature receipt, and locate discrepant fields |
| Response limit | Matches the answer length required by the page; check the switch and slider position in application settings | Check the length of a single answer and the range of context that can be accommodated, confirm the slider positions of maxResponse and maxContext, and record the reference content budget of quoteMaxToken |
Three common errors
- Phenomenon: the name or student ID of the same student does not match between the student registration form and the skills training record. Cause: the two materials were entered at different times, and version synchronization and field-level comparison were not performed.
- Phenomenon: the class hour quantity in the teaching plan is inconsistent with the completion quantity in the skills training record. Cause: after the plan was revised, it was not written back to the ledger, and the old version was still referenced.
- Phenomenon: the skills training record lacks an instructor signature or receipt. Cause: process materials were not collected completely by node, and verification only looked at names and dates, missing the signature status.
How to verify the setup
This function's acceptance: submit a question that requires a long answer, check whether the ending is complete, and confirm that the length of a single answer and the range of context that can be accommodated meet the page requirements.
Business test: use one real record to find fields inconsistent with the ledger, form a discrepancy list, and write it back after confirmation by the reviewer.
- In application settings, check the response limit switch and slider position, and confirm that the values of
maxResponseandmaxContextmatch the answer length required by the page. - For the same student's student registration form, teaching plan, and skills training record, compare names, quantities, dates, and signature receipts field by field, write inconsistent items into the discrepancy list, and mark the version.