Details of request “Request for publication of study used to draw up new OS strategy

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
55353  sent  2009-05-25 11:20:56 +0100  waiting_response  2009-05-25 12:20:56 +0100  waiting_response  outgoing  
55354  response  2009-05-25 11:21:10 +0100  waiting_response  2009-05-25 13:02:03 +0100  waiting_response  incoming  
62030  response  2009-06-19 08:42:58 +0100  waiting_response  2009-06-25 15:47:50 +0100  partially_successful  incoming  
62076  followup_sent  2009-06-19 11:07:06 +0100  partially_successful      outgoing  
2097970  overdue  2009-06-23 00:00:00 +0100         
63572  comment  2009-06-25 14:50:20 +0100         
63954  response  2009-06-26 18:22:39 +0100  partially_successful  2009-06-26 22:46:41 +0100  partially_successful  incoming  
70695  response  2009-07-24 11:27:18 +0100  successful  2009-07-28 12:35:46 +0100  successful  incoming  

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.