Last updated
Last updated
This guide will help you get set up quickly using Examine with minimal configuration options. Umbraco ships Examine with 3 indexes: internal, external, and members. The internal index should not be used for searching when returning results on a public website because it includes content that has not been published yet. Instead, you can use the external index to get up and running.
The starter kit comes with some Templates, Document Types, and content nodes created already. We will use some of these to set up a basic search system. This is a 'Quick Start' guide, as many more complex searches are possible with Examine.
We will make it possible to 'search' on the People page, by adding a search bar to the template page: people.cshtml - add the following form at the top of the template, but underneath the <nav> element:
This will create a basic input field at the top of the page and make it post to the same people page when submitted along with the search term.
Let's start by creating a PeopleController that derives from RenderController and add an Index method.
To search anything from our controller, we first need to create a service that handles the actual search logic. We'll start by creating an interface for our service.
Now create a default implementation of the service interface.
And finally register the service in Startup.
To perform the search we will first need to get a reference to the particular Examine index that we want to search. Then we will use this index to access its corresponding Searcher. We use the Searcher to construct the query logic to execute and search the index.
Umbraco ships with three indexes:
ExternalIndex - available to use for indexing published unprotected content.
InternalIndex - which Umbraco's backoffice search uses.
MembersIndex - which Umbraco's Membership implementation uses.
The service IExamineManager is used to retrieve an Examine index by its 'alias', so we need to inject that service into our SearchService.
With the IExamineManager injected in our SearchService, we can implement the SearchContentNames method. We do this using the Searcher for the Examine index 'ExternalIndex'.
The Searcher has a CreateQuery method, where you can choose to search content, media or members eg:
From here you can see how we can chain together the logic to perform the search. In the example, we are searching all content using the person Document Type, where the nodeName is equal to the search term that was typed in the input bar.
Calling .Execute() at the end of the query logic triggers the search and returns a set of matching search results, which we can loop through to get the IDs of the resulting content items.
We want to retrieve the actual content from the IDs. For that, we need the UmbracoHelper, which must be injected into our service as well. The final implementation of SearchService then looks like this.
After getting the ids from our search, we then loop through the list and return the content.
We will now need a custom view model so that we can pass our search results to the view. Our view model needs to inherit from PublishedContentWrapped because our People view is expecting a model that is content. We then wrap the content and add the search data, all in a convenient view model.
Now that we've created our service to handle the actual search logic, and our view model to pass the search results to the view, let's look at using them in the controller. We will want to update the Index() method to get out the query string from the request, then create a view model and populate the SearchResults property by using our service.
The final thing we need to do is update the view to use our new view model. We do that by changing the @inherits line in the view.
Let's now use the view model to display the search results. We'll place them directly under the form we created earlier.
Examine has a lot of different ways to query data. Building upon the example from before, here are a few other searches that can be done to get different data:
Let's say you want to search through all content nodes by their file names. You could amend the query from before like this:
To do the search like above, but only use Lucene to query, amend the query from before like this:
To search through all child nodes of a specific node by their bodyText property, amend the query from before like this:
The best practice for POST requests is to encapsulate the request handling in a controller. To do this we will leverage the concept of .
if you need to analyse text in a different language for example.