Details of request 'MV Derbyshire clarifications'

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
32484 sent Tue Feb 10 19:48:21 UTC 2009 waiting_response Tue Feb 10 19:48:21 UTC 2009 waiting_response outgoing
33147 response Thu Feb 12 16:23:25 UTC 2009 waiting_response Mon Feb 16 08:44:05 UTC 2009 waiting_response incoming
39322 response Tue Mar 10 15:55:44 UTC 2009 incoming
40576 followup_sent Mon Mar 16 19:39:53 UTC 2009 waiting_response Mon Mar 16 19:40:13 UTC 2009 waiting_response outgoing
47314 followup_sent Tue Apr 21 09:41:12 UTC 2009 internal_review Tue Apr 21 10:41:12 UTC 2009 internal_review outgoing
48051 response Thu Apr 23 14:53:15 UTC 2009 internal_review Mon Apr 27 08:05:21 UTC 2009 internal_review incoming
54563 response Wed May 20 15:20:21 UTC 2009 internal_review Sun Jun 14 11:49:41 UTC 2009 internal_review incoming
58828 comment Mon Jun 08 14:13:06 UTC 2009 error_message
58836 destroy_incoming Mon Jun 08 14:28:47 UTC 2009
58837 edit_comment Mon Jun 08 14:29:07 UTC 2009 successful
58840 edit Mon Jun 08 14:29:36 UTC 2009 internal_review
58841 edit Mon Jun 08 14:30:40 UTC 2009
59705 destroy_incoming Wed Jun 10 17:02:20 UTC 2009 internal_review
59711 status_update Wed Jun 10 17:13:05 UTC 2009
60463 destroy_incoming Fri Jun 12 22:14:13 UTC 2009
60464 edit Fri Jun 12 22:14:37 UTC 2009
60563 destroy_incoming Sat Jun 13 23:59:07 UTC 2009
60564 destroy_incoming Sat Jun 13 23:59:25 UTC 2009 waiting_response
60574 status_update Sun Jun 14 00:34:26 UTC 2009 partially_successful
60575 edit Sun Jun 14 00:35:00 UTC 2009
60602 destroy_incoming Sun Jun 14 10:47:59 UTC 2009 partially_successful
60604 edit Sun Jun 14 10:49:04 UTC 2009 internal_review
60606 edit Sun Jun 14 10:49:41 UTC 2009
60953 edit Mon Jun 15 16:22:14 UTC 2009
61003 edit Mon Jun 15 21:40:16 UTC 2009
61005 destroy_incoming Mon Jun 15 21:41:07 UTC 2009 internal_review
61392 edit Tue Jun 16 22:00:17 UTC 2009
61723 response Thu Jun 18 10:03:29 UTC 2009 rejected Mon Jun 22 10:09:51 UTC 2009 rejected incoming
66445 edit Tue Jul 07 16:02:56 UTC 2009
80586 followup_sent Fri Aug 21 09:45:57 UTC 2009 outgoing
83549 followup_sent Wed Sep 02 09:55:18 UTC 2009 outgoing
85215 response Tue Sep 08 10:51:42 UTC 2009 waiting_response Sat Sep 12 08:37:09 UTC 2009 waiting_response incoming
88780 response Mon Sep 21 15:07:14 UTC 2009 not_held Tue Sep 22 12:36:00 UTC 2009 not_held 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.