diff options
Diffstat (limited to 'todo.txt')
| -rw-r--r-- | todo.txt | 45 |
1 files changed, 22 insertions, 23 deletions
@@ -1,36 +1,30 @@ -Next (things that will reduce admin time mainly) -==== - -holding_pen - detect ones with just bad checksum +Make incoming mail script tell exim to hold messages and try redelivery when + it goes wrong +And email admins Things to make bots not crawl: /request/13683/response?internal_review=1 /request/febrile_neutropenia_154?unfold=1 + /list/recent?page=671 -Cache some common pages, such as "view requests": - http://www.whatdotheyknow.com/list/successful -And all individual requests. - -/request/13683/response?internal_review=1 +Next (things that will reduce admin time mainly) +==== Factor out "defunct/not_apply" from request_email into own field so defunct authorities can still have followups to existing requests. Probably into tags. -Add help about not adding extraneous or possibly libelous content to -requests or followups. Explain how to write things to avoid libel law. -Perhaps use these house rules: +Have proper house rules / site terms and conditions page. +Perhaps borrow from these house rules: http://www.theyworkforyou.com/houserules/ -Button for people to say "this status is really quite wrong please -fix it"? - Lots of authorities are starting to complain about how their record looks on their page - e.g responses not classified by users. That users may classify incorrectly. Change wording to make it clear statuses are users opinion ?. * Meanwhile mention in help that authorities can do this * And ask that they include URL of requests in emails when talking about them +Finish up the request game, and market it a bit more. Check up on how the public old request status editing is being used in practice. Think about UI a bit more to try and up rate, and UI of alerts to requester. @@ -42,10 +36,14 @@ valid reason for delay. Allow for deadline extension for schools. -Put the request from address in the database, then change the rule for making it. +Put the request from address in the database, + XXX not so sure about that, as need fuzzy rule for matching/guessing according to type +then change the rule for making it. * Use maybe words for generated email address? Name of the person and a request number (i.e. number of that persons request, so there are few numbers)? julian.todd@section44.whatdotheyknow.com +* Use words from a dictionary, e.g. cat, mouse, rat, hat etc. +* Use single words from the request, e.g. section, terrorism, allotment * Make sure avoid FROM_ENDS_IN_NUMS rule in Spam Assassin * Identify authority by who it is from. * It looks like an error generated by GFI MailEssentials, see p62 of chapter @@ -63,8 +61,7 @@ Julian things: Use FOI code from them authority to work out where emails are to go Keep FOI code in subject to help them a bit Show requests by authority on user page - Let the user refile ones that have arrived in wrong place - Second request by same person - tell them to use this email + Second request to same authority by same person - tell them to use this email check-recent-requests-sent probably doesn't work, as exim log lines wouldn't be load in case where the envelope from gets broken? @@ -73,19 +70,21 @@ Admin button to resend request one off to particular address Add explicit option for user to select "misdelivered to the wrong request" and let people move them to the right place. +(Julian wants that too) Give authorities interface for editing their request email address and resend messages to them -Page cacheing - the cookie setting stops the expires_on caching working well, -as even when not logged in second page you go to isnt serverd from Squid cache. -Maybe change to fragment caching for things like the "view requests" page? -Then will help logged in users too. - Later ===== +Renaming of a body, or changing its domain, should clear the cached bubbles of +all requests to that body. + +Page cacheing - the cookie setting stops the expires_on caching working well, +as even when not logged in second page you go to isnt serverd from Squid cache. + Emails sent to stopped requests should follow RFC: http://tools.ietf.org/html/rfc3834 Shouldn't bounce message back to Auto-Submitted Should check from address being replied to is valid |