Details of request “Municipal Resolutions

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
12092  sent    2018-07-08 22:07:42 -0400  waiting_response  waiting_response  2018-07-08 22:07:42 -0400  outgoing  
12795  overdue    2018-07-18 00:00:00 -0400         
12899  followup_sent    2018-07-18 23:26:28 -0400  internal_review  internal_review  2018-07-18 23:26:28 -0400  outgoing  
13312  response    2018-07-24 14:43:51 -0400    rejected  2018-08-06 22:29:19 -0400  incoming  
13959  status_update  described_state  2018-08-06 22:29:18 -0400  rejected  rejected  2018-08-06 22:29:19 -0400   
14370  response    2018-08-20 08:32:10 -0400    not_held  2018-08-31 18:00:52 -0400  incoming  
14721  status_update  described_state  2018-08-31 18:00:52 -0400  not_held  not_held  2018-08-31 18:00:52 -0400   
20720  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
20721  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
20722  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
20723  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
20724  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
20725  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
20726  edit metadata  allow_new_responses_from  2018-12-01 03:45:08 -0500         
66153  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66154  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66155  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66156  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66157  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66158  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66159  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66160  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66161  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66162  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66163  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66164  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66165  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -0400         
66166  edit metadata  allow_new_responses_from  2019-09-01 03:45:10 -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.