Details of request “Integrated Doncaster Care Record

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
2706103  sent    2018-01-17 10:06:59 +0000  waiting_response  waiting_response  2018-01-17 10:06:59 +0000  outgoing  
2706228  response    2018-01-17 10:27:24 +0000    waiting_response  2018-01-17 12:04:51 +0000  incoming  
2706562  status_update    2018-01-17 12:04:51 +0000  waiting_response  waiting_response  2018-01-17 12:04:51 +0000   
2707014  response    2018-01-17 15:47:55 +0000    successful  2018-01-17 18:28:15 +0000  incoming  
2707378  status_update  described_state  2018-01-17 18:28:15 +0000  successful  successful  2018-01-17 18:28:15 +0000   
2707379  followup_sent    2018-01-17 18:28:34 +0000        outgoing  
2707381  comment    2018-01-17 18:28:57 +0000         
2943034  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
2943035  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
2943036  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
2943037  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
2943038  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
2943039  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
2943040  edit metadata  allow_new_responses_from  2018-04-18 03:46:09 +0100         
3916088  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916089  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916090  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916091  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916092  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916093  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916094  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916095  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916096  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916097  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916098  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916099  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916100  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +0000         
3916101  edit metadata  allow_new_responses_from  2019-01-18 03:48:49 +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.