Introducing Ingeniux InSite Search: Enhancing Your Website's Search Experience

Ingeniux InSite Search is a powerful, built-in module designed to enhance the search experience on your Ingeniux DSS site. It serves as an excellent alternative to Google Mini Search appliances and Google Site Search services, offering numerous benefits and features to improve website search functionality.

Key Features of InSite Search

• Full-Text Search Queries: Supports wildcard matching, synonyms, and stemming of search terms, enabling comprehensive text-based content searches.
• Document Search: Allows queries within the text content of configured binary file formats like Word documents or PDFs.
• Federated Search: Enables querying across multiple content sources with a single query, including multiple CMS sites, Cartella instances, Active Directory, Localist, or third-party APIs.
• Faceted Search: Provides visitors with the ability to filter results based on facets such as taxonomy category, content type, or other metadata.
• Extensibility: Creates indexes of third-party data sources such as databases, applications, and APIs, allowing for custom facets.
• Globalized Search: Supports searches across content in multiple languages.
• Weighted Display: Prioritizes search results, highlighting specific results more prominently, similar to "keymatches" in other products.

How It Works

InSite Search uses the .NET version of Apache Lucene, a leading open-source search engine, to index published content from one or more Ingeniux CMS instances. When a CMS site is published, the indexer re-indexes the new or updated content.

Understanding the Index

The index contains a copy of text-based data from the published site content, allowing for rapid full-text searches with minimal hardware impact. Leveraging Lucene.NET ensures compatibility with existing Lucene tools.

Indexing Process

InSite Search indexes your published pages, ensuring meaningful results by working with published XML rather than the rendered site. This approach excludes irrelevant content like headers or footers from search results. Administrative settings allow for indexing assets and components based on specific needs.

Search Discovery and Design

Implementing a successful search requires thorough planning and analysis. Key questions to consider include:

• Audience: Who will use the search? Are there multiple audiences, such as internal and external users?
• Content: What will be searched? Do you have multiple repositories? Do different searches cater to various content types?
• Workflow: How do users interact with the search? Do they start with keywords? Are filters applied before or after searching? Is any content protected?
• Content Creation: Who writes and filters the content? Who ensures quality and fine-tuning?
• User Experience: How do users perceive the search? Does it adapt to user behavior automatically or manually?

Exploring InSite Search Features

Indexing External Content

InSite Search can integrate additional features through DEX components, allowing the inclusion of external content sources in your CMS. These sources are seamlessly integrated for use and display.

Keymatches

Keymatches ensure specific search terms display prominently at the top of results. These are stored separately from the content index, unaffected by standard search ranking or boosts.

Synonyms

Synonyms enhance search accuracy by associating alternative terms with keywords, expanding search results to include related terms. This feature works behind the scenes to deliver relevant results.

Search Suggestions

Utilizing the Lucene search indexer, the CMS can recognize misspelled and partial words, generating suggestions for probable intended words to improve the search experience.

Search Navigation

The DEX component retrieves targeted results by leveraging categories or types to narrow down search outcomes. It integrates with the main index without creating a separate index.

Remote Indexers

DEX components support indexing remote content, useful for integrating content from external sources like documentation repository sites.