Multi-tag retrieval must state AND versus OR

What it is

One object can carry many tags. Ticking two words in a filter may mean intersection (both) or union (either). The word “tags” does not say which. The surface has to write the current logic, and the result count has to move in the direction that logic implies. This is not whether words are coined or preset. It is how combined words are evaluated. Folder groups in a save-for-later list and keywords in a search box are nearby analogies, which is why the logic has to be explicit.

Why it happens

Everyday “I want budget and contract” can mean both conditions, or both piles. Checkboxes look like adding constraints, so people expect fewer results (AND). A tag cloud looks like picking topics, so people expect more (OR). When the real operator contradicts the control, the set is either terrifyingly empty or as large as no filter. Count changes on each tick are the only test of the hypothesis: 40 to 8 after a second word looks like AND; 40 to 70 looks like OR. The operator cannot be AND for some tags and OR for others unless those groups are drawn. Negation (not this word) is a third operator; mixing it into the same ticks scrambles AND/OR further.

Studying it

A corpus with known tag combinations. Ask for “client A and contract” and “client A or contract.” Compare unlabeled logic, labeled AND, labeled OR, and whether the count updates on each tick.

Independent variables: default operator, whether copy says “all of / any of,” whether the result count is visible. Dependent variables: correctness on AND versus OR tasks, whether people can self-correct after spotting the opposite operator, whether an empty set leads to switching operator.

A lab that writes “please use AND” in the brief measures vocabulary, not UI. Use the product’s own filter bar. Do not fold search-box keyword match into tag logic.

Where it stops holding

One tag per object has no AND/OR issue. Faceted filters (type, date, tags in separate columns) are usually OR inside a column and AND across columns; write that per column, not one sentence on tags only. A natural-language search “tagged A and B” can fight the filter bar’s default; the two should match, or the results should name which operator ran.

Applying it

• Fix the current operator next to multi-tag filters: “contains all selected tags” or “contains any selected tag,” with a switch.
• Update the result count on every add or remove. On empty, hint that switching to any-of is possible.
• Exclusion is an explicit “does not contain,” not a stateless chip shared with inclusion ticks.
• Verify: three classes of items—both A and B, only A, only B. Ask for items with both. If the operator is unwritten and only-A items appear, the logic was not stated. After switching operator, count direction must match the copy.

Related

• Within the group: H8.10.1 Tag systems need user-defined labels, not only presets · H8.10.3 Unbounded tagging destroys retrieval value · H8.10.4 System tags and user tags need a visible source
• Adjacent: H8.13 Content Search and Location · G3.08 Filters · G1.06 Faceted Classification
• Search terms: tag intersection · AND versus OR · faceted filter