Skip to content
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

obo file formatting problems #5

Closed
bellerbrock opened this issue Sep 2, 2016 · 3 comments
Closed

obo file formatting problems #5

bellerbrock opened this issue Sep 2, 2016 · 3 comments

Comments

@bellerbrock
Copy link
Contributor

format of traits and variables in cropontology.org obo download (http://www.cropontology.org/obo/CO_331):

[Term]
id: CO_331:0000069
name: Storage Root Shape (primary)
namespace: Sweet PotatoTrait
def: "undefined" []
namespace: Sweet PotatoScale
relationship: scale_of CO_331:Morphological%20trait

[Term]
id: CO_331:0000774
name: RtShpP_Et_1to8
synonym: "RTSHP1" EXACT []
namespace: SweetpotatoVariable
relationship: variable_of CO_331:0000069

format needed for sweetpotatobase (and other sgn databases):

[Term]
id: CO_331:0000069
name: Storage Root Shape (primary)
namespace: SweetpotatoTrait
def: "Storage Root Shape described from longitudinal sections made about the middle of freshly harvested storage roots" [Huaman1991:Def_4.2.1]
comment: | Entity: Root | Attribute: Shape | Trait status: Recommended.
synonym: "RtShpP" EXACT []
is_a: CO_331:0000002 ! Morphological trait

[Term]
id: CO_331:0000774
name: Storage Root Shape primary estimating 1-8
namespace: SweetpotatoTrait
def: "Storage Root Shape described from longitudinal sections made about the middle of freshly harvested storage roots" [Huaman1991:Def_4.2.1]
synonym: "RTSHP1" EXACT []
synonym: "RtShpP_Et_1to8" EXACT []
relationship: variable_of CO_331:0000069 ! Storage Root Shape (primary)

@marieALaporte
Copy link
Collaborator

You are right, something is going wrong with output from the website. I will work on that next week.
Thanks !

Le 2 sept. 2016 à 18:43, Bryan Ellerbrock notifications@github.com a écrit :

format of traits and variables in cropontology.org obo download (http://www.cropontology.org/obo/CO_331):

[Term]
id: CO_331:0000069
name: Storage Root Shape (primary)
namespace: Sweet PotatoTrait
def: "undefined" []
namespace: Sweet PotatoScale
relationship: scale_of CO_331:Morphological%20trait

[Term]
id: CO_331:0000774
name: RtShpP_Et_1to8
synonym: "RTSHP1" EXACT []
namespace: SweetpotatoVariable
relationship: variable_of CO_331:0000069

format needed for sweetpotatobase (and other sgn databases):

[Term]
id: CO_331:0000069
name: Storage Root Shape (primary)
namespace: SweetpotatoTrait
def: "Storage Root Shape described from longitudinal sections made about the middle of freshly harvested storage roots" [Huaman1991:Def_4.2.1]
comment: | Entity: Root | Attribute: Shape | Trait status: Recommended.
synonym: "RtShpP" EXACT []
is_a: CO_331:0000002 ! Morphological trait

[Term]
id: CO_331:0000774
name: Storage Root Shape primary estimating 1-8
namespace: SweetpotatoTrait
def: "Storage Root Shape described from longitudinal sections made about the middle of freshly harvested storage roots" [Huaman1991:Def_4.2.1]
synonym: "RTSHP1" EXACT []
synonym: "RtShpP_Et_1to8" EXACT []
relationship: variable_of CO_331:0000069 ! Storage Root Shape (primary)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@bellerbrock
Copy link
Contributor Author

@marieALaporte great, thanks! Updating the .obo output format would be a big help, and not just for sweetpotatobase.

Also, is there any procedure in place for small fixes to the ontology displayed on cropontology.org?

I've come across a few miss-spellings and misplaced characteristics. For example the morphological trait
Storage Root Attachement is spelled wrong, and the biochemical trait Asparagine content has an incorrect trait description - it's displaying the description for Peonidin content.

@marieALaporte
Copy link
Collaborator

@bellerbrock I am closing the issue as I think this has been resolved. Reopen it if it is not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants