mySociety blog » archive for 2009

Constituency boundaries are changing at the next general election in England, Wales, and Northern Ireland. After some amount of fiddling (I’ll go into technical details in another post, but it wasn’t as easy as just importing some shapefiles), as a slightly early Christmas present, TheyWorkForYou now has a section where you can enter your postcode to find out what constituency you are currently in, and what constituency you will be voting in at the election, along with maps of before and after:

http://www.theyworkforyou.com/boundaries/

This service is also available through the TheyWorkForYou API. This is a facility we have been asked for frequently, more so as we approach the forthcoming election; the large amount of boundary changes have led to confusion from our users and elsewhere, so this will hopefully prove useful.

One site that will need the boundaries before the election is DemocracyClub – join to help make this coming election the most transparent ever!

Side effects of the above process include updated council boundaries, so those councils on WriteToThem that we’ve had switched off since May due to lack of boundary data are now back; a more up-to-date postcode dataset; and the beginnings of parish council support (as in they’re now in the database, but the front-end doesn’t know what to do with them yet).

I hope you all have a happy Christmas and New Year.

Wednesday 20th January, in Manchester; mySociety, Democracy Club, and friends invite you to join us in the Briton’s Protection from 7:30 for conversation on democracy, engagement and tea.

mySociety runs projects such as TheyWorkForYou.com,FixMyStreet.com and WhatDoTheyKnow.com, while DemocracyClub.co.uk is the new independent volunteer network for the upcoming election to keep track of how parties campaign in your local community when they think no one elsewhere will notice.

Come join us in the pub (20th Jan, 7:30), or you can sign up to Democracy Club at                            http://www.democracyClub.co.uk

The Briton’s Protection is just behind the Bridgewater Hall, postcode M1 5LE. You’ll find us in one of the two backrooms, wearing a mySociety hoodie or carrying a clear sign. Tom has his picture here: http://www.mysociety.org/about/

A Facebook event is now open.

Like mySociety? Like pubs? Why not come to our pre-Christmas pub meet, this coming monday?

The Banker

2 Cousin Lane, London, EC4R 3TE

21st December from 6.30pm onwards.

Leave a comment on this post if you’re coming. New faces and old hands equally welcome.

Over the last weekend of November 2009 a group of 21 mySociety staff, volunteers and trustees went to a house outside of Bristol to wrestle with the question of what mySociety should build over the next 12 months. This was the fourth time we’ve done it, and these meetings have become a crucial part of our planning.  This year, we were talking not just about what new features to add to our current sites, but also about the possibility of building an entirely new website for the first time in a couple of years. The discussions were lively and passionate because we know we have a lot to live up to: not only is our last major new site (WhatDoTheyKnow) likely to cross the 1 million unique visitors threshold this year, but we understood that there were people and organisations who weren’t there who would be counting on us to set the bar high.

A chunk of the weekend involved vetting the 227 project ideas that were proposed via our Call for Proposals. I’m going to write a separate post on our thoughts about that process, but if you look at the list below you may spot things that were submitted in that call.

One nice innovation that helped us whittle down our ideas from unmanageable to manageable numbers was a pairwise comparison game to help us prioritise ideas, build custom for the occasion by the wonderful and statistically talented Mark Longair.  In other words, we used the technique that powers  KittenWar.com to help decide our key strategic priorities for the next year: after all , if we don’t, who will?

By the end of the weekend we had not battened everything down – there are too many uncertainties around how much time we will have, and some key ideas that need more speccing.  However, we were able to put various things into different buckets, marked according to size and degree of certainty.  So here goes:

1. Things which were decided at the last retreat, which we are definitely building,  and which (mostly) need doing before next year’s stuff starts getting built

• A top level page for each bill on TheyWorkForYou
• Future business (ie the calendar) for events in the House of Commons, including a full set of alerting options.
• Video clips on MP pages on TheyWorkForYou
• Epicly ambitious election data gathering and  quiz building with the lovely volunteers at DemocracyClub

2. Small new things that we are very probably doing because there was lots of consensus

• Publish a standard that councils can use to post problems like potholes in their databases to FixMyStreet and other similiar sites.
• Template requests in WhatDoTheyKnow so that users are strongly encouraged to put in requests that are well structured.
• After the next general election, email new MPs with various bits of info of interest to them including their new login to HearFromYourMP, their page on TheyWorkForYou, explanation of how WriteToThem protects them from spam and abuse, a double check that their contact details are correct, and a introduction to the fact that we record their correspondance responsiveness and voting records.
• Add to WhatDoTheyKnow descriptions about what kind of public authority a specific entity is (ie ‘school’, ‘council’) and the information they are likely to hold if FOIed.
• Show divisions (parliamentary votes) properly on debate pages on TheyWorkForYou, ie show the results of a vote on the same page as the debate where the issue was discussed, with full party breakdowns on each division.
• Add “How to benefit from this site” page on TheyWorkForYou, inspired by OpenCongress.org
• Help Google index TheyWorkForYou faster by creating a sitemap.xml file that is dynamically updated.
• Using the data we expect to have from DemocracyClub’s volunteers, send a press release about every new MP and to all relevent local newspapers
• Incorporate a council GeoRSS problem feed into FMS

3. Slighty more time consuming things we are very probably doing because there was lots of consensus

• 1 day per month developer time that customer support guru Debbie Kerr gets to allocate as she see fit.
• Premium account feature on WhatDoTheyKnow to hide requests so that journalists and bloggers can still get scoops and then share their correspondance later.
• Add Select Committees to TheyWorkForYou, including email alerts on calls for evidence.
• Take professional advice on how to handle PR around the election

4. Much more time consuming things and things around which there is less consensus. NB – We do not currently have the resources to do everything on this list next year – it is an ambitious target list.

