Managing content tags

In the admin: Content tags — the screen this page documents (opens in the running app).

What/why: Content & media — what this screen manages and why it exists.

Purpose: review the facet tags the enrichment engine proposes for ingested content — accept, reject, or correct them — so blog posts, projects, and resources become retrievable by the same facets the guided flow uses.

When to use

• After a corpus ingestion or an enrichment pass has run and proposals are waiting for review.
• Auditing which tags are live on content, or re-running the enrichment pass after the facet vocabulary changed.

Prerequisites

• Admin access with the edit_data capability (any data_editor or admin role).
• Corpus content to tag — see Managing the corpus.

Steps

1. Open Admin → Content tags (/admin/content-tags). The header counts what's to review, live, and rejected.
2. To generate proposals for untagged content, click Run enrichment pass. Nothing is applied silently — every auto-tag lands as a proposed row.
3. For each proposal:
   • Accept — the tag goes live and is consumed by guided-flow retrieval.
   • Reject — the proposal is remembered and never re-proposed for that item/facet.
   • Edit — correct the facet value first, then accept the corrected tag.
4. Every accept/reject/edit is recorded in the audit trail.

Behavior guarantees

• Proposals never affect retrieval until accepted; rejected proposals are never re-proposed.
• The pass only scores currently-untagged, active corpus items — re-running it does not churn reviewed tags.

For the engine, data model, and how accepted tags are consumed by retrieval, see the content enrichment reference.