What this category's data looks like
This page focuses on credit management for primary and secondary school teacher training. The materials come from training notices, credit recognition forms, participant rosters, and ledgers. Training notices are issued by the teacher development center by project batch, and include course names, class hours, start and end dates, and signatures/seals; credit recognition forms are summarized by school administrators by semester, and include teacher names, subjects, credit amounts, recognition dates, and responsible person signatures; participant rosters are receipted by the organizing institution by class session, and include names, units, sign-in dates, and receipt status. The update cadence is summary within two weeks after the end of each batch. The field characteristics are that the same record differs across materials in name spelling, quantity units, and date formats, requiring field-by-field comparison. After the materials enter this function, the training notices and participant rosters serve as comparison sources, the credit recognition forms serve as the object to be verified, and the ledger serves as the baseline; together, the three support discrepancy localization.
Configuration and implementation checks
This step 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. The response limit is controlled by a slider for the length of a single answer. If set too low, the answer will be truncated; if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Training notice | Whether the course name, class hour quantity, start and end dates, and signature/seal are consistent with the ledger | Compare name spelling, quantity units, and date formats item by item, record items missing signatures/seals, and check whether maxResponse matches the answer length |
| Credit recognition form | Whether the teacher name, subject, credit amount, recognition date, and responsible person signature are consistent with the ledger | Locate records by name and subject, compare quantities and dates, mark items missing signatures or receipts, and check the maxContext accommodation range |
| Participant roster | Whether the name, unit, sign-in date, and receipt status are consistent with the ledger | Check sign-in dates and receipts by class session, mark items whose versions are not synchronized, and record the quoteMaxToken reference budget and array item count |
| Ledger | As the baseline record, whether the name, quantity, and date fields are unique and free of duplicates | Use the ledger as the standard, reverse-check the three materials, output a field-level discrepancy list for the reviewer to confirm and write back |
Three common errors
- Phenomenon: The class hour quantity for the same record does not match between the training notice and the credit recognition form. Cause: The name spelling or quantity unit was not unified, and entry was not checked against the ledger baseline.
- Phenomenon: The sign-in date in the participant roster is inconsistent with the ledger. Cause: The version was not synchronized, the old roster was not replaced, and the receipt date was not updated in the ledger.
- Phenomenon: The credit recognition form is missing the responsible person's signature or the receipt is missing. Cause: The signature pages were not fully collected during summary, and the receipt status was not written back, resulting in incomplete materials.
How to verify the setup
This function's acceptance: ask a question that requires a long answer, check whether the ending is complete, and confirm that the response limit matches the answer length required by the page, avoiding breaks in the middle of sentences.
Business test: use one real record to find fields inconsistent with the ledger, check names, quantities, and dates item by item, and output a discrepancy list for the reviewer to confirm and write back.
- In the application settings, check the response limit switch and slider position, compare usage from two runs, and confirm the change in single-run usage after adjusting the limit.
- Compare the training notice, credit recognition form, and participant roster field by field against the ledger, record discrepancies in names, quantities, and dates as well as missing signatures and missing receipt items, and form a discrepancy list.