• Primary New site: TBA in a new post
• Add a new queue feature to WhatDoTheyKnow so that users can write requests, then table them for comments from other users and expert volunteers before they are sent to the public authority
• Relaunch our Volunteer tasks page on our sites, keep it populated with new tasks, specifically allocate resources to handhold potential volunteers. Allocate time to see if any of the ideas that we didn’t build could be parcelled into volunteer tasks.
• Secondary New site (if we have a lot more time than we expect): Exploit extraordinary richness of Audit Comission local government target data in a TheyWorkForYou-like fashion.
• FixMyStreet to become international with  a) maps for most of the world b)  easy to follow instructions explaining how to supply mySociety with the required data to us to enable us to turn on FixMyStreet in non UK countries or areas. This data would includ  ie gettext powered text translation files,  shapefiles of administrative boundaries, and lists of contact data.
• Add votes and proceedings to TheyWorkForYou (where they reveal statutory instrument titles that are not debated but where the law gets changed anyway)
• Carry out usability testing on TheyWorkForYou with then help of volunteer Joe Lanman – then implement changes recommended during a development process taking up to 10 days.
• Add to TheyWorkForYou questions that have been tabled in the house of commons but which haven’t been answered yet.
• Add a new interface for just councils so that they can say if a problem on FixMyStreet has changed status.

Phew. And that’s not even counting the projects we hope to help with in Central and Eastern Europe, our substantial commercial work, or the primary new site idea, which will be blogged in Part 2.

Today we have a strange story about a department that appears to think that it has a duty not to release information under FOI if it makes people angry.

It all starts in January 2009 the Department for Children, Schools and Families (DCSF) appointed an expert by the name of Graham Badman to conduct a review of elective home education in England. It probably goes without saying that this is an issue far from our concerns, and an issue that mySociety has no views on – what makes us interested is the process that followed.

Shortly after the publication of the report, Elaine Walton, a user of mySociety’s freedom of information website WhatDoTheyKnow.com requested copies of communications between the Department for Children, Schools and Families and Nektus Ltd. the company through which it appears Mr Badman was paid for his work.

According to email replies to Ms Walton, the DCSF located two relevant invoices which show how much money was paid, but refused to disclose them.  Strangely, though, they were not refused on grounds of commercial confidentiality, but rather on something more unusual. Here are the exemptions they cited:

• Section 40 – Personal Information
• Section 38 – Health and safety

Health and Safety? A little investigation reveals more.

When Ms Walton appealed against this decision, an internal review was carried out within the DSCF.  The internal review’s findings stated that Mr Badman was likely become a victim of harassment if certain personal details were made public, hence a health and safety concern, and hence no publication of these invoices. Fair enough – nobody would be in favour of revealing private, sensitive information that would endanger anyone’s life or family, especially in the presence of a known threat.  But take a look at this:

“That the Department had initially been drafting a response that included the release of invoices with only personal data redacted. But before the draft was complete it was apparent that there was a campaign of harassment and vilification against Graham Badman and other individuals/organisations that had contributed to the Report. In the light of this, at the weekly review meeting of FOI cases, it was considered that the balance of public interest might have shifted towards withholding.”

What is very curious here is the admission that the department had been thinking of releasing the invoices with personal data hidden (ie no home address, bank details etc).  But then because of a campaign of harassment, it was decided that they wouldn’t publish anything at all. So not just no personal information, but no dates, no amounts of money, nothing.

What is so unease-making about this FOI decision is that it appears to be saying that departments may conceal information on how much public money has been spent on something because releasing that information will make some angry people even angrier. Surely this can’t be right – if it were every budget would be conducted in complete secrecy. We would encourage the Information Commissioner’s Office to take a look.

We know from our inboxes that there are people all over the world who would love to start sites like TheyWorkForYou.com, FixMyStreet.com, or WhatDoTheyKnow.com in their own countries. Building and running these sites is hard, though, and takes time, money, and love. Until now we haven’t been able to do much for these keen correspondents beyond sharing our ideas, sharing our code, and wishing people the very best of luck. We’re happy to say that for at least some of these people, things are about to change for the better.

If you live in Central or Eastern Europe, we’re now in a position to help you get effective democracy and transparency websites built. mySociety have teamed up with the Open Society Institute (OSI) and together we are now looking for determined people with great ideas for new digital transparency and accountability services in their countries.

Over the next few months we are running a Call for Proposals, similar to the one we recently ran in the UK. The big difference is that this time we’re not looking for projects that we will build. We’re looking for projects you want to build, but that for lack of funds or lack of the right skills, you can’t get started yourself.

Each month the Open Society Institute and mySociety will work closely together to select a series of projects to fund and mentor. Crucially, the call isn’t solely for existing NGOs: the process is absolutely open to submissions from individuals or groups with no prior direct experience of working in the transparency and accountability sector, but who have a good idea that addresses a problem they see in their country. We will, however, look more favourably on applicants with access to the advanced programming skills required to build sites like this.

The criteria are simple, though demanding:

1. The projects have to generate some kind of meaningful transparency, accountability, or democratic empowerment of another kind.
2. The projects must seize the unique benefits that the Internet brings with it, such as scalability, two way communication, easy data analysis and so on.

More details are available over at our new CEE site, but even if you don’t live in one of the eligible countries please help us spread the word about this exciting new opportunity!

mySociety’s Freedom of Information website WhatDoTheyKnow is designed to appear simple and straightforward to users. That appearance belies the fact that behind the scenes a significant amount of effort goes into making sure both those making freedom of information requests and those answering them have a positive experience of the site. While the site is almost entirely automated sometimes human involvement is necessary. This article highlights those key “edge cases” which are dealt with by the staff and volunteers who make up the WhatDoTheyKnow team.

In the last year 15,233 freedom of information requests have been made via WhatDoTheyKnow.

Message Delivery
444 messages on 360 requests (2.3%) had to be manually placed on the correct request as a result of authorities not sending replies to the email address given. The errors are introduced as authorities apparently manually transcribe email addresses from incoming email into correspondence management systems. There have been suggestions some may even print out and scan-in emails into such systems. WhatDoTheyKnow’s code has been improved in light of experience, common errors are now detected automatically and in many cases the system suggests which request the message was intended to be directed to.

