{"action":"created","issue":{"url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/1003","labels_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/1003/labels{/name}","comments_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/1003/comments","events_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/1003/events","html_url":"https://github.com/mozilla/teach.webmaker.org/issues/1003","id":86347787,"number":1003,"title":"Creating reports from site admin UI","user":{"login":"ldecoursy","id":4885898,"avatar_url":"https://avatars.githubusercontent.com/u/4885898?v=3","gravatar_id":"","url":"https://api.github.com/users/ldecoursy","html_url":"https://github.com/ldecoursy","followers_url":"https://api.github.com/users/ldecoursy/followers","following_url":"https://api.github.com/users/ldecoursy/following{/other_user}","gists_url":"https://api.github.com/users/ldecoursy/gists{/gist_id}","starred_url":"https://api.github.com/users/ldecoursy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ldecoursy/subscriptions","organizations_url":"https://api.github.com/users/ldecoursy/orgs","repos_url":"https://api.github.com/users/ldecoursy/repos","events_url":"https://api.github.com/users/ldecoursy/events{/privacy}","received_events_url":"https://api.github.com/users/ldecoursy/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mozilla/teach.webmaker.org/labels/clubs%20workflow","name":"clubs workflow","color":"bfd4f2"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-06-08T22:01:43Z","updated_at":"2015-06-09T16:02:44Z","closed_at":null,"body":"As part of the Clubs workflow, when someone submits a club, our goal is to assign them to an RC, who would follow-up with that person and have a short discussion before determining whether to approve/deny a club. Unfortunately the description isn't always enough to go by, and as part of the organizing model, we want to provide a level of personalization to build lasting relationships. \r\n\r\nWe currently have 99 clubs in the system, and are trying to determine the best way to divvy up the current list among RCs and Staff Organizers so we can test the workflow/process. \r\n\r\nIn the best case scenario, we could export a report that includes:\r\n* Name\r\n* Location\r\n* Email\r\n* Club description\r\n\r\nFor now, if possible to just have emails added to the admin view, that would be a big help. That information is currently only available when we receive an email that a club has been added (but we won't want all RCs to receive those emails). Since RCs will be doing follow-up, we'll need an easier way to get them that info. "},"comment":{"url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/comments/110415893","html_url":"https://github.com/mozilla/teach.webmaker.org/issues/1003#issuecomment-110415893","issue_url":"https://api.github.com/repos/mozilla/teach.webmaker.org/issues/1003","id":110415893,"user":{"login":"toolness","id":124687,"avatar_url":"https://avatars.githubusercontent.com/u/124687?v=3","gravatar_id":"","url":"https://api.github.com/users/toolness","html_url":"https://github.com/toolness","followers_url":"https://api.github.com/users/toolness/followers","following_url":"https://api.github.com/users/toolness/following{/other_user}","gists_url":"https://api.github.com/users/toolness/gists{/gist_id}","starred_url":"https://api.github.com/users/toolness/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toolness/subscriptions","organizations_url":"https://api.github.com/users/toolness/orgs","repos_url":"https://api.github.com/users/toolness/repos","events_url":"https://api.github.com/users/toolness/events{/privacy}","received_events_url":"https://api.github.com/users/toolness/received_events","type":"User","site_admin":false},"created_at":"2015-06-09T16:02:44Z","updated_at":"2015-06-09T16:02:44Z","body":"Doh sorry lol, I submitted that last comment before I had looked up the relevant issue I'd mentioned it in. I also mis-wrote--I meant \"staff notes\", not \"club status\", and I mentioned it in https://github.com/mozilla/teach.webmaker.org/issues/911#issuecomment-105879915:\r\n\r\n> Given the fact that clubs will be managed by different individuals with different roles at different times, and that the approval flow will likely involve lots of different phases, I'm wondering if we should add a \"staff notes\" field to the Club model.\r\n\r\n> This would be a field that is only visible to staff users of the [admin UI](https://github.com/mozilla/teach.webmaker.org/issues/925#issuecomment-104705395), and they could update it with any information relevant to the current approval flow status of the club that isn't otherwise captured by the system, e.g. \"RC alice has set up a 1:1 interview w/ the club lead on june 5\". This way more information is stored in the DB for all staff to see, rather than e.g. stuffed in an email thread somewhere that only a few people can see.\r\n\r\nThere are definite downsides to that approach, though, which we talked a bit about on a stand or something."}}