Summary
Enabling topic tagging on a preset produces no visible tags. Tagging runs and writes to the topic_tags Postgres table, but nothing ever reads them back.
Details
- Write path works:
topic_tag_stage → indexer_actor._replace_topic_tags_if_needed → topic_tag_repo.bulk_insert (table topic_tags, document-level).
- Read path is missing:
topic_tag_repo.get_by_document / search exist but are never called anywhere.- No API route exposes topic tags.
- No search / document / chunk response includes them.
- The admin UI only configures tagging (
presets.tsx) — there is no view that displays generated tags.
So tags are write-only; they never reach a user.
Suggested fix
Add a read path — an API endpoint and/or fold tags into the document/search responses — and surface them in the admin UI (e.g. on the document detail view).
Area: full-stack (backend read endpoint + admin-ui display).
Summary
Enabling topic tagging on a preset produces no visible tags. Tagging runs and writes to the
topic_tagsPostgres table, but nothing ever reads them back.Details
topic_tag_stage→indexer_actor._replace_topic_tags_if_needed→topic_tag_repo.bulk_insert(tabletopic_tags, document-level).topic_tag_repo.get_by_document/searchexist but are never called anywhere.presets.tsx) — there is no view that displays generated tags.So tags are write-only; they never reach a user.
Suggested fix
Add a read path — an API endpoint and/or fold tags into the document/search responses — and surface them in the admin UI (e.g. on the document detail view).
Area: full-stack (backend read endpoint + admin-ui display).