{"action":"created","issue":{"url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End/issues/2709","repository_url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End","labels_url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End/issues/2709/labels{/name}","comments_url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End/issues/2709/comments","events_url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End/issues/2709/events","html_url":"https://github.com/zooniverse/Panoptes-Front-End/issues/2709","id":161327458,"number":2709,"title":"subject exports have duplicate subject_ids in different rows","user":{"login":"vrooje","id":2357126,"avatar_url":"https://avatars.githubusercontent.com/u/2357126?v=3","gravatar_id":"","url":"https://api.github.com/users/vrooje","html_url":"https://github.com/vrooje","followers_url":"https://api.github.com/users/vrooje/followers","following_url":"https://api.github.com/users/vrooje/following{/other_user}","gists_url":"https://api.github.com/users/vrooje/gists{/gist_id}","starred_url":"https://api.github.com/users/vrooje/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vrooje/subscriptions","organizations_url":"https://api.github.com/users/vrooje/orgs","repos_url":"https://api.github.com/users/vrooje/repos","events_url":"https://api.github.com/users/vrooje/events{/privacy}","received_events_url":"https://api.github.com/users/vrooje/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-06-21T00:51:25Z","updated_at":"2016-06-21T20:58:44Z","closed_at":null,"body":"I'm working with GZBL data (project_id == 3) and the subject export has ~2x as many rows as there are subject_ids in the project. I think that's because I have several thousand subjects that are in multiple subject sets and multiple workflows, and the subject exporter is giving me one row per subject_id+workflow_id combination. Or per subject_id+subject_set_id combination; I can't tell which. Here's an excerpt from the subject export, sorted by subject_id (the unsorted row number is at the far left):\r\n![screen shot 2016-06-20 at 5 47 16 pm](https://cloud.githubusercontent.com/assets/2357126/16214635/508f3972-370f-11e6-8cbf-68c69657e948.jpg)\r\n\r\nThe retired_in_workflow seems to have the info about all workflows in all rows, but the classifications_by_workflow isn't combining into a single list in the same way. This is not the intended behavior, correct?"},"comment":{"url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End/issues/comments/227569730","html_url":"https://github.com/zooniverse/Panoptes-Front-End/issues/2709#issuecomment-227569730","issue_url":"https://api.github.com/repos/zooniverse/Panoptes-Front-End/issues/2709","id":227569730,"user":{"login":"vrooje","id":2357126,"avatar_url":"https://avatars.githubusercontent.com/u/2357126?v=3","gravatar_id":"","url":"https://api.github.com/users/vrooje","html_url":"https://github.com/vrooje","followers_url":"https://api.github.com/users/vrooje/followers","following_url":"https://api.github.com/users/vrooje/following{/other_user}","gists_url":"https://api.github.com/users/vrooje/gists{/gist_id}","starred_url":"https://api.github.com/users/vrooje/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vrooje/subscriptions","organizations_url":"https://api.github.com/users/vrooje/orgs","repos_url":"https://api.github.com/users/vrooje/repos","events_url":"https://api.github.com/users/vrooje/events{/privacy}","received_events_url":"https://api.github.com/users/vrooje/received_events","type":"User","site_admin":false},"created_at":"2016-06-21T20:58:44Z","updated_at":"2016-06-21T20:58:44Z","body":"Just to clarify, that would mean the `retired_in_workflow` column in the screenshot above would, for the above example where the subjects are retired in all workflows, be a duplicate of the `workflow_ids` column?\r\n\r\nWhat I'd originally thought was that this should just be 2 rows, with the `workflow_ids`, `subject_set_id`, and `classifications_by_workflow` columns showing the combined info that's currently on separate rows. But thinking further that does potentially lose info about which subject_set_id was associated with the workflow, and that's why this is this way, right?\r\n\r\nSorry for thinking \"out loud\" here -- but, yes, if the `retired_in_workflow` column reflected only the ssid and workflow_id relevant to that row that would make it easier to combine these or keep them separate as needed. Thanks.\r\n\r\nIs this documented anywhere yet on the project builder side @aliburchard ?"}}
{"actor":{"display_login":"vrooje"}}