Details of request “Marko Milić - postupak za utvrđivanje povreda odredaba ZOSI-a

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
85947  set_embargo  2023-08-16 11:17:05 +0200         
85948  sent  2023-08-16 11:17:05 +0200  waiting_response  2023-08-16 11:17:06 +0200  waiting_response  outgoing  
86022  response  2023-08-22 14:04:15 +0200    2023-08-22 14:13:42 +0200  successful  incoming  
86024  status_update  2023-08-22 14:13:42 +0200  successful  2023-08-22 14:13:42 +0200  successful   
91835  embargo_expiring  2023-11-08 00:00:00 +0100         
92330  expire_embargo  2023-11-16 01:00:12 +0100         
105479  edit  2024-05-23 05:45:08 +0200         
105480  edit  2024-05-23 05:45:09 +0200         
105481  edit  2024-05-23 05:45:09 +0200         
105482  edit  2024-05-23 05:45:09 +0200         
105483  edit  2024-05-23 05:45:09 +0200         
105484  edit  2024-05-23 05:45:09 +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.