Skip to main content

Tag Acceptance Models

When integrating Geneea into a Content Management System (CMS), one of the most important decisions is how journalists will interact with the suggested tags.

We categorize these workflows into three models: Opt-in, Opt-out, and Mixed.

General recommendations for all models:

  • Tags should be suggested automatically (e.g., every 60 s when the article changes, when a paragraph is finished, etc.). We do not advise relying on jurnalists to request the tags manually, because they sometimes forget to do so.
  • No tags returned by the Media API should be hidden from the journalist. Filtering of tags by relevance should be done on the side of the service by Geneea, especially when the feedback loop is implemented.

1. Opt-in Model​

In this mode, tags are suggested, but none are applied to the article until a journalist manually selects them.

  • How it works: The CMS displays a list of suggested tags. The journalist selects the ones they want to add to the article. They might add additional tags manually.
  • Filtering: Geneea Media API is configured to return tags above a certain threshold.
  • Pros: 100% human-verified; virtually no incorrect tags are displayed on the public site.
  • Cons: Slow; tags may be forgotten if the journalist is in a hurry.
  • Best for: High-stakes editorial environments where tagging accuracy is more important than speed.

2. Opt-out Model​

In this mode, all the returned tags are automatically applied to the article by default; the journalist might reject them.

  • How it works: The CMS displays a list of suggested tags. The journalist inspects them and removes those they consider incorrect or irrelevant. They might add additional tags manually.
  • Pros: Fast; ensures every article is tagged even if the journalist does nothing.
  • Cons: Higher risk of incorrect or irrelevant tags reaching the public site.
  • Best for: High-volume newsrooms, breaking news, or SEO-heavy workflows where maximum coverage is the priority.

3. Mixed Model (Recommended)​

This is our recommended approach, combining the best of both models above.

  • How it works: The CMS displays all suggested tags split into two groups based on their relevance scores: accepted by default and rejected by default. When the journalist disagrees with Geneea Media API on the relevance of a tag, it is easy to correct: they can move a tag from the accepted to the rejected bin and vice versa.
  • Best for: Most professional newsrooms.
  • Pros: Automates the "obvious" work while leaving the nuanced decisions to the W. It drastically reduces (i) the number of clicks required, and (ii) the need for entering tags manually, while maintaining a high-quality bar.

Notes:

  • We recommend using the threshold of 80 for the split.
  • The CMS should remember when a journalist accepts or rejects any of the tags and maintain that state after the Media API returns updated results. We recommend indicating such "pinned" status visually, distinguishing: accepted explicitly (✓), accepted by default, rejected by default, and rejected explicitly (✗).

Comparison Summary​

ModelDefault tag statusSpeedEditorial Control
Opt-inAll tags are "Suggestions"LowMaximum
Opt-outAll tags are "Applied"HighMinimum
MixedHigh relevance = Applied; Medium and low = SuggestionHighBalanced