Details
-
Feature
-
Status: Dismissed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
None
Description
Current Situation
- If users use the "Advanced Search" for large result sets then a default sort order (usually by name) is provided. However, if a different sort order is desired then a user will click the respective column and will have to wait for the results to be queried once again,
Desired Behavior
- Searching for results in a specific sort order should not require to re-execute the query and to double the time required for display of hits in the desired sort order.
Maintainer Notes
- The behavior has been improved with
JOC-433that performs sorting locally with the client browser. - The performance penalties with previous releases are due to the fact that the volatile API had been used for each entry on every sort operation. With
JOC-433the volatile API is used just once for each entry, therefore sorting is much quicker and does not require the sort order to be considered by the permanent API. Therefore this issue is dismissed.