Details of request “Troškovnik postavljanja živice na Remetinečkoj cesti

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
262  sent  2015-04-13 08:53:24 +0200  waiting_response  2015-04-13 08:53:24 +0200  waiting_response  outgoing  
1338  response  2015-04-28 12:01:24 +0200    2015-04-28 21:07:52 +0200  waiting_response  incoming  
1349  status_update  2015-04-28 21:07:51 +0200  waiting_response  2015-04-28 21:07:52 +0200  waiting_response   
1350  followup_sent  2015-04-28 21:09:10 +0200        outgoing  
1631  followup_sent  2015-05-22 22:44:19 +0200  internal_review  2015-05-22 22:44:19 +0200  internal_review  outgoing  
1640  response  2015-05-25 08:08:34 +0200        incoming  
1643  followup_sent  2015-05-25 09:24:42 +0200  internal_review  2015-05-25 09:24:42 +0200  internal_review  outgoing  
1644  comment  2015-05-25 09:33:32 +0200         
1645  response  2015-05-25 09:40:15 +0200        incoming  
1646  followup_sent  2015-05-25 09:49:10 +0200  internal_review  2015-05-25 09:49:10 +0200  internal_review  outgoing  
2571  comment  2015-07-29 14:06:14 +0200         
2572  edit  2015-07-29 14:08:55 +0200  waiting_response  2015-07-29 14:08:56 +0200  waiting_response   
4100  redeliver_incoming  2015-11-02 13:38:20 +0100         
4122  status_update  2015-11-02 20:35:42 +0100  waiting_response  2015-11-02 20:35:42 +0100  waiting_response   
5786  comment  2016-01-25 19:55:44 +0100         
5787  followup_sent  2016-01-25 19:57:09 +0100        outgoing  
6197  comment  2016-03-27 19:29:17 +0200         
6198  status_update  2016-03-27 19:31:25 +0200  rejected  2016-03-27 19:31:25 +0200  rejected   
6199  edit_comment  2016-03-27 19:33:31 +0200         
6200  comment  2016-03-27 20:11:53 +0200         
6795  response  2016-04-26 10:47:16 +0200    2016-04-26 10:48:28 +0200  successful  incoming  
6796  status_update  2016-04-26 10:48:28 +0200  successful  2016-04-26 10:48:28 +0200  successful   

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.