Configuring Data Model Properties

First configure the type of each document meta you want to index.

For example, if the document meta contains:

• Textual values, select alphanum.

• Dates, select Date (with time) or Date (without time).

• Numerical values, select Integer, Double or Unsigned Integer.

• Geographical coordinates, select GPS point or XY point.

When adding a new alphanumeric property, you must assign it a semantic type. It defines the global semantic processing to apply when indexing document metas. If required, you can then customize this semantic processing at the Analysis pipeline level (Index > Data Processing > Semantic Processors).

Exalead CloudView includes default semantic types, but you can modify them or create additional ones in Data Model > Semantic Types.

Table 1. Default Semantic Types

Semantic type	Description
text	Apply this semantic type to document metas containing several words or sentences. For example, you would apply this semantic type for a meta with a value like: “Deep Blue was a chess-playing computer. It is known for being the first piece of artificial intelligence to win both a chess game and a chess match against a reigning world champion under regular time controls.” Also use this semantic type to perform extra processing treatment in the analysis pipeline.
metadata	Apply this semantic type to document metas containing a few words that do not require language detection and spell-checking. For example, if we have the meta value Deep Blue Searching for deep blue in lowercase would work, as well as searching for deep only or for blue only.
identifier	Apply this semantic type to document metas containing IDs. With this semantic type, document metas will be searched in their normalized forms, but they will not be tokenized and the language will not be detected. For example, if we have the meta value Deep Blue Searching for “deep blue” (with quotes) would work, but searching for deep only or blue only would not work.
url	Apply this semantic type to document metas containing web addresses.

When creating a data model property, you must specify whether it will be either an index field or a facet, or both.

• Dedicated field: saves the meta as a dedicated field in the index, similar to a database field.

• Category facet: saves the meta in specific index field called categories, used by facets.

This section explains the options available depending on the property type. It can be globally represented by the following schema.

Indexing options for data model properties

Properties have the following options:

• Searchable with prefix: allows users to search for matches in this particular meta, using a prefix. For example, to search for “API” in the title of a document, enter the search query title:API.

• Searchable without prefix: allows users to perform a simple text search, without using a prefix. For example, to search for “API” in a document, enter the search query API.

• Retrievable: enables this meta to be displayed in the hit content of search results.

• RAM based: stores this meta in RAM. Use this option if you need to sort search results on this meta, or when using this meta as a virtual facet.

  Note: Property options may impact performance. For more details, see How Property Options Impact Performance in the Exalead CloudView Configuration Guide .