InSite Search

InSite Search: InSite Search (ISS) uses Apache Lucene to index the published content of one or more Ingeniux CMS instances and ancillary data. After configuration, publishing a CMS site triggers the indexer to re-index the new or updated content to the main content index. An index contains a copy of the text-based data from the published site's content.


InSite Search (ISS) uses Apache Lucene to index the published content of one or more Ingeniux CMS instances and ancillary data. After configuration, publishing a CMS site triggers the indexer to re-index the new or updated content to the main content index. An index contains a copy of the text-based data from the published site's content. It is stored in such a way that full-text searches can be performed very rapidly and with minimal impact on hardware resources.

InSite Search offers many benefits and features:

  • Full-text search queries of all text-based content. This includes support for wildcard matching and advanced search technology like synonyms and search-term stemming.
  • Document search queries the text in configured binary file formats like Word documents and PDFs.
  • Federated search indexes and queries across multiple content sources with a single query. Sources could include multiple CMS sites, a CMS instance and a Cartella instance, or a CMS and other external sources such as Active Directory or third-party APIs.
  • Facets let users filter results by taxonomy category, content type, or any other metadata included in the content source.
  • Extensibility to create an index of third-party data sources like databases, other applications, and APIs. It's also possible to generate custom facets against these other data sources.
  • Globalized search across content in multiple languages.
  • Weighted display to prioritize and control search results rankings, promoting specific search results, sometimes called "keymatches," in the results display.
  • Styling and branding control over all design aspects of the search experience and user interface with CSS and HTML.
  • Security awareness for controlling visibility of search results based on Ingeniux Runtime Authentication or any other site-specific application logic.
  • Mobile support for using the latest responsive design or adaptive techniques for displaying search results.

Prerequisites

Developers should be familiar with ASP.NET 4.5 and MVC 5 development using C# in order to create search views.

In most cases, the easiest way to implement InSite Search (ISS) is to use Dynamic Execute (DEX) Search components, which run against search indexes that are local to your DSS server. These DEX search components are available within Ingeniux CMS. To use DEX search components, ensure that:

  • Your CMS instance is up-to-date with the latest service release of Ingeniux CMS 10.0, including the most recent InSite Search NuGet package.
  • Your DSS have a basic search results page schema and view.

There are four types of DEX search components:

  • Ingeniux Search
    Among the DEX components, this is the most common search implementation. It is used to return results against a local search index for DSS content. The configuration file Search.config acts as a hub, which references ancillary configuration files. For Ingeniux Search, Search.config references SearchSource.config.

  • Search Navigation
    This DEX search component returns results from index files based on Category (Taxonomy) or Type (Schema).

  • Keymatch Search
    The Keymatch component provides a means for terms to display at the top of the results lists regardless of boost value, etc. Search.config references KeymatchSource.config.

  • Search Suggest
    This DEX component is used for searching against an independent SearchSuggest index. This DEX search component offers spellchecking options to users.

InSite Search Default Indexing of Publishing Target Data

InSite Search searches across published Ingeniux CMS pages. By default, InSite Search indexes the following CMS publishing target data:

  • Text-based element fields (e.g., plain text, XHTML editor, XML).
  • Embedded components that contain text-based elements.
  • Canonical path of the page.
  • Taxonomy category IDs.

This section includes:

  • ISS Configuration Overview: Provides a high-level map of the procedures necessary to get InSite Search running on your DSS server.
  • Updating ISS: Each CMS release includes a base version of the InSite Search package and the DEX Search Components. You can update InSite Search through the NuGet package manager within Visual Studio.
  • Configuring ISS: Provides an overview and links to details about how to configure InSite Search.
  • Creating DEX Search Components: Describes how to create DEX Search components within a search results page.
  • Supplemental Configurations: Lists the supplemental configuration files within the Config folder.
  • Testing ISS Configurations: This topic offers suggestions as to how you can test your InSite Search configurations.
  • Troubleshooting ISS: Links to details about how to troubleshoot InSite Search.

Quick ReferencesQuick reference topics may be particularly useful to administrators and developers who only require an abbreviated roadmap to get a prototype up and running.:

  • Ingeniux DEX Configuration: This quick reference is for users who only require an abbreviated roadmap to get a prototype of the Ingeniux DEX search component up and running.