Searching for stops with very simple names does not work properly

[senritsu]

Due to a combination of issues some stops can't be reported by name search.

• Only X items listed per result page, and no pagination option
• The fuzzy search does not prioritize match quality/distance enough, leaving exact matches somewhere far down the list for shorter names that are also contained in a lot of other stop names

This leads to the correct stop not being listed in the results, and no way to paginate to it.

As a workaround location search can be used instead of name search.

[Chefkeks]

This is due to the fact that we use %searchterm% instead of searchterm%.
But yes, that is an issue which we should get solved either by pagination or optimizing the search or both :)

EDIT:
Can you give an example search term and result list?

[senritsu]

Without knowing specifics about the search used, just by similarity with SQL i would assume that searchterm% roughly equates to regex searchterm.* and only matches beginning of word with wildcard on the end, which would solve this problem somewhat but would also lead to lots of actual positive matches being discarded (with the term in the middle or end of the word). Not sure if this solution doesn't actually make things worse overall.

For a proper solution there is probably no way around either pagination (cumbersome but would make all options selectable) or a better search algorithm with an adjusted score/metric for match quality.

I will try to provide an example when i get home.

[senritsu]

Example result for searchterm "Statue":