Details of request “Ugovor za sustav za automatku naplatu prijevoza - ticketing

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
5885  sent  2016-02-04 10:32:16 +0100  waiting_response  2016-02-04 10:32:17 +0100  waiting_response  outgoing  
5929  response  2016-02-12 15:34:08 +0100    2016-04-09 12:35:33 +0200  rejected  incoming  
5951  status_update  2016-02-15 10:27:48 +0100  waiting_response  2016-02-15 10:27:48 +0100  waiting_response   
5952  followup_sent  2016-02-15 10:28:36 +0100        outgoing  
6097  comment  2016-03-14 23:15:01 +0100         
6335  comment  2016-04-09 12:35:11 +0200         
6336  status_update  2016-04-09 12:35:33 +0200  rejected  2016-04-09 12:35:33 +0200  rejected   
6338  comment  2016-04-10 13:38:58 +0200         
6803  comment  2016-04-26 18:13:03 +0200         
15573  comment  2017-03-21 22:15:43 +0100         
21315  comment  2017-11-08 21:43:34 +0100         
21316  followup_sent  2017-11-08 21:49:54 +0100        outgoing  
21317  edit  2017-11-08 21:50:28 +0100         
21318  edit  2017-11-08 21:50:45 +0100         
21330  response  2017-11-09 10:45:30 +0100        incoming  
21331  response  2017-11-09 10:47:03 +0100    2017-11-11 11:43:05 +0100  successful  incoming  
21332  followup_sent  2017-11-09 10:50:58 +0100        outgoing  
21395  comment  2017-11-11 11:42:58 +0100         
21396  status_update  2017-11-11 11:43:05 +0100  successful  2017-11-11 11:43:05 +0100  successful   
51444  edit  2022-01-26 04:56:52 +0100         
51445  edit  2022-01-26 04:56:52 +0100         
51446  edit  2022-01-26 04:56:52 +0100         
51447  edit  2022-01-26 04:56:52 +0100         
51448  edit  2022-01-26 04:56:52 +0100         
51449  edit  2022-01-26 04:56:52 +0100         
51450  edit  2022-01-26 04:56:52 +0100         
51451  edit  2022-01-26 04:56:52 +0100         
51452  edit  2022-01-26 04:56:52 +0100         
51453  edit  2022-01-26 04:56:52 +0100         
51454  edit  2022-01-26 04:56:52 +0100         
51455  edit  2022-01-26 04:56:52 +0100         
51456  edit  2022-01-26 04:56:52 +0100         
51457  edit  2022-01-26 04:56:52 +0100         
51458  edit  2022-01-26 04:56:52 +0100         
51459  edit  2022-01-26 04:56:52 +0100         
51460  edit  2022-01-26 04:56:52 +0100         
51461  edit  2022-01-26 04:56:52 +0100         
51462  edit  2022-01-26 04:56:52 +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.