Details of request “Policies and training on Domestic Violence between 2004 and 2006.

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
2300081  sent  2017-03-16 11:36:02 +0000  waiting_response  2017-03-16 11:36:03 +0000  waiting_response  outgoing  
2307843  response  2017-03-23 07:28:55 +0000    2017-03-23 10:32:44 +0000  waiting_response  incoming  
2308043  followup_sent  2017-03-23 10:32:20 +0000        outgoing  
2308044  status_update  2017-03-23 10:32:44 +0000  waiting_response  2017-03-23 10:32:44 +0000  waiting_response   
2309311  response  2017-03-24 08:50:31 +0000    2017-03-24 09:55:52 +0000  waiting_response  incoming  
2309434  followup_sent  2017-03-24 09:55:42 +0000        outgoing  
2309435  status_update  2017-03-24 09:55:52 +0000  waiting_response  2017-03-24 09:55:52 +0000  waiting_response   
2312800  response  2017-03-28 07:57:10 +0100    2017-03-28 10:40:53 +0100  waiting_response  incoming  
2313081  followup_sent  2017-03-28 10:40:44 +0100        outgoing  
2313084  status_update  2017-03-28 10:40:53 +0100  waiting_response  2017-03-28 10:40:53 +0100  waiting_response   
2410720  overdue  2017-04-19 00:00:00 +0100         
2346942  response  2017-04-27 10:32:45 +0100    2017-04-27 11:06:49 +0100  waiting_response  incoming  
2347050  followup_sent  2017-04-27 11:06:39 +0100        outgoing  
2347053  status_update  2017-04-27 11:06:49 +0100  waiting_response  2017-04-27 11:06:49 +0100  waiting_response   
2347075  followup_sent  2017-04-27 11:10:59 +0100        outgoing  
2347076  status_update  2017-04-27 11:11:16 +0100  waiting_response  2017-04-27 11:11:16 +0100  waiting_response   
2418186  very_overdue  2017-05-18 00:00:00 +0100         
2376036  response  2017-05-24 10:57:59 +0100        incoming  
2376257  response  2017-05-24 13:02:13 +0100    2017-05-24 19:34:14 +0100  waiting_response  incoming  
2376802  followup_sent  2017-05-24 19:34:06 +0100        outgoing  
2376803  status_update  2017-05-24 19:34:13 +0100  waiting_response  2017-05-24 19:34:14 +0100  waiting_response   
2377466  response  2017-05-25 12:52:54 +0100    2017-06-14 20:26:24 +0100  waiting_response  incoming  
2398582  followup_sent  2017-06-14 20:26:10 +0100        outgoing  
2398583  status_update  2017-06-14 20:26:24 +0100  waiting_response  2017-06-14 20:26:24 +0100  waiting_response   
2402450  response  2017-06-19 09:36:58 +0100    2017-06-19 23:04:45 +0100  waiting_response  incoming  
2404168  followup_sent  2017-06-19 23:04:33 +0100        outgoing  
2404169  status_update  2017-06-19 23:04:45 +0100  waiting_response  2017-06-19 23:04:45 +0100  waiting_response   
2425558  followup_sent  2017-06-23 01:05:23 +0100        outgoing  
2426430  response  2017-06-23 12:15:29 +0100    2017-07-06 20:11:06 +0100  not_held  incoming  
2443402  status_update  2017-07-06 19:53:08 +0100  waiting_response  2017-07-06 19:53:08 +0100  waiting_response   
2443405  followup_sent  2017-07-06 20:10:46 +0100        outgoing  
2443406  status_update  2017-07-06 20:11:05 +0100  not_held  2017-07-06 20:11:05 +0100  not_held   

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.