Details of request “Adresar matičnih županijskih knjižnica (otvaranje baze podataka)

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
3977  sent  2015-10-29 04:27:24 +0100  waiting_response  2015-10-29 04:27:24 +0100  waiting_response  outgoing  
4065  followup_sent  2015-10-31 09:24:14 +0100        outgoing  
4075  response  2015-11-02 09:09:39 +0100    2015-11-02 09:57:42 +0100  waiting_response  incoming  
4081  status_update  2015-11-02 09:57:41 +0100  waiting_response  2015-11-02 09:57:42 +0100  waiting_response   
4218  response  2015-11-10 10:46:48 +0100    2015-11-10 11:11:33 +0100  waiting_response  incoming  
4223  status_update  2015-11-10 11:11:33 +0100  waiting_response  2015-11-10 11:11:33 +0100  waiting_response   
4224  followup_sent  2015-11-10 11:16:12 +0100        outgoing  
4231  response  2015-11-10 14:45:32 +0100    2015-11-10 15:07:45 +0100  waiting_response  incoming  
4232  status_update  2015-11-10 15:07:45 +0100  waiting_response  2015-11-10 15:07:45 +0100  waiting_response   
4272  response  2015-11-11 15:52:16 +0100    2015-11-12 21:44:47 +0100  waiting_response  incoming  
4308  status_update  2015-11-12 21:44:47 +0100  waiting_response  2015-11-12 21:44:47 +0100  waiting_response   
4625  response  2015-11-24 15:34:53 +0100    2015-11-24 16:03:17 +0100  waiting_response  incoming  
4627  followup_sent  2015-11-24 16:03:11 +0100        outgoing  
4628  status_update  2015-11-24 16:03:17 +0100  waiting_response  2015-11-24 16:03:17 +0100  waiting_response   
4637  response  2015-11-25 14:49:10 +0100    2015-12-02 22:37:15 +0100  partially_successful  incoming  
4739  status_update  2015-12-02 22:37:15 +0100  partially_successful  2015-12-02 22:37:15 +0100  partially_successful   
5091  followup_sent  2015-12-14 19:15:40 +0100        outgoing  
5128  response  2015-12-15 14:55:46 +0100        incoming  
5159  response  2015-12-16 10:09:28 +0100    2015-12-18 17:56:50 +0100  waiting_response  incoming  
5177  followup_sent  2015-12-18 17:56:38 +0100        outgoing  
5178  status_update  2015-12-18 17:56:50 +0100  waiting_response  2015-12-18 17:56:50 +0100  waiting_response   
5194  response  2015-12-21 07:45:58 +0100    2015-12-21 07:59:45 +0100  successful  incoming  
5195  status_update  2015-12-21 07:59:45 +0100  successful  2015-12-21 07:59:45 +0100  successful   
5420  move_request  2015-12-31 11:19:19 +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.