Details of request “Otvaranje baze podataka - Registar kemikalija

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
2381  sent  2015-07-21 10:32:34 +0200  waiting_response  2015-07-21 10:32:34 +0200  waiting_response  outgoing  
2417  response  2015-07-22 20:43:16 +0200    2015-07-23 10:33:27 +0200  waiting_response  incoming  
2423  followup_sent  2015-07-23 10:33:20 +0200        outgoing  
2424  status_update  2015-07-23 10:33:27 +0200  waiting_response  2015-07-23 10:33:27 +0200  waiting_response   
3003  response  2015-08-24 09:09:29 +0200    2015-08-24 09:55:27 +0200  waiting_response  incoming  
3004  followup_sent  2015-08-24 09:55:21 +0200        outgoing  
3005  status_update  2015-08-24 09:55:27 +0200  waiting_response  2015-08-24 09:55:27 +0200  waiting_response   
3126  response  2015-09-02 10:57:50 +0200        incoming  
3127  response  2015-09-02 10:59:57 +0200    2015-09-06 09:45:04 +0200  waiting_response  incoming  
3199  status_update  2015-09-06 09:45:04 +0200  waiting_response  2015-09-06 09:45:04 +0200  waiting_response   
3586  response  2015-10-12 14:13:50 +0200    2015-10-13 07:50:25 +0200  waiting_response  incoming  
3598  followup_sent  2015-10-13 07:50:15 +0200        outgoing  
3599  status_update  2015-10-13 07:50:24 +0200  waiting_response  2015-10-13 07:50:25 +0200  waiting_response   
3608  response  2015-10-13 11:35:58 +0200    2015-10-13 11:52:12 +0200  waiting_response  incoming  
3610  followup_sent  2015-10-13 11:52:06 +0200        outgoing  
3611  status_update  2015-10-13 11:52:11 +0200  waiting_response  2015-10-13 11:52:12 +0200  waiting_response   
3632  followup_sent  2015-10-15 09:41:11 +0200        outgoing  
3637  response  2015-10-15 12:22:10 +0200    2015-10-16 15:40:46 +0200  partially_successful  incoming  
3654  followup_sent  2015-10-16 14:52:33 +0200        outgoing  
3655  followup_sent  2015-10-16 14:57:06 +0200        outgoing  
3656  status_update  2015-10-16 15:40:46 +0200  partially_successful  2015-10-16 15:40:46 +0200  partially_successful   
3818  response  2015-10-26 12:05:20 +0100    2015-10-26 12:10:07 +0100  successful  incoming  
3819  status_update  2015-10-26 12:10:07 +0100  successful  2015-10-26 12:10:07 +0100  successful   
15593  edit  2017-03-21 22:53:24 +0100         
15594  edit  2017-03-21 22:53:25 +0100         
39308  comment  2020-09-10 14:05:21 +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.