What this category's data looks like
International student admissions and enrollment management involves three types of materials: admission brochures, admission letters, and visa application forms. The sources are the international student offices and admissions systems of each school, and the update cadence follows admissions batches and visa policy adjustments. Admission brochures contain program names, tuition, application deadlines, and signature fields; admission letters contain student name, student ID, admitted program, registration date, signature, and acknowledgment; visa application forms contain passport name, date of birth, visa type, and signature. After these three types of materials enter this feature, admission brochures and admission letters serve as terminology sources and comparison drafts, while visa application forms serve as field verification and back-reference. The same term must be consistent throughout and its translated name must be able to back-reference the original text, and fields, dates, and signatures must be aligned across materials.
Configuration and implementation checks
This stage is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). "Unified terminology glossary and comparison draft" is then completed by retrieval and subsequent processing. After parsing is completed, parsed chunks are immediately persisted as visible data rows and bound to a unique data identifier; data awaiting indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Admission brochure | The same term is consistent throughout and its translated name can back-reference the original text; fields, dates, and signature are complete | Check program names, tuition, application deadlines, and signature fields; check whether chunkSize and chunkSplitter split terms completely |
| Admission letter | Student name, student ID, admitted program, registration date, and acknowledgment can correspond in the admission brochure | Separately check the file records and data rows, confirm that the name, quantity, and date of the same record are consistent in both materials, and check the trainingType value |
| Visa application form | Passport name, date of birth, visa type, and signature can back-reference the original text | Check that the data row status is one of parsed / indexing / indexed and is consistent with the interface display, and check whether signature and acknowledgment are missing |
| Data row | Status is consistent with the interface display, and the rebuild scope only covers data whose indexing has been completed | Open the data row to check the status, and see whether the data rows covered by the rebuild task include only the indexed status |
Three common errors
- Symptom: The name and date of birth of the same student do not match between the admission letter and the visa application form. Cause: The name, quantity, and date of the same record in the two materials were not aligned across materials.
- Symptom: The admission brochure has been updated, but the admission letter still references the old program name. Cause: The version was not synchronized, and the old-version material was not replaced with the new batch.
- Symptom: The visa application form is missing a signature or acknowledgment, and the material is returned. Cause: The signature and acknowledgment fields were not verified after parsing, and missing items were not discovered.
How to verify the setup
This feature acceptance: Upload one material and observe the data row status transitions and the coverage scope of the rebuild task; confirm that the status transitions according to parsed / indexing / indexed, that rebuild targets only data whose indexing has been completed, and that the initial training covers data awaiting indexing.
Business test: Sample three terms to check whether their spelling is consistent throughout, and confirm that the translated names can back-reference the original text.
- Open the data row to check whether the status is one of parsed / indexing / indexed and is consistent with the interface display
- Separately check the file records and data rows, and confirm that the identities of the file records and data rows are distinguishable