I’ve been working with the embedded search function in the Lucid interface to look at the relevancy score using the &debug=on functionality. I also wanted to use the qf parameter to boost fields at the query level but I’m not having any success with it. Regardless of what I add to the search url there is no difference in the results and there is no difference in the calculations using the Explain function.
I’ve set the query parser to lucid, dismax and edismax but no difference in the results.
Does the embedded search function in the Lucid interface honor the qf parameter in the query URL? Is there anything else I need to set in Lucid or Solr to get this working?
Here's a partial of the query URL I'm trying.
q=policy&commit=Search&qf=description^20&debug=on
Does the embedded search function in the Lucid interface honor the qf parameter in the query URL?
(6 posts) (2 voices)-
Posted 4 months ago #
-
No, the built-in LucidWorks search UI does not pass through general Solr parameters in that way. Building your own search UI is generally how folks integrate and have full control over the parameters sent to Solr. You can go directly to Solr's URL (linked from the LucidWorks collection admin page) to tinker at that level and see the results.
Posted 4 months ago # -
is this just because support for it has never been added or is there an issue to add support for it? If no issue would highly recommend support for it is added.
Posted 4 months ago # -
It's pretty typical that a search UI would NOT pass arbitrary user parameters through to Solr and vet/filter/morph any that do go through, possibly adding others (such as the users role in LWE, for example). We'll certainly consider opening this up for some parameters, but in the qf case you can adjust this using the field editor (or via the REST API) and setting "Search by default" for the desired fields.
Posted 4 months ago # -
Agree with you on the principle that for mainstream search use cases there is probably no benefit and potentially more risk to allow paramaters but for the UI within Lucid which end users are not going to get to I was expecting the search UI to have features that make it an administrative tool. I think the more tools and capabilities you can bake into that UI the more viable Lucid becomes to a wider range of adopters. In the intranet world there is significant value placed on tools that make search easier to administer and translate into lower cost of ownership.
Posted 4 months ago # -
Thomas - point well taken. In fact, we've had this pass through feature in the past with other incarnations of the search UI. I've opened an issue to add this capability in the future (pending engineering team approval and scheduling, of course).
Posted 4 months ago #
Reply
You must log in to post.