What this category's data looks like
This page addresses the scenario of degree conferral and certificate information reporting. Materials come from degree application forms, thesis review forms, defense resolutions, and certificate receipts, and the update cadence follows batch reporting and material supplementation. The degree application form carries the applicant's identity, discipline, and date fields; the thesis review form carries the review conclusion, reviewers, and signatures; the defense resolution carries the defense date, voting result, and signatures; the certificate receipt carries the collection record. During multilingual materials and terminology handling, the name, quantity, and date of the same record must be consistent across materials, translated names must be able to refer back to the original text, and a missing signature or receipt is considered unclosed. After materials enter parsing and training tasks, each becomes a retrievable data row, for subsequent generation and verification of the unified glossary and comparison draft.
Configuration and implementation checks
This step is executed by parsing and training tasks (server-side tasks), outputting data rows and index status (parsed, indexing, indexed). The unified glossary and comparison draft are 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; the index transitions through three states, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Degree application form | Fields, dates, and signatures must be aligned item by item with the thesis review form and defense resolution | Check whether the data row status is parsed, indexing, or indexed, and inspect the chunkSize and chunkSplitter records |
| Thesis review form | The review conclusion, reviewers, and signatures must be consistent with the date and voting result of the defense resolution | Check whether the identifiers of the file record and the data row are distinguishable, and record trainingType |
| Defense resolution | The defense date, voting result, and signatures must be closed with the collection record of the certificate receipt | Open the data row to check the status, and confirm that the rebuild task only covers data whose indexing has been completed |
| Certificate receipt | The name, quantity, and date of the collection record must be consistent with the degree application form | Check the file record and the data row separately, and confirm that the three index states are consistent with the interface display |
Three common errors
- Symptom: The name, quantity, or date of the same record does not match between the degree application form and the defense resolution. Cause: Multilingual materials and terminology handling are not unified, and material versions are not synchronized.
- Symptom: The certificate receipt is missing or the signature field is blank, so the reporting materials cannot be closed. Cause: The material supplementation step has no receipt, and versions are not synchronized.
- Symptom: Newly uploaded materials cannot be found. Cause: The data row is still in parsed or indexing, and data pending indexing does not participate in recall.
How to verify the setup
This feature acceptance: Upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the three index states parsed, indexing, and indexed are consistent with the interface display, and check the records of the three identifiers chunkSize, chunkSplitter, and trainingType.
Business test: Sample three terms and check whether their spelling is consistent throughout the entire document, confirming that the same term is consistent throughout and that translated names can refer back to the original text.
- Open the data row to check the status, and confirm that it is in one of the three states and consistent with the interface display.
- Check the file record and the data row separately, and confirm that the identifiers of the file and the data row are distinguishable.