Details of request “Is glyphosate safe? We have the right to know!

Event history

This table shows the technical details of the internal events that happened to this request on AsktheEU.org. 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 AsktheEU.org. 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
19684  sent    2016-03-15 18:06:33 +0100  waiting_response  waiting_response  2016-03-15 18:06:33 +0100  outgoing  
19698  edit_outgoing  body, prominence_reason  2016-03-16 14:33:40 +0100        outgoing  
19699  resent    2016-03-16 14:33:57 +0100  waiting_response      outgoing  
19703  edit_outgoing  body  2016-03-16 15:16:23 +0100        outgoing  
19706  response    2016-03-16 16:20:09 +0100    waiting_response  2016-03-17 15:29:11 +0100  incoming  
19733  followup_sent    2016-03-17 15:29:01 +0100        outgoing  
19734  status_update    2016-03-17 15:29:10 +0100  waiting_response  waiting_response  2016-03-17 15:29:11 +0100   
19825  response    2016-03-21 12:06:04 +0100    waiting_response  2016-03-29 12:13:51 +0200  incoming  
19940  status_update    2016-03-29 12:13:51 +0200  waiting_response  waiting_response  2016-03-29 12:13:51 +0200   
20259  response    2016-04-11 21:50:27 +0200    waiting_clarification  2016-04-15 13:05:07 +0200  incoming  
20352  status_update    2016-04-15 13:04:43 +0200  waiting_response  waiting_response  2016-04-15 13:04:43 +0200   
20353  status_update  described_state  2016-04-15 13:05:07 +0200  waiting_clarification  waiting_clarification  2016-04-15 13:05:07 +0200   
20685  followup_sent    2016-04-25 15:40:54 +0200  waiting_response  waiting_response  2016-04-25 15:40:54 +0200  outgoing  
53191  overdue    2016-05-21 00:00:00 +0200         
21639  followup_sent    2016-05-23 19:00:38 +0200        outgoing  
21729  response    2016-05-25 17:56:27 +0200    waiting_response  2016-05-30 00:16:50 +0200  incoming  
21812  status_update    2016-05-30 00:16:49 +0200  waiting_response  waiting_response  2016-05-30 00:16:50 +0200   
21883  response    2016-05-31 16:57:36 +0200    waiting_response  2016-06-10 15:33:38 +0200  incoming  
22188  followup_sent    2016-06-10 15:32:59 +0200        outgoing  
22189  status_update  described_state  2016-06-10 15:33:15 +0200  waiting_clarification  waiting_clarification  2016-06-10 15:33:15 +0200   
22190  status_update  described_state  2016-06-10 15:33:38 +0200  waiting_response  waiting_response  2016-06-10 15:33:38 +0200   
56385  very_overdue    2016-06-11 00:00:00 +0200         
22471  response    2016-06-20 19:05:37 +0200        incoming  
22930  response    2016-07-08 19:28:11 +0200        incoming  
23016  response    2016-07-12 17:57:21 +0200        incoming  
23098  response    2016-07-15 16:47:07 +0200    waiting_response  2016-07-19 09:25:53 +0200  incoming  
23143  followup_sent    2016-07-19 09:25:48 +0200        outgoing  
23144  status_update    2016-07-19 09:25:53 +0200  waiting_response  waiting_response  2016-07-19 09:25:53 +0200   
23195  followup_sent    2016-07-20 16:28:04 +0200        outgoing  
23206  response    2016-07-21 19:07:09 +0200    waiting_response  2016-07-22 12:58:52 +0200  incoming  
23208  status_update    2016-07-22 12:58:52 +0200  waiting_response  waiting_response  2016-07-22 12:58:52 +0200   
23532  response    2016-08-03 15:23:19 +0200    waiting_response  2016-08-25 16:50:21 +0200  incoming  
53366  overdue    2016-08-11 00:00:00 +0200         
24092  status_update    2016-08-25 16:50:21 +0200  waiting_response  waiting_response  2016-08-25 16:50:21 +0200   
56481  very_overdue    2016-09-02 00:00:00 +0200         
24584  comment    2016-09-20 16:00:49 +0200         
25095  response    2016-10-12 12:19:33 +0200    waiting_response  2016-10-28 13:08:07 +0200  incoming  
25610  followup_sent    2016-10-28 13:07:56 +0200        outgoing  
25611  status_update    2016-10-28 13:08:07 +0200  waiting_response  waiting_response  2016-10-28 13:08:07 +0200   
25614  response    2016-10-28 15:21:41 +0200    waiting_response  2016-11-09 14:06:40 +0100  incoming  
25787  status_update    2016-11-09 14:06:40 +0100  waiting_response  waiting_response  2016-11-09 14:06:40 +0100   
26360  followup_sent    2016-12-15 11:58:43 +0100        outgoing  
26432  response    2016-12-19 17:17:40 +0100        incoming  
26563  response    2016-12-21 18:41:25 +0100        incoming  
26564  comment    2016-12-21 18:43:52 +0100         
26944  followup_sent    2017-01-13 09:11:31 +0100  internal_review  internal_review  2017-01-13 09:11:31 +0100  outgoing  
27600  response    2017-02-01 15:23:34 +0100    internal_review  2017-02-12 19:23:24 +0100  incoming  
27853  status_update    2017-02-12 19:23:24 +0100  internal_review  internal_review  2017-02-12 19:23:24 +0100   
29524  edit metadata    2017-04-19 16:49:42 +0200         
29525  response    2017-04-19 16:50:12 +0200    partially_successful  2017-05-15 11:31:47 +0200  incoming  
30027  status_update  described_state  2017-05-15 11:31:47 +0200  partially_successful  partially_successful  2017-05-15 11:31:47 +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 AsktheEU.org 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.