Details of request “FOI Administration Info

Event history

This table shows the technical details of the internal events that happened to this request on Demo Alaveteli. 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 Demo Alaveteli. 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
3245460  set_embargo  2018-06-26 16:56:00 +0100         
3245461  sent  2018-06-26 16:56:00 +0100  waiting_response  2018-06-26 16:56:01 +0100  waiting_response  outgoing  
3751212  overdue  2018-07-26 00:00:00 +0100         
3751310  very_overdue  2018-08-24 00:00:00 +0100         
3814405  embargo_expiring  2018-12-18 00:00:00 +0000         
3825215  response  2018-12-21 13:16:12 +0000    2019-06-17 13:54:22 +0100  partially_successful  incoming  
3832445  expire_embargo  2018-12-26 01:16:10 +0000         
4277739  edit  2019-03-22 03:45:17 +0000         
4277740  edit  2019-03-22 03:45:17 +0000         
4277741  edit  2019-03-22 03:45:17 +0000         
4277742  edit  2019-03-22 03:45:17 +0000         
4277743  edit  2019-03-22 03:45:17 +0000         
4277744  edit  2019-03-22 03:45:18 +0000         
4277745  edit  2019-03-22 03:45:18 +0000         
4277746  edit  2019-03-22 03:45:18 +0000         
4277747  edit  2019-03-22 03:45:18 +0000         
7106649  edit  2020-06-18 03:47:50 +0100         
7106650  edit  2020-06-18 03:47:51 +0100         
7106651  edit  2020-06-18 03:47:51 +0100         
7106652  edit  2020-06-18 03:47:51 +0100         
7106653  edit  2020-06-18 03:47:51 +0100         
7106654  edit  2020-06-18 03:47:52 +0100         
7106655  edit  2020-06-18 03:47:52 +0100         
7106656  edit  2020-06-18 03:47:52 +0100         
7106657  edit  2020-06-18 03:47:52 +0100         
7106658  edit  2020-06-18 03:47:53 +0100         
7106659  edit  2020-06-18 03:47:53 +0100         
7106660  edit  2020-06-18 03:47:53 +0100         
7106661  edit  2020-06-18 03:47:54 +0100         
7106662  edit  2020-06-18 03:47:54 +0100         
7106663  edit  2020-06-18 03:47:54 +0100         
7106664  edit  2020-06-18 03:47:54 +0100         
7106665  edit  2020-06-18 03:47:55 +0100         
7106666  edit  2020-06-18 03:47:55 +0100         
7106667  edit  2020-06-18 03:47:55 +0100         
14  destroy_incoming  2021-06-02 12:58:27 +0100         
25  destroy_incoming  2021-06-02 13:03:08 +0100         
225  status_update  2021-11-09 14:22:44 +0000  partially_successful  2021-11-09 14:22:44 +0000  partially_successful   

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 Demo Alaveteli 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.