Airgentic Help
Search scopes control the top-level search views or tabs visitors use to move between result types.
Examples:
Scopes are configured from Search Configuration > Scopes & Facets. During rollout, this tab may be visible only to Airgentic support or superusers.
A scope can control:
| Setting | What it does |
|---|---|
| Label | The tab name visitors see, such as Programs. |
| ID | The stable internal name used in configuration and URLs, such as programs. |
| Page type | The indexed category value this scope filters to, such as Programs. |
| Visible | Whether the scope appears as a tab in the search UI. |
| Filters shown in this scope | Which enabled Search Fields appear as filters when the scope is active. |
| Sort | The default sort for this scope, such as relevance or date order. |
| Sort options shown in this scope | Which sort choices visitors can see when this scope is active. |
| Result template | The result display template, usually default. |
| Advanced filter JSON | A power-user override for unusual scope filters. |
For most services, each scope maps to a page_type value. For example, the Programs scope filters results where page_type is Programs.
Scopes work with categories and Search Fields:
page_type assigned to each indexed page.delivery, credential, or subject.Example:
| Scope | Page type | Filters shown |
|---|---|---|
| All | All results | No filters, or broad filters only. |
| Programs | Programs |
Format, Delivery, Credential, School. |
| Courses | Courses |
Course Location, Course Start Date, Course Subject. |
| News | News |
Date, Topic. |
The Global Scope Settings panel controls how the scope list behaves.
| Setting | Description |
|---|---|
| Show All tab | Shows an All tab that searches across every category. |
| Default scope | The scope selected when search first opens. |
| Discover from page type | Allows the search UI to create tabs directly from indexed page type values. Turn this off when only configured scope rows should appear. |
| Append missing categories | Adds category mappings that are not already listed as scope rows. Configured scopes stay first; missing categories are appended after them. |
For enterprise-style search pages, it is usually best to configure the important scopes explicitly so their filters and default sort are predictable.
The Page type dropdown is built from:
page_type values, when availableIndexed values appear after crawling or reindexing. If the value you need does not exist yet, use Custom value so you can configure the scope before indexing is complete.
Each scope can have a default sort and a curated list of sort options shown to visitors.
Relevance uses the normal Airgentic hybrid ranking. Field-based sorts, such as date or alphabetical order, use eligible indexed fields.
Sort options are generated from Search Fields that can safely be sorted, including:
Text and hierarchy fields are not usually shown as sort options.
The scope's configured Sort is the default selected option. Sort options shown in this scope controls the dropdown list users can choose from. This is useful when the full generated list is too long, or when some sorts only make sense for particular tabs.
For example, a Programs scope might expose Relevance, Credential, Delivery, and School sorts, while a News scope might expose only Relevance and Date sorts.
When visitors change the sort in the search UI, that choice applies to the current search. If a visitor arrives with a URL requesting a sort that is not exposed for the active scope, Airgentic falls back to the scope's configured default sort.
Most scopes should use the normal Page type dropdown.
Use Advanced filter JSON only when a scope needs a custom filter that cannot be represented by a single page_type value. For example, Airgentic support may use it for a scope that combines several categories or applies a more specific metadata filter.
When Advanced filter JSON is supplied, it overrides the normal Page type setting for that scope.
Changing which filters appear in a scope usually does not require reindexing.
Reindexing or reprocessing may be needed when:
page_type valuesUse Search Configuration > Preview or the live search page to confirm scopes, filters, counts, and sorting after saving.