What this category's data looks like
The data for this category looks like this: The establishment and annual reports of Sino-foreign cooperative education institutions involve three core types of materials: the establishment application, the cooperation agreement, and the articles of association. Material sources include standard forms from the approving authority, documents signed by both cooperating parties, and annual submission receipts. The update rhythm is based on the nodes of establishment approval, change of cooperation term, amendment of the articles of association, and annual report submission. Field characteristics are concentrated in institution name, education level, enrollment scale, partner name, signing date, and signature and seal positions. After materials enter the document parsing and chunking stage, the establishment application handles field extraction and date comparison, the cooperation agreement handles quantity and rights-and-responsibilities verification, and the articles of association handle name and governance structure validation. Together, the three support the establishment of a version ledger and change records.
Configuration and implementation checks
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 version ledger and change records are then completed by retrieval and subsequent processing. After parsing is completed, parsing chunks are immediately persisted as visible data rows and bound to a unique data identifier. Indexing flows through three states, and data pending indexing does not participate in recall.
| Object | Check | Verification action |
|---|---|---|
| Establishment application | Whether the institution name, education level, enrollment quantity, signing date, and signature and seal are consistent with the cooperation agreement and articles of association | Separately check the document records and data rows, confirm the field values and date/signature positions, and check whether fields span chunks after chunking by chunkSize and chunkSplitter |
| Cooperation agreement | Whether the partner name, cooperation term, quantity, and date match those in the establishment application and articles of association | Open the data row and check whether the status is parsed, indexing, or indexed, and confirm that the processing mode corresponding to trainingType is consistent with the interface display |
| Articles of association | Whether the institution name, governance structure, signing date, and signature receipt are consistent with the other two materials | Check whether the data rows covered by the rebuild task include only indexed, and confirm that the old version is traceable and references are synchronized |
| Version ledger and change records | The current version is unique, the old version is traceable, and references are synchronized | After changing one piece of content, check whether the version number and references are updated synchronously, and check whether the rebuild scope covers only data that has completed indexing |
Three common errors
- Phenomenon: The same institution name is written inconsistently in the establishment application and the articles of association. Cause: The two materials were entered separately and no field-level comparison was performed, and the versions were not synchronized, so references still point to the old version.
- Phenomenon: The enrollment quantity in the cooperation agreement does not match the annual report data. Cause: The quantity field spans chunks during parsing and chunking or is not bound to the same data identifier, and retrieval hits old-version content.
- Phenomenon: The articles of association lack a signature or receipt, and an empty data row remains after training fails. Cause: The material entered parsing before signing was completed, and the index status remained at parsed or indexing, not reaching indexed.
How to verify the setup
Acceptance for this feature: Upload one material, observe the status transitions of the data row and the coverage scope of the rebuild task, and confirm that the status transitions among parsed, indexing, and indexed and that rebuild covers only indexed data rows.
Business test: Change one piece of content, check whether the version number and references are updated synchronously, and verify the processing results corresponding to chunkSize, chunkSplitter, and trainingType.
- Open the data row and check whether the status is consistent with the interface display, separately verify the file record and the data row identity, and confirm that data pending indexing does not participate in recall.
- View the data rows covered by the rebuild task, confirm that they include only data that has completed indexing, that the rebuild scope after changing the model meets expectations, and that the old version remains traceable.