...

There are 22 different Comparison Types: 

FreeText

This Comparison Type is unique. All Filters with a FreeText Comparison Type are gathered into a single filter with an ID of "freetext". 

...

Due to the inner workings of how such filters work, any search, which has a freetext filter, MUST be populated (see UseSolr for a guide on how to populate a search).

Equals

Tests whether a Filter's parameter matches exactly with the data, the filter works on.

...

Accepts a single parameter.

EqualsWithZeroAsNull

The same as Equals, but treats a value of "0" as null.

Accepts a single parameter. 

EqualsOrNull

The same as with Equals except that results with a null value are not filtered out.

Accepts a single parameter.

AllInList

Filters out any items with data, which does not exactly match all the supplied parameters.

...

This filter will filter out any items, whose keywords does not contain the supplied keywords, ie if an asset has the keywords "pink", "fluffy", "SithLord" 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.  

Accepts 1-many parameters.

InList

Filters out any items with data, which does not exactly match any of the supplied parameters.

...

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".

NotInList

Filters out any results, which does match any of the supplied parameters. 

...

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".

Like

Works almost exactly like the SQL "like" operator. 

...

A Like filter is very expensive, so be wary using this Comparison Type, as it may result in very slow searches.

Between

"Between" is a very specific Comparison Type: it can only be used with filters, which does work on dates or DateTimes, eg "asset.start_date" and "asset.end_date".

If a similar functionality is needed, but in the context of data other than dates or DateTimes, eg filtering out results whose IDs are between 5 and 11, that functionality MUST be mimicked by creating two filters. An example of such two filters can be two filters with respective Comparison Types of GreaterThan with a parameter value of 11 and LessThan, with a parameter value of 5:

GreaterThan

Filters out any results whose data is not greater than the supplied parameter, ie it works exactly like the ">" operator.

LessThan

Filters out any results whose data is not less than the supplied parameter, ie it works exactly like the "<" operator.

EqualsOrGreaterThan

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

Works exlusively with folders located in the table layoutfolders. As such, this Comparison Type will NOT work with other data.

Filters out assets, which do not belong to a folder, which is a child of the folder with the supplied layout folder ID parameter.

RecursiveDamcatalogfolder

Works exactly like RecusiveLayoutfolder, except that it looks at the folders defined in damcatalog_folder.

IsDescendantOf

Works exlusively with data, which is an SQL hierarchy ID. Filters out any results, which are not descendants.

Empty

Filters out results, whose data is or an empty string. 

NotEmpty

Filters out results, whose data is not null or an empty string.

EmptyCheckField

The same as Empty, except that this filter will not be applied, if the user does not supply a parameter.

NotEmptyCheckField

The same as NotEmpty, except that this filter will not be applied, if the user does not supply a parameter.