What this category's data looks like
This page focuses on data versions and change maintenance in graduate training process management, covering three types of materials: training plans, thesis proposals, and mid-term assessment forms. A training plan contains course credits, supervisor signature, and date; a thesis proposal contains the topic title, review comments, and receipt; a mid-term assessment form contains the assessment conclusion, grade, and signature. The materials come from electronic documents and scanned copies submitted at each training stage, and the update cadence changes as the semester progresses, review milestones occur, and signature receipts are supplemented. After entering the document parsing and chunking feature, the training plan serves as the baseline for course and credit fields, the thesis proposal serves as the comparison for topic and review information, and the mid-term assessment form serves as the verification for assessment conclusions and dates. Together, the three support the version ledger and change records, ensuring that the current version is unique, old versions are traceable, and references stay in sync.
Configuration and implementation checks
This step is executed by the parsing and training task (server-side task), which outputs data rows and index status (parsed, indexing, indexed). The "version ledger and change records" are then completed by retrieval and subsequent processing. After parsing is complete, 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 |
|---|---|---|
| Training plan | Course name, credit count, supervisor signature, and date are verifiable across versions | Check the file record against the data row identifier, see whether the data row status matches the interface, and confirm that the signature and date fields are complete |
| Thesis proposal | Topic title, review comments, and receipt date are consistent with other materials | Check the file record and the data row separately, and verify whether the name and date of the same record match across the two materials |
| Mid-term assessment form | Assessment conclusion, grade, and signature do not conflict with the training plan date | Open the data row to check its status, confirm that the version was not synchronized when a signature or receipt is missing, and check whether the reference points to the current version |
| Data row | Is in one of the three states and matches the interface display; rebuild only covers data whose indexing is completed | Inspect the data rows covered by the rebuild task, and check the processing mode corresponding to chunkSize, chunkSplitter, and trainingType |
Three common errors
- Symptom: the name, quantity, and date of the same record do not match between the training plan and the mid-term assessment form. Cause: the version was not synchronized, the old version is still referenced, and the change was not written back to the ledger.
- Symptom: the thesis proposal is missing a signature or receipt but has already entered the retrieval results. Cause: successful parsing does not equal a retrieval hit, and the index status and signature/receipt were not verified in a linked manner.
- Symptom: a newly uploaded material cannot be found, and a failed training run leaves an empty data row. Cause: data pending indexing does not participate in recall, failed training data was not cleaned up, or the rebuild scope mistakenly covered data pending indexing.
How to verify the setup
Feature acceptance: upload one material, observe the data row status transitions and the coverage scope of the rebuild task, confirm that the statuses are parsed, indexing, and indexed in order, and that switching models rebuilds only data whose indexing is completed.
Business test: change one piece of content, see whether the version number and references are updated in sync, whether the old version is traceable, and whether the current version is unique.
- Open the data row to check its status, confirm that it matches 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 only data whose indexing is completed is covered and that data pending indexing does not participate in the rebuild.