In terms of outgoing messages just 52 (0.3%) requests over the course of the year were marked as receiving an error message in response and users marked 94 (0.6%) as requiring administrator attention. These are generally either transient errors which simply require a message to be resent or prompt us to check and update the contact details we hold for a particular organisation. Regularly there are problems with authority’s spam filters and we have to encourage them to change the way their filters are set up to allow messages from WhatDoTheyKnow.com through.

Gone Postal
119 (0.8%) requests were at some point marked as “Handled by Post”. In many of these cases users eventually persuaded authorities to release the information in electronic form. Where information is supplied outside the site users can add annotations describing the information released, then can link to copies of the data they have posted online, or as has been done in respect of 14 requests (0.1% of the total, 11% of those handled by post) they can supply the information to WhatDoTheyKnow to upload manually. When the site was being designed there was a worry that authorities would reply to many requests by post. This has not occurred, in part perhaps because the freedom of information act contains a provision (section 11) requiring the requestor’s preferred means of communication to be used where it is reasonable. A requestor using an @whatdotheyknow email address is clearly expressing a preference for a reply to be made electronically via the site.

Libel
One of the major challenges facing the site is keeping it operating in the face of the UK’s libel laws. Unlike in other countries, such as the US, we cannot publish statements on our users’ behalf without taking the risk of being sued for libel ourselves. Even simply republishing FOI responses from public authorities is not without risk in the UK. While we don’t actively police the site a lot of administrator time is taken up dealing with cases where potentially libelous or defamatory comments have been brought to our attention. Cases can be very complicated and involve a great deal of correspondence. mySociety is lucky to have the services of a specialist internet and technology barrister with expertise in libel who provides his services free of charge. We try and act in such a way as to maximise transparency while ensuring that the existence of WhatDoTheyKnow and mySociety are not threatened by legal risks.

In the last year there have been only seven significant cases where requests have been hidden from public view on the site due to concerns relating to potential libel and defamation. Three of those cases have involved groups of twenty or so requests made by the same one or two users. While actual number of requests we have had to hide is around 70 (0.4% of the total) even this small fraction overstates the situation due to the repetition of the same potentially libellous accusations and comments in different requests. In all cases we have kept as much information up on the site as possible. Our policy with respect to all requests to remove information from the site is that we only take down information in exceptional circumstances; generally only when the law requires us to do so.

Personal Information
Sometimes people accidentally post personal information to the site; for example they make a request which is not a Freedom of Information request but a subject access request under the Data Protection Act. We are happy to remove such requests. On occasion we get requests from both our users and public sector employees asking us to remove their names from the site. As we are trying to build up a FOI archive we are very reluctant to remove information from the site, our policy is only to remove names in exceptional circumstances. Often information, such as an out of office reply, which a public body or civil servant considers irrelevant and asks to be removed is in fact critical to the correspondence thread and timeline of a response.

Copyright and Control of Information Released
The fact information is subject to copyright and restrictions on re-use does not exempt it from disclosure under the Freedom of Information Act (though there is a closely related exemption relating to “commercial interest”). Occasionally public bodies will offer to reply to a request, but in order to deter wider dissemination of the material they will refuse to reply via WhatDoTheyKnow.com. Southampton University have released information in protected PDF documents and the House of Commons has refused to release information via WhatDoTheyKnow.com which it has said it would be prepared to send to an individual directly.

Mantaining and Expanding The List of Authorities
WhatDoTheyKnow lists around 3,000 public authorities, there is a regular turnover of changes in contact details. Our coverage, while large, is not comprehensive so we have requests to add bodies such as parish councils, schools, and doctors surgeries which we have not yet attempted to add in a systemic manner based on official sources of information.

We have also had to carefully consider what we do when for handling the various situations where an authority becomes defunct and its responsibilities are taken over by another body for example as a result of reorganisations of local government and the creation and merging of government departments.

Providing Advice and Assistance
The team at WhatDoTheyKnow.com often provide advice to users. We encourage users to keep their requests focused so as to reduce the chance of any problems due to libel or requests being classed vexatious. On occasion we suggest appropriate authorities for users to direct requests to, provide advice to those unhappy with the response to their request, and answer a broad range of other queries as they arise such as if particular bodies are subject to the act or not. Increasingly we link to authority’s publication schemes which are intended to let people know what information an authority has and how it can be accessed.

Spam
Lastly, like all websites which allow people to post content online WhatDoTheyKnow.com occasionally suffers from spam in various forms. Most is dealt with automatically but some has to be removed by hand. With spam, like the other aspects of running the site, the site’s code and processes are constantly being developed and improved to reduce the fraction of cases requiring any manual intervention.

This article was prompted in part by a team in New Zealand considering launching their own version on the site asking us what’s involved.

Come to the pub with us!

12th October 2009, from about 6.30, at the Banker just under Cannon Street station.

We won’t bite. Probably.

Statistics were recently released on the performance of UK central government departments with respect to their handling of freedom of information requests. The latest figures are for the second quarter of 2009. We have been able to use these to calculate the fraction of all requests which are made via mySociety’s freedom of information website WhatDoTheyKnow.com.

• 13.1% of all FOI requests to “Departments of State” in the second quarter of 2009 were made via WhatDoTheyKnow.com. In absolute terms this was 753 out of 5769 requests; this is up from 8.5% in the first quarter of 2009.
• 32.3% of FOI requests to the Home Office (which includes the UKBA and the IPS) were made via WhatDoTheyKnow in the second quarter of 2009. In absolute terms this was 206 out of 638 requests.
• The latest figures show that in twelve of the UK’s twenty-one Departments of State more than 10% of FOI requests were made via WhatDoTheyKnow.

What these statistics mean is that an ever increasing fraction of the information released in response to freedom of information requests is being archived and made publicly available by WhatDoTheyKnow.com. Hopefully this will reduce the number of duplicate requests being submitted and ensure the information released is made available to the widest possible audience which in-turn should increase the chances it is acted on.

