Details of request “Court 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
831317  sent    2024-01-04 13:20:33 -0500  waiting_response  waiting_response  2024-01-04 13:20:33 -0500  outgoing  
831323  response    2024-01-04 13:30:26 -0500        incoming  
831324  response    2024-01-04 13:30:39 -0500        incoming  
833563  response    2024-01-08 12:18:13 -0500    successful  2024-01-21 13:10:22 -0500  incoming  
984422  overdue    2024-01-17 00:00:00 -0500         
843020  status_update  described_state  2024-01-21 13:10:22 -0500  successful  successful  2024-01-21 13:10:22 -0500   
984435  very_overdue    2024-02-03 00:00:00 -0500         
956755  response    2024-06-11 10:55:41 -0400    waiting_response  2024-07-08 12:23:05 -0400  incoming  
983147  status_update  described_state  2024-07-08 12:23:05 -0400  waiting_response  waiting_response  2024-07-08 12:23:05 -0400   
1134905  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134906  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134907  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134908  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134909  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134910  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134911  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134912  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1134913  edit metadata  allow_new_responses_from  2025-01-09 03:45:08 -0500         
1647149  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647150  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647151  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647152  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647153  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647154  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647155  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647156  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647157  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647158  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647159  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647160  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647161  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647162  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647163  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647164  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647165  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -0400         
1647166  edit metadata  allow_new_responses_from  2026-07-09 03:45:13 -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.