-
Notifications
You must be signed in to change notification settings - Fork 37
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
EuPMC returns a different number of results by API than by UI #95
Comments
Yup, the UI search seems pretty broken to me at the moment. A search for an article title often returns 20 other articles before the one with the exact name. |
Ah - the EPMC UI is giving massive false positives? that makes sense. The API seems to give fewer hits. We should probably have a filter that checks whether the paper actually contains the search phrase or words. If it doesn't maybe we have to filter it out? Or does Lucene do concept searches? |
Lucene can do lots of different kinds of searches - it depends what indexers have been set up. So for example it can do normal NLP processing and match shared stems etc, or it can resolve synonyms, or whatever. I think we should, for now, trust the results from eupmc. However, my https://github.com/blahah/yunodb is built for doing this kind of refined search on the client side. |
Note that iterative filtering is on the general to-do list and will be in science fair's miner |
I'm now struggling to replicate this issue: Something to keep an eye on is that the UI groups the whole search with () before appending OPEN_ACCESS:Y. Perhaps there are some cases (I haven't yet found them) where we also need to do this.
|
No description provided.
The text was updated successfully, but these errors were encountered: