You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: