Details of request “Records of discussions of ADRVP members relating to Essendon players

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
14389  sent  2016-05-08 00:56:34 +1000  waiting_response  2016-05-08 00:56:34 +1000  waiting_response  outgoing  
14478  response  2016-05-12 11:19:30 +1000    2016-05-16 09:42:24 +1000  partially_successful  incoming  
14519  status_update  2016-05-16 09:42:24 +1000  partially_successful  2016-05-16 09:42:24 +1000  partially_successful   
14625  comment  2016-05-19 22:37:15 +1000         
14724  response  2016-05-23 16:08:05 +1000    2016-05-23 18:08:51 +1000  waiting_response  incoming  
14730  followup_sent  2016-05-23 18:08:09 +1000        outgoing  
14731  status_update  2016-05-23 18:08:51 +1000  waiting_response  2016-05-23 18:08:51 +1000  waiting_response   
14732  comment  2016-05-23 18:11:51 +1000         
14743  response  2016-05-24 09:48:43 +1000    2016-05-29 01:43:24 +1000  waiting_response  incoming  
14811  status_update  2016-05-29 01:43:24 +1000  waiting_response  2016-05-29 01:43:24 +1000  waiting_response   
14812  status_update  2016-05-29 01:44:26 +1000  waiting_response  2016-05-29 01:44:26 +1000  waiting_response   
53390  overdue  2016-06-08 00:00:00 +1000         
15183  response  2016-06-21 16:51:55 +1000    2016-06-23 14:10:09 +1000  waiting_response  incoming  
15214  followup_sent  2016-06-23 14:09:04 +1000        outgoing  
15215  status_update  2016-06-23 14:10:09 +1000  waiting_response  2016-06-23 14:10:09 +1000  waiting_response   
15216  response  2016-06-23 15:08:51 +1000    2016-06-23 16:56:21 +1000  waiting_response  incoming  
15217  followup_sent  2016-06-23 16:55:16 +1000        outgoing  
15218  status_update  2016-06-23 16:56:21 +1000  waiting_response  2016-06-23 16:56:21 +1000  waiting_response   
15236  response  2016-06-24 13:28:44 +1000    2016-06-24 14:06:09 +1000  waiting_response  incoming  
15239  followup_sent  2016-06-24 14:05:26 +1000        outgoing  
15240  status_update  2016-06-24 14:06:09 +1000  waiting_response  2016-06-24 14:06:09 +1000  waiting_response   
15243  followup_sent  2016-06-24 18:36:28 +1000        outgoing  
15244  comment  2016-06-25 02:03:15 +1000         
15284  followup_sent  2016-06-28 19:51:40 +1000  internal_review  2016-06-28 19:51:41 +1000  internal_review  outgoing  
15476  response  2016-07-12 16:59:49 +1000    2016-07-12 18:01:21 +1000  internal_review  incoming  
15478  comment  2016-07-12 18:01:02 +1000         
15479  status_update  2016-07-12 18:01:21 +1000  internal_review  2016-07-12 18:01:21 +1000  internal_review   
15500  response  2016-07-14 12:29:46 +1000    2016-07-16 22:24:16 +1000  internal_review  incoming  
15521  followup_sent  2016-07-16 22:23:48 +1000        outgoing  
15522  status_update  2016-07-16 22:24:16 +1000  internal_review  2016-07-16 22:24:16 +1000  internal_review   
15530  response  2016-07-18 12:11:29 +1000    2016-07-18 14:26:35 +1000  internal_review  incoming  
15531  followup_sent  2016-07-18 14:25:59 +1000        outgoing  
15533  status_update  2016-07-18 14:26:34 +1000  internal_review  2016-07-18 14:26:35 +1000  internal_review   
15548  response  2016-07-19 13:56:07 +1000        incoming  
15554  followup_sent  2016-07-19 23:12:23 +1000        outgoing  
15559  response  2016-07-20 11:52:31 +1000    2016-07-21 15:23:20 +1000  rejected  incoming  
15583  status_update  2016-07-21 15:23:20 +1000  rejected  2016-07-21 15:23:20 +1000  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.