Details of request “Oyster facilities at stations and up-to-date OSI List

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
432535 sent 2011-10-20 01:11:51 +0100 waiting_response 2011-10-20 01:11:51 +0100 waiting_response outgoing
432807 response 2011-10-20 14:07:05 +0100 waiting_response 2011-10-24 08:47:37 +0100 waiting_response incoming
2121940 overdue 2011-11-18 00:00:00 +0000
449429 followup_sent 2011-11-22 02:16:57 +0000 outgoing
450571 response 2011-11-23 12:19:47 +0000 waiting_response 2011-12-07 13:02:51 +0000 waiting_response incoming
2214012 very_overdue 2011-12-17 00:00:00 +0000
472000 followup_sent 2012-01-06 13:14:20 +0000 internal_review 2012-01-06 13:14:21 +0000 internal_review outgoing
473194 response 2012-01-09 14:30:30 +0000 internal_review 2012-01-09 15:20:04 +0000 internal_review incoming
499897 response 2012-02-17 17:18:48 +0000 successful 2012-02-17 18:33:47 +0000 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.