Details of request “Ordinance

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
14970  sent    2018-09-12 00:20:54 -0400  waiting_response  waiting_response  2018-09-12 00:20:54 -0400  outgoing  
15320  overdue    2018-09-22 00:00:00 -0400         
15358  followup_sent    2018-09-23 21:27:06 -0400        outgoing  
15373  response    2018-09-24 10:39:33 -0400    successful  2018-09-24 23:58:30 -0400  incoming  
15399  followup_sent    2018-09-24 23:58:23 -0400        outgoing  
15400  status_update  described_state  2018-09-24 23:58:30 -0400  successful  successful  2018-09-24 23:58:30 -0400   
15405  response    2018-09-25 07:54:38 -0400    successful  2019-03-09 18:47:39 -0500  incoming  
22708  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
22709  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
22710  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
22711  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
22712  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
22713  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
22714  edit metadata  allow_new_responses_from  2018-12-26 03:45:08 -0500         
31956  status_update    2019-03-09 18:47:39 -0500  successful  successful  2019-03-09 18:47:39 -0500   
117190  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117191  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117192  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117193  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117194  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117195  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117196  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117197  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117198  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117199  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117200  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117201  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117202  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117203  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -0400         
117204  edit metadata  allow_new_responses_from  2020-03-10 03:45:18 -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.