geneontology / noctua-form-legacy

Simple annoton editor workbench for Noctua.
BSD 3-Clause "New" or "Revised" License
3 stars 3 forks source link

better error messages #58

Closed krchristie closed 5 years ago

krchristie commented 6 years ago

It's really great that the error messages are now showing up in the Table view of the SAE.

I think that we need to work on making the error messages more comprehensible to curators, and maybe also thinking through what the likely error really was.

Here is a pair of errors I am seeing today, first the annoton with two rows highlighted, and then each of the two error messages when I click the exclamation point:

20180418-errorflags

This first error message:

20180418-errormessage1

This is not very human readable when it uses the ID, nor I suspect, is it true that it expected the root node of biological process, but rather that it expected any BP term.

  1. It would be more human readable if the last phrase said something in words, rather than using an ID.
  2. However, the real error here is not that I have selected the wrong GO term, but rather that I have used the wrong relationship. Considering that the autocomplete allows curators to see exactly what term they have selected, it seems much less likely for a curator to have selected the wrong GO term than to have selected the wrong relationship, so when there is a mismatch between the aspect of the GO term and the relationship used, it is probably more likely that the error is in the relationship. So an error message that would accurately tell me what to fix is to tell me that I have incorrectly used the part_of relationship. Modeled after the current error message, that could look something like this:

    MF part of Cellular Component: Wrong relationship. Expected 'occurs in'

The second error message:

20180418-errormessage2

This seems like it actually shouldn't even be an error message.

This is a 'part of' relationship between two CC terms, which is fine. It seems like it is a problem for the error checking to assume the Aspect of the term based on the relationship, rather than use the actual Aspect of the GO term used. If it did that, and had known that this is a 'part of' between two CC terms, this wouldn't even get flagged, and in fact, it disappeared when I corrected the relationship as described above.

I think that the SAE should show the actual aspect of the term that is present, rather than assuming the aspect of the term based on the relationship used.

Here is a sample model reconstructed to show just these error messages: http://68.181.125.145:8910/workbench/simple-annoton-editor/?model_id=gomodel:5ac3d47600001092

krchristie commented 6 years ago

Here's another example of an error that I think is not telling the curator something useful and is also interfering with something I want to say.

In this model: http://68.181.125.145:8910/editor/graph/gomodel:5ac3d47600001213 I entered two annotons via the DEFAULT template, and then, using the graph editor, I connected a BP term to a cell type (CL) term within each annoton because I actually want to say that the BP occurs in that cell type:

Here's the graph of the two template entered annots, plus each has an occurs in relationship between a BP term and a CL term: 20180420-snx10-graph1

Here is the SAE table view, showing errors: 20180420-saetableview

Error 1 (ruffle assembly occurs in osteoclast) 20180420-snx10error2

Error 2 (gastric acid secretion occurs in peptic cell) 20180420-snx10error1

These two above errors of "Not accepted triple" really don't mean anything to a curator. I also don't understand why it isn't accepting that a "BP occurs in a CL". I thought this was how we were supposed to say this.

On the chance that it didn't like the fact that the cell type was connected to both the MF and the BP, I removed the direct link between a MF and the CL term, but the error is unchanged: 20180420-snx10-graph2

cmungall commented 6 years ago

On 20 Apr 2018, at 17:57, Karen R Christie wrote:

These two above errors of "Not accepted triple" really don't mean anything to a curator. I also don't understand why it isn't accepting that a "BP occurs in a CL". I thought this was how we were supposed to say this.

You are correct, this seems like a bug.

vanaukenk commented 6 years ago

First error message should be changed to: "Incorrect association between term and relationship."

vanaukenk commented 6 years ago

An example of a new suggestion for the error message:

Incorrect association between 'lipid transporter activity' and 'lipid transport'

Then the image would show a graphical view of the incorrect triple.

vanaukenk commented 6 years ago

Update to 'Incorrect relationship between 'lipid transporter activity' and lipid transport'.'

tmushayahama commented 5 years ago

@vanaukenk I think this can be closed. Also thinking, if we assume that all the models are correct. Will there be a need for an error message?

vanaukenk commented 5 years ago

@tmushayahama - I think we can close the ticket here, but the issue of curator friendly error messages is something we still need to work on generally wrt Noctua.

I'm willing to bet we have some existing models that will fail shex validation, but I'm not so clear on what our SOP will be for fixing them. That may depend on the type of error.