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 matchType as a value for the include parameter #62

Open
jvendetti opened this issue Jan 8, 2020 · 0 comments
Open

Allow matchType as a value for the include parameter #62

jvendetti opened this issue Jan 8, 2020 · 0 comments

Comments

@jvendetti
Copy link
Member

End user reported the desire to retrieve "matchType" when using the include parameter with the search endpoint:

Using the 'Term Search' endpoint in your REST API, I would like to receive the 'properties' field alongside the 'matchType' field. Right now it is only possible to receive the 'matchType' if I don't add the 'include' parameter. Using 'include=properties' removes the 'matchType' and the 'include' does not accept 'matchType'. Also, 'include=all' does not work. Is it possible to receive both fields in one response?

The following example call:

http://data.bioontology.org/search?q=melanoma&include=matchType,properties

... results in a 400 error:

"The `include` query string parameter cannot accept matchType, please use only prefLabel, synonym, definition, notation, cui, semanticType, properties"

Leaving matchType out of the list of allowed include parameters appears to have been an oversight.

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

No branches or pull requests

1 participant