What this category's data looks like
The data for this category looks like this: Self-taught examination registration records and graduation review involve three types of materials: registration archives, course qualification certificates, and graduation application forms. Registration archives are updated by the provincial examination office after each score release, with fields including admission ticket number, name, course code, score, and date obtained; course qualification certificates are issued by the host institution in batches, with fields including course name, credits, qualification date, and seal; graduation application forms are filled out by candidates and then signed and approved level by level, with fields including major name, number of courses, graduation conclusion, signature, and receipt. When the three types of materials enter the material verification and discrepancy localization function, their roles differ: registration archives serve as the baseline ledger, course qualification certificates serve as item-by-item comparison evidence, and graduation application forms serve as summary declaration documents. The material update rhythm is that registration archives are updated on a rolling basis with score releases, course qualification certificates are updated by issuance batch, and graduation application forms are updated by declaration cycle. The field characteristics are that the same course has differences in name spelling, quantity statistics caliber, and date format across different materials, requiring field-by-field localization.
Configuration and implementation checks
Configuration and implementation checks: This step is executed by application settings (reply limit, etc.), outputting the length of a single answer and the context range it can accommodate. The "discrepancy list" is then completed by the model. The reply limit is controlled by a slider for the length of a single answer; if set too low, the answer will be truncated, and if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Registration archives | Whether the course name, quantity, and date of the same record are consistent between the registration archives and the course qualification certificate | Compare course codes and qualification dates item by item, record discrepancy fields, and check whether the values of maxContext and maxResponse match the answer length |
| Course qualification certificate | Whether the credits, qualification date, and seal of the same record are complete in the course qualification certificate and the graduation application form | Check whether the seal and receipt are missing, compare date formats, record discrepancy items, record the number of citations separately, and quoteMaxToken only checks the tokens of the quoted text |
| Graduation application form | Whether the major name, number of courses, and graduation conclusion of the same record are consistent between the graduation application form and the registration archives | Check the signature and receipt, compare the statistical caliber of the number of courses, and record fields whose versions are not synchronized |
| Registration archives and course qualification certificate | Whether the versions of the two materials are synchronized, and whether there are old-version course names or old-version qualification dates | Check the material version number and issuance batch, and mark unsynchronized fields |
Three common errors
- Phenomenon: The same course has different name spellings in the registration archives and the course qualification certificate, causing comparison to break down. Cause: The two materials are entered in different stages, and name normalization has not been performed.
- Phenomenon: The qualification dates in the course qualification certificate and the graduation application form do not match, and the quantity statistics are also inconsistent. Cause: Versions are not synchronized, and old-version materials are still in circulation.
- Phenomenon: The graduation application form lacks a signature or receipt, and the discrepancy list cannot be closed. Cause: The signing and approval stage has not written back, and the materials have not been collected.
How to verify the setup
How to verify the setup: For acceptance of this function: ask a question that requires a long answer and see whether the ending is complete; if the answer breaks off in the middle of a sentence, increase the reply limit and retry.
Business test: Use a real record to find fields inconsistent with the ledger, write them into the discrepancy list, submit them to the reviewer for confirmation, and write back.
- In the application settings, check the reply limit switch and slider position, and confirm that they match the answer length required by the page.
- Compare the usage of two runs to confirm that the change in single-run usage after adjusting the limit is within expectations.