Details of request “Uppdrag till rapport

Event history

This table shows the technical details of the internal events that happened to this request on Handlingar.se. 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 Handlingar.se. 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
17837  sent    2023-07-10 21:41:30 +0200  waiting_response  waiting_response  2023-07-10 21:41:30 +0200  outgoing  
17838  response    2023-07-10 21:58:43 +0200    waiting_response  2023-07-13 00:18:59 +0200  incoming  
17844  overdue    2023-07-13 00:00:00 +0200         
17843  status_update    2023-07-13 00:18:58 +0200  waiting_response  waiting_response  2023-07-13 00:18:59 +0200   
17846  status_update    2023-07-13 09:38:56 +0200  waiting_response  waiting_response  2023-07-13 09:38:56 +0200   
17847  response    2023-07-13 10:27:22 +0200        incoming  
17851  response    2023-07-14 14:05:17 +0200    gone_postal  2023-07-18 08:52:06 +0200  incoming  
17880  very_overdue    2023-07-18 00:00:00 +0200         
17862  status_update  described_state  2023-07-18 08:52:06 +0200  gone_postal  gone_postal  2023-07-18 08:52:06 +0200   
17869  followup_sent    2023-07-19 12:56:20 +0200        outgoing  
17870  response    2023-07-19 13:12:46 +0200    waiting_response  2023-07-23 09:35:12 +0200  incoming  
17879  status_update  described_state  2023-07-23 09:35:12 +0200  waiting_response  waiting_response  2023-07-23 09:35:12 +0200   
17906  followup_sent    2023-07-31 22:10:15 +0200        outgoing  
17907  response    2023-07-31 22:26:46 +0200    waiting_response  2023-08-03 10:55:54 +0200  incoming  
17929  status_update    2023-08-03 10:55:54 +0200  waiting_response  waiting_response  2023-08-03 10:55:54 +0200   
17933  response    2023-08-04 10:27:00 +0200    gone_postal  2023-08-08 10:19:49 +0200  incoming  
17952  status_update  described_state  2023-08-08 10:19:49 +0200  gone_postal  gone_postal  2023-08-08 10:19:49 +0200   
17969  followup_sent    2023-08-10 21:32:42 +0200  internal_review  internal_review  2023-08-10 21:32:42 +0200  outgoing  
17970  response    2023-08-10 21:48:46 +0200        incoming  
17971  followup_sent    2023-08-11 13:45:26 +0200  internal_review  internal_review  2023-08-11 13:45:26 +0200  outgoing  
17972  response    2023-08-11 13:46:19 +0200    waiting_response  2023-08-15 10:53:48 +0200  incoming  
17979  status_update  described_state  2023-08-15 10:53:48 +0200  waiting_response  waiting_response  2023-08-15 10:53:48 +0200   
18155  response    2023-08-29 16:57:45 +0200    waiting_response  2023-09-02 10:02:28 +0200  incoming  
18163  status_update    2023-09-02 10:02:28 +0200  waiting_response  waiting_response  2023-09-02 10:02:28 +0200   
20176  edit metadata  allow_new_responses_from  2024-03-03 03:45:19 +0100         
20177  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20178  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20179  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20180  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20181  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20182  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20183  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20184  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20185  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20186  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20187  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20188  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20189  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20190  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20191  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20192  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20193  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20194  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20195  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20196  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20197  edit metadata  allow_new_responses_from  2024-03-03 03:45:20 +0100         
20198  edit metadata  allow_new_responses_from  2024-03-03 03:45:21 +0100         
20199  edit metadata  allow_new_responses_from  2024-03-03 03:45:21 +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 Handlingar.se 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.