Only forty-three central government bodies have their freedom of information performance monitored centrally. This is a tiny fraction of the three thousand or so bodies currently listed by WhatDoTheyKnow.

Raw Data

• Freedom of Information Act: statistics on implementation in central government – UK Ministry of Justice
• Detailed statistics on WhatDoTheyKnow’s share of requests on a per department basis.

We are very happy to announce that Duncan Parkes has joined mySociety, bringing our team of full time core developers up to four.

Duncan is the incredibly prolific author of screen scrapers for the lovely PlanningAlerts.com which he runs with Richard Pope.

He also has a PhD in Mathematics, which I expect you’ll want to read all of here, and is an editor of Open Source programming books with APress. During the vetting process he listed one of the passions of his life as being ‘Unit Testing‘, which, combined with his love of postbox crowdsourcing, made picking him more or less a no brainer.

In the short run we’ve let him loose, under the tutelage of Francis Irving, on the scaling challenges presented by Mapumental – I can’t wait to see what comes out of it.

I’ve been doing lots of research around “cloud computing” recently, so we can change how Mapumental works and take it out of private beta.

One thing that’s struck me is that there doesn’t seem to be a proper, industry standard name to distinguish what to me are two fundamentally different sorts of “cloud computing”. I’m focusing here entirely on cloud services for programmers (let’s leave what it means to end users or businesses for another day).

Here are my own names and descriptions of them:

1) Cloud hardware server provision (Cloud HSP)
Low level APIs for making and destroying (virtual) servers, and loading machine images onto them. e.g. Amazon Elastic Compute Cloud, Rackspace Cloud Servers, Eucalyptus’s EC2 bits. Basically, what Eucalyptus v 1.5 can do and what libcloud should do. (By analogy, this is the assembly language of cloud computing)

2) Cloud developer service provision (Cloud DSP) A service that a developer accesses with one name and a simple API, and behind the scenes it scales for him, automatically. e.g. Amazon Queue Service, Rackspace Cloud Files. (By analogy, this layer is the C programming language of cloud computing)

[as an aside, Google AppEngine is an interesting one. It is definitely in the Cloud DSP category, but I think it is larger than that - it is a whole set of APIs all in that category. Something like Google DataStore is a single Cloud DSP, albeit one apparently only accessible within AppEngine apps]

It’s possible to use a Cloud HSP (assembly language), along with a bunch of your own software or open source software, to build new Cloud DSPs (C code). Right now this is pretty hard – even quite well known open source distributed datasbases like CouchDB still need scripting to even make them replicate. The code that makes and destroys servers and gives the service one name, needs manually stringing with quite new bits of wire (things like scalr and Wackamole).

For this reason, I’m reluctant for mySociety to get into the “making our own Cloud DSP out of Cloud HSP” game. It feels to me like a suck of time, and like we wouldn’t be able to guarantee without lots of careful and expensive testing that it would scale. I’m more tempted to use the commercial Cloud DSP services where possible, even though they are proprietary. But use them via our own abstraction layer, so we can change as we need to. Of course, we have some C++ code (the public transport route finder), so will have to use the Cloud HSP API to get that going, perhaps with Amazon’s Auto Scaling. But it can jolly well use AQS and S3 to talk to other services.

So, what do you think about the names Cloud HSP/DSP? Are there already existing names for the distinction that I’m making? Is it a useful distinction for you? Can you think of better names?

On Saturday John Cross and Richard Taylor, two volunteers who work on mySociety’s freedom of information website WhatDoTheyKnow.com, gave a workshop on FOI to a meeting of activists from Republic, an organisation which campaigns for an elected head of state in the UK.

mySociety and WhatDoTheyKnow are non-partisan and don’t get involved in campaigning except in specific areas relating to openness and transparency. That said, members of the WhatDoTheyKnow team are be happy to consider invitations from any groups wishing to hold a workshop discussing freedom of information.

Many of those present at Saturday’s event were active campaigners on a wide range of subjects ranging from human rights to fair trade as well as having an interest in constitutional reform. The FOI workshop was oversubscribed with the majority of those present at the event deciding to attend the session. Unlike a previous workshop held at OpenTech where most attendees had made an FOI request themselves prior to the event, at this workshop all but one had not done so.

The Royals and FOI
Given the audience, the status of the royals with respect to FOI was particularly pertinent. The FOI act exempts information if it relates to: “communications with Her Majesty, with other members of the Royal Family or with the Royal Household, or the conferring by the Crown of any honour or dignity”. This exemption does not apply though if it is determined that it is in the public interest for the information to be released. The requirement for this public interest test is under threat as the Prime Minister has been moving to strengthen the restrictions on releasing information related to the Royal family. On the 10th of June 2009 in a speech to Parliament on Constitutional Renewal Gordon Brown said:

…we have considered the need to strengthen protection for particularly sensitive material, and there will be protection of royal family and Cabinet papers as part of strictly limited exemptions.

Following that speech BBC journalist Martin Rosenbaum obtained a statement from the Ministry of Justice clarifying that in practice what Gordon Brown’s words meant was:

… the relevant exemption in the Freedom of Information Act will be made absolute for information relating to communications with the Royal Household that is less than 20 years’ old.

In FOI jargon an “absolute exemption” is one not subject to a public interest test.

Even with the law as it stands it is not easy to obtain information on how the royals are, or are attempting to, influence government. For example John Cross has asked the Ministry of Justice to supply him with copies of correspondence they had received from the Queen and Prince of Wales. They rejected his request on the grounds that the public interest in non-disclosure exceeded the public interested in disclosure; as well as suggesting exemptions relating to “information provided in confidence” and “personal information” also applied.

The Royal Household’s position on FOI
The Royal Household is not subject to the freedom of information act; though it has made a statement on the subject saying:

Despite its exemption from the FOI Acts, the Royal Household’s policy is to provide information as freely as possible in other areas, and to account openly for its use of public money.

