Details of request “"Cases to be allocated and new processes for RTK detention log requests"

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
4323  sent  2014-04-11 23:59:01 +1000  waiting_response  2014-04-11 23:59:02 +1000  waiting_response  outgoing  
4370  response  2014-04-16 11:59:13 +1000    2014-04-19 22:41:37 +1000  waiting_response  incoming  
4401  status_update  2014-04-19 22:41:37 +1000  waiting_response  2014-04-19 22:41:37 +1000  waiting_response   
4514  response  2014-04-28 19:20:22 +1000        incoming  
4540  response  2014-05-01 10:09:43 +1000    2014-05-01 10:35:41 +1000  waiting_response  incoming  
4541  followup_sent  2014-05-01 10:35:34 +1000        outgoing  
4542  status_update  2014-05-01 10:35:41 +1000  waiting_response  2014-05-01 10:35:41 +1000  waiting_response   
4545  response  2014-05-01 11:53:58 +1000    2014-05-01 13:45:43 +1000  waiting_response  incoming  
4548  followup_sent  2014-05-01 13:45:38 +1000        outgoing  
4549  status_update  2014-05-01 13:45:43 +1000  waiting_response  2014-05-01 13:45:43 +1000  waiting_response   
4551  response  2014-05-01 16:45:07 +1000    2014-05-01 17:07:37 +1000  waiting_response  incoming  
4552  followup_sent  2014-05-01 17:07:31 +1000        outgoing  
4553  status_update  2014-05-01 17:07:37 +1000  waiting_response  2014-05-01 17:07:37 +1000  waiting_response   
4575  response  2014-05-05 12:59:55 +1000    2014-05-09 10:30:22 +1000  waiting_response  incoming  
4620  followup_sent  2014-05-08 12:23:17 +1000        outgoing  
4632  status_update  2014-05-09 10:30:22 +1000  waiting_response  2014-05-09 10:30:22 +1000  waiting_response   
4652  response  2014-05-12 14:56:45 +1000    2014-05-15 11:19:37 +1000  waiting_response  incoming  
52908  overdue  2014-05-13 00:00:00 +1000         
4668  status_update  2014-05-15 11:19:37 +1000  waiting_response  2014-05-15 11:19:37 +1000  waiting_response   
4833  response  2014-05-29 17:03:36 +1000    2014-05-30 12:09:49 +1000  user_withdrawn  incoming  
4863  status_update  2014-05-30 12:09:18 +1000  waiting_response  2014-05-30 12:09:18 +1000  waiting_response   
4865  status_update  2014-05-30 12:09:48 +1000  user_withdrawn  2014-05-30 12:09:49 +1000  user_withdrawn   
4866  followup_sent  2014-05-30 12:10:26 +1000        outgoing  
4879  response  2014-05-30 14:19:09 +1000        incoming  
4881  edit  2014-05-30 14:55:13 +1000         

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.