What Are Search Scopes?
CES 7.0.5639+ (July 2013)
On the Coveo Master server, you can also centrally define one or more search scopes so that you can later assign to .NET search interfaces from one or more Coveo Front-End servers. Search scopes are defined using filter expressions and/or collections on the local and/or remote Coveo indexes.
When two or more search scopes are assigned to a .NET search interface, the Search In facet automatically appears in the .NET search interface to allow end-users to easily switch between search scopes without having to select another .NET search interface.
Example: In your Los Angeles head office, you can create search scopes that exclusively search
in the Boston and Paris remote indexes within your organization. End-users can select
the desired search scope when needed from the Search In facet that appears in the .NET search interface.
Search scopes are useful when included in a .NET search interface that has a large scope (such as the out-of-the-box All Content .NET search interface) or when you want to include one or more remote indexes. When you plan to assign more than one search scope to a .NET search interface, you typically define search scopes with mutually exclusive scopes so that an end-user can toggle the search between these separate contents.
Note: CES 7.0.5556– (June 2013) Use the deprecated custom search feature (see Configuring a Custom Scope With the .NET Interface Editor).
What's Next?
Centrally defines one or more search scopes using the Administration Tool (see Adding a Search Scope).