Details of request “Lacey Twp. EMS 2018 Expenses

Event history

This table shows the technical details of the internal events that happened to this request on OPRAmachine. 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 OPRAmachine. 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
25859  sent    2019-01-22 10:19:09 -0500  waiting_response  waiting_response  2019-01-22 10:19:09 -0500  outgoing  
25861  comment    2019-01-22 10:23:42 -0500         
26487  response    2019-01-28 10:19:33 -0500        incoming  
26761  followup_sent    2019-01-31 15:19:26 -0500  internal_review  internal_review  2019-01-31 15:19:26 -0500  outgoing  
26767  response    2019-01-31 15:54:55 -0500        incoming  
26878  response    2019-02-01 14:28:20 -0500    successful  2019-02-05 18:32:42 -0500  incoming  
27610  status_update  described_state  2019-02-05 18:32:42 -0500  successful  successful  2019-02-05 18:32:42 -0500   
40708  edit metadata  allow_new_responses_from  2019-05-06 03:45:08 -0400         
40709  edit metadata  allow_new_responses_from  2019-05-06 03:45:08 -0400         
40710  edit metadata  allow_new_responses_from  2019-05-06 03:45:08 -0400         
40711  edit metadata  allow_new_responses_from  2019-05-06 03:45:08 -0400         
40712  edit metadata  allow_new_responses_from  2019-05-06 03:45:08 -0400         
40713  edit metadata  allow_new_responses_from  2019-05-06 03:45:09 -0400         
40714  edit metadata  allow_new_responses_from  2019-05-06 03:45:09 -0400         
103510  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103511  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103512  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103513  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103514  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103515  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103516  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103517  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103518  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103519  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103520  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103521  edit metadata  allow_new_responses_from  2020-02-06 03:45:11 -0500         
103522  edit metadata  allow_new_responses_from  2020-02-06 03:45:12 -0500         
103523  edit metadata  allow_new_responses_from  2020-02-06 03:45:12 -0500         

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 OPRAmachine 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.