Details of request “Registar jamstva podrijetla električne energije (otvaranje baze podataka)

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
3879  sent  2015-10-27 23:33:50 +0100  waiting_response  2015-10-27 23:33:50 +0100  waiting_response  outgoing  
4275  response  2015-11-12 08:22:01 +0100        incoming  
4286  response  2015-11-12 15:45:56 +0100    2015-11-14 02:53:40 +0100  not_held  incoming  
4370  status_update  2015-11-14 02:53:40 +0100  not_held  2015-11-14 02:53:40 +0100  not_held   
4418  response  2015-11-16 14:32:46 +0100    2015-11-21 23:21:33 +0100  waiting_clarification  incoming  
4561  status_update  2015-11-21 23:21:33 +0100  waiting_clarification  2015-11-21 23:21:33 +0100  waiting_clarification   
4565  followup_sent  2015-11-21 23:46:11 +0100  waiting_response  2015-11-21 23:46:11 +0100  waiting_response  outgoing  
4566  status_update  2015-11-21 23:46:21 +0100  waiting_clarification  2015-11-21 23:46:21 +0100  waiting_clarification   
4613  response  2015-11-24 10:00:41 +0100        incoming  
4785  followup_sent  2015-12-05 01:27:09 +0100  waiting_response  2015-12-05 01:27:09 +0100  waiting_response  outgoing  
4786  status_update  2015-12-05 01:27:23 +0100  partially_successful  2015-12-05 01:27:23 +0100  partially_successful   
4849  response  2015-12-07 10:23:35 +0100    2015-12-11 01:12:01 +0100  waiting_response  incoming  
5029  status_update  2015-12-11 01:12:00 +0100  waiting_response  2015-12-11 01:12:01 +0100  waiting_response   
5147  followup_sent  2015-12-15 23:01:22 +0100        outgoing  
5167  response  2015-12-17 12:52:17 +0100    2016-01-08 14:49:27 +0100  waiting_response  incoming  
5419  move_request  2015-12-31 11:17:50 +0100         
5477  comment  2016-01-04 11:47:08 +0100         
5570  followup_sent  2016-01-08 08:31:00 +0100        outgoing  
5571  status_update  2016-01-08 08:31:06 +0100  waiting_clarification  2016-01-08 08:31:06 +0100  waiting_clarification   
5579  edit  2016-01-08 14:49:27 +0100  waiting_response  2016-01-08 14:49:27 +0100  waiting_response   
5602  response  2016-01-14 12:01:58 +0100        incoming  
5604  response  2016-01-14 12:57:26 +0100        incoming  
5605  response  2016-01-14 13:03:33 +0100    2016-01-18 13:59:26 +0100  successful  incoming  
5665  followup_sent  2016-01-18 13:58:03 +0100        outgoing  
5666  status_update  2016-01-18 13:59:26 +0100  successful  2016-01-18 13:59:26 +0100  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.