Details of request “Ban on Face to Fave Meetings

Event history

This table shows the technical details of the internal events that happened to this request on Right to Know. 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 Right to Know. 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
65518  set_embargo  2021-07-04 19:17:20 +1000         
65519  sent  2021-07-04 19:17:20 +1000  waiting_response  2021-07-04 19:17:21 +1000  waiting_response  outgoing  
65808  response  2021-07-09 19:34:05 +1000    2021-07-10 08:50:53 +1000  waiting_response  incoming  
65860  followup_sent  2021-07-10 08:50:34 +1000        outgoing  
65861  status_update  2021-07-10 08:50:53 +1000  waiting_response  2021-07-10 08:50:53 +1000  waiting_response   
67020  response  2021-07-23 14:14:08 +1000    2021-07-26 15:00:03 +1000  waiting_response  incoming  
67235  status_update  2021-07-26 15:00:03 +1000  waiting_response  2021-07-26 15:00:03 +1000  waiting_response   
67800  overdue  2021-08-04 00:00:00 +1000         
68393  response  2021-08-12 16:54:41 +1000    2022-01-07 11:06:10 +1100  successful  incoming  
69416  status_update  2021-08-27 15:58:51 +1000  waiting_response  2021-08-27 15:58:51 +1000  waiting_response   
69795  very_overdue  2021-09-03 00:00:00 +1000         
78214  status_update  2022-01-07 11:06:10 +1100  successful  2022-01-07 11:06:10 +1100  successful   
100670  embargo_expiring  2022-06-26 00:00:00 +1000         
101443  expire_embargo  2022-07-04 00:00:20 +1000         
101855  edit  2022-07-08 03:45:14 +1000         
101856  edit  2022-07-08 03:45:14 +1000         
101857  edit  2022-07-08 03:45:14 +1000         
101858  edit  2022-07-08 03:45:14 +1000         
101859  edit  2022-07-08 03:45:14 +1000         
101860  edit  2022-07-08 03:45:14 +1000         
101861  edit  2022-07-08 03:45:14 +1000         
101862  edit  2022-07-08 03:45:14 +1000         
101863  edit  2022-07-08 03:45:14 +1000         
101864  edit  2022-07-08 03:45:14 +1000         
101865  edit  2022-07-08 03:45:14 +1000         
101866  edit  2022-07-08 03:45:14 +1000         
101867  edit  2022-07-08 03:45:15 +1000         
101868  edit  2022-07-08 03:45:15 +1000         
221015  edit  2024-01-08 03:45:21 +1100         
221016  edit  2024-01-08 03:45:21 +1100         
221017  edit  2024-01-08 03:45:21 +1100         
221018  edit  2024-01-08 03:45:21 +1100         
221019  edit  2024-01-08 03:45:21 +1100         
221020  edit  2024-01-08 03:45:21 +1100         
221021  edit  2024-01-08 03:45:21 +1100         
221022  edit  2024-01-08 03:45:21 +1100         
221023  edit  2024-01-08 03:45:21 +1100         
221024  edit  2024-01-08 03:45:21 +1100         
221025  edit  2024-01-08 03:45:21 +1100         
221026  edit  2024-01-08 03:45:21 +1100         
221027  edit  2024-01-08 03:45:21 +1100         
221028  edit  2024-01-08 03:45:21 +1100         
221029  edit  2024-01-08 03:45:22 +1100         
221030  edit  2024-01-08 03:45:22 +1100         
221031  edit  2024-01-08 03:45:22 +1100         
221032  edit  2024-01-08 03:45:22 +1100         
221033  edit  2024-01-08 03:45:22 +1100         
221034  edit  2024-01-08 03:45:22 +1100         
221035  edit  2024-01-08 03:45:22 +1100         
221036  edit  2024-01-08 03:45:22 +1100         
221037  edit  2024-01-08 03:45:22 +1100         
221038  edit  2024-01-08 03:45:22 +1100         
221039  edit  2024-01-08 03:45:22 +1100         
221040  edit  2024-01-08 03:45:22 +1100         
221041  edit  2024-01-08 03:45:22 +1100         
221042  edit  2024-01-08 03:45:22 +1100         

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 Right to Know 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.