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
Primary example is on the term tracker Gene Breakdown.
Organisms like dog, cow, pig, chicken are of lower use. Since most of these annotations are computational, and the number of people using them is small, I'm not sure it adds enough value.
It should be a server configuration to choose which organisms to work with so we can re-enable them if we feel the need.
The text was updated successfully, but these errors were encountered:
Just to clarify, there's probably no major downside to keeping these orgs in our database and allowing the API to support them. Just about the web interface.
(Are these the organisms you'd like enabled on production?)
What is currently not supported is differentiating organisms loaded from organisms displayed thus allowing a situation where we display a subset of organisms in the UI but allow all in the API.
JacobsonMT
changed the title
Possibly drop support for all but main model organisms + H.s.
Differentiate organisms loaded from organisms displayed in UI
Mar 6, 2018
Primary example is on the term tracker Gene Breakdown.
Organisms like dog, cow, pig, chicken are of lower use. Since most of these annotations are computational, and the number of people using them is small, I'm not sure it adds enough value.
It should be a server configuration to choose which organisms to work with so we can re-enable them if we feel the need.
The text was updated successfully, but these errors were encountered: