{"action":"created","issue":{"url":"https://api.github.com/repos/SEED-platform/seed/issues/781","repository_url":"https://api.github.com/repos/SEED-platform/seed","labels_url":"https://api.github.com/repos/SEED-platform/seed/issues/781/labels{/name}","comments_url":"https://api.github.com/repos/SEED-platform/seed/issues/781/comments","events_url":"https://api.github.com/repos/SEED-platform/seed/issues/781/events","html_url":"https://github.com/SEED-platform/seed/issues/781","id":135589044,"number":781,"title":"Mapping hangs if there is a duplicate field name in the data","user":{"login":"RDmitchell","id":6314950,"avatar_url":"https://avatars.githubusercontent.com/u/6314950?v=3","gravatar_id":"","url":"https://api.github.com/users/RDmitchell","html_url":"https://github.com/RDmitchell","followers_url":"https://api.github.com/users/RDmitchell/followers","following_url":"https://api.github.com/users/RDmitchell/following{/other_user}","gists_url":"https://api.github.com/users/RDmitchell/gists{/gist_id}","starred_url":"https://api.github.com/users/RDmitchell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RDmitchell/subscriptions","organizations_url":"https://api.github.com/users/RDmitchell/orgs","repos_url":"https://api.github.com/users/RDmitchell/repos","events_url":"https://api.github.com/users/RDmitchell/events{/privacy}","received_events_url":"https://api.github.com/users/RDmitchell/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/SEED-platform/seed/labels/2","name":"2","color":"fbca04"},{"url":"https://api.github.com/repos/SEED-platform/seed/labels/Mapping","name":"Mapping","color":"5319e7"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/SEED-platform/seed/milestones/32","html_url":"https://github.com/SEED-platform/seed/milestones/June%202016%20Release","labels_url":"https://api.github.com/repos/SEED-platform/seed/milestones/32/labels","id":1436517,"number":32,"title":"June 2016 Release","description":"End of June release","creator":{"login":"RDmitchell","id":6314950,"avatar_url":"https://avatars.githubusercontent.com/u/6314950?v=3","gravatar_id":"","url":"https://api.github.com/users/RDmitchell","html_url":"https://github.com/RDmitchell","followers_url":"https://api.github.com/users/RDmitchell/followers","following_url":"https://api.github.com/users/RDmitchell/following{/other_user}","gists_url":"https://api.github.com/users/RDmitchell/gists{/gist_id}","starred_url":"https://api.github.com/users/RDmitchell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RDmitchell/subscriptions","organizations_url":"https://api.github.com/users/RDmitchell/orgs","repos_url":"https://api.github.com/users/RDmitchell/repos","events_url":"https://api.github.com/users/RDmitchell/events{/privacy}","received_events_url":"https://api.github.com/users/RDmitchell/received_events","type":"User","site_admin":false},"open_issues":45,"closed_issues":2,"state":"open","created_at":"2015-12-01T02:12:12Z","updated_at":"2016-02-23T00:31:01Z","due_on":"2016-06-30T07:00:00Z","closed_at":null},"comments":3,"created_at":"2016-02-23T00:30:38Z","updated_at":"2016-02-23T01:01:46Z","closed_at":null,"body":"If a file being imported has a duplicate field name, ie, two field names that are either identical or interpreted by the program as identical, the program hangs during the mapping phase. \r\n\r\nThe question is what to do in this case? Seems like there are a few options:\r\n\r\n1. Inform the user that they need to fix their data and reimport it\r\n2. rename internally the file names so that they are no longer duplicated (this seems like a bad idea to me)\r\n3. Give the user the opportunity to edit their original field name (not just the SEED header field name) in the mapping screen -- this is a bit tricky because then the original raw data in SEED doesn't match the raw data in their original spreadsheet, but maybe this is ok. \r\n4. **Allow the user to just select one of the fields to be imported** -- right now you can do that, but it doesn't work, so maybe this is the best option to pursue. So the user could uncheck one of the duplicate fields, and the program would not import it and would therefore not have the duplicate field name conflict.\r\n"},"comment":{"url":"https://api.github.com/repos/SEED-platform/seed/issues/comments/187458608","html_url":"https://github.com/SEED-platform/seed/issues/781#issuecomment-187458608","issue_url":"https://api.github.com/repos/SEED-platform/seed/issues/781","id":187458608,"user":{"login":"RDmitchell","id":6314950,"avatar_url":"https://avatars.githubusercontent.com/u/6314950?v=3","gravatar_id":"","url":"https://api.github.com/users/RDmitchell","html_url":"https://github.com/RDmitchell","followers_url":"https://api.github.com/users/RDmitchell/followers","following_url":"https://api.github.com/users/RDmitchell/following{/other_user}","gists_url":"https://api.github.com/users/RDmitchell/gists{/gist_id}","starred_url":"https://api.github.com/users/RDmitchell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/RDmitchell/subscriptions","organizations_url":"https://api.github.com/users/RDmitchell/orgs","repos_url":"https://api.github.com/users/RDmitchell/repos","events_url":"https://api.github.com/users/RDmitchell/events{/privacy}","received_events_url":"https://api.github.com/users/RDmitchell/received_events","type":"User","site_admin":false},"created_at":"2016-02-23T01:01:46Z","updated_at":"2016-02-23T01:01:46Z","body":"@rebrownlbnl  -- Right, I didn't understand it at first either. \r\nThe program can deal with two fields in the original data file that have different names, but SEED gives them the same \"SEED Header\" name suggestion. The user can then change the SEED Header name to not be duplicated. \r\n\r\nHowever, this is a case where the actual original data has the same field name -- that is the case that the program can't handle. So we just have to figure out a nice way to handle it, and I think the 4th option I list in my original (edited) comment might be the way to go. But the other option, that the user could pick, would be to fix their original data and reimport it. "}}