Search on database does not give me the most important options FixedQuerysender etc

[jjansenvr]

When searching on "database" I do not see the Fixed / Direct/xml qurysender

[thomaspj10]

The old Frank!Doc had the problem of including too many results, so the search was switched to weighted search. The weight of the attributes and description is quite low right now. Maybe it should be a bit higher? Be aware that this might make other results less desirable. We could also increase the number of visible results for a given query by reducing the threshold with a max of 25 items for example. The less desirable results are always at the bottom, so it doesn't matter very much.

Another thing I noticed is that searching for the name of an attribute for example columnsReturned of FixedQuerySender does not yield any results. This should also be added to the keys which should be searched.

Fun fact, you can use pretty advanced expressions to further articulate your search query:
https://www.fusejs.io/examples.html#extended-search

[Matthbo]

It's already expected that the search has to be tweaked more, I sort of guessed what properties of an element would be important and gave it a weight accordingly which initially seemed to work pretty well. Not sure if conditional weights can be a thing in case only 1 type of element (for example only pipes) need to have a different weight on certain properties

Off-topic:
Maybe I could add a ? button that opens a modal to give a simple explanation of how the search works and the extended search table.

[thomaspj10]

I do have one idea on how to improve the accuracy of the search.

Currently we have one super search, which has to balance each key we want to search. It also has the responsibility of correctly ranking each result. All the weights are internally normalised to a value between 0 and 1, so the keys can drown each other out. We can create multiple search methods which each are focussed on a specific thing. This will return a subset of all available elements, which might be vaguely relevant to the given search query. A search on the name, fullName and elementNames, a search on categories and a search on descripion and attributes for example.

A re-ranker can then be used to order the provided results based on relevance. For example: https://github.com/tensorlakeai/rerank-ts. The least relevant results can be thrown away

Would also be really really cool to have some popularity statistic we can also include in this rank. We do not have this tho, so I doubt that this is do-able.

If we really want to supercharge our search we should also have semantic search instead of just lexical search. This does require the use of an AI model, so I doubt we will do that

[Matthbo]

The biggest issue seems to be inherited attributes, for example with columnsReturned of FixedQuerySender.
columnsReturned is inherited from AbstractJdbcQuerySender and so it only shows that as the result.
I really don't know how to approach this problem unless we do preprocessing of inherited attributes for every element when the angular application is initialised, however that seems like a heavy task to just casually do.

Another solution could be having keywords added to the elements so they're more easy to find.
This would help Jeroen's example since there is barely any mention of database in the Fixed / Direct/xml querysender