Details of request “Accident Reports

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
50897  sent    2019-06-24 19:23:42 -0400  waiting_response  waiting_response  2019-06-24 19:23:42 -0400  outgoing  
51246  response    2019-06-26 09:48:26 -0400    waiting_clarification  2019-06-26 18:24:20 -0400  incoming  
51290  followup_sent    2019-06-26 18:24:12 -0400        outgoing  
51291  status_update  described_state  2019-06-26 18:24:20 -0400  waiting_clarification  waiting_clarification  2019-06-26 18:24:20 -0400   
51292  followup_sent    2019-06-26 18:25:32 -0400  waiting_response  waiting_response  2019-06-26 18:25:32 -0400  outgoing  
51853  response    2019-06-28 09:28:58 -0400    not_held  2019-06-29 20:28:22 -0400  incoming  
52091  status_update  described_state  2019-06-29 20:28:22 -0400  not_held  not_held  2019-06-29 20:28:22 -0400   
71458  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
71459  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
71460  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
71461  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
71462  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
71463  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
71464  edit metadata  allow_new_responses_from  2019-10-01 03:45:10 -0400         
162020  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162021  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162022  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162023  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162024  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162025  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162026  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162027  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162028  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162029  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162030  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162031  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162032  edit metadata  allow_new_responses_from  2020-07-01 03:45:13 -0400         
162033  edit metadata  allow_new_responses_from  2020-07-01 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.