Each content property has a data type that determines how the property values are treated by the metadata query engine. The possible data types are:
- String
- The metadata query engine indexes the value as a text string. The value is handled as a single unit, even if it contains white space. Users cannot base queries on individual terms within a string value.
- Tokenized
- The metadata query engine indexes the value as a text string after breaking it into tokens. A token is a string of either alphabetic or numeric characters. For example, the value SSN12345789 becomes this string of two tokens: ssn 123456789. Tokens are not case sensitive.
- The metadata query engine treats white space and special characters as token separators. For example, the value 12A Elm Street, apt. 2D becomes this string of seven tokens: 12 a elm street apt 2 d.
- Users can base queries on any individual token or sequence of tokens within a tokenized string.
- Boolean
- The metadata query engine indexes the value as true or false. Values that start with 1, t, or T are treated as true. Any other values are treated as false.
- Integer
- The metadata query engine indexes the value as an integer. Users can base queries on comparative numeric values.
- The metadata query engine indexes values for a content property with a data type of integer only if the values conform to the format for the property.
- Float
- The metadata query engine indexes the value as a decimal number with or without an exponent, depending on the value. Users can base queries on comparative numeric values.
- The metadata query engine indexes values for a content property with a data type of float only if the values conform to the format for the property.
- Datetime
- The metadata query engine indexes the value as a date and time. Users can base queries on comparative datetime values.
- The metadata query engine indexes values for a content property with a data type of date only if the values conform to the format for the property.