WhatDoTheyKnow’s policy is to include such organisations which have indicated they are willing to voluntarily comply with the act to the site. While we list The Royal Household, at the time of writing no-one has yet used the facility to request information.

Using WhatDoTheyKnow for Campaigning
While we stress the importance of keeping freedom of information requests focused, FOI is a powerful tool for campaigners. We were asked if it would be possible for a group like Republic to set up an account on WhatDoTheyKnow for their campaign? The answer to this is: “Yes! – WhatDoTheyKnow wants to encourage groups to use the site”. The information commissioner has confirmed that it is acceptable to use the name of a “corporate body” when making a FOI request, that’s a broad term which encompasses many organisations, groups and charities.

Republic themselves use FOI extensively and often generate major national news stories as a result of responses to their requests. They want to be able to either offer journalists exclusive stories or write a press release based on information released. They can’t do this if the story gets out first via WhatDoTheyKnow so would be interested in an ability to make requests initially in private. mySociety and WhatDoTheyKnow have been considering an option for journalists to be able to make hidden requests via the site. Such a feature could potentially generate an income stream for the site as well as encourage a greater proportion of FOI requests to be made via it. Once the article had been published then the FOI correspondence could be opened up to the public providing access to the source material backing up the story.

As well as meeting those who use, or might want to use, the site to make requests WhatDoTheyKnow also wants to engage positively with public authorities; we see them as important users of our service too. Developer Francis Irving represented the site at the FOI Live conference for information professionals in June and will be speaking at the Freedom of Information Scotland conference in December.

Parliamentary boundary changes appear to be a source of confusion to many people and organisations. The facts are quite simple – parliamentary boundary changes, proposed by the various Boundary Commissions, do not take effect until the next general election. Until then, your MP remains whoever they have been, no matter what literature you may get through your letter box, or what anyone may tell you.

As one example, take Birmingham City Council. Their page on constituencies and wards correctly states that Birmingham is divided into eleven parliamentary constituencies, but then goes on to list only ten – they are listing the new constituencies which do not yet exist, as Birmingham is losing one constituency at the next election. It appears that they have organised themselves along the new boundaries in advance – which is fine, but this doesn’t affect current Parliamentary representation, and so they should explain this clearly, as otherwise members of the public get confused (and blame us for giving them the “wrong” MP, when we haven’t done so). As you can see from the maps above (which highlight Birmingham, Hall Green), the constituencies will be changing their boundaries quite a bit, and we have had reports of people receiving letters from candidates in the next election who are MPs of different neighbouring constituencies, simply referring to themselves as an MP, which is a great source of confusion.

An inhabitant of St Josephs Avenue, Birmingham (behind the Royal Orthopaedic Hospital), which is currently within the Selly Oak parliamentary constituency (red), and the Northfield ward of Birmingham City Council (green), would, on looking at Birmingham City Council’s website, assume they’re in a parliamentary constituency called Northfield. Northfield is currently the constituency to the west of Selly Oak; at the next election, its boundary with Selly Oak will change to the blue line, at which point St Josephs Avenue will be in the Northfield constituency. But not until then.

As another example (chosen purely as it has come up in user support), the Labour candidate for Streatham has a page about the constituency – obviously you would expect a candidate to be talking about the future constituency, but would it hurt to add some explanation that Streatham is currently a slightly different shape?

Boundaries of different things are all independent – if a ward boundary moves due to some local issue, the corresponding Parliamentary boundary does not necessarily change with it (probably not, in fact). So when Birmingham changed its ward boundaries back in 2003, they became out of sync with the Parliamentary constituencies. From the next election, things will be more in sync as the new Parliamentary boundaries are based on more recent ward boundaries, but this will again separate over time. All we can do is always clearly explain the current situation, and ask that others do the same.

Last week a user of mySociety’s Freedom of Information website WhatDoTheyKnow.com made a request for the release of the results of research into pollutants and urban greenspace in London which had been carried out by The Forestry Commission. Despite this work having been led by the government department responsible for the UK’s woodlands, carried out in collaboration with UK universities, and largely funded by public money distributed via the Engineering and Physical Sciences Research Council the results of the research were not freely accessible. The user was referred to an academic paper entitled An integrated tool to assess the role of new planting in PM10 capture and the human health benefits: A case study in London which has been published in the October 2009 edition of Elsevier Ltd’s Environmental Pollution journal. The publishing company are currently offering a A PDF version of the publication for $31.50 via their website.

Exemptions Applicable to Research
In terms of the freedom of information act there are a number of provisions which can be used to exempt the output of publicly funded scientific research:

• Section 22 of the act excludes “Information intended for future publication”, a large fraction of research cumulates in the publication of an academic paper so comes into this category.
• Section 21 excludes “Information accessible to applicant by other means.” This means that once research work has been published a requestor can merely be directed to the publication. Section 21(2)a of the act makes clear “information may be [considered] reasonably accessible to the applicant even though it is accessible only on payment.”

With the above exemptions in mind it might well be possible to phrase requests in such a way that they don’t apply. For example I have had some limited success in relation to a request for a research protocol.

First Come First Served?
Our user was offered a hard copy of the publication; the reason this request was drawn to our attention was that the team to was contacted to help the two parties to get in touch directly. I suspect the reason that an electronic copy of the document was not supplied via WhatDoTheyKnow may have been related to a concern over breach of copyright on the research results which has probably been transferred or licensed to the publisher. While one individual may have obtained a copy of the information, it is still not accessible to everyone. Tony Hutchings, the Forestry Commission’s Head of Land Regeneration and Urban Greenspace, who led the research told me: “We have prints of the paper which we could supply you with”. How many printed copies he has to distribute and what happens when he runs out is not clear.

Open Access Publishing
Ideally the results of publicly funded scientific research ought be published in an unrestricted format in open access journals. The UK government, is moving towards such a stance but at a painfully slow pace. I asked the author of the research why he had taken the decision not to publish in a more accessible journal. He responded by saying:

