What this category's data looks like
This page is for kindergarten game activity organization scenarios. The materials come from the kindergarten's observation records, area activity plans, material placement lists, activity objective tables, and reflections turned into next week's plans. After these materials enter parsing and training tasks, each has a different role: observation records and area plans are used to check goal achievement and plan updates, material placement lists are used to check whether quantities meet activity needs, and reflection records are used to determine whether next week's plan carries forward this week's issues. The update rhythm usually rolls by week or by activity cycle. Field characteristics include activity name, area, placed materials and quantities, observation points, objective items, reflection conclusions, and next week's adjustments. After material parsing is completed, it is immediately stored as visible data rows and bound to a unique data identifier for subsequent retrieval and basis item generation.
Configuration and implementation checks
Parsing and training tasks (server-side tasks) only output data rows and index status (parsed, indexing, indexed). Basis items that can point back to the original text must be handled by retrieval and subsequent processing. Data pending indexing is naturally isolated at the retrieval layer and is not recalled. Changing models only rebuilds data that has already completed indexing.
| Object | Check | Verification action |
|---|---|---|
| Observation records and area plans | Whether the observed behavior can correspond to the objective items in the area plan; when objectives and observations do not match, it is necessary to point back to the original text for verification | Open the data row to check whether the status is indexed, then check whether the observation records and the objective items in the area plan can be matched one by one |
| Material placement list | Whether the placed quantity meets the activity needs; when materials are insufficient, it is necessary to point back to the specific activity and area in the list | Check whether the data row status and the file record identity can be distinguished, then search material quantities by activity name |
| Reflections turned into next week's plan | Whether the reflection conclusions are carried into next week's plan; when the plan is not updated, it is necessary to point back to the original reflection text | Check whether the data rows covered by the rebuild task only include data that has completed indexing, then check the corresponding items between the reflections and next week's plan |
| Activity objective achievement | Whether the objective items are consistent with the observation evidence; when objectives and observations do not match, it is necessary to point back to the original objective table text | Check the file records and data rows separately, then use chunkSize and chunkSplitter to see whether chunking preserves the context of the objective items |
Three common errors
- Phenomenon: newly uploaded materials cannot be found. Cause: the data row is in parsed or indexing status, and data pending indexing is naturally isolated at the retrieval layer and is not recalled.
- Phenomenon: material quantities do not match activity needs. Cause: the material placement list was not updated with the area plan, and insufficient materials and an unupdated plan appear at the same time.
- Phenomenon: objectives do not match observation records. Cause: the observation records did not point back to the original objective table text, and old objective items were reused when reflections were turned into next week's plan.
How to verify the setup
This feature acceptance: upload one material, observe the data row status transition and the coverage scope of the rebuild task; the status should go from parsed to indexing to indexed, the rebuild task should only cover data rows that have completed indexing, and check the processing mode corresponding to trainingType.
Business test: ask a basis question across materials, see whether the answer gives a source that can be pointed back to, and check whether the number of cited items and the tokens of the cited text are recorded separately.
- Open the data row to check whether the status is indexed, and separately check the identity identifiers of the file record and the data row.
- Check whether the data rows covered by the rebuild task only include data that has completed indexing, and confirm that data pending indexing did not participate in the rebuild.