Details of request “Employee Payroll Records

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
3792  sent    2017-12-07 01:18:40 -0500  waiting_response  waiting_response  2017-12-07 01:18:40 -0500  outgoing  
4730  response    2017-12-12 15:58:50 -0500    waiting_response  2017-12-12 17:31:31 -0500  incoming  
4752  followup_sent    2017-12-12 17:31:19 -0500        outgoing  
4753  status_update    2017-12-12 17:31:31 -0500  waiting_response  waiting_response  2017-12-12 17:31:31 -0500   
5374  overdue    2017-12-19 00:00:00 -0500         
6363  very_overdue    2018-01-09 00:00:00 -0500         
9699  followup_sent    2018-05-11 13:13:07 -0400        outgoing  
10277  response    2018-05-23 08:05:29 -0400    user_withdrawn  2018-05-25 13:38:53 -0400  incoming  
10370  followup_sent    2018-05-25 12:58:15 -0400        outgoing  
10371  status_update    2018-05-25 12:58:25 -0400  waiting_response  waiting_response  2018-05-25 12:58:26 -0400   
10374  edit_incoming  prominence, prominence_reason  2018-05-25 13:26:42 -0400        incoming  
10378  followup_sent    2018-05-25 13:38:33 -0400        outgoing  
10379  status_update  described_state  2018-05-25 13:38:53 -0400  user_withdrawn  user_withdrawn  2018-05-25 13:38:53 -0400   
10500  response    2018-05-31 15:18:30 -0400        incoming  
46102  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46103  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46104  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46105  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46106  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46107  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46108  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46109  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46110  edit metadata  allow_new_responses_from  2019-06-01 03:45:11 -0400         
46111  edit metadata  allow_new_responses_from  2019-06-01 03:45:12 -0400         
46112  edit metadata  allow_new_responses_from  2019-06-01 03:45:12 -0400         
46113  edit metadata  allow_new_responses_from  2019-06-01 03:45:12 -0400         
46114  edit metadata  allow_new_responses_from  2019-06-01 03:45:12 -0400         
46115  edit metadata  allow_new_responses_from  2019-06-01 03:45:12 -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.