What this category's data looks like
In the deployment, operations, and application handover phase of adult college entrance examination registration and admission management, the core materials include registration forms, preferential scoring materials, and admission rosters. Registration forms are filled in by candidates and preliminarily reviewed by registration points; the fields include name, ID number, application level, and subject category; the date is the registration deadline; and signatures from both the candidate and the reviewer are required. Preferential scoring materials are submitted by candidates and rechecked by the admissions office; the fields include the bonus item, certificate number, and review conclusion; the date is the review date; and the reviewer's signature plus a receipt are required. Admission rosters are reported by admitting institutions and filed by the provincial admissions office; the fields include candidate number, admitted major, and admission batch; the date is the admission date; and signatures from both the institution and the admissions office are required. After deployment and upgrade, these three types of materials enter version upgrade and migration task records, respectively assuming the verification roles of registration data, bonus basis, and admission results, with the update rhythm advancing through the three stages of registration, review, and admission.
Configuration and implementation checks
This step is executed by the deployment environment and the administrator version upgrade page (server-side operation), outputting the image version, migration task records, and data row index status. The handover-ready deployment status and operation records are then completed by operations handover and business use.
| Object | Check | Verification action |
|---|---|---|
| Registration form | The name, ID number, and date of the same candidate in the registration form and the preferential scoring materials must be consistent, and signatures and receipts must be complete | Compare the name, ID number, and date in the two materials one by one, check the signature field and receipt number, and confirm that the status of this record in the database pointed to by MONGODB_URI is indexed |
| Preferential scoring materials | The bonus item name, certificate number, and review date must be consistent with the corresponding records in the registration form and admission roster | Extract the bonus record, compare the name, quantity, and date against the registration form and admission roster, check the reviewer's signature, and verify that the status of this record in the database connected by PG_URL is parsed |
| Admission roster | The candidate number, admitted major, and batch must form a closed loop with the registration form and bonus materials, and handover is not allowed when the version is not synchronized | Check the fields and dates of the roster against the registration form and bonus materials according to the handover sheet, confirm signatures and receipts from both parties, and verify that the status of this record in the cache of REDIS_URL is indexed |
| Image version and migration task records | The two image version identifiers are consistent, and the two migration scripts are executed in order with complete records | Check the image version identifiers, review the migration task records in order, and sample one data row to verify the index status field |
Three common errors
- Symptom: The name, ID number, or date of the same candidate in the registration form and the preferential scoring materials do not match. Cause: The two materials were entered separately, were not compared item by item according to the handover sheet, and signatures or receipts are missing.
- Symptom: The service can start, but the data row status is still the old marker. Cause: Consistent image versions do not mean the business data has completed migration, and the migration task records were not verified in order.
- Symptom: The name, quantity, and date of the admission roster do not match the registration form and bonus materials. Cause: The version was not synchronized, migration was triggered before the old instance was fully stopped, and records are missing.
How to verify the setup
Function acceptance: verify the two image version identifiers, then verify the execution records of the two migration scripts in order, confirm that the migration task records are complete and the data row index status is the new system, and verify the three connection identifiers MONGODB_URI, PG_URL, and REDIS_URL and the record statuses indexed and parsed.
Business test: check item by item once according to the handover sheet, see which record is missing, and confirm that the fields, dates, and signatures of the registration form, preferential scoring materials, and admission roster are complete.
- Verify the image version identifiers and migration task records, confirm that the two scripts are executed in order and do not block service startup, and check the
DB_MAX_LINKconnection identifier. - Sample one data row to verify the index status field, and check the signatures and receipts of the registration form, bonus materials, and admission roster.