-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restore ability to searching for public body by note body #7552
Comments
+1 on rationalising the searching. They currently give different results, which is quite annoying.
The one benefit of the SQL search was it tended to rank direct name matches higher – see #4426 for lots of discussion on that. The benefit of the Xapian searching is that you can generally find something if you don't know the exact name: e.g. searching for "City of Cardiff Council" (which is in the notes field of that body:
Either way, I think having fewer search mechanisms is generally better, and then we can spend the time tuning the search engine. |
Yes the SQL search is given better results I wonder if we could do something like #7553 to improve Xapian. Would need to consider how to update our large Xapian indexes. |
Looks like something we considered last time we looked at this, but can't immediately see any evidence that we tried it #4426 (comment) |
This appears to be the case right now. I just dealt with a case identical to #4426 (comment) (NHS England not appearing for the first 10 pages). The search results were all highlighting matches of "NHS England" in notes. Is this just because these bodies haven't been reindexed since #7212? That doesn't seem true, as e.g. this authority was last updated at 2023-08-28, so presumably long after. |
This issue has been automatically closed due to a lack of discussion or resolution for over 12 months. |
On
/body/list/all
searching for public bodies by note body hasn't been working correct since #7212 as its not using the new Note model. In #7269 the spec for this feature has been disabled.We could switch this search to use Xapian searching and remove a complex SQL query in the process.
The text was updated successfully, but these errors were encountered: