Details of request “Zahtjev za evidenciju istrage nesreće zrakoplova

Event history

This table shows the technical details of the internal events that happened to this request on Imamo pravo znati. 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 Imamo pravo znati. 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
81059  sent    2023-03-22 01:50:42 +0100  waiting_response  waiting_response  2023-03-22 01:50:42 +0100  outgoing  
82057  overdue    2023-04-07 00:00:00 +0200         
82157  followup_sent    2023-04-17 12:11:15 +0200        outgoing  
82163  response    2023-04-17 15:44:11 +0200    attention_requested  2023-04-17 16:02:43 +0200  incoming  
82164  status_update  described_state  2023-04-17 15:58:20 +0200  correction_asked  correction_asked  2023-04-17 15:58:20 +0200   
82165  report_request  attention_requested  2023-04-17 16:02:43 +0200  attention_requested       
82166  followup_sent    2023-04-17 16:31:33 +0200        outgoing  
82167  comment    2023-04-17 16:39:43 +0200         
82168  edit metadata  described_state  2023-04-17 16:40:14 +0200         
82169  comment    2023-04-17 17:13:56 +0200         
82246  comment    2023-04-19 14:13:50 +0200         
82281  very_overdue    2023-04-22 00:00:00 +0200         
82297  response    2023-04-24 13:40:34 +0200    rejected  2023-04-24 13:59:06 +0200  incoming  
82300  status_update  described_state  2023-04-24 13:59:06 +0200  rejected  rejected  2023-04-24 13:59:06 +0200   
82301  response    2023-04-24 14:10:47 +0200    rejected  2023-04-24 14:20:15 +0200  incoming  
82303  status_update    2023-04-24 14:20:15 +0200  rejected  rejected  2023-04-24 14:20:15 +0200   
101410  edit metadata  allow_new_responses_from  2024-01-25 04:45:09 +0100         
101411  edit metadata  allow_new_responses_from  2024-01-25 04:45:09 +0100         
101412  edit metadata  allow_new_responses_from  2024-01-25 04:45:09 +0100         
101413  edit metadata  allow_new_responses_from  2024-01-25 04:45:09 +0100         
101414  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101415  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101416  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101417  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101418  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101419  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101420  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101421  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101422  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101423  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101424  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         
101425  edit metadata  allow_new_responses_from  2024-01-25 04:45:10 +0100         

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 Imamo pravo znati 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.