On Tue, Jul 28, 2009 at 5:19 PM, Matthew Somerville <[email protected]>wrote:
> 80n wrote: > > It doesn't really change my point which is that if you are telling the > > council something that the user doesn't see then there is an increased > > possibility of confusion and misunderstanding. > > I agree, but it does explain the extra information as such in the email > to the council - sadly we can't make councils always comprehend it. > > > Is there any reason why this derived address cannot be shown to the > > user, preferrably *before* the report is sent to the council? > > It takes time to perform the lookup so really needs to run as a back-end > process (it does it when sending the email to the council). It could be > included whilst someone is checking for their confirmation email, but > it's a bit late then for your purposes (I guess it could be included in > the confirmation email, but I imagine most people wouldn't see it). I > also think it could be confusing to a normal user - why are we giving > them this address when they've selected a point on the map already? > Obviously the best solution would be to do it at the time the user selects the location. The later it is in the process the less optimal it is. The current solution of *never* telling the user about it is very unsatisfactory. It's actually even worse than this. The user doesn't even have a clue that you might be telling the council something different from what the user actually submitted. At the very minimum the user ought to be copied on the exact message sent to the council. 80n
_______________________________________________ Mailing list [email protected] Archive, settings, or unsubscribe: https://secure.mysociety.org/admin/lists/mailman/listinfo/developers-public
