Details of request “Vendor History Reports "2nd Request"

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
26860  sent    2019-02-01 09:48:12 -0500  waiting_response  waiting_response  2019-02-01 09:48:12 -0500  outgoing  
26862  response    2019-02-01 10:02:37 -0500        incoming  
26863  response    2019-02-01 10:02:52 -0500    waiting_response  2019-02-01 10:03:34 -0500  incoming  
26864  status_update    2019-02-01 10:03:34 -0500  waiting_response  waiting_response  2019-02-01 10:03:34 -0500   
28387  response    2019-02-11 13:22:58 -0500        incoming  
28393  response    2019-02-11 13:49:40 -0500        incoming  
28394  response    2019-02-11 13:51:52 -0500    successful  2019-02-11 16:50:49 -0500  incoming  
28424  status_update  described_state  2019-02-11 16:50:49 -0500  successful  successful  2019-02-11 16:50:49 -0500   
42194  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42195  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42196  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42197  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42198  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42199  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42200  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
42201  edit metadata  allow_new_responses_from  2019-05-12 03:45:10 -0400         
106406  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106407  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106408  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106409  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106410  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106411  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106412  edit metadata  allow_new_responses_from  2020-02-12 03:45:13 -0500         
106413  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106414  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106415  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106416  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106417  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106418  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106419  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106420  edit metadata  allow_new_responses_from  2020-02-12 03:45:14 -0500         
106421  edit metadata  allow_new_responses_from  2020-02-12 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.