In the Filters section of the Search bars tab, a radar icon is available for each metadata element as follows:
If the radar icon is selected for one or more metadata keys, a new option called Contextual search appears in the Quick filters menu after expanding the Filters window as follows:
When an end-user selects the Contextual search option, the search results they obtain will only contain other content that shares certain metadata (the metadata for which an administrator selected the radar icon) with the content currently open in the Reader page.
Example
In the Filters section of the Search bars tab, an administrator has configured the following metadata to appear as filters when searching in all documents:
-
Version_FT
-
Category
-
Platform
-
audience
The following image shows that the radar icon is selected next to Category
and Platform
:
Imagine that an end-user is reading a document in the Reader page that has the metadata Category: Technical Notes
as follows:
The end-user stops reading and performs the following actions:
-
The end-user selects the search bar in the header of the Reader page to search in all documents.
-
They select the Contextual search option in the Quick filters menu of the Filters window.
As soon as the end-user selects the Contextual search option, the checkbox next to the Technical Notes
value for the Category
metadata key is automatically selected as follows:
This filter is automatically selected because contextual search means searching for other content that shares the same metadata as the content currently open in the Reader page.
Since the document open in the Reader page has the metadata Category: Technical Note
, and since an administrator selected the radar icon next to the Category
metadata in the Reader page administration interface, the end-user's query is automatically filtered to only return other content that also has the metadata Category: Technical Note
.
Although the administrator also selected the radar icon next to the Platform
metadata, this filter is not automatically selected because the document the end-user has open in the Reader page does not have this metadata configured.