Details of request “Registar o vodozaštitnim područjima (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
3913  sent  2015-10-28 01:20:42 +0100  waiting_response  2015-10-28 01:20:43 +0100  waiting_response  outgoing  
4061  followup_sent  2015-10-31 09:21:20 +0100        outgoing  
4067  response  2015-10-31 10:20:16 +0100    2015-11-02 20:14:11 +0100  waiting_response  incoming  
4114  status_update  2015-11-02 20:14:11 +0100  waiting_response  2015-11-02 20:14:11 +0100  waiting_response   
4301  response  2015-11-12 21:27:17 +0100    2015-11-12 21:30:56 +0100  waiting_response  incoming  
4303  status_update  2015-11-12 21:30:56 +0100  waiting_response  2015-11-12 21:30:56 +0100  waiting_response   
4304  followup_sent  2015-11-12 21:40:31 +0100        outgoing  
4309  response  2015-11-12 21:53:43 +0100    2015-11-12 21:55:00 +0100  waiting_response  incoming  
4310  status_update  2015-11-12 21:55:00 +0100  waiting_response  2015-11-12 21:55:00 +0100  waiting_response   
4657  response  2015-11-27 10:23:28 +0100    2015-11-28 10:22:16 +0100  rejected  incoming  
4659  status_update  2015-11-28 10:22:16 +0100  rejected  2015-11-28 10:22:16 +0100  rejected   
4700  comment  2015-12-02 00:24:59 +0100         
15191  comment  2017-01-28 12:11:09 +0100         
15192  followup_sent  2017-01-28 12:18:16 +0100        outgoing  
15317  response  2017-02-08 22:10:41 +0100    2017-02-11 13:48:14 +0100  waiting_response  incoming  
15336  followup_sent  2017-02-11 13:48:08 +0100        outgoing  
15337  status_update  2017-02-11 13:48:14 +0100  waiting_response  2017-02-11 13:48:14 +0100  waiting_response   
15350  response  2017-02-15 19:19:48 +0100    2017-02-16 06:47:51 +0100  waiting_response  incoming  
15351  status_update  2017-02-16 06:47:51 +0100  waiting_response  2017-02-16 06:47:51 +0100  waiting_response   
15422  response  2017-03-01 21:52:09 +0100    2017-03-01 22:24:30 +0100  waiting_response  incoming  
15425  followup_sent  2017-03-01 22:24:21 +0100        outgoing  
15426  status_update  2017-03-01 22:24:30 +0100  waiting_response  2017-03-01 22:24:30 +0100  waiting_response   
15428  response  2017-03-02 11:11:44 +0100    2017-03-11 15:22:45 +0100  partially_successful  incoming  
15487  status_update  2017-03-11 15:22:45 +0100  partially_successful  2017-03-11 15:22:45 +0100  partially_successful   
15592  edit  2017-03-21 22:53:09 +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.