Details of request “Victorian Government funding to Rugby Union

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
32432  sent  2018-04-05 12:24:43 +1000  waiting_response  2018-04-05 12:24:43 +1000  waiting_response  outgoing  
32433  status_update  2018-04-05 12:26:14 +1000  user_withdrawn  2018-04-05 12:26:14 +1000  user_withdrawn   
32575  status_update  2018-04-14 12:27:09 +1000  error_message  2018-04-14 12:27:09 +1000  error_message   
32620  resent  2018-04-16 18:29:34 +1000  waiting_response      outgoing  
32621  destroy_incoming  2018-04-16 18:29:46 +1000         
32623  response  2018-04-16 18:33:58 +1000    2018-04-16 18:35:52 +1000  waiting_response  incoming  
32624  status_update  2018-04-16 18:35:52 +1000  waiting_response  2018-04-16 18:35:52 +1000  waiting_response   
32661  response  2018-04-18 16:14:26 +1000    2018-04-24 20:27:44 +1000  waiting_response  incoming  
32764  status_update  2018-04-24 20:27:44 +1000  waiting_response  2018-04-24 20:27:44 +1000  waiting_response   
32833  response  2018-04-30 11:14:43 +1000    2018-06-13 23:42:42 +1000  waiting_response  incoming  
33061  status_update  2018-05-16 20:06:20 +1000  waiting_response  2018-05-16 20:06:20 +1000  waiting_response   
33167  response  2018-05-22 09:43:01 +1000    2018-05-23 03:49:42 +1000  waiting_clarification  incoming  
33180  status_update  2018-05-23 03:49:42 +1000  waiting_clarification  2018-05-23 03:49:42 +1000  waiting_clarification   
33181  followup_sent  2018-05-23 03:54:05 +1000  waiting_response  2018-05-23 03:54:05 +1000  waiting_response  outgoing  
33182  response  2018-05-23 03:54:27 +1000    2018-05-23 03:55:35 +1000  waiting_response  incoming  
33183  status_update  2018-05-23 03:55:35 +1000  waiting_response  2018-05-23 03:55:35 +1000  waiting_response   
33288  redeliver_incoming  2018-05-29 01:30:34 +1000         
33548  response  2018-06-13 12:18:54 +1000    2018-06-13 23:42:42 +1000  waiting_clarification  incoming  
33568  status_update  2018-06-13 23:42:42 +1000  waiting_clarification  2018-06-13 23:42:42 +1000  waiting_clarification   
33580  followup_sent  2018-06-14 19:16:10 +1000  waiting_response  2018-06-14 19:16:10 +1000  waiting_response  outgoing  
33581  response  2018-06-14 19:16:33 +1000    2018-06-14 19:18:32 +1000  waiting_response  incoming  
33582  status_update  2018-06-14 19:18:31 +1000  waiting_response  2018-06-14 19:18:31 +1000  waiting_response   
54325  overdue  2018-07-17 00:00:00 +1000         
34240  followup_sent  2018-07-31 13:43:55 +1000        outgoing  
34241  response  2018-07-31 13:50:40 +1000    2018-07-31 13:51:35 +1000  waiting_response  incoming  
34242  status_update  2018-07-31 13:51:35 +1000  waiting_response  2018-07-31 13:51:35 +1000  waiting_response   
34247  status_update  2018-07-31 22:06:19 +1000  waiting_response  2018-07-31 22:06:19 +1000  waiting_response   
56100  very_overdue  2018-08-14 00:00:00 +1000         
34508  response  2018-08-20 15:47:19 +1000    2018-09-01 04:37:27 +1000  rejected  incoming  
34722  status_update  2018-09-01 04:37:27 +1000  rejected  2018-09-01 04:37:27 +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.