{"action":"created","issue":{"url":"https://api.github.com/repos/zooniverse/Panoptes/issues/1098","labels_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/1098/labels{/name}","comments_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/1098/comments","events_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/1098/events","html_url":"https://github.com/zooniverse/Panoptes/issues/1098","id":94679459,"number":1098,"title":"Retiring subjects via API","user":{"login":"marten","id":277,"avatar_url":"https://avatars.githubusercontent.com/u/277?v=3","gravatar_id":"","url":"https://api.github.com/users/marten","html_url":"https://github.com/marten","followers_url":"https://api.github.com/users/marten/followers","following_url":"https://api.github.com/users/marten/following{/other_user}","gists_url":"https://api.github.com/users/marten/gists{/gist_id}","starred_url":"https://api.github.com/users/marten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marten/subscriptions","organizations_url":"https://api.github.com/users/marten/orgs","repos_url":"https://api.github.com/users/marten/repos","events_url":"https://api.github.com/users/marten/events{/privacy}","received_events_url":"https://api.github.com/users/marten/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-07-13T09:31:58Z","updated_at":"2015-07-13T11:07:14Z","closed_at":null,"body":"I'm figuring out how to retire subjects by API call. The logical place for that seems to be using the `SetMemberSubjectController` (as per @edpaget's comments in #519). \r\n\r\nBut to use that API (and for things like `SubjectWorkflowCount#retire!`), the API caller needs the id of the join model (why does a join table even have it's own ids?), which has been hidden since #519.\r\n\r\nHow do we see this fitting in the API?\r\n\r\n/cc @camallen @edpaget "},"comment":{"url":"https://api.github.com/repos/zooniverse/Panoptes/issues/comments/120891687","html_url":"https://github.com/zooniverse/Panoptes/issues/1098#issuecomment-120891687","issue_url":"https://api.github.com/repos/zooniverse/Panoptes/issues/1098","id":120891687,"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":"2015-07-13T11:07:14Z","updated_at":"2015-07-13T11:07:14Z","body":"Yeah that makes sense. So how about a retire action on the `workflows` controller, perhaps `/api/worfklows/:id/retire_subject` with the params `subject_id: X` and it will figure out the SMS id's and do the retirement across subject_sets for that worklow. Is this what you want?"}}