Details of request “HP na Viroexpo 2018

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.

Be careful! 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 details created_at described_state calculated_state last_described_at link
30895  sent    2018-05-31 22:06:03 +0200  waiting_response  waiting_response  2018-05-31 22:06:03 +0200  outgoing  
30977  response    2018-06-14 11:31:13 +0200    successful  2018-11-22 20:48:18 +0100  incoming  
30984  followup_sent    2018-06-14 15:45:32 +0200        outgoing  
30985  status_update    2018-06-14 15:45:37 +0200  waiting_response  waiting_response  2018-06-14 15:45:38 +0200   
31180  followup_sent    2018-07-15 15:36:35 +0200        outgoing  
31181  comment    2018-07-15 15:51:26 +0200         
31182  status_update  described_state  2018-07-15 15:51:36 +0200  rejected  rejected  2018-07-15 15:51:36 +0200   
31729  comment    2018-11-22 20:48:08 +0100         
31730  status_update  described_state  2018-11-22 20:48:18 +0100  successful  successful  2018-11-22 20:48:18 +0100   
34951  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34952  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34953  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34954  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34955  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34956  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34957  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34958  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
34959  edit metadata  allow_new_responses_from  2019-11-06 04:45:20 +0100         
61718  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61719  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61720  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61721  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61722  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61723  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61724  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61725  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61726  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61727  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61728  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61729  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61730  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61731  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61732  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61733  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61734  edit metadata  allow_new_responses_from  2022-01-26 06:11:07 +0100         
61735  edit metadata  allow_new_responses_from  2022-01-26 06:11:08 +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.