Details of request “Documents in regard Monitoring and Translocation of Native Dormouse under licence 2015-8387-EPS-MIT

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
1654455  sent    2016-01-26 13:24:11 +0000  waiting_response  waiting_response  2016-01-26 13:24:11 +0000  outgoing  
1654458  response    2016-01-26 13:24:46 +0000        incoming  
1655692  response    2016-01-27 13:44:44 +0000        incoming  
1656520  response    2016-01-28 10:15:42 +0000    waiting_response  2016-02-03 18:57:09 +0000  incoming  
1663723  status_update    2016-02-03 18:57:09 +0000  waiting_response  waiting_response  2016-02-03 18:57:09 +0000   
1671033  followup_sent    2016-02-09 13:08:40 +0000        outgoing  
1671043  response    2016-02-09 13:12:50 +0000        incoming  
1671795  followup_sent    2016-02-09 20:36:03 +0000        outgoing  
1671797  response    2016-02-09 20:36:39 +0000    waiting_response  2016-02-09 21:45:03 +0000  incoming  
1671843  status_update    2016-02-09 21:45:03 +0000  waiting_response  waiting_response  2016-02-09 21:45:03 +0000   
1677936  followup_sent    2016-02-15 18:57:34 +0000  internal_review  internal_review  2016-02-15 18:57:34 +0000  outgoing  
1677937  response    2016-02-15 18:58:10 +0000    internal_review  2016-02-15 18:58:26 +0000  incoming  
1677938  status_update    2016-02-15 18:58:26 +0000  internal_review  internal_review  2016-02-15 18:58:26 +0000   
1686226  response    2016-02-23 12:15:46 +0000    internal_review  2016-03-02 12:33:32 +0000  incoming  
1696592  status_update    2016-03-02 12:33:32 +0000  internal_review  internal_review  2016-03-02 12:33:32 +0000   
1696616  followup_sent    2016-03-02 12:41:01 +0000  internal_review  internal_review  2016-03-02 12:41:01 +0000  outgoing  
1696758  response    2016-03-02 13:58:48 +0000    internal_review  2016-03-04 12:36:19 +0000  incoming  
1696916  followup_sent    2016-03-02 15:25:39 +0000        outgoing  
1699782  status_update    2016-03-04 12:36:19 +0000  internal_review  internal_review  2016-03-04 12:36:19 +0000   
1704999  response    2016-03-08 14:56:16 +0000    internal_review  2016-03-13 09:09:08 +0000  incoming  
1711423  status_update    2016-03-13 09:09:08 +0000  internal_review  internal_review  2016-03-13 09:09:08 +0000   
1733798  followup_sent    2016-03-31 15:34:37 +0100  internal_review  internal_review  2016-03-31 15:34:37 +0100  outgoing  
1733821  response    2016-03-31 15:41:07 +0100        incoming  
1734300  response    2016-04-01 09:24:39 +0100    not_held  2016-04-07 13:16:31 +0100  incoming  
1742094  status_update  described_state  2016-04-07 13:16:31 +0100  not_held  not_held  2016-04-07 13:16:31 +0100   
1762502  followup_sent    2016-04-24 11:14:07 +0100  internal_review  internal_review  2016-04-24 11:14:07 +0100  outgoing  
1770679  response    2016-04-29 14:00:39 +0100    internal_review  2016-06-09 16:05:59 +0100  incoming  
1816935  status_update    2016-06-09 16:05:59 +0100  internal_review  internal_review  2016-06-09 16:05: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.