Details of request “Registar prostornih jedinica (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
2619  sent  2015-08-03 15:32:45 +0200  waiting_response  2015-08-03 15:32:46 +0200  waiting_response  outgoing  
2620  response  2015-08-03 15:32:53 +0200    2015-08-03 15:39:37 +0200  waiting_response  incoming  
2626  resent  2015-08-03 15:39:37 +0200  waiting_response      outgoing  
2779  destroy_incoming  2015-08-06 13:21:29 +0200         
2797  status_update  2015-08-07 08:50:02 +0200  waiting_response  2015-08-07 08:50:02 +0200  waiting_response   
4118  followup_sent  2015-11-02 20:23:23 +0100        outgoing  
4134  response  2015-11-03 13:55:39 +0100    2015-11-03 14:05:08 +0100  waiting_response  incoming  
4139  resent  2015-11-03 14:05:08 +0100  waiting_response      outgoing  
4144  followup_sent  2015-11-03 14:22:50 +0100        outgoing  
4146  response  2015-11-03 14:40:16 +0100    2015-11-03 14:42:37 +0100  waiting_response  incoming  
4148  status_update  2015-11-03 14:42:37 +0100  waiting_response  2015-11-03 14:42:37 +0100  waiting_response   
4276  response  2015-11-12 09:16:03 +0100    2015-11-12 21:44:09 +0100  waiting_response  incoming  
4306  followup_sent  2015-11-12 21:44:04 +0100        outgoing  
4307  status_update  2015-11-12 21:44:09 +0100  waiting_response  2015-11-12 21:44:09 +0100  waiting_response   
4493  followup_sent  2015-11-19 07:35:48 +0100        outgoing  
4504  response  2015-11-19 12:41:46 +0100    2015-11-19 12:50:15 +0100  waiting_response  incoming  
4505  followup_sent  2015-11-19 12:50:03 +0100        outgoing  
4506  status_update  2015-11-19 12:50:15 +0100  waiting_response  2015-11-19 12:50:15 +0100  waiting_response   
4604  response  2015-11-23 15:56:01 +0100    2015-11-23 16:10:55 +0100  waiting_clarification  incoming  
4605  status_update  2015-11-23 16:10:55 +0100  waiting_clarification  2015-11-23 16:10:55 +0100  waiting_clarification   
4606  followup_sent  2015-11-23 16:23:03 +0100  waiting_response  2015-11-23 16:23:03 +0100  waiting_response  outgoing  
4754  response  2015-12-03 15:27:18 +0100    2015-12-03 15:37:01 +0100  rejected  incoming  
4755  status_update  2015-12-03 15:37:01 +0100  rejected  2015-12-03 15:37:01 +0100  rejected   
4756  comment  2015-12-03 15:38:21 +0100         
4757  followup_sent  2015-12-03 15:42:15 +0100        outgoing  
4856  response  2015-12-07 14:29:16 +0100    2015-12-07 15:12:26 +0100  waiting_response  incoming  
4860  status_update  2015-12-07 15:12:26 +0100  waiting_response  2015-12-07 15:12:26 +0100  waiting_response   
5082  response  2015-12-14 16:09:36 +0100    2015-12-14 18:22:29 +0100  waiting_response  incoming  
5084  followup_sent  2015-12-14 18:22:24 +0100        outgoing  
5085  status_update  2015-12-14 18:22:29 +0100  waiting_response  2015-12-14 18:22:29 +0100  waiting_response   
5494  response  2016-01-04 16:11:05 +0100    2016-01-19 17:33:04 +0100  waiting_response  incoming  
5708  followup_sent  2016-01-19 17:32:59 +0100        outgoing  
5709  status_update  2016-01-19 17:33:04 +0100  waiting_response  2016-01-19 17:33:04 +0100  waiting_response   
5811  response  2016-01-27 16:19:08 +0100    2016-02-04 10:14:53 +0100  rejected  incoming  
5879  status_update  2016-02-04 10:14:53 +0100  rejected  2016-02-04 10:14:53 +0100  rejected   
5881  comment  2016-02-04 10:25:45 +0100         
17306  comment  2017-05-17 20:33:17 +0200         
17307  followup_sent  2017-05-17 20:36:33 +0200        outgoing  
17308  response  2017-05-17 20:36:52 +0200        incoming  
17309  followup_resent  2017-05-17 23:21:27 +0200        outgoing  
17310  response  2017-05-17 23:21:46 +0200    2017-05-17 23:25:23 +0200  waiting_response  incoming  
17311  followup_sent  2017-05-17 23:25:17 +0200        outgoing  
17312  status_update  2017-05-17 23:25:23 +0200  waiting_response  2017-05-17 23:25:23 +0200  waiting_response   
17533  comment  2017-05-31 08:18:03 +0200         
17534  followup_sent  2017-05-31 08:25:37 +0200        outgoing  
17616  followup_sent  2017-06-03 18:43:27 +0200        outgoing  
17628  response  2017-06-05 08:37:45 +0200    2017-06-10 10:42:16 +0200  waiting_response  incoming  
17673  status_update  2017-06-10 10:42:16 +0200  waiting_response  2017-06-10 10:42:16 +0200  waiting_response   
17934  followup_sent  2017-07-06 22:42:50 +0200        outgoing  
17939  response  2017-07-07 15:30:26 +0200    2017-07-11 08:38:21 +0200  waiting_response  incoming  
17950  status_update  2017-07-11 08:38:21 +0200  waiting_response  2017-07-11 08:38:21 +0200  waiting_response   
18629  edit  2017-07-25 18:46:48 +0200         
18630  response  2017-07-25 18:48:11 +0200    2017-08-14 22:08:16 +0200  rejected  incoming  
18828  status_update  2017-08-14 22:08:16 +0200  rejected  2017-08-14 22:08:16 +0200  rejected   
18829  followup_sent  2017-08-14 22:14:32 +0200        outgoing  
18844  response  2017-08-23 19:13:15 +0200    2017-08-23 19:22:34 +0200  rejected  incoming  
18845  comment  2017-08-23 19:16:03 +0200         
18846  status_update  2017-08-23 19:22:34 +0200  rejected  2017-08-23 19:22:34 +0200  rejected   

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.