Modify the search.properties file to configure the number of documents to retrieve for top-N processing and clustering and also to control the attributes available for grouping and sorting. These settings affect the default query application. The search.properties file is located in the ORACLE_HOME/search/webapp/config directory.
When modifying search.properties, use only ASCII characters or Unicode escape characters. Non-ASCII characters are ignored.
For example, the Unicode escape characters for the Hiragana for "aiueo" are: \u3042\u3044\u3046\u3048\u304A. In search.properties, you would enter these characters for the group_tab_order property to specify the order of groups aiueo, ghi, def, and abc:
ses.qapp.group_tab_order=\u3042\u3044\u3046\u3048\u304A,ghi,def,abc
Unicode conversion tools are available on the World Wide Web.
The default top-N documents setting specifies the number of documents retrieved by default as part of the AJAX call for result clustering, grouping, and sorting:
ses.qapp.default_topn_docs=100
To page through a very large result set, say 500 documents, the user may view a page of results beyond the default top-N value. Suppose top-N is set to the default 100, and the user wants to view the results numbered 150-160. To provide result clustering and sorting/grouping, the browser must request 160 results. If the user views page 490-500, then the browser would be requesting 500 results through the AJAX call. This may result in reduced performance.
The maximum top-N documents setting represents a threshold above which the query application displays only a single page of results.
This mode does not provide any sorting, grouping, or result clustering. However, it lets a user to view the entire result set without the costly subsequent retrievals of top-N results.
Suppose max_topn_docs is to 200. If an end user is viewing results 30-40, then the browser would retrieve the default of 100 results. If the user views results 170-180, then the browser would request 180 documents. If the user views results above 200, then the query application would display only the current page of results. For example:
ses.qapp.max_topn_docs=300
The set of attributes available in the Group By and Sort By drop-down lists in the query page also can be configured in the search.properties file. The attributes available for grouping are configured by setting the ses.qapp.groupable_attrs property value, and the attributes available for sorting are configured by setting the ses.qapp.sortable_attrs property value.
The property value for either grouping or sorting is an ordered, alternating comma-delimited list of the search attribute name followed by the display name.
Table 5-2 lists the default grouping attributes:
| Description | Attribute Name | Display |
|---|---|---|
|
No grouping |
|
(none) |
|
Source group |
|
Source |
|
Last modified date |
|
Date |
|
Author |
|
Author |
|
File format |
|
File Format |
The property value for this default set for grouping is the following:
ses.qapp.groupable_attrs=ses_none,-,ses_sourceGroup,-,lastModifiedDate,-,
author,-,mimetype,-
Table 5-3 lists the default sorting attributes:
| Description | Attribute Name | Display |
|---|---|---|
|
Relevance |
|
Relevance |
|
Last modified date |
|
Date |
|
Author |
|
Author |
|
File format |
|
File Format |
|
Document title |
|
Title |
|
URL |
|
Path |
|
Language |
|
Language |
The property value for this default set for sorting is the following:
ses.qapp.sortable_attrs=ses_score,-,lastModifiedDate,-,author,-,
mimetype,-,title,-,infosource path,-,language,-
To use the translated name of a search attribute for display instead of providing a fixed display name, insert a dash (-) for the display name. For example, if the search attribute "Test1" has translated names configured on the Global Settings page in the Oracle SES Administration GUI, then the following uses the translated names for display:
ses.qapp.sortable_attrs=ses_score,-,Test1,-,lastModifiedDate,-, ...
See Also:
"Searching on Date Attributes"