What this category's data looks like
Student award, grant, loan, and hardship determination materials include the family economic hardship determination form, the scholarship and grant application form, and the loan receipt. The determination form comes from student submissions and class review, and is updated centrally by academic year; its fields include family population, income sources, hardship level, and review signatures. The application form comes from individual applications and department review, and is updated by batch; its fields include the applied item, amount tier, and review comments. The loan receipt comes from the handling institution, and is updated by disbursement cycle; its fields include the contract number, disbursement date, and receipt seal. After these three types of materials enter this feature, the determination form serves as the eligibility record, the application form serves as the basis for disbursement, and the receipt serves as the proof of arrival. The deployment and operations side is only responsible for making the services and databases that carry them connectable; the names, quantities, dates, and signatures of the materials themselves are checked by handover and subsequent business processing.
Configuration and implementation checks
This part is handled by the connection configuration of the deployment environment (server side), not by the capability execution of a model node, and outputs whether the connection is available (service startup result and connection logs). The handover-ready deployment status and operation records are completed by deployment handover and subsequent business processing. The main business database, log database, cache, and vector database can point to different instances respectively; when the log database is not configured separately, it reuses the main database.
| Object | Check | Verification action |
|---|---|---|
| Main business database connection variable | Points to the main business database actually in use and can connect; the value matches the database address | In the deployment environment, check that the MONGODB_URI value matches the database address; after restart, check the connection result in the startup logs |
| Log database connection variable | Configured separately, or left empty per the instructions to reuse the main database; the database written to by logs can be checked | Check whether this variable is set and verify the database written to by logs; if not set, confirm that the main database is reused |
| Cache connection variable | The cache instance can connect and returns available | Connect once to REDIS_URL with a client and check the return; then check the startup logs for no connection timeout |
| Vector database connection variable | Matches the vector database actually in use; the address corresponds to the selected database | Check the selected vector database and address against the deployment instructions, and check whether PG_URL is consistent with the deployment instructions |
Three common errors
- Symptom: the hardship level and dates for the same student do not match between the determination form and the application form. Cause: the versions of the two materials were not synchronized, and the application form was not backfilled after review.
- Symptom: the loan receipt lacks a seal, or the contract number is inconsistent with the application form. Cause: the receipt was not archived, and items were not checked one by one against the form during handover.
- Symptom: after startup, the logs continuously report connection timeouts, and retrieval reports vector database errors. Cause: the connection variables are inconsistent with the actual instances, or the log database and the main database are mixed in the same place.
How to verify the setup
Feature acceptance: connect once to the main business database, log database, cache, and vector database item by item, check the connection results in the startup logs, and confirm that the instances corresponding to MONGODB_URI, REDIS_URL, and PG_URL can connect.
Business test: check once item by item according to the handover form to see which record is missing, focusing on whether the names, quantities, dates, and signatures of the determination form, application form, and loan receipt are complete.
- Check the fields, dates, and signatures of the determination form, application form, and loan receipt item by item according to the handover form; register missing items and pass them to the next shift.
- Check the version and connection records: confirm that the deployment version, connection results, and task records are consistent; write inconsistent items into the operation records.