Details of request “istraživanje i eksploatacija ugljikovodika i hidrauličko frakturiranje na poljima Murska depresija, Dravska depresija, Savska depresija, Slavonsko-Srijemska depresija

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
18885  sent  2017-09-02 15:15:23 +0200  waiting_response  2017-09-02 15:15:23 +0200  waiting_response  outgoing  
18886  response  2017-09-02 15:15:38 +0200    2017-09-04 17:12:26 +0200  waiting_response  incoming  
18890  status_update  2017-09-02 15:45:13 +0200  error_message  2017-09-02 15:45:13 +0200  error_message   
18894  comment  2017-09-02 18:14:03 +0200         
18899  comment  2017-09-04 17:12:20 +0200         
18900  resent  2017-09-04 17:12:26 +0200  waiting_response      outgoing  
19018  response  2017-09-12 09:41:53 +0200    2017-10-02 20:37:39 +0200  waiting_response  incoming  
19235  status_update  2017-10-02 20:37:39 +0200  waiting_response  2017-10-02 20:37:39 +0200  waiting_response   
19314  followup_sent  2017-10-06 18:31:54 +0200  internal_review  2017-10-06 18:31:54 +0200  internal_review  outgoing  
19315  followup_sent  2017-10-06 18:35:03 +0200  internal_review  2017-10-06 18:35:03 +0200  internal_review  outgoing  
20529  status_update  2017-10-26 12:06:35 +0200  internal_review  2017-10-26 12:06:35 +0200  internal_review   
20609  followup_sent  2017-10-27 12:40:48 +0200        outgoing  
20616  followup_sent  2017-10-27 12:48:16 +0200        outgoing  
20751  edit  2017-10-30 21:08:08 +0100  waiting_response  2017-10-30 21:08:08 +0100  waiting_response   
20903  status_update  2017-11-03 09:35:21 +0100  waiting_response  2017-11-03 09:35:21 +0100  waiting_response   
21796  response  2017-11-16 10:09:51 +0100        incoming  
21797  response  2017-11-16 10:26:42 +0100    2017-11-28 18:31:03 +0100  partially_successful  incoming  
22004  status_update  2017-11-28 18:31:03 +0100  partially_successful  2017-11-28 18:31:03 +0100  partially_successful   
22007  followup_sent  2017-11-28 19:03:47 +0100        outgoing  
22078  response  2017-12-04 14:38:48 +0100    2017-12-05 18:45:02 +0100  successful  incoming  
22090  status_update  2017-12-05 18:45:02 +0100  successful  2017-12-05 18:45:02 +0100  successful   
22109  comment  2017-12-08 22:26:10 +0100         
51736  edit  2022-01-26 04:57:18 +0100         
51737  edit  2022-01-26 04:57:18 +0100         
51738  edit  2022-01-26 04:57:18 +0100         
51739  edit  2022-01-26 04:57:18 +0100         
51740  edit  2022-01-26 04:57:18 +0100         
51741  edit  2022-01-26 04:57:18 +0100         
51742  edit  2022-01-26 04:57:18 +0100         
51743  edit  2022-01-26 04:57:19 +0100         
51744  edit  2022-01-26 04:57:19 +0100         
51745  edit  2022-01-26 04:57:19 +0100         
51746  edit  2022-01-26 04:57:19 +0100         
51747  edit  2022-01-26 04:57:19 +0100         
51748  edit  2022-01-26 04:57:19 +0100         
51749  edit  2022-01-26 04:57:19 +0100         
51750  edit  2022-01-26 04:57:19 +0100         
51751  edit  2022-01-26 04:57:19 +0100         
51752  edit  2022-01-26 04:57:19 +0100         
51753  edit  2022-01-26 04:57:19 +0100         
51754  edit  2022-01-26 04:57:19 +0100         
51755  edit  2022-01-26 04:57:19 +0100         
51756  edit  2022-01-26 04:57:19 +0100         
51757  edit  2022-01-26 04:57:19 +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.