Skip to content
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

Allow joining complex searches using "AND" and document search better #834

Open
adelavega opened this issue Oct 21, 2024 · 0 comments
Open

Comments

@adelavega
Copy link
Member

"AND" is not behaving as expected when joining complex "or" searches.

A user wrote to us via appzi as follows:

"I tested the following sets of keywords and noticed some surprising results:
Set 1: "autism"
This search yielded 608 results on Neurosynth Compose
Set 2: ❨"autism" OR "ASD" OR "autistic"❩ AND ❨"decision" OR "option"❩
This search yielded 867 results on Neurosynth Compose
For comparison, I ran similar searches on the PubMed search engine:
A search for "autism" yields around 90,000 results
Adding the additional keywords with AND constraints, i.e. ❨"autism" OR "ASD" OR "autistic"❩ AND ❨"decision" OR "option"❩, reduces the results to around 2,000
The PubMed behavior aligns with my expectations, as adding more constraints with the AND operator should reduce the number of matching articles. However, I was surprised to see that on Neurosynth Compose, adding those additional keywords actually increased the number of results from 608 to 867."

Looking into this I realized that "and" after a set of ors in parantheses does not work as expected:

"However, unfortunately, it looks like we don't currently support chaining operators together.For example: (autism or ASD or autistic) and sdlfkjldsf results in the same number of hits, which tells me the last term is being treated as an additional "or"."

If we can implement PubMed like search we should, otherwise let's document well how our search works.
Allowing users to join two complex searches using an AND (i..e get the set that meets both criteria) would be very useful going forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant