Details of request “OPRA Requests

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. 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.

Be careful! To use this data in an honourable way, you will need a good internal knowledge of user behaviour on OPRAmachine. 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 details created_at described_state calculated_state last_described_at link
783  sent    2017-11-20 19:25:35 -0500  waiting_response  waiting_response  2017-11-20 19:25:35 -0500  outgoing  
2790  overdue    2017-12-02 00:00:00 -0500         
3305  followup_sent    2017-12-05 22:42:11 -0500        outgoing  
3705  response    2017-12-06 15:32:14 -0500    waiting_response  2017-12-06 15:41:33 -0500  incoming  
3713  followup_sent    2017-12-06 15:41:22 -0500        outgoing  
3714  status_update    2017-12-06 15:41:33 -0500  waiting_response  waiting_response  2017-12-06 15:41:33 -0500   
5692  very_overdue    2017-12-20 00:00:00 -0500         
9712  followup_sent    2018-05-11 13:41:16 -0400        outgoing  
10055  response    2018-05-17 16:16:52 -0400    waiting_response  2018-05-18 10:55:09 -0400  incoming  
10084  followup_sent    2018-05-18 10:55:00 -0400        outgoing  
10085  status_update    2018-05-18 10:55:09 -0400  waiting_response  waiting_response  2018-05-18 10:55:09 -0400   
10103  response    2018-05-18 14:05:40 -0400    successful  2018-05-18 14:40:52 -0400  incoming  
10105  followup_sent    2018-05-18 14:40:43 -0400        outgoing  
10106  status_update  described_state  2018-05-18 14:40:52 -0400  successful  successful  2018-05-18 14:40:52 -0400   
10107  status_update    2018-05-18 14:43:12 -0400  successful  successful  2018-05-18 14:43:12 -0400   
43958  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43959  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43960  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43961  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43962  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43963  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43964  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43965  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43966  edit metadata  allow_new_responses_from  2019-05-19 03:45:08 -0400         
43967  edit metadata  allow_new_responses_from  2019-05-19 03:45:09 -0400         
43968  edit metadata  allow_new_responses_from  2019-05-19 03:45:09 -0400         
43969  edit metadata  allow_new_responses_from  2019-05-19 03:45:09 -0400         
43970  edit metadata  allow_new_responses_from  2019-05-19 03:45:09 -0400         
43971  edit metadata  allow_new_responses_from  2019-05-19 03:45:09 -0400         
43972  edit metadata  allow_new_responses_from  2019-05-19 03:45:09 -0400         

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 OPRAmachine 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.