aboutsummaryrefslogtreecommitdiffstats
path: root/todo.txt
blob: 6e17e67d7c3089c174c826b8da41ff842aeaf3b5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
Send confirmation email

Make it say "dear" as default letter

Escape/simplify short name properly in URLs of public bodies
For public bodies whose short names are renamed, make old URL still work and redirect

Shitty using sessions for redirect back - you lose if you click login
   link elsewhere in same browser, and then do sign in on original.
   It trashes your whole request.

Use something other than session for post redirect store, so can go via email
If you recently made a request, then a login will try to make it again because
    all the stuff for the post redirect is in the session. Consider again

Write some tests (try it their way, at every level)

Tidying
=======

Links to user pages with <sup> etc. in don't work
Check that when on such a page <title> etc. is right

Prevent double posting of same request

If summary is blank, says "title must be filled in" grrrr
Tidy up error message text (like "body must be filled in") on info request form

Set "null" and "default" options more in schema
Add SQL foreign keys to database schema
    execute 'ALTER TABLE researchers ADD CONSTRAINT fk_researchers_departments FOREIGN KEY ( department_id ) REFERENCES departments( id ) '
    http://wiki.rubyonrails.org/rails/pages/UsingMigrations link to:
        http://www.surfdewey.com/2.html
        http://www.redhillconsulting.com.au/rails_plugins.html#foreign_key_migrations
        http://rubyforge.org/projects/mig-constraints/
Call "delete from sessions where now() - updated_at > 3600" (one hour) or whatever

Legal/privacy
=============

Check act to see if can use pseudonym for FOI request?
"We will not reveal your email address to anybody" - are there circumstances
 (e.g. somebody messaging creator of a request and it bouncing) where we
 may reasonably do this, and should say it may happen?

Maybe we SHOULD reveal their email to the public body, why not?


Later
=====

Add postal address at City University to request

Read wiki page lots
http://www.mysociety.org/moin.cgi/FreedomOfInformation
And comments on proposal
http://www.mysociety.org/2006/04/04/freedom-of-information-archive/

Check FOE site lots
http://community.foe.co.uk/tools/right_to_know/request_generator.html

Look at this basic US site
http://www.rcfp.org/foi_letter/generate.php

Add spelling checker as in WTT

For grey hints in input fields
http://pauldowman.com/projects/fieldhints/

Somehow validate all pages with HTML validate

Consider having link to publications scheme type pages for each body:
http://www.ordnancesurvey.co.uk/oswebsite/aboutus/foi/index.html
http://www.ordnancesurvey.co.uk/oswebsite/aboutus/foi/coiindex.html

Maybe prepend letter for them with "this is FOI request blah" boilerplate?

Sources of public bodies
========================

Schools list: www.edubase.gov.uk

Heather has some for central departments