Details of request “Planning board approvals

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
36100  sent    2019-04-11 18:08:32 -0400  waiting_response  waiting_response  2019-04-11 18:08:32 -0400  outgoing  
36176  response    2019-04-12 10:27:38 -0400        incoming  
36177  response    2019-04-12 10:27:44 -0400    waiting_response  2019-04-12 11:07:08 -0400  incoming  
36184  status_update    2019-04-12 11:07:08 -0400  waiting_response  waiting_response  2019-04-12 11:07:08 -0400   
36185  response    2019-04-12 11:21:35 -0400    waiting_response  2019-04-16 07:14:13 -0400  incoming  
36790  status_update    2019-04-16 07:14:13 -0400  waiting_response  waiting_response  2019-04-16 07:14:13 -0400   
37722  overdue    2019-04-23 00:00:00 -0400         
41992  very_overdue    2019-05-10 00:00:00 -0400         
55911  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55912  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55913  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55914  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55915  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55916  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55917  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
55918  edit metadata  allow_new_responses_from  2019-07-17 03:45:10 -0400         
129014  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129015  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129016  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129017  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129018  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129019  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129020  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129021  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129022  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129023  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129024  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129025  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129026  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129027  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129028  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -0400         
129029  edit metadata  allow_new_responses_from  2020-04-17 03:45:17 -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.