{"action":"opened","issue":{"url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/14","labels_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/14/comments","events_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/14/events","html_url":"https://github.com/OpenTechStrategies/swoptact/issues/14","id":64353097,"number":14,"title":"Update event model","user":{"login":"cecilia-donnelly","id":1497818,"avatar_url":"https://avatars.githubusercontent.com/u/1497818?v=3","gravatar_id":"","url":"https://api.github.com/users/cecilia-donnelly","html_url":"https://github.com/cecilia-donnelly","followers_url":"https://api.github.com/users/cecilia-donnelly/followers","following_url":"https://api.github.com/users/cecilia-donnelly/following{/other_user}","gists_url":"https://api.github.com/users/cecilia-donnelly/gists{/gist_id}","starred_url":"https://api.github.com/users/cecilia-donnelly/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cecilia-donnelly/subscriptions","organizations_url":"https://api.github.com/users/cecilia-donnelly/orgs","repos_url":"https://api.github.com/users/cecilia-donnelly/repos","events_url":"https://api.github.com/users/cecilia-donnelly/events{/privacy}","received_events_url":"https://api.github.com/users/cecilia-donnelly/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-25T19:28:58Z","updated_at":"2015-03-25T19:28:58Z","closed_at":null,"body":"* Remove map and address fields.\r\n* Each event is either a “terminal” event or a “prep” event. This will be expressed via a new field “prep/terminal.”  If prep, then we will show another field that links to the terminal event.  They will have several planning/prep meetings before any action. The prep meetings would have the action event as their terminal event.  Most events, then, will be of the \"prep\" variety, and will link to a terminal event (e.g. \"Rally with the Governor\" or similar).\r\n* Add \"tags\" to each event.  This system would be for admins, who will control tag namespace and use them for reporting (possible tags: “housing,” “TTM”).  The number of tags is unlimited.  New tags are defined by users.\r\n* Add 200-char \"Event Description\" field (reads something like: “education, parent mentors, pre-vacation meeting”).  This will later be used by admins to assign tags.  It is fine if this is left empty.\r\n* On a cosmetic level, the event page should show name, description, and tags horizontally across the top.\r\n* From the event page, users should still be able to add a person to the event (regardless of spreadsheet handling page, #13), but via a simple dropdown, not the current horizontal filter setup.  Users found the filter confusing/distracting."}}