What this category's data looks like
This page is intended for university admissions physical examination organizations. Materials include physical examination forms, re-examination applications, and restricted major notifications. Sources are the admissions offices and physical examination stations of each institution, updated according to admissions batches and re-examination cycles. After materials enter parsing and training tasks, physical examination forms are responsible for field and signature verification, re-examination applications are responsible for date and receipt tracking, and restricted major notifications are responsible for comparing major names with restricted conclusions. Field characteristics are the coexistence of multilingual terminology, dates, quantities, signatures, and receipts. The same record often appears in two materials with inconsistent names, quantities, and dates, versions are not synchronized, and signatures or receipts are missing. After parsing and chunking, data is first stored as visible data rows, then enters the three-state index flow. Data pending indexing does not participate in recall. Changing models only rebuilds data that has already been indexed.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index statuses (parsed, indexing, indexed). The "unified terminology table and comparison draft" is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Physical examination form | Fields, dates, and signatures are complete and consistent with the corresponding record in the re-examination application | Check that the data row status is consistent with the interface display, inspect the field boundaries after chunking by chunkSize and chunkSplitter, and confirm that signatures and receipts are not missing |
| Re-examination application | Dates and receipts can be traced back to the original text of the physical examination form, and the name and quantity of the same record match | Check the file record and the data row identifier separately, and inspect whether the index status under the processing mode corresponding to trainingType is parsed, indexing, or indexed |
| Restricted major notification | Major names and restricted conclusions are consistent throughout the text, and translated names can be traced back to the original text | Open the data row to check the status, sample three terms to check whether their usage is consistent throughout the text, and confirm that versions are synchronized |
| Rebuild task | Only covers data that has already been indexed; data pending indexing does not participate in rebuilding | Look at the data rows covered by the rebuild task, and confirm that after changing models the rebuild scope is limited to indexed data |
Three common errors
- Symptom: newly uploaded materials cannot be found. Cause: the data row is in parsed or indexing, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Symptom: the name, quantity, and date of the same record in the physical examination form and the re-examination application do not match. Cause: the versions of the two materials are not synchronized, and the terminology table is not unified.
- Symptom: after a training failure, empty data rows are left behind, or after changing models the rebuild takes abnormally long. Cause: failed data was not edited or deleted, and the rebuild scope mistakenly covered data pending indexing.
How to verify the setup
Acceptance for this feature: upload one material, observe the data row status flow and the coverage scope of the rebuild task, and confirm that the status flows among parsed, indexing, and indexed and that rebuilding only covers data that has already been indexed.
Business test: sample three terms to check whether their usage is consistent throughout the text, and verify the fields, dates, and signatures of the physical examination form, re-examination application, and restricted major notification.
- Open the data row to check the status, confirm that it is consistent with the interface display, and check the file record and the data row identifier separately.
- Inspect the data rows covered by the rebuild task, and confirm that after changing models only data that has already been indexed is rebuilt.