I appreciate what you guys do, but I would much rather have a new status 'this response relates to a different request' - tick it, and let the system bounce it back to the sender.
When I want to create a new FoI and have a couple that need classifying - thats not too big a deal if its just ticking a box - but if I have to trawl through finding with message is supposed to be linked to which request etc - and then remember not to reply until they have been moved, I am better off just going to gmail... As it is, I now think - shall I have a quick check on WhatDoTheyKnow? Oh no, there are a load that need moving, I'll wait 'till I have a decent chunk of time... and of course it gets put off.... and off... Simply knowing that this is all down to the authority using the wrong email address helps! I guess I can do my own 'this does not relate to the FoI request at this email address, you need to send it to the correct address as given on the original request'. Regards Paul /)+) On 16 March 2012 10:22, Helen Cross <[email protected]> wrote: > Hi, > > > On 16/03/2012 09:24, paul perrin wrote: > >> >> Now I have an idea of what they see - it seems they are using the address >> for a request about school closures for everything right now >> >> Here is the latest wrong reply >> http://www.whatdotheyknow.com/**request/notice_of_school_** >> closure_st_marg#incoming-**264209<http://www.whatdotheyknow.com/request/notice_of_school_closure_st_marg#incoming-264209> >> > > I've moved this to http://www.whatdotheyknow.com/** > request/have_jobsposts_been_**lost_as_a_re#incoming-264668<http://www.whatdotheyknow.com/request/have_jobsposts_been_lost_as_a_re#incoming-264668> > > and > > http://www.whatdotheyknow.com/**request/notice_of_school_** >> closure_st_marg#incoming-**262254<http://www.whatdotheyknow.com/request/notice_of_school_closure_st_marg#incoming-262254>- >> To do with speed limits >> > to http://www.whatdotheyknow.com/**request/consideration_of_** > increased_vehic#incoming-**264671<http://www.whatdotheyknow.com/request/consideration_of_increased_vehic#incoming-264671> > > The best thing to do when this happens is to contact > [email protected] as we're happy to move these (takes less than a > minute to do) and to tell the council to check they are using the correct > address in future. It is also best not to reply to a message that has been > sent to the wrong place until it has been moved, as this makes things > harder for us to sort out and the council will get a message from the wrong > address and think that it is an ok one to use. > > More generally, misdirected responses aren't too big an issue. We deal > with about 18 - 19 a week, with almost all of those being caused by typos > in the request address, which are caught by the system and sent to the > Holding Pen before they can be delivered to the wrong place. > > It is extremely rare for an authority to store one WDTK address in their > system and insist on sending all responses to that address, as by now, most > seem to understand the basic idea of how WDTK works. > > In Paul's case, Brighton are consistently using one email address to reply > to several different requests. I think this is most likely to be caused by > human error, rather than by a general issue with their systems, as they > have successfully dealt with multiple requests from one user in the past > without any responses going astray. They probably just need a nudge to > remind them to reply to the address the message comes from. > > Regards, > ------ > Helen - WhatDoTheyKnow.com volunteer. > > > > > ______________________________**_________________ > developers-public mailing list > developers-public@lists.**mysociety.org<[email protected]> > https://secure.mysociety.org/**admin/lists/mailman/listinfo/** > developers-public<https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public> > > Unsubscribe: https://secure.mysociety.org/**admin/lists/mailman/options/** > developers-public/paul%**40idltd.com<https://secure.mysociety.org/admin/lists/mailman/options/developers-public/paul%40idltd.com> >
_______________________________________________ developers-public mailing list [email protected] https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public Unsubscribe: https://secure.mysociety.org/admin/lists/mailman/options/developers-public/archive%40mail-archive.com