The Research Councils (as do many funders from both private industry and public bodies) assess the quality of the research undertaken by the impact factors of the papers produced. … To my knowledge there are unfortunately few open access journals with high impact factors.

The EPSRC who funded his research have a Policy on Access to Research Outputs which states: “knowledge derived from publicly-funded research must be made available and accessible for public use”. When I asked them for a comment on this particular case Dr Sue Smart their Head of Performance and Evaluation responded saying: “Tony Hutchings is mistaken in his assertion that we use journal impact factors in assessing the quality of research”, but she also ruled his offer of a paper copy of the research article was: “in keeping with the principles of the RCUK (Research Councils UK) position statement [on access to research outputs].”

Like the other volunteers who help out with WhatDoTheyKnow.com I use the site for my own activism and campaign independently for more openness and transparency in a range of areas. I have written an extended article on my own website on the subject of open access publishing where I have included more details of the responses from the research council and researcher quoted above.

WhatDoTheyKnow keeps growing and growing, sucking people in from Google as its archive of maybe 8.5% of Freedom of Information requests gets more and more detailed.

(Graph of number of FOI requests made using WhatDoTheyKnow over time; click for larger version)

There’s round about 8Gb of unfettered Government data in the core database, plus a whole bunch more for indexing and caching. For comparison, TheyWorkForYou (which now goes back to 1935) has 12Gb. And it’s catching up on traffic also – WhatDoTheyKnow has about half the number of visitors as TheyWorkForYou.

Unfortunately, this new found traffic has led to performance problems. You might have seen errors when using WhatDoTheyKnow in the last week or two. This post is firstly an apology for that. Thank you for your patience. Hopefully it is fixed now – do let us know if you get problems still. And secondly it is some techy stuff about debugging such problems in Ruby on Rails…

When WhatDoTheyKnow started failing, we did the obvious things to start with – moving the database to a separate server, and moving some other services off the same server, to give WDTK more room to breathe. It still kept breaking.

None of my server monitoring tools shed any very clear light as to the problem. I upgraded to the latest version of Passenger, the best Rails deployment tool I’ve seen yet. It’s pretty good, but still not mature enough for my liking. I was still getting the same problems with it, but reporting tools like passenger-memory-stats were really helpful.

Eventually I worked out that it was to do with memory use of the Rails processes. Individual ones would leap up to 1Gb, and never drop back down. If several did, the server (with 4Gb of RAM) would start swapping and grind to a halt. The world of Ruby and Rails memory monitoring software is patchwork at best, and in the end I found the simplest tools the most useful. Here’s some:

• I found some Rails processes were getting jammed, and not dieing even when I restarted Apache. I think in the end this was due to the Passenger spawning method, and our use of the Xapian Ruby module. Running Passenger in RailsSpawnMethod conservative mode made things much more robust.
• Monit, which in a previous life had a job holding up vital structural pillars of buildings with duct tape, makes you feel dirty. Actually it is really useful. Given I couldn’t quickly fix the problem, Monit let me at least reduce the suffering for people trying to use the site meanwhile. Here’s the rule I used, which gives Apache a kick every time server memory use is too high. It was firing every 5 or 10 minutes…
  

  check system localhost
      if memory > 3500 MB then exec "/usr/sbin/apache2ctl graceful"

• I found memory_profiler on a blog. It helps you find the kind of memory leak where you unintentionally continue to reference an object you don’t use any more. With a specialist subject of string objects. This led to a fix to do with declaring static arrays in classes vs. modules, which I still don’t really understand. But it wasn’t the cause of the big 1Gb memory munching, there were no large enough leaks of this sort.
• The record_memory function in WDTK’s application controller came from another blog. It’s handy as it shows you how much of the system memory in the Ruby process each request causes an increase by. With caveats, this was the best way for me to identify the most damaging requests (search results, and certain public body pages). And it also brought focus on the actual problem – the peak memory use during a request. That’s really important, because Ruby’s memory manager never returns memory to the operating system… The Gb leaps in memory use were because of temporary memory used during certain requests, which the Ruby memory manager then never frees later.
• I made a bunch of functions culminating in allocated_string_size_around_gc. This was really useful in use with the “just add lots of print statements and fiddle” school of debugging. Not everyone’s favourite school, but if your test code can’t catch it, one I often end up using (it gets really involved rarely enough that it doesn’t seem worth setting up an interactive debugger). It led me to various peak memory savings, such as calling “text.gsub!” rather than “text = text.gsub” while removing (email addresses and private information) from FOI request responses, which help quite a bit when dealing with multi-megabyte attachments.
• Finally, I used the overlooked debugging tool, and the one you should never rely on, being common sense. That is, common sense informed by days of careful use of all the other tools. In order to quickly show text extracts when searching, WDTK stores the extracted attachment text in the database. A few of these attachments are quite large, and led to 50Mb fields, often several of which were being loaded and processed in one page request. That this would cause a high peak of memory use all became just obvious to me some time yesterday. I checked that that was the case, and this morning, I changed it to use the full text for indexing, but to at most keep 1Mb for use in snippets. So sometimes now you won’t get a good search extract for queries, but it is rare, and it will at least still return the right result.

I’ve more work to do, I think there are quite a few other quick wins, all of which are making the site faster too. I’m quite happy that WhatDoTheyKnow also has a bunch more test code as a result of all this.

On the other hand, what a disappointing disaster for open source languages beginning with P/R (as opposed to J). Yes, the help and tools were just about there to work it out, but would seem primitive if you’d used say Java’s Memory Analyzer. Indeed somebody over on StackOverflow suggested running your site in JRuby and using exactly that tool…

Note: This post is a work in progress, I need your help to improve it, especially with knowledge of non-English sites

I was recently in Washington DC catching up with mySociety’s soul-mates at the Sunlight Foundation. As we talked about what was going on in the field of internet-enabled transparency, it came clear to me that there are now more identifiable categories of transparency website than there used to be.

