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
{{ message }}
This repository was archived by the owner on Apr 28, 2025. It is now read-only.
The team discussed using the genegraph-ui (genegraph explorer) as the place to implement this, but putting this under the genegraph project.
Given the generic nature of the genegraph graphql model, where SEPIO class values are passed as arguments to queries, we need to devise a strategy for allowing our internal and external graphql users to search the SEPIO ontology easily to find necessary values.
Some of the functionality I would envision:
limit the SEPIO ontology being queried to a specific domain (i.e gene disease validity, gene dosage)
ability to query just classes, just properties or both
ability to query by sepio term, or description term(s)
ability to visualize the inheritance model of terms
The team discussed using the genegraph-ui (genegraph explorer) as the place to implement this, but putting this under the genegraph project.
Given the generic nature of the genegraph graphql model, where SEPIO class values are passed as arguments to queries, we need to devise a strategy for allowing our internal and external graphql users to search the SEPIO ontology easily to find necessary values.
Some of the functionality I would envision: