Comments (10)
Another comment from a user who was alerted on the same incoming message twice - because it had changed state.
from alaveteli.
Just to note WhatDoTheyKnow gets one support email every few months about this.
from alaveteli.
I agree with the above comments which suggest an alert message to a user tracking a request or search term should be prompted by an incoming message, and not a change in classification.
Also the email which goes out should make clear why the alert is being issued; the below example email to the WhatDoTheyKnow support address quotes an alert message which doesn't say that it was a classification on the 19th of March which prompted it, in fact it suggests there's a new update on teh thread, which there isn't from the point of view of the reader:
Hi there, this was 2 months ago, is this the speed of update notifications?
Kind regards----Original Message----
From: [removed]
Date: 19/03/2018 2:25
To: [removed]
Subj: Your WhatDoTheyKnow email alertNew updates for the request 'Delegation of Police Crime Commissioner Duties and published reports / recommendations as under the Police reform and Responsibility Act 2011'
Norfolk Police and Crime Commissioner sent a response to Wayne Leigthon (19 January 2018)
"Dear Mr Leighton Please find attached a response from Mark Stokes. Kind regards ===================================================================..."
https://www.whatdotheyknow.com/request/delegation_of_police_crime_commi?nocache=incoming-1098717#incoming-1098717
from alaveteli.
Just to offer another example showing the need to explain why an alert has been sent:
On Thu, Aug 2, 2018, 6:19 PM WhatDoTheyKnow <track@[domain]> wrote:
New updates for the request '[request subject]'
Home Office sent a response to [user name] (25 April 2016)
"Dear Sir or Madam FOI [number] Please find attached a reply to your Freedom of Information request that you sent on 24 March. Regards..."
[url]
Another related idea: when old responses, say those received over 2-3 months ago, are classified - don't send alerts on classification
from alaveteli.
Another comment from a user who was alerted on the same incoming message twice - because it had changed state.
I just had one of these.
New updates for the request 'FixMyStreet questionnaire results'
===============================================================
Oxfordshire County Council sent a response to Helen Highwater (24 September 2018)
It looks broken, because we're saying "sent a response" and the date is last year.
What actually happened was that the user changed the classification.
from alaveteli.
I just had another of these, and something looks fishy.
New updates for the request 'FixMyStreet Pro'
=============================================
Lincolnshire County Council sent a response to Abdul Hai (15 January 2019)
"Good morning Please see the attached response to your FOI request from 25th August 2018. Sincere apologies for the delay. Kind regards ..."
https://www.whatdotheyknow.com/request/fixmystreet_pro?nocache=incoming-1293348#incoming-1293348
I'd need to really read the code around described_state
and calculated_state
to remember how all this works, but it looks like the request was classified as successful when the response came in on 2019-01-15 (1). Then, on 2019-06-18, the request was re-classified as successful from awaiting_response
(2).
I'd already received an alert from the initial classification on 2019-01-15.
Looking back at #27 (comment), we see the same pattern – this time with not_held
:
The several edit
events are caused by #4776, which I didn't think was related, but I wonder if the addition of creating an InfoRequestEvent
in 0f79949 means that we lose the "calculated state" from the response
event?
from alaveteli.
Not 100% sure if this is the correct issue to add this to, but...
A user today contacted WDTK support saying:
I have an alert for "aberdeen" set up and today got an item in the digest for an FOI request dated in 2018
https://www.whatdotheyknow.com/request/you_have_and_office_in_the_marsc?nocache=incoming-1268033#incoming-1268033
No idea what happened there, perhaps there was an update that was then deleted but thought I'd flag it you anyway.
This request was categorised by me earlier in the day.
from alaveteli.
A user has today suggested that alerts should be sent to those following a request when new correspondence arrives on the thread.
That is how I would expect the alert / track / follow to work too.
from alaveteli.
A user has today suggested that alerts should be sent to those following a request when new correspondence arrives on the thread.
That is how I would expect the alert / track / follow to work too.
To my knowledge, we do exactly what is being suggested here; however, after a substantive event happens (e.g. after a response is classified), we appear to generate the same tracking message again.
Case in point:
I have a track setup for request 624904 on WDTK (tid:152807). A track message received on 8th January contained:
New updates for the request 'RSAS accreditation
================================================
Bob Packard sent a follow up message to Police Crime Prevention Initiatives Ltd ( 8 January 2020)
"I note that I have not received a response to my Freedom of Information request dated 3 December 2019, nor, have you had the courtesy to acknowledge..."
https://www.whatdotheyknow.com/request/rsas_accreditation?nocache=outgoing-979977#outgoing-979977
Police Crime Prevention Initiatives Ltd sent a response to Bob Packard ( 8 January 2020)
"Thank you for your request for information, and apologies for the delay in replying to your request. Please find attached our response to your request...."
https://www.whatdotheyknow.com/request/rsas_accreditation?nocache=incoming-1497226#incoming-1497226
However, when the response was eventually classified on the evening of the 10th of June (e.g. six months later!) we generated the same tracking message again:
New updates for the request 'RSAS accreditation'
================================================
Police Crime Prevention Initiatives Ltd sent a response to Bob Packard ( 8 January 2020)
"Thank you for your request for information, and apologies for the delay in replying to your request. Please find attached our response to your request...."
https://www.whatdotheyknow.com/request/rsas_accreditation?nocache=incoming-1497226#incoming-1497226
Are we generating this second tracking message because Alaveteli is detecting the change of classification (or event being generated) as a reason to which it should send a track?
If so, I ponder if we should either include the reason for sending it (e.g. the request has been classified, which might prompt a casual reader to look at it in more detail), or stop Alaveteli from generating tracks based on classification events.
from alaveteli.
+1 A user has got in touch to let us know about a dupe alert that they received. This was caused by the request being classified a month after the first alert.
from alaveteli.
Related Issues (20)
- Button to revert status of requests marked for admin attention
- Consider practicality of generating alerts when Excel files containing hidden data are released
- Add dropdown or similar with suggested comment when adding censor rules
- Ability to delete an incoming message but leave an explanation
- Improve post-report messaging
- Add the ability to search by request email address to the admin interface
- Renaming a user account can leave the profile url slug unchanged
- Make the tag edit box on the body admin page bigger HOT 3
- Hide "Authority: Respond to request" in actions menu
- `remove_tag` method is broken for `key:value` tags
- Topic pages - make search box less prominent
- Topic pages - default to show successful/partially requests
- Erronous shebang in docker/reset HOT 2
- Allow users to edit request titles
- List Projects in Pro Dashboard
- Allow Pro Users to Create Projects
- Ability to Publish Project Dataset
- Make it possible to extend an embargo by clicking on a link in the expiration reminder email.
- Show that foi_no authorities are not subject to FOI on the authority search listing pages
- Allow users to check authority email address HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from alaveteli.