Details of request “Parking Infringement Data 2016/2017

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
27922  sent  2017-08-03 16:14:46 +1000  waiting_response  2017-08-03 16:14:46 +1000  waiting_response  outgoing  
27923  response  2017-08-03 16:16:15 +1000    2017-08-06 15:18:59 +1000  waiting_response  incoming  
27964  status_update  2017-08-06 15:18:58 +1000  waiting_response  2017-08-06 15:18:58 +1000  waiting_response   
28028  response  2017-08-08 14:07:15 +1000    2017-08-09 12:44:54 +1000  waiting_clarification  incoming  
28412  status_update  2017-08-09 12:44:53 +1000  waiting_clarification  2017-08-09 12:44:54 +1000  waiting_clarification   
28413  followup_sent  2017-08-09 12:46:17 +1000  waiting_response  2017-08-09 12:46:17 +1000  waiting_response  outgoing  
28574  status_update  2017-08-14 13:52:29 +1000  waiting_response  2017-08-14 13:52:29 +1000  waiting_response   
28971  followup_sent  2017-08-22 22:54:02 +1000  internal_review  2017-08-22 22:54:02 +1000  internal_review  outgoing  
29019  response  2017-08-24 16:07:25 +1000        incoming  
29179  response  2017-08-31 15:25:00 +1000        incoming  
29180  response  2017-08-31 15:28:15 +1000        incoming  
29211  followup_sent  2017-09-03 10:21:23 +1000        outgoing  
29277  response  2017-09-07 09:43:00 +1000    2017-09-21 12:36:04 +1000  partially_successful  incoming  
29497  status_update  2017-09-21 12:36:03 +1000  partially_successful  2017-09-21 12:36:04 +1000  partially_successful   
29498  followup_sent  2017-09-21 12:41:30 +1000        outgoing  
29603  response  2017-09-28 14:17:37 +1000        incoming  
29604  response  2017-09-28 14:18:15 +1000    2019-04-02 23:34:05 +1100  successful  incoming  
29629  edit_incoming  2017-09-29 14:44:43 +1000        incoming  
39291  status_update  2019-04-02 23:34:04 +1100  successful  2019-04-02 23:34:05 +1100  successful   
39292  comment  2019-04-02 23:36:08 +1100         
39293  comment  2019-04-02 23:36:49 +1100         

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.