Details of request “Troškovi kartica i bruto plaće u DAB-u

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
17313  sent  2017-05-18 08:27:27 +0200  waiting_response  2017-05-18 08:27:27 +0200  waiting_response  outgoing  
17314  comment  2017-05-18 08:29:25 +0200         
17541  followup_sent  2017-05-31 09:58:51 +0200        outgoing  
17704  comment  2017-06-15 21:50:52 +0200         
17933  comment  2017-07-06 22:39:10 +0200         
18668  response  2017-07-28 19:13:01 +0200    2017-08-14 09:38:35 +0200  waiting_response  incoming  
18826  status_update  2017-08-14 09:38:35 +0200  waiting_response  2017-08-14 09:38:35 +0200  waiting_response   
18827  followup_sent  2017-08-14 09:53:42 +0200        outgoing  
18883  comment  2017-09-02 13:30:36 +0200         
19212  comment  2017-10-01 20:25:35 +0200         
19472  comment  2017-10-18 20:20:44 +0200         
19476  followup_sent  2017-10-18 21:28:42 +0200        outgoing  
30860  comment  2018-05-12 13:36:52 +0200         
30861  followup_sent  2018-05-12 13:37:49 +0200        outgoing  
30862  response  2018-05-12 13:38:04 +0200    2018-06-08 19:40:46 +0200  rejected  incoming  
30863  followup_resent  2018-05-12 17:06:23 +0200        outgoing  
30864  status_update  2018-05-12 17:06:59 +0200  waiting_response  2018-05-12 17:06:59 +0200  waiting_response   
30890  followup_sent  2018-05-26 12:13:35 +0200        outgoing  
30899  followup_sent  2018-06-01 21:26:23 +0200        outgoing  
30922  comment  2018-06-08 19:40:27 +0200         
30923  status_update  2018-06-08 19:40:45 +0200  rejected  2018-06-08 19:40:46 +0200  rejected   
51661  edit  2022-01-26 04:57:16 +0100         
51662  edit  2022-01-26 04:57:16 +0100         
51663  edit  2022-01-26 04:57:16 +0100         
51664  edit  2022-01-26 04:57:16 +0100         
51665  edit  2022-01-26 04:57:16 +0100         
51666  edit  2022-01-26 04:57:16 +0100         
51667  edit  2022-01-26 04:57:16 +0100         
51668  edit  2022-01-26 04:57:16 +0100         
51669  edit  2022-01-26 04:57:16 +0100         
51670  edit  2022-01-26 04:57:16 +0100         
51671  edit  2022-01-26 04:57:16 +0100         
51672  edit  2022-01-26 04:57:16 +0100         
51673  edit  2022-01-26 04:57:16 +0100         
51674  edit  2022-01-26 04:57:16 +0100         
51675  edit  2022-01-26 04:57:16 +0100         
51676  edit  2022-01-26 04:57:16 +0100         
51677  edit  2022-01-26 04:57:16 +0100         
51678  edit  2022-01-26 04:57:16 +0100         
51679  edit  2022-01-26 04:57:16 +0100         
51680  edit  2022-01-26 04:57:16 +0100         
51681  edit  2022-01-26 04:57:16 +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.