Details of request “Interlocal Services Agreement - E. Lacey Rd.

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
24733  sent    2019-01-14 10:21:04 -0500  waiting_response  waiting_response  2019-01-14 10:21:05 -0500  outgoing  
24775  response    2019-01-14 15:40:18 -0500    waiting_response  2019-01-14 16:16:44 -0500  incoming  
24781  status_update    2019-01-14 16:16:44 -0500  waiting_response  waiting_response  2019-01-14 16:16:44 -0500   
25285  followup_sent    2019-01-17 09:07:55 -0500        outgoing  
25293  response    2019-01-17 10:08:11 -0500    successful  2019-01-17 10:09:23 -0500  incoming  
25294  followup_sent    2019-01-17 10:09:19 -0500        outgoing  
25295  status_update  described_state  2019-01-17 10:09:23 -0500  successful  successful  2019-01-17 10:09:23 -0500   
37113  edit metadata  allow_new_responses_from  2019-04-18 03:45:09 -0400         
37114  edit metadata  allow_new_responses_from  2019-04-18 03:45:09 -0400         
37115  edit metadata  allow_new_responses_from  2019-04-18 03:45:09 -0400         
37116  edit metadata  allow_new_responses_from  2019-04-18 03:45:10 -0400         
37117  edit metadata  allow_new_responses_from  2019-04-18 03:45:10 -0400         
37118  edit metadata  allow_new_responses_from  2019-04-18 03:45:10 -0400         
37119  edit metadata  allow_new_responses_from  2019-04-18 03:45:10 -0400         
97435  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97436  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97437  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97438  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97439  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97440  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97441  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97442  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97443  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97444  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97445  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97446  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97447  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -0500         
97448  edit metadata  allow_new_responses_from  2020-01-18 03:45:14 -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.