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 has been archived by the owner on Jun 21, 2022. It is now read-only.
In OLS it is possible to specify linkouts from xrefs and to display reference images. We should take advantage of this to get links to VFB and to supply reference images to OLS.
Expansion of the xrefs into hyperlinks is driven by the GOdb-xrefs.yaml doc. Although OLS could take additional docs for this. We should investigate extending this yaml to allow specification of a logo PNG for linking ( CC @cmungall ).
This provides one route for specifying linkouts as we already roll these to drive linkouts from FlyBase:
These xrefs are added to nervous system terms as part of the release pipeline (@temjones do you know if this still happens?) and are used to provide linkouts from FlyBase to VFB.
A simpler mechanism would be to use the short_form or OBO ID (curie) to drive linkouts to the same term in OLS on a range of alternative browsers (for GO this could be Amigo & QuickGO). The obvious place to specify this would be in the obofoundry spec: https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/ontology/fbbt.md. This already has generic browser links. It would be great if these could be turned into link recipes to allow linking on specific terms (CC @cmungall would this be overloading? )
The text was updated successfully, but these errors were encountered:
@dosumis My understanding is that the VFB xrefs are added manually upon creation of new anatomy terms, in OBO the line:
Hmmm - that's slightly terrifying. Some will undoubtedly fall through the cracks. I'm sure I had this automated at some point and we should be able to do so again.
I don’t remember this being automated, but yes, it would be better if so.
What we show in VFB (and wanted linkouts from) has also changed though: we use to only show neural terms, and I think now the queries are not restricted. I think I’d made a ticket about this a couple of months ago (I don’t know where this now).
On 18 Dec 2017, at 14:34, David Osumi-Sutherland ***@***.***> wrote:
@dosumis <https://github.com/dosumis> My understanding is that the VFB xrefs are added manually upon creation of new anatomy terms, in OBO the line:
Hmmm - that's slightly terrifying. Some will undoubtedly fall through the cracks. I'm sure I had this automated at some point and we should be able to do so again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#39 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AByQ0yEoVNjoZcbP3r05byONJve185y3ks5tBnf_gaJpZM4RFfpe>.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In OLS it is possible to specify linkouts from xrefs and to display reference images. We should take advantage of this to get links to VFB and to supply reference images to OLS.
e.g. liver has xrefs to MA and EMAPA:
And an image of a liver:
![image](https://user-images.githubusercontent.com/112839/34108449-ff996640-e3f7-11e7-9086-f408fa578ee7.png)
Expansion of the xrefs into hyperlinks is driven by the GOdb-xrefs.yaml doc. Although OLS could take additional docs for this. We should investigate extending this yaml to allow specification of a logo PNG for linking ( CC @cmungall ).
This provides one route for specifying linkouts as we already roll these to drive linkouts from FlyBase:
![image](https://user-images.githubusercontent.com/112839/34108618-b007170c-e3f8-11e7-928b-0e0cf54d2ddc.png)
These xrefs are added to nervous system terms as part of the release pipeline (@temjones do you know if this still happens?) and are used to provide linkouts from FlyBase to VFB.
A simpler mechanism would be to use the short_form or OBO ID (curie) to drive linkouts to the same term in OLS on a range of alternative browsers (for GO this could be Amigo & QuickGO). The obvious place to specify this would be in the obofoundry spec: https://github.com/OBOFoundry/OBOFoundry.github.io/blob/master/ontology/fbbt.md. This already has generic browser links. It would be great if these could be turned into link recipes to allow linking on specific terms (CC @cmungall would this be overloading? )
The text was updated successfully, but these errors were encountered: