Details of request 'Scientology: CCHR: FTP complaints'

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
82189 sent Thu Aug 27 15:03:02 UTC 2009 waiting_response Thu Aug 27 16:03:02 UTC 2009 waiting_response outgoing
82321 response Fri Aug 28 08:33:57 UTC 2009 waiting_response Fri Aug 28 13:01:31 UTC 2009 waiting_response incoming
87775 response Thu Sep 17 14:53:37 UTC 2009 rejected Thu Sep 17 18:00:53 UTC 2009 rejected incoming
87818 followup_sent Thu Sep 17 18:07:50 UTC 2009 internal_review Thu Sep 17 18:07:50 UTC 2009 internal_review outgoing
87942 response Fri Sep 18 09:51:35 UTC 2009 internal_review Fri Sep 18 22:47:35 UTC 2009 internal_review incoming
88130 followup_sent Fri Sep 18 22:48:10 UTC 2009 outgoing
95722 response Fri Oct 09 13:46:10 UTC 2009 rejected Tue Oct 20 17:12:32 UTC 2009 rejected incoming
100889 followup_sent Tue Oct 20 17:13:23 UTC 2009 outgoing
100890 comment Tue Oct 20 17:13:48 UTC 2009

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.