-
Notifications
You must be signed in to change notification settings - Fork 39
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
Add 'curator note' property to selected classes #13384
Comments
Discussed on the ontology editors call. We think this is a good idea. How do you find the relevant notes for child terms when the note is on a parent? |
We will have a SPARQL construct that will be run periodically to propagate these down in the editors ontology. @dougli1sqrd can implement. |
@geneontology/ontology - can you provide @dougli1sqrd an example of a curator note and its associated GO ID so we can get started on this. Should we use this example: #14275 ? |
[Term] |
@ukemi Should we make this 'high priority'? |
We need examples first, don't you think? |
I thought your comment above was an example. |
OK. But I thought there was the additional step of adding a different kind of comment for obsoletions, ontology editor comments etc. We need to specify the requirements a little more. |
You mean we want more than one new type of comment? I thought this all
going to be lumped under comment for curator.
Le jeu. 31 mai 2018 à 3:02 PM, David Hill <[email protected]> a
écrit :
… OK. But I thought there was the additional step of adding a different kind
of comment for obsoletions, ontology editor comments etc. We need to
specify the requirements a little more.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#13384 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEj7UNtqrU8QptWtZz1QEQhgUUJozw1Fks5t3-n2gaJpZM4NB52d>
.
|
I didn't think so. Perhaps this is a topic for an ontology call. |
@ukemi you provided Did you intend to provide GO:0044848 ! biological phase as the example, with the intent that the same curator note is propagated down to all subclasses? |
Yes. The point was the propagation of curator notes to children following specific properties. |
We recently added editor note. I don't see how this differs from curator note. But we aren't doing any of this propagation. Is this still desired? |
On the managers call http:https://wiki.geneontology.org/index.php/Manager_Call_2017-04-19#Documentation
@pgaudet suggested improving curator documentation centered around particular terms in the ontology. I propose that we embed this directly in the ontology.
We are no longer restricted to the grab-bag 'comment' field for additional notes on a class, so I propose we create a new property or reuse something like IAO:0000232
curator note
We could add axiom annotations to each such owl annotation assertion indicating if and how this should be propagated down to descendant terms.
For some of these, it could go in the design pattern too.
By default a non-comment property will not be visible in most browsers, but these could be configured to add these.
Would this work for P2Go @tonysawfordebi?
The text was updated successfully, but these errors were encountered: