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
Well, since we're about to switch to the new upstream geneontology/go-site/metadata/db-xrefs.yaml, this will be pushed down the road a little. Punt to 2.3.
kltm
changed the title
Switch to the new go-db-xrefs.json produced on kltm/go-site
Switch to the new go-db-xrefs.json produced on @geneontology/go-site
Apr 7, 2015
AmiGO currently does not really use entity types, just the database name for the look ups. However, that means that for things like TAIR, we're just using the last one for the map. Is that acceptable behavior? I seems to be the current behavior, and I'm not sure of an easy fix, but it might be good to talk about it.
As stated, switch to the new go-db-xrefs.json produced on kltm/go-site. This depends on geneontology/go-site#33.
The text was updated successfully, but these errors were encountered: