Description
1) The CMS search does not include a sort order in the query. By default, JCR has a insane stupid order if no order is specified, namely, on SCORE ASCENDING : Thus, worst hits first
2) The CMS uses a limit of 100 : The worst 100 hits are taken
3) The worst 100 hits are sorted by lexical order on their title
Suggested FIX:
1) Include @jcr:score descending to get the most relevant hits first
2) Have the document hits by default shown in order of deceasing relevancy
Optional:
Give the cms user feedback when there are more than 100 hits
Attachments
Issue Links
- relates to
-
CMS-6790 SearchDocumentsProvider does not keep search results in order in which they are retrieved from the repository
- Closed