Identifying and categorising these types of site turns out to be surprisingly useful.  First, it can help people ask “Why don’t we have anyone doing that in our country?” Second, it can help mySociety to make sure that when we’re planning ahead we don’t fail to consider certain options that be currently off our radar. Also, it gives me an excuse to tell you about some sites that you may not have seen before.

Anyway, enough preamble. Here they are as I see them – please give me more suggestions as you find them. As you can see there’s a lot more activity in some fields than others.

1. Transparency blogs & newspapers – At the technically simplest, but most manual labour-intensive end of the scale is sites, commercial and volunteer driven, whose owners use transparency to help them to write stories. Given almost every political blog does this a bit, it can be hard to name specific examples, but I will note that Heather Brooke is the UK’s pre-eminent FOI-toting journalist/blogger, and we’ve just opened a blog for our awesome volunteers on WhatDoTheyKnow to show their FOI skills to an as-yet unsuspecting public.

2. What Politicians do in their parliaments – These sites primarily include lists of politicians, and information about their primary activities in their assemblies, such as voting or speaking. This encompasses mySociety’s TheyWorkForYou.com, Rob McKinnon’s one man labour of love TheyWorkForYou.co.nz, Italy’s uber-deep OpenPolis.it (6 layers of government, anyone?), Germany’s almost-un-typable Abgeordnetenwatch,  Romania’s writ-wielding IPP.ro, Josh Tauberer’sGovTrack.us, plus the bonny bouncing babies OpenAustralia and Kildare Street (Ireland). Of special note here are Mzalendo (Kenya) who unlike everyone else, can’t reply on access to a parliamentary website to scrape raw data from, and Julian Todd’s UNDemocracy (International), that has to fight incredible technical barriers to get the information out.

3. Databases of questions and answers posed to politicians – These sites let people post politicians questions, and the publish the questions and answers. The Germans running Abgeordnetenwatch (Parliament Watch) seem to have had considerable success here, with newspapers citing what politicians say on their site. Yoosk has some politicians in the UK on it, too.

4. Money in politics – This comes in two forms, money given to candidates (MAPlight), and money bunged by politicians to their favourite causes (Earmark watch). In the UK, as far as I know, the Electoral Commission’s database remains currently unscraped, perhaps because the data is so ungranular.

5. Government spending – where the big money goes. In the US the dominant site is FedSpending.org, and in the UK we have ukpublicspending.co.uk.

6. Websites containing bills going through parliament, or the law as voted on – This includes the increasingly substantial OpenCongress in the US which saw major traffic during the Health Care debates, and the UK government’s own Acts database and  Statute Law Database. Much of the legal database field, however, remains essentially private.

7. Services that create transparency as a side effect of delivering services – Our own sites lead the way here: FixMyStreet‘s public problem reports and WhatDoTheyKnow’s FOI archive are both created by people who aren’t primarily using the site to enrich it – they’re using it to get some other service.

8. Election websites – These come in many forms, but what they have in common is their desire to shed light on the positions and histories of candidates, whether incumbents or new comers. The biggest beast here is Stemwijzer (Netherlands), probably in relative terms the most used transparency or democracy site ever. However these sites are popular in several places,  the big but highly labour intensive VoteSmart (US), Smartvote.ch (Switzerland), plus others.  mySociety is shortly to start to recruit constituency volunteers to help with our take on this problem, keep an eye on this blog if you want to know more.

9. Political document archives - This is a new category, now occupied by Sunlight’s Partytime archive for invitation to political events, and TheStraightChoice, Julian Todd and Richard Pope’s wonderful new initiative for archiving election leaflets and other paper propoganda.

10. Bulk data - Online transparency pioneer Carl Malamud doesn’t do sites, he does data. Big globs zipped up and made publicly available for coders and researchers to download and process. The US government has now stepped into this field itself with Data.gov, doubtless soon to be followed by data.gov.uk.

——

Please don’t shoot me if I’ve missed anything here, the world is a big place. But I thought that was a useful and interesting exercise, and I hope you’ll both find it useful, and help me improve it too. Comment away.

Earlier this week someone browsing mySociety’s freedom of information website WhatDoTheyKnow.com contacted us reporting they couldn’t open a PDF document Southampton University had sent in reply to a request asking about the amount of printer credit purchased at the institution. The user suspected the file might be corrupt.

We investigated and determined the attachment is in fact in a fancy PDF format which cannot be read by many PDF readers. Those applications which are able to open the document present a cover page inviting the reader to agree to an “intellectual property rights notice”. The terms of the notice forbid “use” of the “material” without “the written permission of the university”. The intent appears to be to ensure only those agreeing to the terms are given access to the document’s content.

The Freedom of Information Act requires authorities to release information whether or not the person making the request wants to enter into an agreement with respect to its use; so one could argue the university are not properly discharging their responsibilities. In any case their stance is silly because anyone who wants to can request their own copy of the information. All they’re doing is creating more work for themselves.

What were they thinking?
An article John Ozimek of The Register has written in response to the correspondence reports the university explaining their actions by saying:

The Freedom of Information Act gives applicants the right to have information held by public authorities communicated to them, not to documents. Applicants are entitled to use that information so long as they do not breach the intellectual property rights of the public authority: taking the information and using it in a document of their own is acceptable, making use of a document which contains not only the information requested but copyright material is not.

One problem with this was pointedly highlighted by a comment on the Register article saying: Ask yourself, “how do I prove my facts if I can’t publish the evidence?”

WhatDoTheyKnow routinely publishes information released under FOI despite a wide variety of copyright and other legal notices and disclaimers suggesting we shouldn’t. (Read the policy on copyright.) This has been the first relatively elaborate technological attempt to circumvent WhatDoTheyKnow’s efforts to make the responses to FOI requests easily accessible to everyone.

Actions
WhatDoTheyKnow’s staff, volunteers, and users have responded to the university’s actions in a number of ways:

