What this category's data looks like
Vocational college skills competition organization involves three types of materials: competition regulations, registration forms, and training plans. The sources are the competition event executive committee, college academic affairs, and coaching teams. They are updated in batches as the competition schedule progresses. Fields include contestant name, event name, group, date, quantity, signature, and receipt. Regulations provide the basis for events and rules, registration forms carry contestant and team information, and training plans record stage arrangements and coach signatures. After the materials enter the parsing and chunking stage, each becomes a searchable data row, used for subsequent terminology unification and generation of comparison drafts. Multilingual materials and terminology processing require the same term to be consistent throughout the entire text and the translated name to be traceable back to the original text. Therefore, the name, quantity, date, and signature fields of the three types of materials need to remain verifiable after parsing and chunking.
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 terminology list and comparison draft are then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Competition regulations | Event name, group, date, and signature fields must match the registration form and training plan | Open the data row to check whether the status is parsed, indexing, or indexed, and compare the event name and date in the regulations and registration form |
| Registration form | Contestant name, quantity, group, and receipt fields must be consistent with the training plan | Check the identity identifiers of the file record and the data row separately, and check whether the quantity and date in the registration form and training plan are consistent |
| Training plan | Stage arrangements, coach signature, and date fields must be synchronized with the regulation version | View the data rows covered by the rebuild task, confirm that only data with completed indexing is covered, and check whether signatures and receipts are complete |
| Parsing and chunking | Chunking parameters and training type affect data row generation and index status | Check whether chunkSize, chunkSplitter, trainingType, and the data row status transitions are consistent |
Three common errors
- Phenomenon: The same contestant's name is written differently in the registration form and training plan. Cause: The two materials were entered separately, terminology was not unified, and cross-material comparison was not performed after parsing and chunking.
- Phenomenon: The regulations have been updated, but the training plan still references the old version's dates and quantities. Cause: The versions were not synchronized, and data pending indexing was mixed with data with completed indexing.
- Phenomenon: The registration form lacks a coach signature or receipt, but the regulations and training plan show them as complete. Cause: The signature and receipt fields were not parsed and stored together with the materials, and verification only looked at the interface without looking at the data rows.
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; status values only recognize parsed, indexing, and indexed, and rebuild only covers data with completed indexing.
Business test: Sample three terms to check whether their wording is consistent throughout the entire text, and confirm that the translated names can be traced back to the original text.
- Open the data row to check whether the status is parsed, indexing, or indexed, and confirm that the interface display is consistent with the data row status.
- Check the identity identifiers of the file record and the data row separately, then check whether the data rows covered by the rebuild task only contain data with completed indexing.