InSite Search: Implement InSite Search (ISS) in Ingeniux CMS 9.x to execute full-text search queries, document search queries, facets, extensibility, and more.
Ingeniux InSite Search is a module that can be easily integrated with an Ingeniux DSS site to deliver improved search functionality. It's a great option to replace Google Mini Search appliances or Google Site Search services.
Ingeniux 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, Localist, or third-party APIs.
- Facets let users filter results by taxonomy category, content type, or any othermetadata 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.
InSite Search in Detail
How Does ISS work?
The InSite Search library uses Apache Lucene to index the published content of one or more Ingeniux CMS instances. After configuring InSite Search, publishing a CMS site triggers the indexer to re-index the new or updated content.
What is the Index?
The index contains a copy of the text-based data from the published site's content. However, it is stored in such a way that full-text searches can be performed very rapidly and with minimal impact on hardware resources. Best of all, because it uses Lucene.NET, any tools that work with Lucene can work with the site index.
What Gets Indexed?
The InSite Search library indexes a site's published pages. Because it works with published XML and not the rendered site, it returns meaningful results. For example, searching for a word that appears in a header or footer doesn't return results for the entire site, but only for those pages where the word appears in the page content. It also indexes documents in your documents directory. If you have the appropriate IFilter installed on the machine were the indexing is happening, the indexer can extract the information from the document and index it as well. This could include Word documents, PDFs, or anything else where a valid IFilter exists.
The following prerequisites are required to use InSite search within your DSS site:
- The source CMS must be on the latest service release of CMS 9.0
- The target DSS must be upgraded to the latest release of CMS 9.0.
- Developers should be familiar with ASP.NET 4.5 and MVC 5 development using C#.
There are two configuration options for InSite Search:
- Standard configuration: Most sites should set up search as follows:
- Custom configuration: InSite Search can be customized in a number of ways. These include how the index is built and queried, adding search facets, and working with keymatches.
This section includes: