Details of request “Code Enforcement Complaints

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.

Caveat emptor! 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 OPRA law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
15624  sent  2018-10-02 08:55:18 -0400  waiting_response  2018-10-02 08:55:18 -0400  waiting_response  outgoing  
15630  response  2018-10-02 09:47:22 -0400    2018-10-13 13:19:25 -0400  waiting_response  incoming  
16233  overdue  2018-10-13 00:00:00 -0400         
16198  status_update  2018-10-13 13:19:25 -0400  waiting_response  2018-10-13 13:19:25 -0400  waiting_response   
16369  followup_sent  2018-10-15 09:07:03 -0400        outgoing  
16498  response  2018-10-16 11:00:37 -0400    2018-10-20 09:12:56 -0400  waiting_response  incoming  
17018  status_update  2018-10-20 09:12:56 -0400  waiting_response  2018-10-20 09:12:56 -0400  waiting_response   
17019  followup_sent  2018-10-20 09:13:27 -0400        outgoing  
18156  response  2018-10-30 16:16:10 -0400    2018-11-04 12:48:00 -0500  partially_successful  incoming  
18696  status_update  2018-11-04 12:48:00 -0500  partially_successful  2018-11-04 12:48:00 -0500  partially_successful   
27515  edit  2019-02-05 03:45:08 -0500         
27516  edit  2019-02-05 03:45:08 -0500         
27517  edit  2019-02-05 03:45:08 -0500         
27518  edit  2019-02-05 03:45:08 -0500         
27519  edit  2019-02-05 03:45:08 -0500         
27520  edit  2019-02-05 03:45:08 -0500         
27521  edit  2019-02-05 03:45:08 -0500         
27522  edit  2019-02-05 03:45:08 -0500         
27523  edit  2019-02-05 03:45:08 -0500         
27524  edit  2019-02-05 03:45:08 -0500         
78379  edit  2019-11-05 03:45:08 -0500         
78380  edit  2019-11-05 03:45:08 -0500         
78381  edit  2019-11-05 03:45:08 -0500         
78382  edit  2019-11-05 03:45:08 -0500         
78383  edit  2019-11-05 03:45:08 -0500         
78384  edit  2019-11-05 03:45:08 -0500         
78385  edit  2019-11-05 03:45:08 -0500         
78386  edit  2019-11-05 03:45:08 -0500         
78387  edit  2019-11-05 03:45:08 -0500         
78388  edit  2019-11-05 03:45:08 -0500         
78389  edit  2019-11-05 03:45:08 -0500         
78390  edit  2019-11-05 03:45:08 -0500         
78391  edit  2019-11-05 03:45:09 -0500         
78392  edit  2019-11-05 03:45:09 -0500         
78393  edit  2019-11-05 03:45:09 -0500         
78394  edit  2019-11-05 03:45:09 -0500         
78395  edit  2019-11-05 03:45:09 -0500         
78396  edit  2019-11-05 03:45:09 -0500         
78397  edit  2019-11-05 03:45:09 -0500         
78398  edit  2019-11-05 03:45:09 -0500         

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.