{"action":"opened","issue":{"url":"https://api.github.com/repos/VirtualFlyBrain/VFB/issues/703","labels_url":"https://api.github.com/repos/VirtualFlyBrain/VFB/issues/703/labels{/name}","comments_url":"https://api.github.com/repos/VirtualFlyBrain/VFB/issues/703/comments","events_url":"https://api.github.com/repos/VirtualFlyBrain/VFB/issues/703/events","html_url":"https://github.com/VirtualFlyBrain/VFB/issues/703","id":106019595,"number":703,"title":"Fixing confusing type column in Display table","user":{"login":"dosumis","id":112839,"avatar_url":"https://avatars.githubusercontent.com/u/112839?v=3","gravatar_id":"","url":"https://api.github.com/users/dosumis","html_url":"https://github.com/dosumis","followers_url":"https://api.github.com/users/dosumis/followers","following_url":"https://api.github.com/users/dosumis/following{/other_user}","gists_url":"https://api.github.com/users/dosumis/gists{/gist_id}","starred_url":"https://api.github.com/users/dosumis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dosumis/subscriptions","organizations_url":"https://api.github.com/users/dosumis/orgs","repos_url":"https://api.github.com/users/dosumis/repos","events_url":"https://api.github.com/users/dosumis/events{/privacy}","received_events_url":"https://api.github.com/users/dosumis/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/VirtualFlyBrain/VFB/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/VirtualFlyBrain/VFB/labels/VFB_1.5","name":"VFB_1.5","color":"eb6420"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-11T14:16:01Z","updated_at":"2015-09-11T14:16:01Z","closed_at":null,"body":"The name column display table in VFB 1.5 is a mix of individuals and classes.  The type column is a mix of types (for individuals) and parent classes (for classes).  e.g.\r\n\r\n![screen shot 2015-09-11 at 3 00 34 pm](https://cloud.githubusercontent.com/assets/112839/9816598/e9b92062-5895-11e5-8129-1ac8a0a20769.png)\r\n\r\nGad1-F-200073 is an individual (to simplify the interface, perhaps better referred to an image?).  Its type is 'adult antennal lobe projection neuron DL1 adPN'.  Lateral horn is a class.  Its parent class is 'synaptic neuropil domain.\r\n\r\nThis is confusing. An all round better solution would be to treat painted domains as individuals.\r\n\r\n![screen shot 2015-09-11 at 3 04 03 pm](https://cloud.githubusercontent.com/assets/112839/9816670/608fa170-5896-11e5-952d-9d999cf17e9c.png)\r\n\r\nI've generated individuals for all painted domains on the JFRC2 template (I haven't bothered to create separate individuals for left and right domains.). I can do the same for the Ito half brain.  Linking these to thumbnails as for  other registered images should allow image display to slot into the existing system (e.g. showing up at the bottom of TermInfo pages.\r\n\r\nI've been puzzling over how to fill in data source fields and fields used to create links.  There are a couple of issues.\r\n\r\n(i) The current system is designed for serving external links.  This doesn't play nicely with internal links (where we want to change the base URI to fit test servers).  Any suggestions for how to cope with this?\r\n(ii) It makes sense to use the same reference as we have on the site for the JFRC standard brain.  I'm wondering whether we should change this to reference the GAL4 driver line paper http://www.cell.com/action/showImagesData?pii=S2211-1247%2812%2900292-6  - Adding a note about subsequent modifications by Jenett and Shinomiya to fit with BrainName standard.\r\n\r\n\r\n\r\n\r\n\r\n"}}