Details of request “Minutes of all meetings of the Australian Maritime Defence Council (1982-present)

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
16572  sent  2016-09-13 18:58:54 +1000  waiting_response  2016-09-13 18:58:54 +1000  waiting_response  outgoing  
16576  response  2016-09-14 08:59:49 +1000    2016-09-21 14:39:22 +1000  waiting_response  incoming  
16887  status_update  2016-09-21 14:39:21 +1000  waiting_response  2016-09-21 14:39:22 +1000  waiting_response   
16896  response  2016-09-21 15:03:43 +1000    2016-09-21 16:59:01 +1000  waiting_response  incoming  
16905  followup_sent  2016-09-21 16:55:32 +1000        outgoing  
16906  comment  2016-09-21 16:58:53 +1000         
16907  status_update  2016-09-21 16:59:01 +1000  waiting_response  2016-09-21 16:59:01 +1000  waiting_response   
16927  response  2016-09-22 12:38:41 +1000    2016-09-22 13:02:43 +1000  waiting_response  incoming  
16928  status_update  2016-09-22 13:02:43 +1000  waiting_response  2016-09-22 13:02:43 +1000  waiting_response   
16929  followup_sent  2016-09-22 13:04:17 +1000        outgoing  
16965  response  2016-09-23 10:23:57 +1000        incoming  
17011  comment  2016-09-26 14:08:14 +1000         
17012  comment  2016-09-26 14:10:21 +1000         
17015  comment  2016-09-26 18:31:14 +1000         
17242  response  2016-10-05 14:37:09 +1100        incoming  
17327  followup_sent  2016-10-07 17:02:41 +1100        outgoing  
17373  response  2016-10-10 15:15:19 +1100    2016-10-10 15:45:49 +1100  waiting_clarification  incoming  
17377  status_update  2016-10-10 15:45:49 +1100  waiting_clarification  2016-10-10 15:45:49 +1100  waiting_clarification   
17379  followup_sent  2016-10-10 15:50:56 +1100  waiting_response  2016-10-10 15:50:56 +1100  waiting_response  outgoing  
17417  response  2016-10-11 15:45:57 +1100        incoming  
17420  followup_sent  2016-10-11 17:15:26 +1100        outgoing  
17436  response  2016-10-12 11:40:27 +1100    2016-10-17 14:25:40 +1100  waiting_clarification  incoming  
17527  followup_sent  2016-10-17 14:25:04 +1100        outgoing  
17528  status_update  2016-10-17 14:25:40 +1100  waiting_clarification  2016-10-17 14:25:40 +1100  waiting_clarification   
17537  response  2016-10-17 16:35:39 +1100        incoming  
17543  response  2016-10-17 17:31:54 +1100        incoming  
17547  followup_sent  2016-10-17 17:45:02 +1100  waiting_response  2016-10-17 17:45:03 +1100  waiting_response  outgoing  
19488  response  2016-11-16 16:48:41 +1100    2016-11-18 16:46:31 +1100  waiting_response  incoming  
53530  overdue  2016-11-17 00:00:00 +1100         
19577  followup_sent  2016-11-18 16:46:21 +1100        outgoing  
19578  status_update  2016-11-18 16:46:31 +1100  waiting_response  2016-11-18 16:46:31 +1100  waiting_response   
19634  response  2016-11-21 16:55:54 +1100    2016-11-21 18:11:36 +1100  waiting_response  incoming  
19637  status_update  2016-11-21 18:11:35 +1100  waiting_response  2016-11-21 18:11:35 +1100  waiting_response   
19638  comment  2016-11-21 18:15:35 +1100         
19977  followup_sent  2016-11-29 16:54:26 +1100        outgoing  
19979  response  2016-11-29 17:01:41 +1100        incoming  
20282  response  2016-12-05 16:37:24 +1100    2016-12-05 17:01:33 +1100  successful  incoming  
20284  status_update  2016-12-05 17:01:33 +1100  successful  2016-12-05 17:01:33 +1100  successful   
20302  response  2016-12-06 10:17:41 +1100    2016-12-14 16:38:28 +1100  successful  incoming  
20718  status_update  2016-12-14 16:38:28 +1100  successful  2016-12-14 16:38:28 +1100  successful   

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.