What this category's data looks like
This page handles student awards, grants, loans, and hardship determination materials, including three types of sources: family economic hardship determination forms, award and grant application forms, and loan receipts. Determination forms are filled out by students, reviewed by the class, and then submitted level by level; the fields include family population, income, hardship level, and signature. Application forms are updated with the academic year batch and include student ID, department, award name, amount, and date. Loan receipts are issued by the bank or the county-level funding center and include contract number, disbursement amount, arrival date, and seal. The three types of materials enter parsing and chunking as scanned copies, tables, and system exports, respectively taking on the roles of identity and hardship facts, application intent and amount, and disbursement and arrival proof. The update rhythm rolls forward by academic year and batch, and the same record needs to cross-reference each other between two materials.
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 "unified terminology table and comparison draft" is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Family economic hardship determination form | The name, quantity, and date of the same record do not match across the two materials | Check whether the name, family population, hardship level, and date in the determination form and application form are consistent, and check whether the signature fields are complete |
| Award and grant application form | Versions are not synchronized, and multiple application forms with different fields appear in the same academic year | Check the application form version number and batch, and check whether the award name, amount, and date can cross-reference the original text across the three types of materials |
| Loan receipt | Signature or receipt is missing, and the disbursement amount and arrival date have no proof | Check the contract number, disbursement amount, arrival date, and seal on the receipt, and confirm they are consistent with the amount in the application form |
| Data rows and index status | Is in one of the three states and is consistent with the interface display | Check the parsed / indexing / indexed status of the data rows corresponding to chunkSize, chunkSplitter, and trainingType |
Three common errors
- Phenomenon: The name and family population of the same student do not match between the determination form and the application form. Cause: The two materials were entered by different handlers, and no cross-table cross-reference or unified terminology table comparison was performed.
- Phenomenon: Multiple application forms with different fields appear in the same academic year, and the amounts and dates contradict each other. Cause: Versions are not synchronized, old batch materials are not marked invalid, and they still enter the same index after parsing.
- Phenomenon: The loan receipt lacks a signature or seal, and the disbursement amount and arrival date have no proof. Cause: The receipt is submitted as a scanned copy, the signature page is missing or was not uploaded together with the materials, and the original document cannot be cross-referenced after parsing.
How to verify the setup
This feature acceptance: Upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the three states parsed / indexing / indexed are consistent with the interface display, and that the rebuild only covers data whose indexing has been completed.
Business test: Sample three terms and check whether their writing is consistent throughout the entire text, confirm that the same term is consistent throughout the entire text and that the translated name can cross-reference the original text.
- Open the data rows to check the status, separately check the identity identifiers of the file records and the data rows, and confirm that the identities of the file records and the data rows can be distinguished from each other.
- View the data rows covered by the rebuild task, confirm that only data whose indexing has been completed is covered, and that data pending indexing does not participate in the rebuild; the reference limit checks the tokens of the referenced text, and the number of array entries is recorded separately.