Configure Standard CMS Document Search

You can configure certain aspects of the standard document search in Bloomreach Content.

Info: The Advanced Search module offers additional search features and configuration options beyond the standard search.

Configure Result Limit and Wildcarding

The plugin org.hippoecm.frontend.plugins.cms.browse.section.SearchingSectionPlugin manages document search behavior. You can configure this plugin at /hippo:configuration/hippo:frontend/cms/cms-tree-views/documents/sectionPlugin using the following optional properties:

Property	Description	Default
result.limit	Maximum number of search results returned	300
wildcarded.minimal.length	Minimum length a search term must have before wildcarding applies. Values below 3 are not accepted.	3

You can also configure the SearchingSectionPlugin at sibling nodes under /hippo:configuration/hippo:frontend/cms/cms-tree-views for assets, images, and document types.

Restrict Search to Specific Document Types

By default, the search only includes documents. You can customize which document types are included in the search results.

For brXM version 15.6 and later:

1. At /hippo:configuration/hippo:frontend/cms/cms-tree-views/documents, add primaryTypes to the existing multi-valued property frontend:properties.
2. At /hippo:configuration/hippo:frontend/cms/cms-browser/documentsTreeLoader/cluster.config, add a multi-valued string property primaryNodetypes and specify the primary document types to include in the search.

For versions earlier than 15.6:

• At /hippo:configuration/hippo:frontend/cms/cms-browser/documentsTreeLoader/cluster.config, add a multi-valued string property nodetypes and specify the primary document types to include in the search.

You can configure the images and assets search boxes in the same way at the corresponding sibling nodes under imagesTreeLoader and assetsTreeLoader.

Lucene Analyzer Behavior

The search box uses the Lucene analyzer to interpret tokens entered by users. By default, Bloomreach Content uses the StandardAnalyzer, which relies on the StandardTokenizer. The tokenizer applies the following rules:

• Splits words at punctuation characters and removes punctuation. However, a dot not followed by whitespace remains part of the token.
• Splits words at hyphens, unless the token contains a number. In that case, the entire token is treated as a product number and is not split.
• Treats email addresses and internet hostnames as single tokens.

Implications:

• You cannot search for hyphens unless the word contains a number. For example, searching for "foo-bar" is not possible, but "foo-bar-5" is.
• You can search for parts of a hyphenated word. For example, searching for "bar" will match "foo-bar".
• You cannot search for punctuation except for dots within words. For example, "foo,bar" cannot be searched, but "foo.bar" can.

You can configure a different Lucene analyzer if you need different tokenization behavior.