Details of request “Investigation outcomes/Probable reasons for loss/Recovery efforts and outcome - Firearms, Munitions, ballistic armour, and controlled items unaccounted for between January 2007 and September 2017

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. This could be used to generate information about the speed with which authorities respond to requests, the number of requests which require a postal response and much more.

Caveat emptor! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on Right to Know. How, why and by whom requests are categorised is not straightforward, and there will be user error and ambiguity. You will also need to understand FOI law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
29639  sent  2017-09-30 02:49:01 +1000  waiting_response  2017-09-30 02:49:01 +1000  waiting_response  outgoing  
29640  response  2017-09-30 02:49:56 +1000    2017-09-30 02:58:10 +1000  waiting_response  incoming  
29641  status_update  2017-09-30 02:58:10 +1000  waiting_response  2017-09-30 02:58:10 +1000  waiting_response   
29681  response  2017-10-03 11:13:22 +1100    2017-10-13 23:56:00 +1100  waiting_response  incoming  
30058  status_update  2017-10-13 23:56:00 +1100  waiting_response  2017-10-13 23:56:00 +1100  waiting_response   
30354  response  2017-10-30 10:33:39 +1100    2017-10-30 23:39:27 +1100  waiting_response  incoming  
30410  followup_sent  2017-10-30 23:39:10 +1100        outgoing  
30411  status_update  2017-10-30 23:39:27 +1100  waiting_response  2017-10-30 23:39:27 +1100  waiting_response   
30412  response  2017-10-30 23:40:32 +1100    2017-10-30 23:46:27 +1100  waiting_response  incoming  
30413  followup_sent  2017-10-30 23:46:21 +1100        outgoing  
30414  status_update  2017-10-30 23:46:27 +1100  waiting_response  2017-10-30 23:46:27 +1100  waiting_response   
30415  response  2017-10-30 23:47:37 +1100        incoming  
54141  overdue  2017-10-31 00:00:00 +1100         
30449  response  2017-11-01 16:13:52 +1100    2017-11-01 20:14:05 +1100  waiting_response  incoming  
30451  followup_sent  2017-11-01 20:13:56 +1100        outgoing  
30452  status_update  2017-11-01 20:14:05 +1100  waiting_response  2017-11-01 20:14:05 +1100  waiting_response   
30453  response  2017-11-01 20:15:04 +1100    2017-11-05 11:31:50 +1100  waiting_response  incoming  
30485  status_update  2017-11-05 11:31:49 +1100  waiting_response  2017-11-05 11:31:50 +1100  waiting_response   
30516  response  2017-11-07 13:03:50 +1100    2017-11-07 18:37:09 +1100  waiting_response  incoming  
30526  followup_sent  2017-11-07 18:37:02 +1100        outgoing  
30527  status_update  2017-11-07 18:37:09 +1100  waiting_response  2017-11-07 18:37:09 +1100  waiting_response   
30528  response  2017-11-07 18:38:09 +1100    2017-11-07 18:40:52 +1100  waiting_response  incoming  
30529  status_update  2017-11-07 18:40:52 +1100  waiting_response  2017-11-07 18:40:52 +1100  waiting_response   
30762  status_update  2017-11-24 22:31:28 +1100  waiting_response  2017-11-24 22:31:29 +1100  waiting_response   
30824  status_update  2017-11-29 21:44:12 +1100  waiting_response  2017-11-29 21:44:12 +1100  waiting_response   
55974  very_overdue  2017-11-30 00:00:00 +1100         
30945  status_update  2017-12-08 04:42:46 +1100  waiting_response  2017-12-08 04:42:46 +1100  waiting_response   
30947  response  2017-12-08 11:03:07 +1100    2017-12-09 00:33:40 +1100  waiting_response  incoming  
30961  followup_sent  2017-12-09 00:33:16 +1100        outgoing  
30962  status_update  2017-12-09 00:33:40 +1100  waiting_response  2017-12-09 00:33:40 +1100  waiting_response   
31235  followup_sent  2018-01-02 07:40:28 +1100  internal_review  2018-01-02 07:40:28 +1100  internal_review  outgoing  
31236  response  2018-01-02 07:41:46 +1100    2018-01-07 22:55:34 +1100  internal_review  incoming  
31294  status_update  2018-01-07 22:55:34 +1100  internal_review  2018-01-07 22:55:34 +1100  internal_review   
31529  response  2018-01-19 12:42:43 +1100        incoming  
31556  response  2018-01-22 10:30:46 +1100    2018-03-04 13:55:08 +1100  rejected  incoming  
31562  status_update  2018-01-22 15:14:27 +1100  internal_review  2018-01-22 15:14:27 +1100  internal_review   
32086  status_update  2018-03-04 13:55:08 +1100  rejected  2018-03-04 13:55:08 +1100  rejected   
32315  response  2018-03-23 11:32:54 +1100    2018-03-23 15:11:35 +1100  rejected  incoming  
32318  status_update  2018-03-23 15:11:35 +1100  rejected  2018-03-23 15:11:35 +1100  rejected   

Here described means when a user selected a status for the request, and the most recent event had its status updated to that value. calculated is then inferred by Right to Know for intermediate events, which weren't given an explicit description by a user. See the search tips for description of the states.

You can get this page in computer-readable format as part of the main JSON page for the request. See the API documentation.