{"action":"created","issue":{"url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/13","labels_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/13/comments","events_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/13/events","html_url":"https://github.com/OpenTechStrategies/swoptact/issues/13","id":64352742,"number":13,"title":"Add \"sign-in-sheet handling page\"","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":[{"url":"https://api.github.com/repos/OpenTechStrategies/swoptact/labels/high-priority","name":"high-priority","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-25T19:27:26Z","updated_at":"2015-04-12T23:21:35Z","closed_at":null,"body":"Most data entry into this system will occur because a user has a paper sign-in sheet from an event and needs to enter the event information and the names of attendees into Swoptact.  This page will make that a seamless process.\r\n\r\nAt top of page, search/create event information: name, date, site.  If the event already exists (if this is the second or nth sign-in sheet from the event, or if the event was created beforehand) then users will be able to start typing its name and choose it from the filtered completion options (just as they should be able to do for people, in the next paragraph).  If it does not exist, then entering the information here will auto-save it.\r\n\r\nBelow the event information, show a table with columns name, institution, phone (these three are the most important, and must appear first), and other participant information so a user can start typing a name and see options below (e.g., typing “Ma” shows “Maria, Mary, Matthew” below, where Maria, Mary, and Matthew are previously entered people in the database). When the user chooses one of these previously entered people, his/her information fills in the remaining columns. If the person being entered is a new person, then that new record is saved in the db, _and_ that new person record is linked to this event.  When a row is entered, a new empty one appears below, and the previous entries stay on the screen.  Each row (each person linked to the event) should auto-save, in case something goes wrong before they finish entering the whole sign-in sheet."},"comment":{"url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/comments/92150643","html_url":"https://github.com/OpenTechStrategies/swoptact/issues/13#issuecomment-92150643","issue_url":"https://api.github.com/repos/OpenTechStrategies/swoptact/issues/13","id":92150643,"user":{"login":"cwebber","id":55698,"avatar_url":"https://avatars.githubusercontent.com/u/55698?v=3","gravatar_id":"","url":"https://api.github.com/users/cwebber","html_url":"https://github.com/cwebber","followers_url":"https://api.github.com/users/cwebber/followers","following_url":"https://api.github.com/users/cwebber/following{/other_user}","gists_url":"https://api.github.com/users/cwebber/gists{/gist_id}","starred_url":"https://api.github.com/users/cwebber/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cwebber/subscriptions","organizations_url":"https://api.github.com/users/cwebber/orgs","repos_url":"https://api.github.com/users/cwebber/repos","events_url":"https://api.github.com/users/cwebber/events{/privacy}","received_events_url":"https://api.github.com/users/cwebber/received_events","type":"User","site_admin":false},"created_at":"2015-04-12T23:21:34Z","updated_at":"2015-04-12T23:21:34Z","body":"I originally wrote this on #14, but it's more appropriate here, so moving it.\r\n\r\n@cecilia-donnelly asked me to look into why the inline representation of the many-to-many display of \"participants\" wasn't showing up as anything other than a dropdown.  Django's docs [appear to give the answer for this](https://docs.djangoproject.com/en/1.7/ref/contrib/admin/#working-with-many-to-many-models) but in reality it seems that Cecilia has correctly executed the advice from this and given [other conversations on the internet](http://stackoverflow.com/questions/10904848/adding-inline-many-to-many-objects-in-django-admin), very confusingly seeing the many to many dropdown is \"expected\"??? Which doesn't seem right.\r\n\r\nSuggestions on that thread are that we subclass the form and modify the [.form attribute](https://docs.djangoproject.com/en/1.7/ref/contrib/admin/#django.contrib.admin.ModelAdmin.form) in order to get the behavior we want.  Which, okay, though that seems like a surprising amount of work for something that seemed implied like it would work having followed the docs' instructions for many2many fields."}}