Details of request “Korištenje DOF podataka - DGU

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
15556  sent  2017-03-20 19:23:11 +0100  attention_requested  2017-03-20 19:23:11 +0100  waiting_response  outgoing  
15557  edit  2017-03-20 19:27:57 +0100  waiting_response  2017-03-20 19:27:57 +0100  waiting_response   
15581  edit  2017-03-21 22:32:34 +0100         
16648  response  2017-04-03 15:30:31 +0200    2017-04-05 21:34:18 +0200  waiting_clarification  incoming  
16670  comment  2017-04-03 21:33:49 +0200         
16719  status_update  2017-04-05 21:34:17 +0200  waiting_clarification  2017-04-05 21:34:17 +0200  waiting_clarification   
16722  followup_sent  2017-04-05 21:52:36 +0200  waiting_response  2017-04-05 21:52:36 +0200  waiting_response  outgoing  
16741  followup_sent  2017-04-06 09:01:03 +0200        outgoing  
16748  edit  2017-04-06 09:33:12 +0200         
17152  comment  2017-05-03 21:15:22 +0200         
17193  followup_sent  2017-05-07 21:58:17 +0200        outgoing  
17524  response  2017-05-29 14:05:22 +0200    2018-03-29 15:52:46 +0200  rejected  incoming  
17675  followup_sent  2017-06-12 06:47:48 +0200        outgoing  
17684  status_update  2017-06-13 15:28:31 +0200  waiting_response  2017-06-13 15:28:32 +0200  waiting_response   
17685  status_update  2017-06-13 15:29:05 +0200  waiting_response  2017-06-13 15:29:05 +0200  waiting_response   
17686  status_update  2017-06-13 15:29:28 +0200  internal_review  2017-06-13 15:29:29 +0200  internal_review   
25814  comment  2017-12-12 22:46:37 +0100         
25815  edit  2017-12-12 22:46:47 +0100  waiting_response  2017-12-12 22:46:47 +0100  waiting_response   
30657  comment  2018-03-29 15:52:26 +0200         
30658  status_update  2018-03-29 15:52:45 +0200  rejected  2018-03-29 15:52:45 +0200  rejected   
51590  edit  2022-01-26 04:57:12 +0100         
51591  edit  2022-01-26 04:57:12 +0100         
51592  edit  2022-01-26 04:57:12 +0100         
51593  edit  2022-01-26 04:57:12 +0100         
51594  edit  2022-01-26 04:57:12 +0100         
51595  edit  2022-01-26 04:57:12 +0100         
51596  edit  2022-01-26 04:57:12 +0100         
51597  edit  2022-01-26 04:57:12 +0100         
51598  edit  2022-01-26 04:57:12 +0100         
51599  edit  2022-01-26 04:57:12 +0100         
51600  edit  2022-01-26 04:57:12 +0100         
51601  edit  2022-01-26 04:57:12 +0100         
51602  edit  2022-01-26 04:57:12 +0100         
51603  edit  2022-01-26 04:57:13 +0100         
51604  edit  2022-01-26 04:57:13 +0100         
51605  edit  2022-01-26 04:57:13 +0100         
51606  edit  2022-01-26 04:57:13 +0100         
51607  edit  2022-01-26 04:57:13 +0100         
51608  edit  2022-01-26 04:57:13 +0100         
51609  edit  2022-01-26 04:57:13 +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.