Skip to main content

TRAC: Boolean Special Operators Reference Sheet

This article will provide some practical examples of how to use NEAR, Wildcard and Case Sensitivity operators in TRAC's search set up

1. Wildcard Operator

Requirements

  1. Must be in AND (with at least one non-wildcard term)

    • ACCEPTED: court* AND events

    • REJECTED: court*

    • REJECTED: court* AND event* (because it has no non-wildcard term in the conjunction)

  2. Only prefix wildcards are supported

    • ACCEPTED: range*

    • REJECTED: *range

    • REJECTED: ran*ge

  3. Prefix must have at least four letters

    • ACCEPTED: goal* (4 letters before the *)

    • REJECTED: hat* (only 3 letters)

    • REJECTED: in* (only 2 letters)

  4. Historics Unavailable

    • Currently, wildcard operators can only be used in real-time tracking.

    • If a wildcard is used in a search, the Historics section will not show data sources available (similar to how certain social platforms might not show).

  5. Cannot be used within other special operators

    • REJECTED: BY_TWITTER(steve*)

    • REJECTED: IN_URL(cost*)

    • REJECTED: "blast* doors"~3

  6. Wildcard limit

    • Currently, you can only have up to 5 wildcard terms in a single search. (Hoping to increase to 10/20 soon.)

Example A: (marketing AND strateg*)

Example B: (innov* AND technology)


2. Case Sensitivity

Requirements

  1. Use the operator (!) before the term (or quotes) you want to enforce case sensitivity on

    • ACCEPTED: !"NASA"

    • REJECTED: "Baseball !BAT" (the ! should appear before the quotes, not in the middle)

    • REJECTED: LASER!

  2. Historics Unavailable

    • Currently, the case sensitivity operator can only be used in real-time tracking.

    • If a case sensitivity operator is used, the Historics section will not show data sources (similar to wildcards).

  3. Cannot be used within other special operators

    • REJECTED: BY_TWITTER(!NASA)

    • REJECTED: IN_URL(!deLaGuerra)

    • REJECTED: !"NASA JPL"~3

  4. No limit on the number of case-sensitive terms

    • You can use as many ! operators as you like in a single search (subject to the rule of not nesting them inside other special operators).

Example A: (!"NASA" OR "SpaceX") AND rocket

Example B: economy AND !GDP


3. NEAR Operator

Requirements

  1. Syntax 1: (Term NEAR/N Term)

Syntax 2: ((Group of Keywords) NEAR/N (Group of Keywords))

Where N (≤ 7) represents the maximum number of words that can separate the two terms or keyword groups.

  • You must specify a distance /X to indicate how far apart the two terms/groups can be.

  • ACCEPTED: (elf NEAR/4 warlock)

  • ACCEPTED: ((dwarf OR human OR tiefling OR "half orc") NEAR/4 (rogue OR paladin OR wizard))

  • REJECTED: (game) NEAR (publisher) (missing /X)

  • REJECTED: NEAR (game developer) (missing terms on at least one side)

  • REJECTED: (dwarf OR human) NEAR/6 (rogue OR wizard) (missing opening and closing bracket should be ((Group of Keywords) NEAR/N (Group of Keywords))

  1. Historics Unavailable

    • Currently, the NEAR operator can only be used in real-time tracking.

    • If a NEAR operator is used, the Historics section will not show data sources (similar to wildcards and case sensitivity).

  2. Cannot be used within other special operators

    • REJECTED: BY_TWITTER(george NEAR/3 carver)

    • REJECTED: IN_URL(graphics NEAR/3 unit)

  3. Cannot include other operators inside the NEAR groups

    • You can only include quoted phrases and OR.

    • REJECTED: ((bath AND bubble) NEAR/4 (soap))

    • REJECTED: (!"SpaceX") NEAR/5 (elon)

    • REJECTED: (shelf*) NEAR/4 (foods)

  4. NEAR/X distance limit

    • X can be up to 7.

    • ACCEPTED: (soccer NEAR/7 stadium)

    • REJECTED: (football NEAR/10 stadium)

  5. No limit on how many NEAR operators

    • You can use as many NEAR operators as you wish in one search.

Example A: ((apple OR banana) NEAR/4 ("fruit salad"))

Example B: ("climate change" NEAR/6 (adaptation OR mitigation))

Did this answer your question?