Sorting Search Results¶
Search results displayed in the Search Results widget are ordered by relevance score (as calculated by the search engine) by default. With the Sort widget, users can control the order of returned results.
Add the widget to a Search Page to begin sorting results.
Out of the box, you can order results in these ways as an alternative to relevance sorting:
alphabetically by Title
by the Modified date (newest first by default, or choose oldest first)
by the Create date (newest first by default, or choose oldest first)
alphabetically by the User that created each matching asset
Choose from one of the Sort widget’s pre-configured sorting strategies or configure your own.
You can also delete unwanted sort options from the widget.
Adding the Sort Widget to a Page¶
To get started with the Sort widget,
Open the Add menu (
) for the page and expand the Widgets section.From the Search category, drag the Sort widget onto the page.
Configuring the Sort Widget¶
From the Sort widget’s Configuration screen, you can
Edit existing Sort options
Delete options
Add new options
To access the widget configuration screen, open the widget Options menu (
) and click Configuration.
Each Sort option has two settings: Label and Field.
Label: Set the displayed label for the type of sort being configured.
Field: Enter the fieldName of the indexed field to sort. Most of the time this is a keyword field. Other acceptable options are date and any numeric datatype. There’s even a way to coerce text fields into behaving with the Sort widget (see below).
Changing the Default Sort Behavior¶
Out of the box, the Relevance option is first in the Sort widget’s list, making it the default sort applied to the page. Therefore, results are sorted by relevance when a search is executed. Searching by relevance is the expected default behavior for most users, but you can exert a different sort strategy on default searches by changing the first option in the Sort widget configuration.
To change the default sort option,
Open the Sort widget’s configuration screen by clicking the Widget Options
button.Click the Add
button below the Relevance option.Duplicate the current Relevance option’s values—this ensures that Relevance is the second option in the list.
Now change the top option. If you choose one of the existing options, make sure you remove the duplicate by clicking its Remove
.Save the configuration. Enter a search and you’ll see the new sort applied.
Finding Sortable Fields¶
To find the fields available for use in the Sort widget, Users with the proper permissions can navigate to Control Panel → Configuration → Search. From there, open the Field Mappings tab and browse the mappings for each index. Scroll to the properties section of the mapping and find any keyword field, date field, or a field with a numeric data type. The type field is instructive:
"type" : "keyword"
"type" : "date"
"type" : "long"
If you really must sort by a text field, add a new version of the field to the index with the type keyword. From the field mappings screen mentioned above, look at the firstName field in the index called liferay-[companyID]:
"firstName" : {
"type" : "text",
"store" : true
},
"firstName_sortable" : {
"type" : "keyword",
"store" : true
},
There’s a corresponding field with the suffix _sortable, and of the correct type for sorting (keyword). The sortable field got there via a portal property:
index.sortable.text.fields=firstName,jobTitle,lastName,name,screenName,title
All the text fields listed here have a fieldName_sortable counterpart created automatically in the index. To add more, copy this property into a portal-ext.properties file into your Liferay Home folder, add any new field names you need to sort by, and restart the server.
Adding New Sort Options¶
To sort by the new field or an existing field of the proper type, use the plus symbol below any existing option’s Field configuration make sure to use the fieldName_sortable version of the field in the widget configuration.
To add a new sort option that’s already of the proper data type, use the plus symbol below any option’s Field configuration and fill in the fields. The order of options here in the configuration screen matches the order in the select list when configuring the widget for search.
Editing and Deleting Sort Options¶
To edit an existing option, edit the text in its configuration section.
To delete an existing option, use the minus symbol below its Field configuration.
Controlling the Sort Order¶
To control the order for the sort option, add a plus or minus symbol after the fieldName. Look how it’s done for the existing sort options labeled Created and Created (oldest first) to understand how it works:
Label: Created
Field: createDate-
The - sign following the field name indicates that the order is descending. Sorting this way brings search results created most recently to the top of the list.
Label: Created (oldest first)
Field: createDate+
The + sign following the field name indicates that the order is ascending. Sorting this way brings the oldest (by creation date) results to the top of the list.
Sorting by Nested Fields¶
Availability: 7.2 FP12+, 7.3 FP2+
As described in Accessing Nested DDM Fields, DDM Fields became nested fields as of Liferay 7.2 SP3+/FP8+ (and on all Liferay 7.3 versions). On the latest Fix Pack and GA release of 7.2 and 7.3, the Elasticsearch Nested query is supported to account for these nested fields.
Your Sort configurations that relied on fields named ddm__keyword__* at the root of the Elasticsearch document continue to be valid—the Search framework itself was adjusted to account for the nested field types. Use these fields as usual in your Sort widget’s Field configuration, even though they’re no longer at the root of the document.
The Sort widget works with keyword, date, and numeric fields. To find DDM keyword fields in existing documents in the index,
GET liferay-20097/_search
{
"query": {
"nested": {
"path": "ddmFieldArray",
"query": {
"wildcard": { "ddmFieldArray.ddmFieldName": "ddm__keyword*" }
}
}
}
}
Replace the Company Id—20097—in the index name parameter to match your instance’s value.
The document returned has a ddmFieldArray object with nested content:
"ddmFieldArray" : [
{
"ddmFieldName" : "ddm__keyword__40806__Textb5mx_en_US",
"ddmValueFieldName" : "ddmFieldValueKeyword_en_US",
"ddmFieldValueKeyword_en_US_String_sortable" : "some text has been entered",
"ddmFieldValueKeyword_en_US" : "some text has been entered"
},
{
"ddmFieldName" : "ddm__keyword__40806__Selectjdw0_en_US",
"ddmValueFieldName" : "ddmFieldValueKeyword_en_US",
"ddmFieldValueKeyword_en_US_String_sortable" : "option 3",
"ddmFieldValueKeyword_en_US" : "value 3"
},
{
"ddmFieldName" : "ddm__keyword__40806__Boolean15cg_en_US",
"ddmValueFieldName" : "ddmFieldValueKeyword_en_US",
"ddmFieldValueKeyword_en_US" : "true",
"ddmFieldValueKeyword_en_US_String_sortable" : "true"
}
],
To use one of these fields in a Sort configuration, enter the ddmFieldName value (e.g., ddm__keyword__40806__Testb5mx_en_US) as the Field setting.