Details of request “Oil spill on Lee navigation February 2018

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 created_at described_state last_described_at calculated_state link
2762804  sent  2018-02-26 13:49:17 +0000  waiting_response  2018-02-26 13:49:17 +0000  waiting_response  outgoing  
2762805  response  2018-02-26 13:49:28 +0000    2018-02-26 14:19:16 +0000  waiting_response  incoming  
2762892  status_update  2018-02-26 14:19:16 +0000  waiting_response  2018-02-26 14:19:16 +0000  waiting_response   
2771952  response  2018-03-02 13:39:39 +0000    2018-03-06 16:51:22 +0000  waiting_response  incoming  
2785102  status_update  2018-03-06 16:51:22 +0000  waiting_response  2018-03-06 16:51:22 +0000  waiting_response   
2864987  response  2018-03-27 15:00:14 +0100    2018-03-28 10:47:00 +0100  partially_successful  incoming  
2868390  status_update  2018-03-28 10:47:00 +0100  partially_successful  2018-03-28 10:47:00 +0100  partially_successful   
2868402  followup_sent  2018-03-28 10:51:35 +0100        outgoing  
2868404  response  2018-03-28 10:51:50 +0100        incoming  
2868436  response  2018-03-28 11:09:13 +0100    2018-03-29 08:35:54 +0100  successful  incoming  
2872018  status_update  2018-03-29 08:35:53 +0100  successful  2018-03-29 08:35:53 +0100  successful   
3259429  edit  2018-06-30 03:45:24 +0100         
3259430  edit  2018-06-30 03:45:24 +0100         
3259431  edit  2018-06-30 03:45:24 +0100         
3259432  edit  2018-06-30 03:45:24 +0100         
3259433  edit  2018-06-30 03:45:24 +0100         
3259434  edit  2018-06-30 03:45:24 +0100         
3259435  edit  2018-06-30 03:45:24 +0100         
3259436  edit  2018-06-30 03:45:24 +0100         
3259437  edit  2018-06-30 03:45:24 +0100         
3259438  edit  2018-06-30 03:45:24 +0100         
3259439  edit  2018-06-30 03:45:24 +0100         
4315213  edit  2019-03-30 03:45:59 +0000         
4315214  edit  2019-03-30 03:45:59 +0000         
4315215  edit  2019-03-30 03:45:59 +0000         
4315216  edit  2019-03-30 03:45:59 +0000         
4315217  edit  2019-03-30 03:45:59 +0000         
4315218  edit  2019-03-30 03:45:59 +0000         
4315219  edit  2019-03-30 03:45:59 +0000         
4315220  edit  2019-03-30 03:45:59 +0000         
4315221  edit  2019-03-30 03:46:00 +0000         
4315222  edit  2019-03-30 03:46:00 +0000         
4315223  edit  2019-03-30 03:46:00 +0000         
4315224  edit  2019-03-30 03:46:00 +0000         
4315225  edit  2019-03-30 03:46:00 +0000         
4315226  edit  2019-03-30 03:46:00 +0000         
4315227  edit  2019-03-30 03:46:00 +0000         
4315228  edit  2019-03-30 03:46:00 +0000         
4315229  edit  2019-03-30 03:46:00 +0000         
4315230  edit  2019-03-30 03:46:00 +0000         
4315231  edit  2019-03-30 03:46:00 +0000         
4315232  edit  2019-03-30 03:46:00 +0000         
4315233  edit  2019-03-30 03:46:00 +0000         
4315234  edit  2019-03-30 03:46:00 +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.