Details of request “Physical Impact Plan for Jackson Trails

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
71811  sent    2019-10-02 19:25:48 -0400  waiting_response  waiting_response  2019-10-02 19:25:48 -0400  outgoing  
73958  overdue    2019-10-12 00:00:00 -0400         
74410  response    2019-10-15 11:44:07 -0400    waiting_response  2019-10-15 11:44:50 -0400  incoming  
74412  followup_sent    2019-10-15 11:44:20 -0400        outgoing  
74413  status_update    2019-10-15 11:44:50 -0400  waiting_response  waiting_response  2019-10-15 11:44:50 -0400   
74414  response    2019-10-15 11:45:06 -0400    not_held  2019-10-15 12:11:10 -0400  incoming  
74421  followup_sent    2019-10-15 12:10:57 -0400        outgoing  
74422  status_update  described_state  2019-10-15 12:11:10 -0400  not_held  not_held  2019-10-15 12:11:10 -0400   
96557  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96558  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96559  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96560  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96561  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96562  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96563  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
96564  edit metadata  allow_new_responses_from  2020-01-16 03:45:09 -0500         
201338  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201339  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201340  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201341  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201342  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201343  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201344  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201345  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201346  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201347  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201348  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201349  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201350  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201351  edit metadata  allow_new_responses_from  2020-10-16 03:45:23 -0400         
201352  edit metadata  allow_new_responses_from  2020-10-16 03:45:24 -0400         
201353  edit metadata  allow_new_responses_from  2020-10-16 03:45:24 -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.