Content classes

Content Platform Tenant Management Help

Version
9.7.x
File Size
4269 KB
Audience
anonymous
Part Number
MK-95HCPH002-19

The Content Classes section displays a list of the content classes defined for the tenant. When you select a content class, an additional field appears in the query area, as shown below.



The dropdown list for the added field contains the content properties in the selected content class.

Each content property has a data type, such as integer or string, that determines the operators and values you can specify. The table below lists the possible data types.

Data type Operator Values
Boolean

is

is not

True (matches 1 or strings starting with T or t)

False (matches all other values)

does

does not

exist
Datetime

is

is not

before

after

Specified date

does

does not

exist
Float

is

is not

greater than

less than

greater than or equals

less than or equals

Floating point number.

Floating point numbers can include a positive or negative sign, digits, a decimal point, and an exponent that starts with E. Here are some sample floating point numbers:

1328.978

-3746.12

954.33E5

does

does not

exist
Integer

is

is not

greater than

less than

greater than or equals

less than or equals

Positive or negative integer

does

does not

exist
String

is

is not

Text string

does

does not

exist
Tokenized

contains

does not contain

contains phrase

does not contain

phrase

One or more search terms

does

does not

exist

The does and does not operators test for the existence of the specified content property. That is, does exist condition matches only objects with custom metadata that have the specified content property. One use for the does exist condition is to limit the scope of the is not and does not contain operators.

The is not and does not contain operators match all objects that don't have the content property value specified by the value field. As a result, the criterion matches objects without the content property, and even those with no custom metadata at all. To make sure that a query matches only objects with custom metadata identified by the content property, use two criteria for the content property, one with an is not or does not contain operator and one with a does operator with the exist value.