- Article Type: General
- Product: Aleph
- Product Version: 21
Desired Outcome Goal:
Increase the result-set and sort limits to increase the number of results displayed
The set_result_set_limit and www_sort_limit are described under www_server.conf and under pc_server_defaults in the Aleph Configuration Guide.
1. setenv set_result_set_limit nnnn" controls how many results are displayed in the Brief List. (minimum value =1000; maximum = 20000; default = 1000)
* If "1000" is specified, either explicitly or by default, even though 9,462 records are retrieved, the Brief List will include only 1,000
* Set this to the highest number that, realistically, a patron would want to look through (remembering, of course, that patrons have the option of refining the search and retrieving a more precise result set).
2. setenv www_sort_limit nnnn" is used to limit the sorting of the result set for performance reasons. The sort limit is a number of up to 6 digits; its default value is 999999 (i.e., no sort limit). This is NOT the best value. It is best to specify a www_sort_limit.
* Testing shows that almost all the time required for large result sets is spent in sorting the results.
* With a higher set_result_set_limit (say 15,000), a www_sort_limit of, say, 5.000, and when there were 8,000 hits, the system would display them all, but they would not be sorted.
Normally, they would be in descending record-number order. See KCS article 8192-5416 (Order of result sets exceeding display (or sort) limit).
* In the example of 8,000 hits described above, customers may prefer to display only 5,000 records but have them sorted (and sortable). In this case, specify set_result_set_limit 5000 and omit www_sort_limit.
* When it is preferred to make the larger result set available, even if it is not sorted (or sortable), specify set_result_set_limit 15000 and www_sort_limit 5000.
Category: Web OPAC (500)
Subject: Search (500)
- Article last edited: 10/8/2013