About search options for the Search Box component

If the application has one or more associated search interfaces, then you can configure text search options for the Search Box component. If there are no search interfaces, then only type-ahead search is supported.

The Search Box component can have:

A search option for each combination of data set and application search interface. When end users select one of these search options, Studio uses the selected application search interface to search within only that data set.
When there are multiple data sets, search options for "All Data".
"All Data" is specific to the Search Box component, and is used to indicate to search across all of the application data sets.

A search interface determines the search behavior for attributes or groups of attributes, and can include rules for:

Relevance ranking
Note that in order for the Search Box to work correctly, each search interface associated with a Studio application must have a relevance ranking strategy.
Matching across multiple attributes
Keywords in context results
Partial matches

For details on available settings for search interfaces, see the Oracle Endeca Server Developer's Guide.

For applications created from file uploads or the Data Source Library, Studio automatically creates a single search interface. See Search configuration for a new data set.

For shared Endeca Server connections, search interfaces are added manually using Integrator ETL. For details on creating search interfaces using Integrator ETL, see the Oracle Endeca Information Discovery Integrator ETL User's Guide.