Details of request “Praksa suda - kršenje Kodeksa sudačke etike

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
15397  sent    2017-02-26 20:09:29 +0100  waiting_response  waiting_response  2017-02-26 20:09:30 +0100  outgoing  
15480  response    2017-03-10 09:40:29 +0100    waiting_response  2017-03-10 12:24:56 +0100  incoming  
15481  followup_sent    2017-03-10 12:24:44 +0100        outgoing  
15482  status_update    2017-03-10 12:24:56 +0100  waiting_response  waiting_response  2017-03-10 12:24:56 +0100   
15597  response    2017-03-22 09:14:36 +0100    partially_successful  2017-03-22 13:50:05 +0100  incoming  
15601  followup_sent    2017-03-22 13:49:55 +0100        outgoing  
15602  status_update  described_state  2017-03-22 13:50:05 +0100  partially_successful  partially_successful  2017-03-22 13:50:05 +0100   
15615  response    2017-03-23 12:56:24 +0100    waiting_response  2017-03-31 09:34:24 +0200  incoming  
15624  edit_incoming  prominence, prominence_reason  2017-03-23 17:37:26 +0100        incoming  
16573  status_update  described_state  2017-03-31 09:34:24 +0200  waiting_response  waiting_response  2017-03-31 09:34:24 +0200   
16701  response    2017-04-04 14:43:12 +0200    waiting_response  2017-04-07 17:42:53 +0200  incoming  
16803  status_update    2017-04-07 17:42:53 +0200  waiting_response  waiting_response  2017-04-07 17:42:53 +0200   
16805  followup_sent    2017-04-07 18:00:41 +0200        outgoing  
19417  followup_sent    2017-10-14 14:32:44 +0200        outgoing  
19418  status_update    2017-10-14 14:33:20 +0200  waiting_response  waiting_response  2017-10-14 14:33:20 +0200   
20734  response    2017-10-30 14:31:31 +0100    successful  2018-01-01 14:52:42 +0100  incoming  
28830  status_update  described_state  2018-01-01 14:52:42 +0100  successful  successful  2018-01-01 14:52:42 +0100   
51573  edit metadata  allow_new_responses_from  2022-01-26 04:57:11 +0100         
51574  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51575  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51576  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51577  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51578  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51579  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51580  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51581  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51582  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51583  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51584  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51585  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51586  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51587  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51588  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +0100         
51589  edit metadata  allow_new_responses_from  2022-01-26 04:57:12 +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.