Details of request “METAREGISTAR - javna nabava

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
15488  sent    2017-03-11 15:30:29 +0100  waiting_response  waiting_response  2017-03-11 15:30:29 +0100  outgoing  
15489  comment    2017-03-11 15:31:03 +0100         
15642  followup_sent    2017-03-25 21:20:29 +0100        outgoing  
16296  response    2017-03-27 15:12:32 +0200    partially_successful  2017-03-27 17:21:00 +0200  incoming  
16302  followup_sent    2017-03-27 17:20:54 +0200        outgoing  
16303  status_update  described_state  2017-03-27 17:21:00 +0200  partially_successful  partially_successful  2017-03-27 17:21:00 +0200   
16467  response    2017-03-29 10:58:00 +0200    successful  2019-04-01 19:27:32 +0200  incoming  
16474  followup_sent    2017-03-29 12:20:15 +0200        outgoing  
16475  status_update    2017-03-29 12:20:23 +0200  partially_successful  partially_successful  2017-03-29 12:20:23 +0200   
17036  comment    2017-04-22 00:23:14 +0200         
17037  comment    2017-04-23 15:38:21 +0200         
32961  comment    2019-04-01 19:22:26 +0200         
32962  edit metadata  allow_new_responses_from  2019-04-01 19:24:35 +0200         
32963  followup_sent    2019-04-01 19:27:20 +0200        outgoing  
32964  status_update  described_state  2019-04-01 19:27:32 +0200  successful  successful  2019-04-01 19:27:32 +0200   
32968  comment    2019-04-01 19:38:35 +0200         
66503  edit metadata  allow_new_responses_from  2022-04-02 05:45:08 +0200         
66504  edit metadata  allow_new_responses_from  2022-04-02 05:45:08 +0200         
66505  edit metadata  allow_new_responses_from  2022-04-02 05:45:08 +0200         
66506  edit metadata  allow_new_responses_from  2022-04-02 05:45:08 +0200         
66507  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66508  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66509  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66510  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66511  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66512  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66513  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66514  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66515  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66516  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66517  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         
66518  edit metadata  allow_new_responses_from  2022-04-02 05:45:09 +0200         

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.