{"action":"created","issue":{"url":"https://api.github.com/repos/sul-dlss/argo/issues/698","repository_url":"https://api.github.com/repos/sul-dlss/argo","labels_url":"https://api.github.com/repos/sul-dlss/argo/issues/698/labels{/name}","comments_url":"https://api.github.com/repos/sul-dlss/argo/issues/698/comments","events_url":"https://api.github.com/repos/sul-dlss/argo/issues/698/events","html_url":"https://github.com/sul-dlss/argo/issues/698","id":143297549,"number":698,"title":"Conflicting statuses being reported in index","user":{"login":"blalbrit","id":796990,"avatar_url":"https://avatars.githubusercontent.com/u/796990?v=3","gravatar_id":"","url":"https://api.github.com/users/blalbrit","html_url":"https://github.com/blalbrit","followers_url":"https://api.github.com/users/blalbrit/followers","following_url":"https://api.github.com/users/blalbrit/following{/other_user}","gists_url":"https://api.github.com/users/blalbrit/gists{/gist_id}","starred_url":"https://api.github.com/users/blalbrit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blalbrit/subscriptions","organizations_url":"https://api.github.com/users/blalbrit/orgs","repos_url":"https://api.github.com/users/blalbrit/repos","events_url":"https://api.github.com/users/blalbrit/events{/privacy}","received_events_url":"https://api.github.com/users/blalbrit/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/sul-dlss/argo/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2016-03-24T16:42:36Z","updated_at":"2016-03-24T22:33:55Z","closed_at":null,"body":"On a daily basis, we're seeing misleading statuses on some objects due to the Argo indexes being out of sync (for example: accessioned objects re-appearing as \"in accessioning\", remediated objects appearing as \"error\", etc.).\r\n\r\nSpecific example:\r\n\r\nObject: druid:fj900yy4220\r\nProcessing status facet = \"In accessioning\"\r\nObject status = \"V1 accessioned\"\r\n\r\n![screenshot 2016-03-24 09 39 15](https://cloud.githubusercontent.com/assets/796990/14023978/4fda1494-f1a4-11e5-9334-a1967ed9dd4f.png)\r\n\r\nThis appears to be happening because of conflicting solr information:\r\n\r\nsee below:\r\n"},"comment":{"url":"https://api.github.com/repos/sul-dlss/argo/issues/comments/201058024","html_url":"https://github.com/sul-dlss/argo/issues/698#issuecomment-201058024","issue_url":"https://api.github.com/repos/sul-dlss/argo/issues/698","id":201058024,"user":{"login":"ndushay","id":96775,"avatar_url":"https://avatars.githubusercontent.com/u/96775?v=3","gravatar_id":"","url":"https://api.github.com/users/ndushay","html_url":"https://github.com/ndushay","followers_url":"https://api.github.com/users/ndushay/followers","following_url":"https://api.github.com/users/ndushay/following{/other_user}","gists_url":"https://api.github.com/users/ndushay/gists{/gist_id}","starred_url":"https://api.github.com/users/ndushay/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ndushay/subscriptions","organizations_url":"https://api.github.com/users/ndushay/orgs","repos_url":"https://api.github.com/users/ndushay/repos","events_url":"https://api.github.com/users/ndushay/events{/privacy}","received_events_url":"https://api.github.com/users/ndushay/received_events","type":"User","site_admin":false},"created_at":"2016-03-24T22:33:55Z","updated_at":"2016-03-24T22:33:55Z","body":"@blalbrit   so will there be a new ticket for   \"The question is now how we are getting objects reflecting two statuses - and the answer seems to be that editing an individual datastream in an object causes a status flip in the processing_status_text_ssi and _code_ssi for some reason.\"  ?   Or will this ticket become that ticket?\r\n\r\nEither way, it seems that this will NOT be promoted to must-have ???"}}