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

exact parameter not functioning correctly in search api #666

Open
ma9253 opened this issue May 21, 2024 · 1 comment
Open

exact parameter not functioning correctly in search api #666

ma9253 opened this issue May 21, 2024 · 1 comment
Assignees
Labels
bug low priority Workaround available

Comments

@ma9253
Copy link

ma9253 commented May 21, 2024

Describe the bug
I am reporting an issue with the "exact" parameter in the search API, as documented on the following page: https://www.ebi.ac.uk/ols4/ols3help.

According to the documentation, setting the "exact" parameter to true should return exact matches. However, this does not seem to be working as expected.

Example To Reproduce
Here is an example:

When I use the following API call with exact=true:
https://www.ebi.ac.uk/ols4/api/search?q=natural%20killer%20cell&ontology=cl&exact=true
The response does not prioritize the exact match. Instead, it returns "immature natural killer cell" as the first entry.

Based on my understanding, "natural killer cell" should be the first response.

In contrast, when I use exact=false:
https://www.ebi.ac.uk/ols4/api/search?q=natural%20killer%20cell&ontology=cl&exact=false
The response correctly prioritizes "natural killer cell" as the first result.

It appears that the check for the "exact" parameter may be functioning oppositely to what is intended.

@ma9253 ma9253 added the bug label May 21, 2024
@haideriqbal haideriqbal added the low priority Workaround available label Jun 12, 2024
@haideriqbal
Copy link
Collaborator

Hi @ma9253 ! sorry for the delayed response. We'll fix this as soon as possible.

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

No branches or pull requests

2 participants