What this category's data looks like
Materials in the student awards, grants, loans, and financial hardship determination category include three types: financial hardship determination forms, scholarship and grant application forms, and loan receipts, which come respectively from student submissions, departmental preliminary reviews, and bank receipts, and are updated by academic year and batch. Determination form fields include household population, income sources, hardship level, and review signatures; application form fields include student ID, award name, amount, and approval signature; loan receipt fields include contract number, disbursement date, and bank seal. When these three types of materials enter the deployment and upgrade function, the determination form and application form play the role of business data, and the receipt plays the role of external credential; all are persisted to the database as data rows for subsequent migration and index status verification.
Configuration and implementation checks
This step is performed by the deployment environment and the administrator version upgrade page (server-side operation), and outputs the image version, migration task records, and data row index status. "Handover-ready deployment status and operation records" are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Financial hardship determination form | Fields, dates, and signatures must be consistent with the review records; if the name, quantity, or date of the same record does not match across the two materials, it is inconsistent | Sample one data row, verify the determination form fields and signature date, and check the index status of that row in the database pointed to by MONGODB_URI |
| Scholarship and grant application form | Fields, dates, and signatures must be consistent with the approval records; a missing signature or receipt is regarded as incomplete materials | Compare the application form amount with the approval signature, and verify the migration task record of that row in the database corresponding to PG_URL |
| Loan receipt | The contract number, disbursement date, and bank seal must be consistent with the application record; when the version is not synchronized, the receipt and application do not match | Verify the receipt contract number and disbursement date, and check the time and status of the task record under the REDIS_URL connection |
| Image version identifier | Both the main service image and the commercial edition image are the same target version | Compare the version identifiers of the two images against the version description, and confirm that no version is unsynchronized |
Three common errors
- Symptom: the service can start but the data row status is still the old marker. Cause: the migration script was not triggered after the old instance was fully stopped and the old task lease expired, so the data row index status was not switched.
- Symptom: the name, quantity, or date of the same record does not match between the determination form and the application form. Cause: the two materials were entered separately, lacking a step to verify item by item against the handover sheet.
- Symptom: the loan receipt is missing a signature or receipt, and the application record and receipt version are not synchronized. Cause: the receipt was not updated with the batch, and the migration task record and data row were not verified together.
How to verify the setup
This function's acceptance: verify the two image version identifiers and confirm that the main service and commercial edition are the same target version; then verify the execution records of the two migration scripts in order, first the historical chunk training task migration, then the knowledge base rebuild status migration, compare the time and status of the two records, and sample one data row to verify the status field.
Business test: verify item by item against the handover sheet once, see which record is missing, and after confirming that the version, connection, and task records are consistent, hand over to operations or the next shift.
- On the administrator version upgrade page, view the execution record of the historical chunk training task migration, and confirm that it was triggered only after the old instance was fully stopped and the old task lease expired.
- Compare the time and status of the two migration records, and sample one data row to verify whether the status field is the new index status system.