Details of request “Procjena opasnosti

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.

Caveat emptor! 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 created_at described_state last_described_at calculated_state link
39423  sent  2020-10-04 22:31:14 +0200  waiting_response  2020-10-04 22:31:15 +0200  waiting_response  outgoing  
39457  response  2020-10-12 11:04:37 +0200    2020-10-12 11:19:13 +0200  waiting_clarification  incoming  
39460  status_update  2020-10-12 11:19:13 +0200  waiting_clarification  2020-10-12 11:19:13 +0200  waiting_clarification   
39461  followup_sent  2020-10-12 11:19:34 +0200  waiting_response  2020-10-12 11:19:35 +0200  waiting_response  outgoing  
39462  response  2020-10-12 13:41:31 +0200    2020-10-13 10:34:51 +0200  attention_requested  incoming  
39465  report_request  2020-10-13 10:34:51 +0200  attention_requested       
39470  comment  2020-10-13 20:57:12 +0200         
39471  edit  2020-10-13 21:02:05 +0200         
39482  response  2020-10-14 13:46:46 +0200    2020-10-14 16:41:26 +0200  successful  incoming  
39484  status_update  2020-10-14 16:41:26 +0200  successful  2020-10-14 16:41:26 +0200  successful   
48846  edit  2022-01-26 04:45:29 +0100         
48847  edit  2022-01-26 04:45:29 +0100         
48848  edit  2022-01-26 04:45:30 +0100         
48849  edit  2022-01-26 04:45:30 +0100         
48850  edit  2022-01-26 04:45:30 +0100         
48851  edit  2022-01-26 04:45:30 +0100         
48852  edit  2022-01-26 04:45:30 +0100         
48853  edit  2022-01-26 04:45:30 +0100         
48854  edit  2022-01-26 04:45:30 +0100         
48855  edit  2022-01-26 04:45:30 +0100         
86891  edit  2023-10-15 05:45:13 +0200         
86892  edit  2023-10-15 05:45:13 +0200         
86893  edit  2023-10-15 05:45:13 +0200         
86894  edit  2023-10-15 05:45:13 +0200         
86895  edit  2023-10-15 05:45:13 +0200         
86896  edit  2023-10-15 05:45:13 +0200         
86897  edit  2023-10-15 05:45:13 +0200         
86898  edit  2023-10-15 05:45:13 +0200         
86899  edit  2023-10-15 05:45:14 +0200         
86900  edit  2023-10-15 05:45:14 +0200         
86901  edit  2023-10-15 05:45:14 +0200         
86902  edit  2023-10-15 05:45:14 +0200         
86903  edit  2023-10-15 05:45:14 +0200         
86904  edit  2023-10-15 05:45:14 +0200         
86905  edit  2023-10-15 05:45:14 +0200         
86906  edit  2023-10-15 05:45:14 +0200         
86907  edit  2023-10-15 05:45:14 +0200         
86908  edit  2023-10-15 05:45:14 +0200         
86909  edit  2023-10-15 05:45:14 +0200         
86910  edit  2023-10-15 05:45:15 +0200         

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.