Fix a tag and approve a health claim

Tags decide which items reach which users. The enrichment job proposes them; you have the last word. A tag you set or approve is never overwritten by the job.

Fix a tag#

1. Open Catalog and find the item. Search, or filter by kind, collection, status, tag kind or enrichment.
2. Open the item. Its tags are grouped by kind, each with a weight.
3. Remove a wrong tag, add a missing one, or change a weight. The tag picker offers the tags of your taxonomy.
4. Save. The change is written to the audit log with your name.

Tag kinds and their colours on the chips:

What the enrichment job may and may not do#

• It tags only against your taxonomy. It cannot invent a tag.
• It writes its tags with source llm. Editor tags and imported tags are never touched.
• It re-tags an item only when the item's text changed.
• An item it could not tag is marked failed and kept for review.

Approve a health claim#

A health-claim tag says the item claims a health effect, such as "improves sleep". Those tags arrive with approved = false and wait for an editor. They show in the Catalog summary as "claims awaiting approval".

1. Open Catalog and filter on claims awaiting approval.
2. Open the item and read the text the claim is based on.
3. Approve the claim tag if the item supports it. Remove it if it does not.
4. A second person approves as well. Health claims follow the two-person rule: one person requests, another approves. The request, approvers and outcome go to the audit log.

Once an editor has approved a claim tag on an item, the job keeps it approved on later runs.

A tag is a health claim when the taxonomy marks it with health_claim: true (GET and PUT https://patterna-api.orven.am/v1/taxonomy), or when it has the claim: prefix, for example claim:verbetert-slaap. Bulk actions never approve a health-claim tag: those always wait for a person.

Many items at once#

Select several items in the table, then choose Approve tags, Add tag, Re-enrich or Archive. Each bulk action writes one audit note.

Through the API#

Your backend can set editor tags directly. Use the tag slugs of your taxonomy. Pass the item's kind as a query parameter; without it the call looks for a document.

curl -sS -X PUT "https://patterna-api.orven.am/v1/catalog/items/doc_1042/tags?kind=document" \
  -H "Authorization: Bearer $PATTERNA_INGEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tags": [
      { "tag": "magnesium", "weight": 1, "approved": true },
      { "tag": "claim:verbetert-slaap", "weight": 1, "approved": false }
    ]
  }'

weight defaults to 1 and approved to true. The call sets the item's editor tags; send the full list you want.

This call does not go through the two-person rule: a claim tag sent with approved: true is approved at once. Send claim tags with "approved": false and approve them in the panel, so a second person signs off.

Check the result#

Open the item again. The tag chips show the new state and the enrichment history shows who changed what. If you want to know how good the job's tags are overall, use the gold set in Catalog: build a sample, fill it in, upload it, and read the precision and recall per tag kind.