Airgentic Help
Filters are controls visitors use to narrow search results.
Examples include:
Filters depend on indexed Search Fields. Before a field can be used as a filter, it must exist in the search index and be enabled as a search filter.
Open Search Configuration > Fields to configure Search Fields. For a typical filter, enable Show this field as a search filter, then use Search Configuration > Filters to review and tune filter-specific settings.
Some advanced filter options may initially be visible only to Airgentic support or superusers.
Filters have two separate settings:
For example, a Button list can be either:
The field editor shows an example beside the selected Filter style so you can see the kind of control visitors will get.
| Filter style | What visitors see | Best for |
|---|---|---|
| Button list | A list of clickable values with counts. | Category/type filters, short lists, or filters that should look like navigation. |
| Checkbox list | A list with checkboxes. | Multi-select filters where visitors may choose several values, such as Format, Delivery, or Location. |
| Single-select menu | A dropdown menu. | Compact single-select filters where space is limited or the list is not important enough to show permanently. |
| Hierarchy / drill-down | A nested path such as Subject > Engineering > Civil. | Category trees, sections, topics, or paths with parent/child levels. |
| Range | Date presets, custom date range, or min/max numeric controls. | Dates, prices, years, durations, or numeric values. |
| On/off toggle | A switch or yes/no control. | Boolean filters such as “Show available courses only”. |
Not every service needs every filter style.
Most website filters use Button list or Checkbox list.
The Sort by dropdown in Advanced settings controls the order of values inside a filter.
Common choices:
Use Selection mode to decide whether the filter behaves like a drill-down or a multi-select filter.
| Selection mode | Behaviour | Example |
|---|---|---|
| Single value at a time | Selecting a value replaces the previous value. Other values in the same filter narrow or disappear because the result set is now constrained to the selected value. | Type, Category, Section. |
| Multiple values | Visitors can select more than one value in the same filter. | Delivery, Format, Campus, Subject tags. |
Use Single value at a time when the values are mutually exclusive or when the filter should feel like navigation. A common example is Type: a result normally belongs to one type, such as News, Events, Policies, or Courses.
Use Multiple values when visitors reasonably expect to combine values. For example, a visitor might want results that are Online or On campus, or documents that are PDF or Word document.
The Single-select menu style is single-select by default. A Button list or Checkbox list can also be configured as single-select when that visual style is preferred.
For filters with Selection mode: Multiple values, choose how multiple selected values are matched.
Most multi-select filters should use Match any selected value. If a visitor selects Online and Evening, results can match either value.
Use Must match all selected values only for multi-valued fields where the same page can contain several values and the visitor expects every selected value to be present. For example, a course tagged with both Online and Evening would match when both are selected.
This matching setting does not usually matter for single-select filters because visitors can only choose one value at a time.
| Requirement | Recommended setup |
|---|---|
| Type/category list where clicking one value should hide or narrow the other values | Button list + Single value at a time. |
| Compact Type/category control | Single-select menu. |
| Format filter such as PDF, Word document, Web page | Checkbox list + Multiple values + Match any selected value. |
| Delivery filter such as Online, In person, Blended | Checkbox list or Button list + Multiple values + Match any selected value. |
| Field where a page can have several tags and all selected tags must be present | Checkbox list + Multiple values + Must match all selected values. |
| Subject tree such as Engineering > Civil | Hierarchy / drill-down. |
| Date filter | Range with quick presets, custom date range, or both. |
| Yes/no filter | On/off toggle. |
Enable Multi-valued when a single page or document can have more than one value for the field. If the website stores those values in one metadata string, set Split multi-value field on to the separator used by the website, such as a comma.
Use Hierarchy / drill-down path as the field type when the value has levels. The hierarchy delimiter and maximum depth are shown in Advanced settings only for hierarchy fields.
Examples:
| Requirement | Recommended setup |
|---|---|
| Delivery filter with values such as Online and In person | Keyword field, list filter. |
| A page with multiple delivery values in one metadata field | Enable Multi-valued and set the split separator. |
| Subject area drill-down such as Engineering > Civil | Hierarchy field, hierarchical filter. |
Different search scopes may show different filters.
For example:
This helps keep the search interface relevant for each type of result.
For example, the Programs scope can show Delivery, Sector, and Credential, while the News scope can show different filters.
Configure scope-specific filter visibility on Search Configuration > Scopes. Category mappings are managed separately on the Categories tab.
See Configuring Search Scopes.
Filter values should be clean and consistent.
For example, these should usually become one value:
onlineOnlineOnline Learningweb-basedAirgentic can normalise values using canonical labels, synonyms, casing rules, and allowed-value lists.
Changing how a filter is displayed may not require reprocessing. Changing the field used by a filter usually does.
Typical examples:
| Change | Typical impact |
|---|---|
| Rename filter label | No reprocess. |
| Change filter style, selection mode, or multiple-value matching | No reprocess. |
| Change filter visibility in a scope | No reprocess. |
| Add filter from existing indexed field | No reprocess. |
| Add new HTML metadata field for filter | Re-extract or index update. |
| Add new XPath or JSON-LD field for filter | HTML Processing, then indexing. |
| Add new URL mapping rules field for filter | Index update. |
| Change value normalisation | Re-extract or reindex. |
When you save field changes on Search Configuration > Fields, the admin console explains whether HTML Processing, an index update, or no processing is needed.
Some advanced filter options, such as value normalisation and scope-specific visibility, may initially be managed by Airgentic support or superusers.