https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14567 --- Comment #58 from Nick Clemens <nick@bywatersolutions.com> --- (In reply to Katrin Fischer from comment #53)

+# This is the temporary entrance point to the API. Once bug #13799 is settled, +# it should be ported to using that. +my $api = $query->param('api');

Should we file a separate bug for this?

Yes, eventually, API endpoint for the search engine is going to be a larger task - comment amended to explain what this variable currently does

- "Browse interface" is a poor link text. Since the actual breadcrumb uses "Browse search", why not use that in the menu too?

Updated

- I'm not quite following the logic of how the actual fuzziness is determined, and it's not obvious in the UI that what the user chooses may not be what they get. At the very least there should be comments in the code describing why it does what it does.

There are comments in the Browse.pm - it uses # of substitutions, ES limits to 2

- Looks like a longer term may get truncated causing the search for records to >fail. An example subject term I encountered is "A history of geographical discovery in the sevente"

Fixed in the mappings we cna set a max - raised to 100

- I think the UI needs to be polished a bit more.

Did you run "yarn build --view=opac"? The list is scrollable I don't think this has to be the same as the scan from 22592 - I think allowing both would allow for comparison to decide if one does work better. On test DB they are comparable at least. -- You are receiving this mail because: You are watching all bug changes.