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

Zooma - sometimes get better result if don't have property type #17

Open
olgavrou opened this issue Nov 8, 2017 · 0 comments
Open

Zooma - sometimes get better result if don't have property type #17

olgavrou opened this issue Nov 8, 2017 · 0 comments

Comments

@olgavrou
Copy link
Contributor

olgavrou commented Nov 8, 2017

I'm not sure if this is a good thing or not, but for some property values I get an automatic (correct) hit if I don't put the property type in, but a 'requires curation' one when I do put the property type in.
I want to maximise the number of automatic hits to really I want the behaviour without the property type being taken into account.
Examples are
embryonic day 13.5 developmental stage
Col-1 ecotype
Somehow it would be good to downgrade the effect of similar property values with the same type, and keep the score for the exact match up.

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