InSite Search 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. The system stores the index in a way that enables rapid performance of full-text searches with minimal impact on hardware resources.
ISS Search Features
ISS benefits and features include:
- Full-text search queries across 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 Microsoft Word documents and PDFs.
- Federated search indexes and queries across multiple content sources with a single query. Sources can 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 to 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 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 Run-Time Authentication (RTA) or any other site-specific application logic.
- Mobile support for using the latest responsive design or adaptive techniques for displaying search results.
Developers should be familiar with using C# for ASP.NET 4.5 and MVC 5 development to create search views.
In most cases, we recommend implementing InSite Search by using Dynamic Execute (DEX) Search components, which run against search indexes local to your DSS server. These DEX search components are available within Ingeniux CMS. To use DEX search components, ensure the following:
- Your CMS instance is up-to-date with the latest service release of Ingeniux CMS 10.x, including the most recent InSite Search NuGet package.
- Your DSS has a basic search results page schema and view.
ISS DEX Types
ISS has four types of DEX search components.
DEX search components include:
- Ingeniux Search
- Among the DEX components, Ingeniux Search serves as the most common search implementation. Use the component 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
- Use the component to return results from index files based on category (i.e., taxonomy) or type (i.e., schema).
- Keymatch Search
- Use the Keymatch component to determine which terms display at the top of the results lists regardless of boost value, etc. Search.config references KeymatchSource.config.
- Search Suggest
- Use this DEX component to search against an independent Search Suggest index. This DEX search component offers spellcheck options to users.
ISS 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 paths of the pages.
- Taxonomy category IDs.
InSite Search Release Notes
Review the InSite Search release notes for recent and past software updates, build compatibility information, improvements, and other details.
InSite Search release notes include:
- Current version
- Past Versions