Full-Text Search

Property

Description

Searchindex address

URL of the search index application for the full-text search, e.g. http://<servername>:8080/FTS-Index (name of the context descriptor file; no file extension).

Init-Threads number

Maximum number of concurrent threads for the initialization of subindices, i.e. the number of feature classes or tables which can be indexed in parallel. A high value may put too much load on the server and increase the total time needed for the initialization. Each init-Thread launches an ArcSOC process at ArcGIS Server.

Maximum indexing duration

Duration in seconds after which the indexing of a subindex (i.e. a feature class) is aborted. Default value: 7200, i.e. 2 hours

Maximum latency

Maximum time that is waited in total when a connection problem occurs while access a service (i.e. feature class). A new connection attempt is started every 3 seconds. Default value: 120, i.e. 2 minutes

Fuzzy search factor

A value between 1.0 and 0.0 which describes the fuzzyness of matching a search term with a result when the search mode "fuzzy search" is used. The value "1.0" indicates a complete match (very strict, not recommended). The value "0.01" matches every result with almost any given search terms (very fuzzy, not recommended).

Phonetic alignment

Defines a comma-separated list of character substitutions that are used when indexing subindices or sending a full-text search request. These substitutions can be used to configure a phonetic search. Some examples (applicable to the German language):

umlaut 'ä' = "ä->a,ae->a"; long vowel 'i' = "ieh->i,ie->i" etc.

The reduced text leads to a higher probability to find a result with a phonetic instead of the correct spelling. Only lower case characters are used for the Phonetic alignment. Caution: The order of the given substitution blocks is important.

Searchindex language

The Locale (two-letter language-code, according to ISO 639-1) that is used to build the search index. However, data in other languages can be indexed as well. The locale is used to transform special characters (e.g. ß, Ž, Ç) for the phonetic alignment, as the full-text search is case-insensitive.

Possible Values: ar, de, en, es, fr, sk, sl, ru and many more (over 100 languages)

Word delimiters

Defines a set of characters (given as a string) which serve as word delimiter. The full-text search is based on word-blocks. Depending on the given data, additional delimiters (e.g. '-', '#', '+' or '/') can improve the search result. The space character is always used as word delimiter. The characters '*' and '~' must not be used as word delimiter.

Search assistance exact?

The value "Yes" (default) activates the "Search assistance exact".

The activation of the "Search assistance exact" provides exact search using the given search input criteria.

Note: Until a search result is reached, the activated search assistants are being used in the following order:

- Search assistance exact

- Search assistance wildcard

- Search assistance fuzzy

- Search assistance LIKE

Note: As soon as one of the search assistants finds any results, these are presented in the client. Any potential subsequent search assistants are skipped.

Note: If all search assistants are deactivated, the search assistant 'wildcard' is being used per default.

Search assistance wildcard?

The value "Yes" (default) activates the "Search assistance wildcard".

The activation of the search assistance increases the chance of a search hit. When the given search term does not return any results/suggestions doing an exact search or fuzzy search, the search term is automatically adjusted and the search runs again a 3rd time (automatically). The "Search assistance wildcard" adds a trailing '*' (=wildcard) to the given search term. The value "true" (default) activates the "Search assistance wildcard". It will be used after the "Search assistance fuzzy" (provided that it is activated).

Note: At least one of the four assistances ("exact", "wildcard", "fuzzy" and "LIKE") has to be enabled ("Yes"). If all four are disabled (set to value "No"), WebOffice 10 R3 will assume "Search assistance wildcard"="Yes" by default.

Note: Until a search result is reached, the activated search assistants are being used in the following order:

- Search assistance exact

- Search assistance wildcard

- Search assistance fuzzy

- Search assistance LIKE

Note: As soon as one of the search assistants finds any results, these are presented in the client. Any potential subsequent search assistants are skipped.

Search assistance fuzzy?

The value "Yes" (default value is "No") activates the "Search assistance fuzzy".

The activation of the "search assistance fuzzy" increases the chance of a search hit. When the given search term does not return any results/suggestions doing an exact search, the search term is automatically adjusted and the search runs again a 2nd time (automatically) in "Fuzzy" mode. The "Search assistance fuzzy" uses the fuzzy search mode. The fuzziness can be defined in the attribute "Fuzzy search factor".

Note: Until a search result is reached, the activated search assistants are being used in the following order:

- Search assistance exact

- Search assistance wildcard

- Search assistance fuzzy

- Search assistance LIKE

Note: As soon as one of the search assistants finds any results, these are presented in the client. Any potential subsequent search assistants are skipped.

Note: If all search assistants are deactivated, the search assistant 'wildcard' is being used per default.

Search assistance LIKE?

The value "Yes" (default value is "No") activates the "Search assistance LIKE".

The activation of the search assistance increases the chance of a search hit. When the given search term does not return any results/suggestions doing an exact search, fuzzy search or wildcard search, the search term is automatically adjusted and the search runs again another time (automatically).

The "search assistance LIKE" adds a leading and a trailing '*' (=wildcard) to the given search term, e.g. search for "*searchtext*".

Caution: A search with wildcards needs more resources than a conventional search. Additionally, it carries the threat of producing too many (and therefore useless) results.

Note: Until a search result is reached, the activated search assistants are being used in the following order:

- Search assistance exact

- Search assistance wildcard

- Search assistance fuzzy

- Search assistance LIKE

Note: As soon as one of the search assistants finds any results, these are presented in the client. Any potential subsequent search assistants are skipped.

Note: If all search assistants are deactivated, the search assistant 'wildcard' is being used per default.

Combined Suggestions?

The value "Yes" (default is No) enables a special wildcard search for suggestions.

For each search value a separate search is executed, one time with and one time without a wildcard.

The results of all these searches are combined and sorted by highest returned search score.

This option only applies for suggestions, not for search results. If activated, any other search assistants for retrieving suggestions are deactivated.

This option is recommended for searching with multiple search values in a data set with a high number of identical values (e.g. address sets).

Separator for suggestions?

Use parameter "Object name concatenator" on result field list for seperating suggestions and multilayer object result of full-text search. If "No" a whitespace (" ") will be used to separate the field values.

Note: If this parameter is set to "Yes" the object name concatenator of the first result field list of the first search result on the respective layer of the first relevant project will be relevant.

Note: Every time the configured concatenator is changed, the existing subindex is "out of date" and has to be recreated.