• Those making requests to the university are now warned what it is up to, and are made aware that section 11 of the freedom of information act allows them to specify the format in which they would like to receive their response.
• The original requestors have asked for the information to be released in a more accessible format. (One is citing the disability discrimination act).
• The text of the responses, along with more accessible PDF versions have been placed on WhatDoTheyKnow.
• FOI requests have been made asking the university about advice and discussions relating to the way responses are marked to warn requestors of the university’s rights under copyright and intellectual property law as well as for details of the software used to create the protected files along with the policy decisions made to use it.

They’ve got form
This is not the first time the freedom of information team at Southampton University have been inventive in their use of PDFs; back in May they responded to a request via a password protected PDF version of a compliments slip which they attached to an email.

In an earlier post, I compared one of mySociety’s sites to another with very similar functionality which had been commissioned by a group of councils, and concluded that mySociety were living up to their aim of “showing the public sector how to use the internet most efficiently to improve lives”.

This week, Paul Clark MP (Gillingham, also Minister for Transport) announced, on Twitter no less, that he was working on “[his] version of FixMyStreet”, and requested feedback about the site.

There are numerous things here to be applauded, not least that an MP is using several new media channels to engage in conversation with his constituents. However, the same question as before comes to mind – is this site going to do anything new, or anything better, than the mySociety site that it replicates?

Perhaps it will target a wider range of reports than FixMyStreet; perhaps users will feel more comfortable using the familiar Google Maps, if that’s what the developers plump for; time will tell.

For what it’s worth, I can’t escape the feeling that a prominent link to FixMyStreet – like the one to the left – would fulfill the needs of both the provider and the users of PaulClarkMP.co.uk, and would take a tiny fraction of the time to implement, but I look forward to being proved wrong.

Still, at least Mr Clark cites FixMyStreet as the example he’s trying to emulate, rather than Medway Council’s own website. Here’s their form for reporting graffiti. Brace yourself, it’s not pretty.

Here is a diagram of how the backend of Mapumental works. Take it in the spirit that Chris Lightfoot set when he made a similar diagram for the No. 10 petitions site – although many such diagrams are useless, hopefully this one contains useful information.

If you haven’t seen Mapumental yet, first take a look at the video, and sign up for the private beta.

(Click on the diagram for a large version)

Below, I’ve explained what the main components are, and some interesting things about them.

Everything can, at least in theory, run on lots of servers. Currently we are only actually using one server for web requests, because of problems with HAProxy. We’re runnning isodaemons on two different servers.

Basic web application – it started out as raw Python, but the more Matthew hacks on it the more Django libraries he pulls in. Soon it’ll be indistinguishable from a Django app. When someone enters a new postcode, it adds it to the work queue in the PostgreSQL database, then refreshes waiting for the job to be finished. Then it displays the flash application (made by Stamen), set up to load the appropriate tile layers.

Tile server and cache – This uses the Python-based TileCache, calling Geospatial Data Abstraction Library (GDAL) to help render the tiles from points. It was originally written by Stamen, and expanded by mySociety. GDAL isn’t perfect, it doesn’t have fancy enough algorithms for my liking. e.g. Using a median rather than a weighted mean.

Isodaemons – These are controlled by a Python script, but the bulk of the code is custom written in C++. Slightly crazily, this can find the quickest route by public transport for each of 300,000 journeys from every station in the UK to a particular station, arriving at a particular time, in 10 to 30 seconds.

I had no idea how to do this, but luckily I live in Cambridge, UK. It’s a city fit to bursting with computer scientists. Many of the jobs are dull, and need little computing, never mind science – like writing interface layers for SQL server. So if you have a real interesting problem it’s easy to get help!

The universal advice was to use Dijkstra’s algorithm, which needed a bit of adaptation to work efficiently over space-time, rather than just space. Normally it is used for planning routes round a map, but public transport isn’t like that, you have to arrive in time for each particular train, so time affects what journeys you can take.

I originally wrote it in Python, which was not only too slow, but used up far far too much RAM. It could never have loaded the whole dataset in. However, the old Python code is still run by the test script, to double check the C++ code against. It is also still used to make the binary timetable files, see below.

Travel times, 1 binary file / postcode – I briefly attempted to insert 300,000 rows into PostgreSQL for each postcode looked up, but it was obvious it wasn’t going to scale. Going back to basics, it now just saves the time taken to travel to each station in a simple binary file – two bytes for each station, 600k in total. The tile server then does random access lookups into that file, as it renders each tile. It only needs to look up the values for the stations it knows are on/near the tile.

There’s various other bits:

• cron jobs for sending out invites
• converting timetable data from ATCO-CIF to the binary format
• loading static layer data into the database
• precaching every tile for static datasets
• Squid and Apache and FastCGI both sit in front of the web applications
• for speed, we cache the mapping background tiles from Cloudmade
• when zoomed out, there is code to cull which stations are used to draw tiles
• of course, a bunch of test code

Thanks to everyone who helped make Mapumental, we couldn’t have done it without lots of clever people.

I realise the above is a sketchy overview, so please ask questions in the comments, and I’ll do my best to answer them.

A number of people report dog fouling through FixMyStreet, using slightly more… colloquial language. A number of councils have strict obscenity filters, blocking anything containing swearing. As I’m a pragmatist and not that interested in campaigning against councils blocking legitimate emails from their citizens (feel free!), FixMyStreet simply changes any “dog shit” reference to “dog poo”. This works well for everyone.

Recently, the infamous Intellectual Property Manager from Portakabin™ Limited got in touch to complain about a couple of reports on FixMyStreet containing the words “portacabin” or “portaloo”. Again, as a pragmatist, I’m not really interested in whether users using trade marks or trade mark variants in a generic way on a problem report actually constitutes trade mark infringment (actually, I’d guess not), I just want legal people to go away and not waste our precious resources. So from now on, any report containing portakabin or similar will become [portable cabin], and portaloo will become [portable loo].

For anyone who’s interested, this is accomplished through a simple regular expression, that looks for porta followed by 0 or more spaces, then cabin, kabin, or loo, and sticks “ble” in the middle.