CoreMedia Blueprint comes with a content type called
Personalized Search that represents a parametrized search query. You can use
SearchFunctions to enrich the query String, which will be evaluated at request
processing time. After evaluation, the SearchFunctions are replaced with values
from contexts resulting in a personalized search query.
CoreMedia Blueprint is shipped with the following
SearchFunctions configured:
| Search Function | Description |
|---|---|
contextProperty |
A search function that adds the value of a single context property to a search string. You can use the following parameters:
Example:
The context named "bar" contains a property "foo" which has a
value "42". Then, the search function
|
userKeywords |
A search function that selects from a user's context a set of keys that fulfill a weight constraint. You can use the following parameters:
Example:
The context object named myContext contains the properties
( |
userSegments |
A search function that selects the set of user segments the active user belongs to. You can use the following parameters:
Example:
The context object named "myContext" contains the properties
('content:42', true), ('content:44', false),
('content:46', true). Then, the search function
|
Table 8.12. Predefined SearchFunctions in CoreMedia
Blueprint
See the [Blueprint Concept Guide] and the [Adaptive Personalization Manual]
for more information on SearchFunctions and the content type Personalized Search.
 |  |  |
 |