Details of request “My Marrickville app development costs

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
12459  sent  2016-02-19 09:19:51 +1100  waiting_response  2016-02-19 09:19:51 +1100  waiting_response  outgoing  
12460  response  2016-02-19 09:20:35 +1100    2016-02-19 10:19:47 +1100  waiting_response  incoming  
12461  status_update  2016-02-19 10:19:47 +1100  waiting_response  2016-02-19 10:19:47 +1100  waiting_response   
12497  response  2016-02-22 15:42:50 +1100    2016-02-22 21:35:49 +1100  waiting_clarification  incoming  
12518  status_update  2016-02-22 21:35:49 +1100  waiting_clarification  2016-02-22 21:35:49 +1100  waiting_clarification   
12519  followup_sent  2016-02-22 21:47:34 +1100  waiting_response  2016-02-22 21:47:35 +1100  waiting_response  outgoing  
12530  response  2016-02-23 07:20:54 +1100        incoming  
12531  response  2016-02-23 07:56:40 +1100    2016-02-23 10:33:12 +1100  waiting_clarification  incoming  
12541  status_update  2016-02-23 10:33:11 +1100  waiting_clarification  2016-02-23 10:33:12 +1100  waiting_clarification   
12625  response  2016-02-25 13:22:18 +1100        incoming  
12725  response  2016-02-26 15:43:41 +1100        incoming  
12880  response  2016-03-01 16:10:37 +1100    2016-03-01 18:33:19 +1100  waiting_clarification  incoming  
12883  status_update  2016-03-01 18:33:19 +1100  waiting_clarification  2016-03-01 18:33:19 +1100  waiting_clarification   
12962  status_update  2016-03-04 11:49:51 +1100  waiting_clarification  2016-03-04 11:49:51 +1100  waiting_clarification   
12963  followup_sent  2016-03-04 11:51:51 +1100  waiting_response  2016-03-04 11:51:51 +1100  waiting_response  outgoing  
12965  response  2016-03-04 12:12:51 +1100    2016-03-08 09:40:27 +1100  waiting_response  incoming  
13016  status_update  2016-03-08 09:40:27 +1100  waiting_response  2016-03-08 09:40:27 +1100  waiting_response   
13047  response  2016-03-10 13:09:56 +1100    2016-03-10 17:21:03 +1100  waiting_response  incoming  
13054  status_update  2016-03-10 17:21:02 +1100  waiting_response  2016-03-10 17:21:03 +1100  waiting_response   
13431  response  2016-03-31 15:05:19 +1100    2016-03-31 17:42:11 +1100  waiting_response  incoming  
13444  followup_sent  2016-03-31 17:42:03 +1100        outgoing  
13445  status_update  2016-03-31 17:42:11 +1100  waiting_response  2016-03-31 17:42:11 +1100  waiting_response   
53327  overdue  2016-04-05 00:00:00 +1000         
13846  response  2016-04-18 11:30:20 +1000    2016-04-22 09:09:53 +1000  waiting_response  incoming  
14028  status_update  2016-04-22 09:09:53 +1000  waiting_response  2016-04-22 09:09:53 +1000  waiting_response   
55451  very_overdue  2016-05-04 00:00:00 +1000         
14794  response  2016-05-27 14:09:24 +1000        incoming  
15064  response  2016-06-14 16:19:11 +1000    2016-06-14 18:58:28 +1000  successful  incoming  
15069  status_update  2016-06-14 18:58:28 +1000  successful  2016-06-14 18:58:28 +1000  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.