Search Interface
One: Concept
It is a named set of properties or dimensions that have been enabled for record search. It enables us to search for one or some dimensions or properties to control the behavior of record search.
Two: the main function
1 Relevance Ranking
2 Matching across multiple properties or dimension(cross-fields)
3 Keyword in context results
4 Partial Match
三：Options for enabling cross-field matches
Cross-Field: For example, if you search for "Nike shoes", if you can cross-field, then MDEX Engine will return all record results matching Brand=Nike and Type=shoes.
There are three setting methods in Search Interface:
- Always; cross-fields matching is possible in any case
- Never: will not match in any case
- On Failure: MDEX Engine will only match across fields when matching a single property or dimension fails.
By default, the record search query will match according to each member property or dimension in the search interface, and then return a combined result set. For example, when you search for Nike Shoes, there are 2 members in the search inerface:
property: type AND dimension: brand, then he first matches type, then gets result set A, then matches brand, gets result set B, and finally combines A and B as a result set.
Sometimes matching against each member is unnecessary, for example a customer searching for Nike Shoes may only be interested in a range of products, but a record search may only return some product name containing the terms Nike and Shoes. In this case, cross-field can be used, and it will match across multiple properties and dimensions in the search interface.
Four: How Cross-Filed Works
When a search interface member is multi-assigned in the record (like the author of the book, there may be more than one)
MDEX Engine will treat them separately, they come from different attributes, a search matching 2 or more terms for the same attribute, MDEX Engine will treat it as a Cross-Filed match.
For example, there are three records:
displayName: Nike ;
displayName: Shoes;
displayName: Nike Shoes;
Then a search for "Nike Shoes" for this displayName will find them all, even if they find that Nike Shoes exist.
The Or connector used by default is queried according to the search interface.
Ntk=actor|director&Ntt=deniro|deniro Query the result that the actor matches deniro and the director matches deniro
Ntk=moviepeople&Ntt=deniro Query the result that the actor matches deniro or the director matches deniro (if the search interface only has actor property and director dimension)