Details of request “Zapisnik sa Izborne skuptine HŠS (Hrvatskog šahovskog saveza) odrzane 20.2.2016. godine

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
10691  sent    2016-09-02 12:30:23 +0200  waiting_response  waiting_response  2016-09-02 12:30:23 +0200  outgoing  
10694  followup_sent    2016-09-05 09:53:50 +0200  internal_review  internal_review  2016-09-05 09:53:50 +0200  outgoing  
10749  response    2016-09-08 17:05:54 +0200        incoming  
10751  comment    2016-09-08 22:41:52 +0200         
10752  move_request  public_body_url_name  2016-09-08 22:43:33 +0200         
10757  followup_sent    2016-09-09 07:24:58 +0200  internal_review  internal_review  2016-09-09 07:24:58 +0200  outgoing  
10763  comment    2016-09-09 14:21:18 +0200         
10795  edit metadata  described_state  2016-09-11 22:07:11 +0200  waiting_response  waiting_response  2016-09-11 22:07:11 +0200   
19014  followup_sent    2017-09-12 07:54:02 +0200        outgoing  
19015  comment    2017-09-12 08:36:44 +0200         
19020  response    2017-09-12 09:59:24 +0200        incoming  
19022  response    2017-09-12 10:39:12 +0200        incoming  
19083  response    2017-09-18 10:49:19 +0200    waiting_response  2017-10-10 23:48:25 +0200  incoming  
19085  comment    2017-09-18 13:17:31 +0200         
19385  status_update    2017-10-10 23:48:25 +0200  waiting_response  waiting_response  2017-10-10 23:48:25 +0200   
36326  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36327  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36328  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36329  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36330  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36331  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36332  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36333  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36334  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36335  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36336  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36337  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36338  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36339  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +0100         
36340  edit metadata  allow_new_responses_from  2019-11-06 04:46:20 +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.