Open sstemann opened 1 year ago
@sstemann is this issue linked with #282 and #342 or is that a completely different issue? I am trying to move along this "no status ticket". Thank you!
I read this as being closer to #342, but it's a wider issue: it would be great if Translator had much stronger ways to explain the provenance of each assertion.
To clarify, when I write 'a dynamic page', I mean a page that is tailored to the specific example being explained, as opposed to a page that explains what the KP/ARA does in generic terms.
Thank you @gglusman ! Those are great points! If I can add to your first point, it could be nice to be able to link in a user readible format to the definitions of our categories and predicates from the biolink model as a way to express possible discrepencies in what is reported by a source and what predicate maps to this definition. That would explain (provenance) the choice of vocabulary presented to the user and internally represented.
@sstemann @gglusman @sandrine-m we are not sure if this ticket has changed from the initial intent or what the feature request actually is. Please advise.
from TAQA: Matt: in the retrieval source object - source_url holds the direct link, but coordinating the implementation of this with KPs hasn't bubbled up yet. Gwenlyn: there is already lots of EPC on the edges from TMKP - we just need a link to that information (e.g. the sentence, provenance of edges -- Bill: the feedback interface built for SEMMED working group - consolidates EPC into a visual form). Gus: this is exactly what we need; need to get back to us on when to implement. seems high priority.
@gprice1129 - is there any priority being discussed for this issue in the UI team?
@sierra-moxon yes, we have discussed this quite a bit. We will be working on this in the future, but it probably won't be implemented by Octopus.
Doing the "math" as Andy calls it of the reasoning is cumbersome for users. We're not sure if this is something the UI can enhance.