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
33974  sent    2019-03-28 12:14:00 -0400  waiting_response  waiting_response  2019-03-28 12:14:00 -0400  outgoing  
35176  response    2019-04-05 11:47:39 -0400    waiting_response  2019-04-06 19:05:33 -0400  incoming  
35320  followup_sent    2019-04-06 19:05:15 -0400        outgoing  
35321  status_update    2019-04-06 19:05:33 -0400  waiting_response  waiting_response  2019-04-06 19:05:33 -0400   
35658  overdue    2019-04-09 00:00:00 -0400         
37248  response    2019-04-18 16:57:54 -0400    successful  2019-04-18 18:58:38 -0400  incoming  
37255  status_update  described_state  2019-04-18 18:58:38 -0400  successful  successful  2019-04-18 18:58:38 -0400   
56474  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
56475  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
56476  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
56477  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
56478  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
56479  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
56480  edit metadata  allow_new_responses_from  2019-07-19 03:45:09 -0400         
129553  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129554  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129555  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129556  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129557  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129558  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129559  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129560  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129561  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129562  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129563  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129564  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129565  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -0400         
129566  edit metadata  allow_new_responses_from  2020-04-19 03:45:13 -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.