You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I omitted GSSO and HP in the initial setup of the GCBO repository because importing respective modules of the above terms leads our QC pipeline to throw errors. There are a lot of issues with GSSO as reported by the OBO Dashboard -- over 1000 errors according to the ROBOT report.
For all the variables above, we have links to ontology terms from other ontologies, e.g., SYMP, NBO, or NCIT. The only two exceptions are:
Many terms in GSSO appear to be copied from other ontologies (such as NCIT) and contain textual definitions that are copied verbatim from Wikipedia - without being marked as direct quotes as far as I can tell. I understand that GSSO is still in development. However, I am hesitant to build on GSSO at this point.
The original mapping of variables in the Global Code Book to ontology terms included the following terms from GSSO and HP:
nih_race GSSO:002199
nih_disability GSSO:001811
nih_disability GSSO:001810
nih_alcohol_yn GSSO:006602
nih_lifetime_use_alcohol GSSO:006602
nih_alcohol_yrs GSSO:006602
nih_alcohol_frequency GSSO:006602
nih_premature_birth GSSO:009644
nih_deaf HP:0000364
I omitted GSSO and HP in the initial setup of the GCBO repository because importing respective modules of the above terms leads our QC pipeline to throw errors. There are a lot of issues with GSSO as reported by the OBO Dashboard -- over 1000 errors according to the ROBOT report.
For all the variables above, we have links to ontology terms from other ontologies, e.g., SYMP, NBO, or NCIT. The only two exceptions are:
nih_premature_birth GSSO:009644
nih_race GSSO:002199
However, in both cases, there are corresponding terms in NCIT that GSSO links to:
nih_premature_birth http://purl.obolibrary.org/obo/NCIT_C92861
nih_race http://purl.obolibrary.org/obo/NCIT_C17049
Can't we use these terms? Why do we need GSSO?
The text was updated successfully, but these errors were encountered: