Analysis modes
An analysis mode tells the engine how aggressively to parse and match. Strict modes accept fewer alternatives, flexible modes accept more.
Catalog#
| Mode | Behavior |
|---|---|
STRICT | Exact matches only. Fastest, lowest recall. Use when input is known-clean. |
MODERATE | Allows minor variations (missing words, light misspellings). Balanced default. |
FLEXIBLE | Aggressive matching: accents tolerated, multiple typos, partial input. Highest recall, more alternatives. |
oneStop Analysis Mode | Tuned for OneStopAnalyze. Optimized for autocomplete and interactive capture. |
SERP TEST | Reproduces Canada Post's SERP evaluation rules. Use only for SERP audits. |
nCode Reserved Analysis Mode | Internal reserved mode. |
Picking a mode#
- Real-time autocomplete →
oneStop Analysis Mode. - Form-validation on submit →
MODERATE(good balance of strictness and recall). - Bulk back-office cleanup →
FLEXIBLE(catch every salvageable record; deal with ambiguity downstream). - SERP audit run →
SERP TEST(the only mode Canada Post accepts for SOA submissions). - Already-validated input →
STRICT(skip recovery work; flag any deviation as an error).
The mode interacts with Correction styles: an aggressive mode may surface alternatives that the configured correction style then renders in a different case or with different keyword spelling.
Custom modes#
Define one with SetAnalysisMode.