Content
View differences
Updated by Wieland Lindenthal 2 days ago
As a user searching by an project-based semantic work package identifier
I want to get exact matches earlier in the search result list
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920585/content">
**Acceptance Criteria**
* exact matches on the work package identifier are at the top of the list of search results, "fuzzy" matches below
* exact matches on the sequence part (example: from `ACSMT-5` the `5`) a ranked higher than fuzzy ones. Search term "5" will show `ACSMT-5` and `XYZ-5` before `ACSMT-51`
**Technical notes**
* Since the ordering of results is independent of which attribute lead to the record being included in the result this may be very hard to do
* Currently the sorting is done by `updated_at`, which works very well for searching in the work package subject or project title. Often the sort order is part of the API query that front-end components send to the back-end. Maybe we need another order-by that is not `updated_at` but something more clever. description in work packages.
* Maybe include some "weight" in the query as first sort criteria (and further sort by `updated_at` if the weight is 0)
**Background**
* https://github.com/opf/openproject/pull/22732#discussion\_r3116004114
I want to get exact matches earlier in the search result list
<img class="op-uc-image op-uc-image_inline" src="/api/v3/attachments/920585/content">
**Acceptance Criteria**
* exact matches on the work package identifier are at the top of the list of search results, "fuzzy" matches below
* exact matches on the sequence part (example: from `ACSMT-5` the `5`) a ranked higher than fuzzy ones. Search term "5" will show `ACSMT-5` and `XYZ-5` before `ACSMT-51`
**Technical notes**
* Since the ordering of results is independent of which attribute lead to the record being included in the result this may be very hard to do
* Currently the sorting is done by `updated_at`, which works very well for searching in the work package subject or project title. Often the sort order is part of the API query that front-end components send to the back-end. Maybe we need another order-by that is not `updated_at` but something more clever.
* Maybe include some "weight" in the query as first sort criteria (and further sort by `updated_at` if the weight is 0)
**Background**
* https://github.com/opf/openproject/pull/22732#discussion\_r3116004114