Details of request “Parking Fine Totals Paid in 2016 and 2017 to date for S2 area, and specifically Shakespeare Street, Mulberry Street and Great William Street

Event history

This table shows the technical details of the internal events that happened to this request on WhatDoTheyKnow. 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 WhatDoTheyKnow. 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 details created_at described_state calculated_state last_described_at link
2494985  sent    2017-08-10 16:27:17 +0100  waiting_response  waiting_response  2017-08-10 16:27:17 +0100  outgoing  
2494987  response    2017-08-10 16:27:43 +0100        incoming  
2495873  response    2017-08-11 08:35:53 +0100    waiting_response  2017-08-11 09:06:24 +0100  incoming  
2495936  followup_sent    2017-08-11 09:06:03 +0100        outgoing  
2495938  status_update    2017-08-11 09:06:24 +0100  waiting_response  waiting_response  2017-08-11 09:06:24 +0100   
2496040  response    2017-08-11 09:38:53 +0100    not_held  2019-01-12 13:17:17 +0000  incoming  
3882112  status_update  described_state  2019-01-12 13:17:17 +0000  not_held  not_held  2019-01-12 13:17:17 +0000   

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 WhatDoTheyKnow 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.