Details of request “Kompletne fajlove (DVD) raznih projekata za Gradsko kupalište u Crikvenici

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
38302  sent    2020-02-28 16:52:01 +0100  waiting_response  waiting_response  2020-02-28 16:52:01 +0100  outgoing  
38303  followup_sent    2020-02-28 17:30:44 +0100        outgoing  
38404  followup_sent    2020-03-20 06:28:11 +0100        outgoing  
38410  overdue    2020-03-21 00:00:00 +0100         
38453  very_overdue    2020-04-11 00:00:00 +0200         
38497  status_update  described_state  2020-05-05 13:32:27 +0200  successful  successful  2020-05-05 13:32:27 +0200   
39142  report_request    2020-07-19 18:44:36 +0200  attention_requested       
39162  edit metadata  described_state  2020-07-22 13:38:55 +0200         
39173  status_update  described_state  2020-07-23 08:05:05 +0200  successful  successful  2020-07-23 08:05:05 +0200   
48317  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48318  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48319  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48320  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48321  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48322  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48323  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48324  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
48325  edit metadata  allow_new_responses_from  2022-01-24 04:45:09 +0100         
85600  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85601  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85602  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85603  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85604  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85605  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85606  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85607  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85608  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85609  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85610  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85611  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85612  edit metadata  allow_new_responses_from  2023-07-24 05:45:11 +0200         
85613  edit metadata  allow_new_responses_from  2023-07-24 05:45:12 +0200         
85614  edit metadata  allow_new_responses_from  2023-07-24 05:45:12 +0200         
85615  edit metadata  allow_new_responses_from  2023-07-24 05:45:12 +0200         
85616  edit metadata  allow_new_responses_from  2023-07-24 05:45:12 +0200         
85617  edit metadata  allow_new_responses_from  2023-07-24 05:45:12 +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.