At present we are showing the descendants for all has_part links in FYPO.
We would like to not follow
has_part links for any descendant of FYPO:0000257
as this leads to misleading term suggestions.
Currently Canto stores only the direct relations not the indirect ones. We will need to store something like the transitive closure to make this work. A quick-ish way to do that would be to create a subset with just FYPO:0000257 and its descendants (probably externally using Oort). We could then load that into Canto and add a flag beside each term that's in that subset.
The has_part link term suggestions are currently really confusing. I think if this is going to take some time we should remove the has_part terms suggestions totally and check out more clearly what we would expect to see (an indeed if this ticket would actually fix it). Some of the suggestions we get don't seem to be correct.
stopgap
remove has_part term suggestions form canto
longer term, reassess if/when we would want to see term suggestions by
i) documenting when a term suggestion which would be useful is missing
ii) based on accumulated decide how best to proceed
Val
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Currently Canto stores only the direct relations not the indirect ones. We will need to store something like the transitive closure to make this work. A quick-ish way to do that would be to create a subset with just FYPO:0000257 and its descendants (probably externally using Oort). We could then load that into Canto and add a flag beside each term that's in that subset.
Related:
https://sourceforge.net/p/pombase/curation-tool/431/
https://sourceforge.net/p/pombase/curation-tool/428/
OK. Let me know if you want me to create the subset in the FYPO files; it wouldn't be very hard.
Hi Kim,
The has_part link term suggestions are currently really confusing. I think if this is going to take some time we should remove the has_part terms suggestions totally and check out more clearly what we would expect to see (an indeed if this ticket would actually fix it). Some of the suggestions we get don't seem to be correct.
stopgap
remove has_part term suggestions form canto
longer term, reassess if/when we would want to see term suggestions by
i) documenting when a term suggestion which would be useful is missing
ii) based on accumulated decide how best to proceed
Val
has_part should be ignored in Canto now.
I just noticed that I had made the change but not released it. I have now.
putting this at 6 to ignore for now, re-evaluating as we curate
also superseded by removing has_part links among "normal" terms in FYPO