Closed lpalbou closed 4 years ago
If you run the reasoner the little red error box appears in the upper left showing a Shex failure. If you click on the box you get an unfriendly but accurate description of why it failed.
I should probably also point out that this works on development.
Thanks for the feedback, two comments:
@lpalbou
That is the same closure on shex and there is no validation on noctua form
@tmushayahama We should restrict the 'Gene Product' field to only allow for an InformationBiomacromolecule (CHEBI:33695) OR a ProteinContainingComplex (GO:0033291)
@vanaukenk thanks, so I will put also OR protein containing complex.
@lpalbou @goodb double check to align with shex, Golr will be ... fq: document_category:"ontology_class" fq: isa_closure:"CHEBI:33695" OR isa_closure:"GO:0032991" q: keyword ...
Thanks @thomaspd for the catch
@tmushayahama as I understand, you are doing GOLr queries on the fly to fill your autocomplete ? It seems you were using a closure of CHEBI_23367 (molecular_entity), so indeed changing it to CHEBI_33695 would do the trick and with a OR:
fq=isa_closure:("CHEBI:33695" "GO:0032991")
This issue is related to the ticket on autocomplete: https://github.com/geneontology/minerva/issues/236 . I would suggest autocomplete to become a priority for the next cycle after May as we need to have something more unified across UIs and SHEX.
@lpalbou
We are working towards aligning the autocompletes on the form with the ShEx.
See, for example: https://github.com/geneontology/noctua-form/issues/66
It is definitely on our radar, although with the caveat that the ShEx has still been under discussion a bit on the GO-CAM specs calls.
Thx.
Tested on noctua-dev and appears to be working as expected.
In this model, @tmushayahama was able to create a model with a compound as an enabler of an activity (see Kanamycin A on the right).