Details of request “Plan rada za 2017. godinu

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
14999  sent  2017-01-03 22:20:27 +0100  waiting_response  2017-01-03 22:20:27 +0100  waiting_response  outgoing  
15041  response  2017-01-08 22:40:54 +0100    2017-02-04 21:18:59 +0100  waiting_response  incoming  
15051  status_update  2017-01-10 08:43:59 +0100  error_message  2017-01-10 08:43:59 +0100  error_message   
15282  resent  2017-02-04 21:18:59 +0100  waiting_response      outgoing  
15320  response  2017-02-09 21:39:21 +0100    2017-03-27 18:13:27 +0200  waiting_response  incoming  
15322  status_update  2017-02-09 22:06:11 +0100  error_message  2017-02-09 22:06:11 +0100  error_message   
16334  resent  2017-03-27 18:13:27 +0200  waiting_response      outgoing  
16607  response  2017-04-01 18:30:51 +0200    2017-04-02 21:30:07 +0200  waiting_response  incoming  
16624  resent  2017-04-02 21:30:07 +0200  waiting_response      outgoing  
16811  response  2017-04-07 21:46:41 +0200    2017-07-08 10:17:18 +0200  waiting_response  incoming  
17184  status_update  2017-05-06 09:19:39 +0200  error_message  2017-05-06 09:19:39 +0200  error_message   
17943  resent  2017-07-08 10:17:18 +0200  waiting_response      outgoing  
17971  response  2017-07-13 10:37:15 +0200    2019-03-03 11:19:56 +0100  waiting_response  incoming  
18801  status_update  2017-08-04 19:05:24 +0200  error_message  2017-08-04 19:05:24 +0200  error_message   
32673  resent  2019-03-03 11:19:56 +0100  waiting_response      outgoing  
65094  edit  2022-03-04 04:45:08 +0100         
65095  edit  2022-03-04 04:45:08 +0100         
65096  edit  2022-03-04 04:45:08 +0100         
65097  edit  2022-03-04 04:45:08 +0100         
65098  edit  2022-03-04 04:45:08 +0100         
65099  edit  2022-03-04 04:45:08 +0100         
65100  edit  2022-03-04 04:45:08 +0100         
65101  edit  2022-03-04 04:45:08 +0100         
65102  edit  2022-03-04 04:45:08 +0100         
65103  edit  2022-03-04 04:45:08 +0100         
65104  edit  2022-03-04 04:45:08 +0100         
65105  edit  2022-03-04 04:45:08 +0100         
65106  edit  2022-03-04 04:45:08 +0100         
65107  edit  2022-03-04 04:45:08 +0100         
65108  edit  2022-03-04 04:45:08 +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.