Details of request “Communication

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.

Caveat emptor! 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 OPRA law, and the way authorities use it. Plus you'll need to be an elite statistician. Please contact us with questions.

id event_type created_at described_state last_described_at calculated_state link
32860  sent  2019-03-18 11:06:30 -0400  waiting_response  2019-03-18 11:06:30 -0400  waiting_response  outgoing  
32878  response  2019-03-18 12:37:15 -0400        incoming  
32893  response  2019-03-18 15:34:13 -0400        incoming  
33363  followup_sent  2019-03-21 23:13:59 -0400  internal_review  2019-03-21 23:13:59 -0400  internal_review  outgoing  
33438  response  2019-03-22 08:21:36 -0400        incoming  
33439  followup_sent  2019-03-22 08:38:49 -0400  internal_review  2019-03-22 08:38:49 -0400  internal_review  outgoing  
33442  response  2019-03-22 08:46:42 -0400    2019-03-26 08:34:03 -0400  waiting_response  incoming  
33693  status_update  2019-03-26 08:34:03 -0400  waiting_response  2019-03-26 08:34:03 -0400  waiting_response   
33830  followup_sent  2019-03-27 13:24:17 -0400  internal_review  2019-03-27 13:24:18 -0400  internal_review  outgoing  
33836  response  2019-03-27 14:46:53 -0400        incoming  
33839  followup_sent  2019-03-27 14:57:32 -0400  internal_review  2019-03-27 14:57:32 -0400  internal_review  outgoing  
33842  response  2019-03-27 15:09:19 -0400        incoming  
33843  followup_sent  2019-03-27 15:21:02 -0400  internal_review  2019-03-27 15:21:02 -0400  internal_review  outgoing  
33846  response  2019-03-27 15:33:04 -0400        incoming  
33847  followup_sent  2019-03-27 15:44:37 -0400  internal_review  2019-03-27 15:44:37 -0400  internal_review  outgoing  
33856  response  2019-03-27 15:58:59 -0400        incoming  
33858  followup_sent  2019-03-27 16:13:07 -0400  internal_review  2019-03-27 16:13:08 -0400  internal_review  outgoing  
33861  response  2019-03-27 16:29:50 -0400    2019-04-12 07:18:31 -0400  rejected  incoming  
36153  status_update  2019-04-12 07:18:31 -0400  rejected  2019-04-12 07:18:31 -0400  rejected   
54853  edit  2019-07-13 03:45:07 -0400         
54854  edit  2019-07-13 03:45:07 -0400         
54855  edit  2019-07-13 03:45:07 -0400         
54856  edit  2019-07-13 03:45:07 -0400         
54857  edit  2019-07-13 03:45:08 -0400         
54858  edit  2019-07-13 03:45:08 -0400         
54859  edit  2019-07-13 03:45:08 -0400         
54860  edit  2019-07-13 03:45:08 -0400         
54861  edit  2019-07-13 03:45:08 -0400         
54862  edit  2019-07-13 03:45:08 -0400         
54863  edit  2019-07-13 03:45:08 -0400         
54864  edit  2019-07-13 03:45:08 -0400         
54865  edit  2019-07-13 03:45:08 -0400         
54866  edit  2019-07-13 03:45:08 -0400         
54867  edit  2019-07-13 03:45:08 -0400         
54868  edit  2019-07-13 03:45:08 -0400         
54869  edit  2019-07-13 03:45:08 -0400         
54870  edit  2019-07-13 03:45:08 -0400         
54871  edit  2019-07-13 03:45:08 -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.