...
This Comparison Type is unique. All Filters with a FreeText Comparison Type are gathered into a single filter with an ID of "freetext".
Here is an example an example to help you grasp the concept:
...
This filter filters out any results, whose item ID does not match a supplied ID.
Accepts a single parameter.
...
Filters out any items with data, which does not exactly match all the supplied parameters.
An example Example filter:
This filter will filter out any items, whose keywords does not contain the supplied keywords, ie if an asset has the keywords "pink", "fluffy", "Sith", and "SithLordLord" and a user inputs "pink" and "kitten", then the "pink fluffy Sith lord" asset will be filtered out. If the user inputs "pink" and "fluffy" then the Sith lord will be returned.
...
Filters out any items with data, which does not exactly match any of the supplied parameters.
Example:
Using this filter, if a user inputs "pink" and "kitten", then in this case, the "pink fluffy sith lord" will not be filtered out because one of the asset's keywords is "pink".
Accepts 1-many parameters.
NotInList
Filters out any results, which does match any of the supplied parameters.
Example:
If a user inputs "pink" and "kitten" then the "pink fluffy sith lord" asset will be filtered out, because one of its keywords is "pink".
Accepts 1-many parameters.
Like
Works almost exactly like the SQL "like" operator.
The easiest way to understand the differences is with a brief example:
The filter:
If the user inputs a parameter with value "key", the final like statement is "like 'key%", ie any meta fields, which does not have a name starting with "key", are filtered out.
...
Filters out any results whose data is not equal to or greater than the supplied parameter, ie it works exactly like the ">=>" operator.
EqualsOrLessThan
Filters out any results whose data is not equal to or less than the supplied parameter, ie it works exactly like the "<=<" operator.
RecursiveLayoutfolder
...