• Article Type: General
• Product: Aleph
• Product Version: 16.02

Description:
When we have:

setenv set_result_set_limit 1000
setenv www_sort_limit 1000

in aleph_start and we do a search which retrieves 1200 records, we find that the displayed result set (the Brief List) is not sorted.

When we have:

setenv set_result_set_limit 1000
setenv www_sort_limit 3000

in aleph_start and we do a search which retrieves 1200 records, we find that the displayed result set *is* sorted.

By increasing the www_sort_limit beyond the set_result_set_limit, we are able to permit the set to be sorted.

Shouldn't www_sort_limit should be working with the displayed result set, not the total result set? The fact that there are 1,200 hits should not affect the ability to sort a displayed result set of 1,000.

Also, if we omit the www_sort_limit entirely, we find that it defaults to 999,999. This works fine -- except in the cases where the total result-set is greater than 999,999. In that case, as described above, the displayed result set is not sorted.

Resolution:
Corrected by:

V16 - rep_change 2127
V18 - rep_change 1251
V19 - rep_ver 14329

so that the www_sort_limit is compared to the displayed result set (rather than the total result set): it is only when the *displayed* result set is greater than www_sort_limit, that the displayed result set is not sorted.

• Article last edited: 10/8/2013