What this category's data looks like
This category covers pre-departure training and overseas safety reminders. Materials include pre-departure training courseware, safety reminder checklists, and accommodation contact sheets. Sources are the academic affairs and overseas services teams, updated weekly. When entering the progress records and statistical verification function, the courseware serves as the baseline for training sessions and sign-ins, the safety reminder checklist serves as the baseline for reminder counts and acknowledgements, and the accommodation contact sheet serves as the baseline for accommodation addresses and contact person fields. Field characteristics are name, quantity, date, signature or acknowledgement. The three types of materials each play a different role in the statistical scope: courseware is used for session totals, the checklist is used for reminder coverage totals, and the contact sheet is used for accommodation confirmation totals. During verification, the header scope prevails, and exceptions are listed separately.
Configuration and implementation checks
This step is executed by the deployment environment's connection configuration (server side), not by the capabilities of a model node, and outputs whether the connection is available (service startup result and connection logs). The "progress table and statistical scope description" is then completed by deployment handover and subsequent business processing.
| Object | Check | Verification action |
|---|---|---|
| Pre-departure training courseware | Name, date, and signature are complete and consistent with the statistical scope header | Verify the courseware sign-in date and signature, compare against the progress table session totals, and check the connection log of the main business database pointed to by MONGODB_URI |
| Safety reminder checklist | Reminder counts and acknowledgements are complete and consistent with the statistical scope header | Verify the checklist counts and acknowledgements, compare against the statistical totals, and check the return of the REDIS_URL cache connection |
| Accommodation contact sheet | Accommodation name, quantity, date, and signature are complete | Verify the contact sheet fields and signature, compare against the accommodation confirmation totals, and check the connection log of the PG_URL vector database |
| Progress table and statistical scope description | Record counts and statistical counts match, and the scope is written in the header | Use one week of records to verify the totals, and check whether the scope and exceptions are clearly written |
Three common errors
- Symptom: the session name, quantity, or date of the same training record does not match between the courseware and the progress table. Cause: the two materials are maintained separately and are not verified uniformly according to the header scope.
- Symptom: the safety reminder checklist has been updated, but statistics still use the old version, and the version is not synchronized. Cause: the update cadence is not aligned, and the old version is not marked as discontinued.
- Symptom: the accommodation contact sheet lacks a signature or acknowledgement, but the total still includes it. Cause: exceptions are not listed separately, and signatures/acknowledgements are not treated as preconditions for statistics.
How to verify the setup
This function's acceptance: connect once to the main business database, log database, cache, and vector database item by item, and verify the connection results in the startup logs.
Business test: use one week of records to verify the totals, and check whether the scope and exceptions are clearly written.
- In the deployment environment, verify that the connection variable values for the main business database, log database, cache, and vector database are consistent with the database addresses.
- Use one week of records to verify the totals, write the scope and exceptions into the header, and include them in the weekly or monthly report.