{"action":"opened","issue":{"url":"https://api.github.com/repos/codaco/Network-Canvas/issues/582","repository_url":"https://api.github.com/repos/codaco/Network-Canvas","labels_url":"https://api.github.com/repos/codaco/Network-Canvas/issues/582/labels{/name}","comments_url":"https://api.github.com/repos/codaco/Network-Canvas/issues/582/comments","events_url":"https://api.github.com/repos/codaco/Network-Canvas/issues/582/events","html_url":"https://github.com/codaco/Network-Canvas/issues/582","id":338991995,"node_id":"MDU6SXNzdWUzMzg5OTE5OTU=","number":582,"title":"Identifying ego in a roster ","user":{"login":"berniehogan","id":1711620,"node_id":"MDQ6VXNlcjE3MTE2MjA=","avatar_url":"https://avatars2.githubusercontent.com/u/1711620?v=4","gravatar_id":"","url":"https://api.github.com/users/berniehogan","html_url":"https://github.com/berniehogan","followers_url":"https://api.github.com/users/berniehogan/followers","following_url":"https://api.github.com/users/berniehogan/following{/other_user}","gists_url":"https://api.github.com/users/berniehogan/gists{/gist_id}","starred_url":"https://api.github.com/users/berniehogan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/berniehogan/subscriptions","organizations_url":"https://api.github.com/users/berniehogan/orgs","repos_url":"https://api.github.com/users/berniehogan/repos","events_url":"https://api.github.com/users/berniehogan/events{/privacy}","received_events_url":"https://api.github.com/users/berniehogan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-07-06T16:02:47Z","updated_at":"2018-07-06T16:02:47Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"If we are doing a roster, we need a way to identify that the respondent is one of the people who are in the roster. \r\n\r\nThis might involve selecting ego from a node form (which would be a Network Canvas issue), or somehow putting ego in the name of the file. Ideally, it should be a way that when we export the data from Server where there is a roster we can link these together in a whole network. \r\n\r\nIt is a Network Canvas issue since we need an 'ego form' that is someone linked to the roster. "}}
{"actor":{"display_login":"berniehogan"}}