Details of request “Solicito Acceso a la API de Trenes Argentinos para su utilización

Event history

This table shows the technical details of the internal events that happened to this request on Derecho al Dato. 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 Derecho al Dato. 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
169  sent  2021-07-27 12:00:09 -0300  waiting_response  2021-07-27 12:00:10 -0300  waiting_response  outgoing  
170  response  2021-07-27 18:08:42 -0300    2021-07-31 10:55:15 -0300  waiting_response  incoming  
171  followup_sent  2021-07-27 22:17:18 -0300        outgoing  
172  status_update  2021-07-31 10:55:14 -0300  waiting_response  2021-07-31 10:55:15 -0300  waiting_response   
196  response  2021-08-12 00:22:19 -0300    2021-08-12 09:30:32 -0300  not_held  incoming  
197  followup_sent  2021-08-12 09:30:00 -0300        outgoing  
198  status_update  2021-08-12 09:30:32 -0300  not_held  2021-08-12 09:30:32 -0300  not_held   
204  response  2021-08-17 11:15:08 -0300    2021-08-17 11:17:24 -0300  successful  incoming  
205  status_update  2021-08-17 11:17:24 -0300  successful  2021-08-17 11:17:24 -0300  successful   
336  edit  2022-02-18 03:45:07 -0300         
337  edit  2022-02-18 03:45:07 -0300         
338  edit  2022-02-18 03:45:07 -0300         
339  edit  2022-02-18 03:45:07 -0300         
340  edit  2022-02-18 03:45:07 -0300         
341  edit  2022-02-18 03:45:07 -0300         
342  edit  2022-02-18 03:45:07 -0300         
343  edit  2022-02-18 03:45:07 -0300         
344  edit  2022-02-18 03:45:07 -0300         
857  edit  2023-08-18 03:45:07 -0300         
858  edit  2023-08-18 03:45:07 -0300         
859  edit  2023-08-18 03:45:07 -0300         
860  edit  2023-08-18 03:45:07 -0300         
861  edit  2023-08-18 03:45:07 -0300         
862  edit  2023-08-18 03:45:07 -0300         
863  edit  2023-08-18 03:45:07 -0300         
864  edit  2023-08-18 03:45:07 -0300         
865  edit  2023-08-18 03:45:07 -0300         
866  edit  2023-08-18 03:45:07 -0300         
867  edit  2023-08-18 03:45:07 -0300         
868  edit  2023-08-18 03:45:07 -0300         
869  edit  2023-08-18 03:45:07 -0300         
870  edit  2023-08-18 03:45:07 -0300         
871  edit  2023-08-18 03:45:07 -0300         
872  edit  2023-08-18 03:45:07 -0300         
873  edit  2023-08-18 03:45:08 -0300         
874  edit  2023-08-18 03:45:08 -0300         

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 Derecho al Dato 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.