{"action":"created","issue":{"url":"https://api.github.com/repos/zooniverse/Panoptes/issues/2196","repository_url":"https://api.github.com/repos/zooniverse/Panoptes","labels_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/2196/labels{/name}","comments_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/2196/comments","events_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/2196/events","html_url":"https://github.com/zooniverse/Panoptes/issues/2196","id":209810848,"number":2196,"title":"Deactivate / ignore finished workflows?","user":{"login":"camallen","id":295329,"avatar_url":"https://avatars.githubusercontent.com/u/295329?v=3","gravatar_id":"","url":"https://api.github.com/users/camallen","html_url":"https://github.com/camallen","followers_url":"https://api.github.com/users/camallen/followers","following_url":"https://api.github.com/users/camallen/following{/other_user}","gists_url":"https://api.github.com/users/camallen/gists{/gist_id}","starred_url":"https://api.github.com/users/camallen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/camallen/subscriptions","organizations_url":"https://api.github.com/users/camallen/orgs","repos_url":"https://api.github.com/users/camallen/repos","events_url":"https://api.github.com/users/camallen/events{/privacy}","received_events_url":"https://api.github.com/users/camallen/received_events","type":"User","site_admin":false},"labels":[{"id":94298936,"url":"https://api.github.com/repos/zooniverse/Panoptes/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-02-23T16:23:22Z","updated_at":"2017-02-23T19:51:16Z","closed_at":null,"body":"Should we deactivate them where we can? Will this impact on the UI of a project and just leave the last one to finish standing? OR should we just ignore finished workflows in selection via a short circuit to a fallback selector? \r\n\r\nThe trick is will be to move volunteers into a new workflow so we'll probably need to deactivate it (if there are other active ones) especially if the project doesn't allow a user to choose their workflow. \r\n\r\nExample:\r\n\r\nProject has 2 active workflows:\r\n1. Start your search\r\n2. Continue your search\r\n\r\nThe project does not allow users to choose which one they work on, a workflow is assigned randomly via the UI on page load and then stored for reference in the api.\r\n\r\nStart your search finishes all the data at 10am but remains active and thus the user preferences keep wiring up the UI to use that finished workflow. The subject selection services return nothing and the api reverts to double checking internal selection (our services can get out of sync).\r\n\r\nSo i think we want all workflow 1 users to get finished / already seen flags in the UI (if they are already on the classify page) and if they navigate back to classify / reload the page we want the second workflow to be wired up. If we don't deactivate the first workflow people won't be able to select the second workflow if due to the UI not allowing it via the get started button. \r\n\r\nMaking the transition seamless in the background with a decent UX is the trick here.\r\n"},"comment":{"url":"https://api.github.com/repos/zooniverse/Panoptes/issues/comments/282100914","html_url":"https://github.com/zooniverse/Panoptes/issues/2196#issuecomment-282100914","issue_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/2196","id":282100914,"user":{"login":"camallen","id":295329,"avatar_url":"https://avatars.githubusercontent.com/u/295329?v=3","gravatar_id":"","url":"https://api.github.com/users/camallen","html_url":"https://github.com/camallen","followers_url":"https://api.github.com/users/camallen/followers","following_url":"https://api.github.com/users/camallen/following{/other_user}","gists_url":"https://api.github.com/users/camallen/gists{/gist_id}","starred_url":"https://api.github.com/users/camallen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/camallen/subscriptions","organizations_url":"https://api.github.com/users/camallen/orgs","repos_url":"https://api.github.com/users/camallen/repos","events_url":"https://api.github.com/users/camallen/events{/privacy}","received_events_url":"https://api.github.com/users/camallen/received_events","type":"User","site_admin":false},"created_at":"2017-02-23T19:51:16Z","updated_at":"2017-02-23T19:51:16Z","body":"I think we can serialize the required information on selection to force the client / UI to reload the workflow state, see https://github.com/zooniverse/Panoptes/issues/2197"}}
{"actor":{"display_login":"camallen"}}