Details of request “VE ST3-1/2 Visoka Zelovo Mišljenje Uprave za zaštitu prirode, EZO

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
38562  sent  2020-05-12 11:27:16 +0200  waiting_response  2020-05-12 11:27:16 +0200  waiting_response  outgoing  
38728  response  2020-06-02 09:18:09 +0200    2020-06-02 10:11:21 +0200  partially_successful  incoming  
38729  followup_sent  2020-06-02 10:11:01 +0200        outgoing  
38730  status_update  2020-06-02 10:11:21 +0200  partially_successful  2020-06-02 10:11:21 +0200  partially_successful   
39007  response  2020-06-29 10:01:02 +0200        incoming  
39046  followup_sent  2020-07-07 16:52:09 +0200  internal_review  2020-07-07 16:52:09 +0200  internal_review  outgoing  
39047  status_update  2020-07-07 16:54:02 +0200  partially_successful  2020-07-07 16:54:02 +0200  partially_successful   
39091  response  2020-07-14 11:17:34 +0200    2020-07-14 15:05:24 +0200  successful  incoming  
39104  followup_sent  2020-07-14 15:05:18 +0200        outgoing  
39105  status_update  2020-07-14 15:05:24 +0200  successful  2020-07-14 15:05:24 +0200  successful   
47997  edit  2022-01-15 04:45:08 +0100         
47998  edit  2022-01-15 04:45:08 +0100         
47999  edit  2022-01-15 04:45:08 +0100         
48000  edit  2022-01-15 04:45:08 +0100         
48001  edit  2022-01-15 04:45:08 +0100         
48002  edit  2022-01-15 04:45:08 +0100         
48003  edit  2022-01-15 04:45:08 +0100         
48004  edit  2022-01-15 04:45:08 +0100         
48005  edit  2022-01-15 04:45:08 +0100         
48006  edit  2022-01-15 04:45:09 +0100         
85224  edit  2023-07-15 05:45:09 +0200         
85225  edit  2023-07-15 05:45:09 +0200         
85226  edit  2023-07-15 05:45:10 +0200         
85227  edit  2023-07-15 05:45:10 +0200         
85228  edit  2023-07-15 05:45:10 +0200         
85229  edit  2023-07-15 05:45:10 +0200         
85230  edit  2023-07-15 05:45:10 +0200         
85231  edit  2023-07-15 05:45:10 +0200         
85232  edit  2023-07-15 05:45:10 +0200         
85233  edit  2023-07-15 05:45:10 +0200         
85234  edit  2023-07-15 05:45:10 +0200         
85235  edit  2023-07-15 05:45:10 +0200         
85236  edit  2023-07-15 05:45:10 +0200         
85237  edit  2023-07-15 05:45:10 +0200         
85238  edit  2023-07-15 05:45:10 +0200         
85239  edit  2023-07-15 05:45:10 +0200         
85240  edit  2023-07-15 05:45:10 +0200         
85241  edit  2023-07-15 05:45:10 +0200         
85242  edit  2023-07-15 05:45:10 +0200         
85243  edit  2023-07-15 05:45:10 +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.