What this category's data looks like
This category's data covers three types of materials involved in undergraduate program planning: program plans, course syllabi, and credit structure tables. Sources are academic affairs system exports and departmental submissions, and the update cadence follows the training cycle and course adjustments. Program plans contain training objectives, program duration, and total credits; course syllabi contain course names, credits, class hours, and assessment methods; credit structure tables contain the credit proportions of each module and signature fields. When these three types of materials enter document parsing and chunking, each is stored as an independent data row, respectively serving the roles of overall outline, course details, and credit summary, and the dates and signature information in the fields are used for version comparison.
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). "Version ledger and change records" is then completed by retrieval and subsequent processing.
| Object | Check | Verification action |
|---|---|---|
| Program plan | The training objectives, program duration, and total credits fields are consistent with the credit structure table summary, and the date and signature fields are complete | Check whether the data row status is parsed, indexing, or indexed, and compare the total credits and signing dates of the program plan and the structure table |
| Course syllabus | The course name, credits, class hours, and assessment method correspond item by item in both the program plan and the syllabus | Check the file records and data rows separately, and check whether the course entries are complete after chunking by chunkSize and chunkSplitter |
| Credit structure table | The credit proportions of each module match the total credits of the program plan, and no signature or receipt items are missing | View the data rows under the processing mode corresponding to trainingType, and check whether the module totals in the structure table are consistent with the program plan |
| Version ledger and change records | The current version is unique, old versions are traceable, references are synchronized, and rebuilding only covers data that has completed indexing | After changing one piece of content, check whether the version number and references are updated synchronously, and confirm that the rebuild task coverage is indexed data rows |
Three common errors
- Symptom: The name, credits, or date of the same course do not match across the two materials. Cause: The program plan and course syllabus are submitted independently, without field-level comparison and version synchronization.
- Symptom: The old program plan is still referenced, and the current version is not unique. Cause: Versions are not synchronized, change records are missing, and the retrieval layer still recalls old data rows.
- Symptom: The credit structure table is missing signatures or receipts. Cause: The material circulation step does not validate signature fields, and incomplete records are not intercepted when data rows are stored.
How to verify the setup
Upload one material and observe the data row status transitions and the coverage of the rebuild task.
Change one piece of content and see whether the version number and references are updated synchronously.
- Open the data rows to check the status, and confirm that it is one of parsed, indexing, or indexed and consistent with the interface display
- Check the file records and data rows separately, and confirm that the identifiers of files and data rows are distinguishable