Details of request “Vendor History Reports

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
26150  sent    2019-01-24 09:38:37 -0500  waiting_response  waiting_response  2019-01-24 09:38:37 -0500  outgoing  
26762  response    2019-01-31 15:20:54 -0500        incoming  
26768  response    2019-01-31 15:59:32 -0500        incoming  
26769  response    2019-01-31 16:01:38 -0500        incoming  
26772  followup_sent    2019-01-31 16:07:39 -0500  internal_review  internal_review  2019-01-31 16:07:39 -0500  outgoing  
26773  response    2019-01-31 16:08:41 -0500    error_message  2019-01-31 16:12:02 -0500  incoming  
26776  status_update  described_state  2019-01-31 16:12:02 -0500  error_message  error_message  2019-01-31 16:12:02 -0500   
39482  edit metadata  allow_new_responses_from  2019-05-01 03:45:11 -0400         
39483  edit metadata  allow_new_responses_from  2019-05-01 03:45:11 -0400         
39484  edit metadata  allow_new_responses_from  2019-05-01 03:45:11 -0400         
39485  edit metadata  allow_new_responses_from  2019-05-01 03:45:11 -0400         
39486  edit metadata  allow_new_responses_from  2019-05-01 03:45:11 -0400         
39487  edit metadata  allow_new_responses_from  2019-05-01 03:45:12 -0400         
39488  edit metadata  allow_new_responses_from  2019-05-01 03:45:12 -0400         
101641  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101642  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101643  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101644  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101645  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101646  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101647  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101648  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101649  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101650  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101651  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101652  edit metadata  allow_new_responses_from  2020-02-01 03:45:17 -0500         
101653  edit metadata  allow_new_responses_from  2020-02-01 03:45:18 -0500         
101654  edit metadata  allow_new_responses_from  2020-02-01 03:45:18 -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.