Details of request “TVL 178 Caution

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
2766640  sent    2018-02-28 20:32:55 +0000  waiting_response  waiting_response  2018-02-28 20:32:55 +0000  outgoing  
2768030  comment    2018-03-01 16:53:41 +0000         
2768146  comment    2018-03-01 20:25:31 +0000         
2768173  comment    2018-03-01 21:10:55 +0000         
2780252  response    2018-03-05 15:48:10 +0000    waiting_response  2018-03-05 16:43:44 +0000  incoming  
2780427  status_update    2018-03-05 16:43:44 +0000  waiting_response  waiting_response  2018-03-05 16:43:44 +0000   
2868486  response    2018-03-28 11:39:34 +0100    not_held  2021-07-27 21:11:59 +0100  incoming  
3255802  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
3255803  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
3255804  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
3255805  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
3255806  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
3255807  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
3255808  edit metadata  allow_new_responses_from  2018-06-29 03:45:28 +0100         
4311052  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311053  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311054  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311055  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311056  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311057  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311058  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311059  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311060  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311061  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311062  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311063  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311064  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
4311065  edit metadata  allow_new_responses_from  2019-03-29 03:46:35 +0000         
9713769  status_update  described_state  2021-07-27 21:11:59 +0100  not_held  not_held  2021-07-27 21:11:59 +0100   

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.