1. Hello Academics of the world, we would like to work with you!

    We at mySociety build and popularise digital tools worldwide that help citizens exert power over institutions and decision-makers. Or do we?

    Wanting to know whether our well-meaning civic tech is actually making a difference, mySociety recently created the post of Head of Research. My name is Dr Rebecca Rumbul, and I have now been installed in that role for about 6 weeks. I want to know if civic tech like ours is having an impact on citizens and governments, and how such sites operate and negotiate issues not just in the UK, but in the 50 or so countries that we know have digital democracy websites operating in them.

    Into the unkown

    There is enormous scope for interesting and important research to be conducted using sites such as the ones that mySociety and our partners operate. The digital nature of our focus means that we can collect large volumes of data online at a low cost.

    That said, there is nothing quite like making connections on the ground or meeting people face to face. mySociety is a small NGO, and does not have the capacity to conduct all of the research activities it would like on its own.

    Therefore, we are actively seeking to work with academic partners on both qualitative and quantitative research focusing on the impact of civic tech.

    We are planning to conduct research in the following countries. If you are an academic based in one of these countries and interested in our research agenda, please get in touch. We will be very happy to hear from you. Contact me via research@mysociety.org

    Countries:

    • Argentina
    • Chile
    • Hungary
    • Kenya
    • Malaysia
    • Mexico
    • Norway
    • South Africa
    • Ukraine
    • Uruguay

    We conduct and disseminate research regularly. If you would like to hear more about our activities and events, sign up for our newsletter.

    Image credit: Into the Unknown by Gary Gao (angrytoast), CC BY-NC 2.0

  2. Parliament without Scottish MPs: how would it have looked different since 1997?

     

    An analysis, with code and data, of which Commons votes would have had different results, if Scottish MPs’ votes hadn’t been counted since 1997.

    By Richard Taylor and Anna Powell-Smith.

    Humble address in the House of CommonsPublicWhip is a wonderful thing. Founded and still run by independent volunteers, it contains the results of every House of Commons vote since 1997, scraped from the official web pages and presented as simple structured data. Here at mySociety, we’ve used it to power TheyWorkForYou for many years.

    Most recently, it helped our staffer Richard create the new voting analyses on TheyWorkForYou’s MP pages. Want a quick, simple summary of your MP’s voting history on same-sex marriage or climate change, or on any of 62 other major issues? You’ll now find the answer on your MP’s TheyWorkForYou page, all based on PublicWhip data.

    But here’s the most exciting thing about PublicWhip. If you know how to get around its slightly forbidding exterior, it contains a treasure-trove of data on MPs’ voting patterns, all structured, openly-licensed and ready for anyone to analyse.

    A data challenge

    Recently, while discussing the upcoming Scottish referendum, Richard posed a question to Anna: could PublicWhip data tell us which House of Commons votes would have had different results, if Scottish MPs’ votes hadn’t been counted?

    This is interesting because if the Scottish people vote “yes” to independence on September 18th, we may see (probably not as soon as 2015, but perhaps soon thereafter) a House of Commons without Scottish MPs. No-one really knows how such a Parliament would be different.

    While it was widely reported that that Scottish MPs’ votes carried the decision to introduce student tuition fees and foundation hospitals in England, those were just two high-profile votes. To our knowledge, no-one has published a comprehensive analysis of all votes that were carried by the Scottish MPs.

    The results

    Anna chose to accept Richard’s challenge, and to use PublicWhip data to carry out this analysis. You can see all their code, and the data they produced, on GitHub.

    The headline finding is that only 21 votes (out of nearly 5000 since 1997) would have gone differently if Scottish MP’s votes hadn’t been counted. This surprised Anna, who expected more.

    Secondly, if there’s any visible pattern, it’s that English MPs seem to have a stronger civil-libertarian bent than their Scottish counterparts. High-profile votes on 42-day detention, “glorifying terrorism”, allowing the Lord Chancellor to suspend inquests, and on control orders: according to Anna’s analysis, all would have gone differently if Scottish MPs had not been in the chamber.

    Other than that – Anna comments – the key finding is perhaps the absence of any other strong trend.

    Here is the full list of votes that would have gone differently – click on the date to see the full vote details on PublicWhip. If Scottish MPs hadn’t been in the chamber:

    2010-date

    • 5 Sep 2014 The majority of MPs would have voted to send the Affordable Homes Bill to a Select Committee rather than a Public Bill Committee.
    • 29 August 2013 The majority of MPs would have voted to agree that a strong humanitarian response to the use of chemical weapons in Syria was required from the international community, and that it may, if necessary, require military action. (You may remember that David Cameron called MPs back from their summer break to vote on this, and MPs rejected the motion.)
    • 29 Jan 2013 The majority of MPs would have voted against postponing a review of the boundaries of parliamentary constituencies until 2018 and against delaying a review of the effect of reducing the number of MPs.
    • 31 Oct 2012 The majority of MPs would have voted against calling on the UK Government to seek a real-terms cut in the European Union budget.
    • 24 Apr 2012 The majority of MPs would have voted to require products containing halal and kosher meat to be labelled as such.
    • 24 Feb 2010 The majority of MPs would have voted for restrictions on the amount of carbon dioxide electricity generation plants are permitted to emit.

    2005-2010

    • 9 Nov 2009 The majority of MPs would have voted against allowing the Lord Chancellor (a minister) to suspend an inquest and replace it with an inquiry and against allowing the use of intercepted communications evidence in inquests.
    • 8 Dec 2008 The majority of MPs would have voted to immediately starting the proceedings of a committee of MPs to investigate the House of Commons procedures in light of the seizure by the police of material belonging to Damian Green MP.
    • 12 Nov 2008 The majority of MPs would have voted to require membership of new regional select committees to be determined taking account of the proportion of members of each party representing constituencies in the relevant region and for at least one member from each of the three largest parties to be on each committee.
    • 11 Jun 2008 The majority of MPs would have voted against extending the period of police detention without making any criminal charges of terrorist suspects from 28 days to 42 days.
    • 2 Jun 2008 The majority of MPs would have voted to require the National Policy Statement to contain policies which contribute to the mitigation of, and adaptation to, climate change.
    • 15 Mar 2006 The majority of MPs would have voted against a proposed timetable for the Parliamentary consideration of the Education and Inspections Bill.
    • 2 Nov 2005 The majority of MPs would have voted against making glorifying the commission or preparation of acts of terrorism an offence.
    • 2 Nov 2005 The majority of MPs would have voted to make the offence of Encouragement of Terrorism only apply to cases where an individual intended their actions to encourage terrorism.

    2001-2005

    • 28 Feb 2005 The majority of MPs would have voted to give a greater role to the courts in relation to the imposition of control orders.
    • 22 Apr 2004 The majority of MPs would have voted against installing a security screen separating the public gallery from the House of Commons Chamber.
    • 31 Mar 2004 The majority of MPs would have voted against the introduction of variable university tuition fees (top-up fees) of up to £3,000 per year in place of the previous fixed fee of £1,250 per year.
    • 27 Jan 2004 The majority of MPs would have voted against allowing university tuition fees to increase from £1,125 per year to up to £3,000 per year, and against making other changes to higher education funding and regulation arrangements.
    • 19 Nov 2003 The majority of MPs would have voted against introducing NHS foundation trusts, bodies with a degree of financial and managerial independence from the Department of Health.
    • 4 Feb 2003 The majority of MPs would have voted for an 80% elected House of Lords.
    • 29 Oct 2002 The majority of MPs would have voted against starting sittings of the House of Commons on Tuesdays at 11.30am rather than 2.30pm.

    In the 1997-2001 Parliament, Anna’s code found no votes that would have had different results.

    IMPORTANT DISCLAIMER! We can’t conclude that all of the above would necessarily have become law if Scottish MPs had not been in the chamber. Bills don’t become law until they have passed through the House of Lords – not to mention the many other forces of history that would have acted differently.

    Get the code and the data

    You can see the code used for this analysis, and the full datasets, on GitHub. You can adapt it yourself if you want to do your own analyses.

    This analysis is the work of one volunteer: we welcome any corrections. Like PublicWhip itself, the whole point is that it is out in open for anyone to analyse and improve.

    Image by Catherine Bebbington. Parliamentary copyright image reproduced with the permission of Parliament.

  3. We’ve analysed every vote since the general election, and why that’s good news for you

    360 degree panorama by Eye of QvoxSince the 2010 election, there have been 1,085 votes in the House of Commons.

    Our team member Richard has now analysed every single one of those votes, and his findings have been added to each MP’s information on TheyWorkForYou.

    We hope that’s great news for users: it means that we can now present a really full picture of how your MP voted on key topics.

    It’s also potentially useful for developers, eDemocracy hackers and campaign groups, who can pick up our data and use it as they please.

    So what exactly is the data?

    Often MPs vote on motions which are, at first glance, rather incomprehensible and cryptic. They might vote for example on a motion to accept:

    Amendments (a) to (d) proposed in lieu of Lords amendments 1 to 4 and 6.

    We’ve done the research to determine what MPs were actually voting on in each case, and turned their archaic language into plain English.

    For every vote we’ve written a sentence to describe the effect of voting either “aye” or “no”. In relation to one MP’s vote on the evening of the 9th of July 2014 we write:

    Mark Pawsey MP, Rugby voted for a residence test as an eligibility criteria for civil legal aid; subject to exceptions for refugees and those who have sought asylum.

    In addition to describing every vote, we have decided whether it should be considered relevant to the topics we list on each MP’s page (see an example MP here, or check your own MP by inputting your postcode on the homepage, then clicking ‘voting record’ on your MP’s page).

    If a vote was relevant to one of the statements we show on TheyWorkForYou, we then determined whether voting ‘aye’ or ‘no’ was a vote for or against the statement and if the vote was very important, or less important. By clicking on the green ‘details’ button beside each statement on an MP’s voting record you can see exactly which individual votes contributed to it as well as how we calculated which wording such as “moderately for” or “strongly against” to apply in each case.

    Matters MPs have voted on since the 2010 general election have ranged from bankers’ bonuses to same sex marriage; from food banks to the “bedroom tax” (all of which have contributed to statements we show on TheyWorkForYou); from daylight saving to the regulation of hairdressers (neither included) – and plenty more. (We’ve written previously about how we select which topics to show on TheyWorkForYou.)

    Of course, Parliament continues to hold votes, and we’ll be continuing to analyse the results as they come in – but it is good to know that we are bang up to date.

    How can this data be used?

    We have plenty of ideas ourselves, and we want to hear yours, too. With the forthcoming general election, one obvious use is for ‘who should I vote for?’ tools, which match users’ opinions with those of each party.

    There’s also potential for comparisons between what constituents believe and what their elected representative has voted for.

    No doubt there are many other ideas that haven’t even occurred to us yet – please do get in touch if you have ideas and you’d like to use this data.

    Image: Eye of Qvox (cc)

     

  4. Straight answers, or slippery digressions? The art of the Written Answer – in numbers

    House of Lords Library: Parliamentary copyright images are reproduced with the permission of Parliament

    The Written Answer is a noble parliamentary tradition, dating back almost 300 years. MPs and peers use them to hold the government to account, getting facts and figures on the record.

    But wriggling out of answering them is also a recognised Parliamentary skill – and one that, while often applied with dexterity, can impede the process of democracy.

    That’s the primary reason that, beside each Written Answer on TheyWorkForYou, we poll our users on a single point:

    “Does this answer the above question?”

    Last month marked the tenth birthday of TheyWorkForYou, and over that time, this unassuming poll has amassed more than 275,000 of these yes or no responses on a total of around 130,000 written answers.

    That’s a substantial sample for us to analyse. Running that data through a few tickertape machines and putting the results in order means that we can now see just how many written answers actually address the question in hand – and which government departments are the best and worst at giving a straight answer.

    Is the current administration more slippery?

    It seems that ministers are getting worse at returning a straightforward answer.

    In the previous government: 47% of written answers that were voted on got more ‘yes’ answers than ‘no’s from our users.

    In the current administration: That figure has dropped to 45%. Even within the current term, the figure has been falling year on year, with a 49% ‘yes’ rate in 2010 comparing to a 42% rate in 2013.

    Best and worst departments for a straight answer

    Breaking down the data by department is also eye-opening – some departments are decidedly more likely to be judged as prevaricators by TheyWorkForYou’s users.

    Accolade for ‘most improved’ goes to the Wales office, who managed an 86% ‘yes’ rate in the current government, against 48% in the last. Worst of the bunch – as perceived by TheyWorkForYou’s users – is the Department of Work and Pensions, with just 31% in this administration.

    We’ve put the full rankings below, for those of you who would like to delve deeper into these figures.

    (more…)

  5. How responsive is your MP?

    Image by Barry (Ennor)

    We’ve just published the WriteToThem responsiveness league table for 2013. Check your MP’s performance here – just enter your postcode.

    League table? What’s that?

    Our website WriteToThem.com allows anyone to send a message to their elected representatives.

    If you’ve ever done this, you’ll know that two weeks later, we email you to ask whether or not your representative replied.

    The information we obtain from this questionnaire is important to us: it helps us check that WriteToThem remains an effective way to contact politicians. But, when it’s analysed further, there are interesting results to be found.

    WriteToThem launched in 2005. Until 2008, we published an annual ‘league table’, ranking MPs by responsiveness. We did this because we believe that it is a fundamental part of an MP’s duty to respond to their constituents’ messages; we wanted to recognise the best performers, and highlight the ones who were falling below expectations.

    We haven’t run this data since 2008 – mainly because we’re a very busy organisation with a wide range of priorities.

    But our users frequently ask for the latest stats, and to that end we’ve now run the 2013 data. Take a look at it here.

    A big WriteToThem gold star to some MPs

    The people of Romsey and Southampton North should rest easy. Their Conservative MP Caroline Nokes is on the case. Top of our league table, she replied to 96% of messages sent through WriteToThem.

    Other good performers include Conservatives John Glen MP for Salisbury, and Justin Tomlinson representing North Swindon. Gloria De Piero, Labour MP for Ashfield, comes in at 4th position. Check your MP’s performance here.

    And ‘could do better, see me’ to others

    Mansfield residents may feel like nobody’s listening; their representative Alan Meale (Labour) comes bottom of the rankings, having replied to a sole message in 2013.

    Other low responders were Khalid Mahmood (Labour), representing Birmingham Perry Barr; Kenneth Clarke (Conservative) for Rushcliffe; and Tom Blenkinsop (Labour) in Middlesbrough South and East Cleveland. Check your MP’s performance here.

    Not just MPs

    WriteToThem isn’t just for contacting your MP. You can also use it to write to Lords, councillors, MEPs and members of the assemblies of Wales, Scotland and Northern Ireland.

    Running this data also allows us to make broad comparisons across all of these bodies – see our figures here.

    The Welsh Assembly comes out looking fairly respectable, with a 70% response rate, while the House of Lords (who, it must be noted, do not have an obligation to respond to correspondence) slink in at 27%.

    We’ve also sliced the data so you can see which political parties perform best and worst overall. Guess who comes top?

    Data and methodology

    • Our figures are based on our follow-up questionnaire, and of course, not all users respond to it. This data is based on 58,573 responses; you can see more about the data below.
    • Letters sent via WriteToThem represent less than 1% of the entire parliamentary postbag, so this has to be taken as a sample rather than giving the full picture across the board.
    • WriteToThem is not the only way that people can contact their representatives. For all we know, those poor performers may be responding perfectly adequately to messages sent by other channels – although we do make it as simple as we can for them to reply to WriteToThem users, and it’s our belief that the channel of communication should not make any difference.

    We know, too, that some messages don’t require an answer. We would not expect to see a 100% response rate, and, by the way, we are considering altering our questionnaire so that it includes the option “I didn’t get a reply, but my message didn’t need one”.

    • It’s also important to note that this league table is not a ‘laziness’ ranking. MPs do many other things besides reply to their constituents’ letters. Poor responders may be incredibly active in their constituency, or in Westminster debates. So it’s what it says it is – a responsiveness league table, no more, no less.
    • WriteToThem sent 96,396 messages to MPs in the year 2013 and 103,965 to other elected representatives.
    • 58,573 people answered our feedback survey about communicating with their MP.

    The survey asked whether people had had a reply (not just an acknowledgement) from their representative.

    People were surveyed initially after 2 weeks, and if they didn’t answer, were surveyed again after 3 weeks.

    Because of this, and because of the way different people interpret the survey, you should interpret the figures with some caution.

    We did not include any MP who received fewer than 20 messages in 2013, as the sample numbers are too small to be indicative. See the bottom of our league table for the MPs affected: here you may also see which MPs do not accept correspondence sent via WriteToThem.

    Before preparing this table, we contacted the lowest performers to ensure that we had the right email addresses for them.

    In the cases of Caroline Flint (9 out of 63 positive responses to our survey), Stephen Dorrell (18 out of 94) and Tom Watson (4 out of 42), we were informed that while the addresses were monitored, there were better ones to use – these are now in place on WriteToThem.

    In the case of Alasdair McDonnell (10 out of 57), we were informed that we had the correct address. Jack Lopresti (4 out of 70) and Stephen Williams (53 out of 267) did not respond.

    Image credit: Barry (CC)
  6. Seeing how your MP voted – now clearer and more comprehensive

    House of Commons Chamber

    Do you know how your MP voted on the issues that matter to you?

    If not, take a look at the new Voting Record section for your MP – accessed easily via TheyWorkForYou.com. Even if you don’t know who your MP is, we’ve made it easy to find their voting activities, and to easy understand their big decisions at a glance.

    We’ve been working hard to increase the coverage of votes (we admit – they had got a bit out of date), as well as to make the experience of reading them much more pleasant. There are now so many bits of analysis we’ve actually split a separate voting page out for each MP, accessible from their main TheyWorkForYou page.

    Now you can see how your MP voted on issues like these:

    • Benefit levels – what goes up or down
    • Foreign policy – including military decisions
    • Social issues – eg gay marriage
    • Constitutional issues – for example, how many MPs there are

    Check your own MP’s voting record here – and don’t forget, if you want to discuss what you find with your MP you can use WriteToThem.com afterwards.

    Keeping things objective

    TheyWorkForYou is a trusted, non-partisan service so we work hard to ensure that these voting lines are unbiased and neutrally worded.

    We’re so keen to ensure that we don’t accidentally introduce unconscious biases, that we try to avoid entirely the business of picking which topics to analyse. Instead, we  prioritise our analysis based on what gets voted on by lots of MPs (accounting for whole party abstentions), not what gets talked about in the news, or what we care about ourselves.

    There are more details about the process in a previous blog post.

    Wording is important

    We  have decided to prioritise clarity over expressing every detailed nuance of votes – this is an intentional choice, reflecting our priority of reaching citizens who have never paid attention to their MPs before. Consequently, vote summaries need to be concise and not use jargon.

    For example, would we be wrong to use the common term ‘bedroom tax’? It’s a phrase that a lot of people would recognise from the press coverage, but the government’s preferred term is ‘removal of the spare room subsidy’.

    In the end, we went with reducing housing benefit for social tenants deemed to have excess bedrooms (which Labour describe as the “bedroom tax”) – a balance between objectivity and clarity.

    The bottom line

    We’ve made lot of changes to the display for information on MPs recently. So if you have any feedback, good or bad,  please us know what you think by leaving a comment below, or dropping us a line

    Image source. Copyright Catherine Bebbington/Parliamentary Copyright. Licence: (CC BY-NC 2.0)

  7. Learning from the Shelter Databank

    If you are interested in attending a mySociety Data Briefing for Breakfast event, drop us a line and we’ll add you to our mailing list.

    28th June: Tristan Carlyon from Shelter

    Shelter's databank

    mySociety’s Data Briefings are all about how to present complex data online, simply. Shelter’s Databank tool is one of the better solutions we’ve seen to this exact problem, so we invited Tristan Carlyon, a key player in its creation, to tell us about it.

    The Shelter Databank pulls together government data on housing issues from a number of sources, and makes it accessible online.

    Although the underlying data is all freely available in various places, it wasn’t previously easy for the casual user to find or to use. Conversely, and crucially, you don’t need to be an expert to use Databank – it has a very simple interface and it outputs the data you need, in the format you need.

     “I created my ideal resource”.

    As with so much great software, the Databank was born when Tristan identified something that would make his own job easier. But it soon became clear that there would be a wider appreciative audience.

    A quick internal assessment helped Tristan calculate that the Shelter media team were spending a total of one day a week answering queries from the press. This fact alone justified the project – it’d make a large efficiency saving.

    The benefits wouldn’t just be internal:  it was also an opportunity to drive traffic to the Shelter website and increase brand awareness for the charity.

    At a previous Breakfast, the question had arisen of how you can get buy-in from higher management for this kind of project, when it may seem not to precisely align with your organisation’s main remit.

    As it happens, the Databank tool does fit pretty solidly within Shelter’s charitable mission – one of their aims is: “to educate the public concerning the nature, causes and effects of homelessness [..] and to conduct and procure research concerning the same and to make available the useful results thereafter to the public.”

     But there are other benefits too, even if your organisation doesn’t have a similar remit. Tristan confirmed that having an effective, useful tool builds the brand, cementing it more firmly in people’s minds.

    Plus, publishing this kind of data enables Shelter to engage with many of their target and actual stakeholders – press, elected representatives at all levels, academics, grassroots campaigners, and developers.

    Looks simple… works hard

    Tristan took us through the tool’s interface: it may appear basic, but a lot of thought has gone into every element. Some of the points he pulled out were:

    •  The input form is all on one page – and if you go back to amend your search, your previous input is saved.
    • The big red ‘get data’ button is unambiguous and unmissable – and happens to be Tristan’s favourite feature of the whole tool.
    • Search queries generate a URL that incorporates the search parameters, and can be easily shared or modified.
    • Glossary tags ensure that any technical terms can be understood by the general public just as well as industry insiders.
    • The tool is free of any spin. Despite its placement on a charity website, it does not exhort you to donate. Its only aim is to present the data without comment or editorial, which helps retain its integrity.

    OK, it’s built. Now you have to run the thing.

    The Databank was built within eight weeks, alongside other development projects. Like almost any such project – and as we at mySociety see with our own data-related sites – it couldn’t just be built and then left to do its work. As its underlying external data sources are refreshed, it must also be updated, and this is rarely a job that can be automated.

    In fact, Tristan currently does the updates manually, taking about a day’s work each quarter. He reckons that it’s still well worth it. The tool still offers massive efficiency savings, for him and for many others. Hundreds of subscribers are signed up to receive an alert whenever the data is refreshed.

    Shelter’s internal systems ensure that projects are always retrospectively assessed to see whether they met the objectives in the initial project plan.

    The Databank stands up well to scrutiny, being one of Shelter’s most consistently visited pages, and continuing to save time for the whole team. Reputation, perhaps, cannot be measured, but it is not a great leap to see that a useful tool like this can only enhance the charity’s image.

    We’ll be continuing our Data for Breakfast briefings, so if you’d like to hear about the next one, please drop us a line with your name and the organisation you work for.

  8. mySociety’s Data Hackday

    Hacking in a Suite at Clarion, by Johan Nilsson

    Over 115,000 Freedom of Information requests.

    Almost 225,000 FixMyStreet reports.

    Close to 3,000 public transport problems.

    Every word spoken in Parliament since 1935.

    So, what would you like to know?

    There’s no doubt about it, mySociety sites store a lot of data. And once you have that much data, you can start finding the answers to interesting questions. Questions like:

    • Which public bodies receive the most FOI requests?
    • Which county gets the most pothole reports?
    • Which train routes are people complaining most about?
    • Which MP has spoken for the longest cumulative time in the history of Parliament?

    There are less obvious questions, too – how about:

    • Which regions of the country are most likely to include bad language when submitting a form online?
    • How many times does the Speaker have to interject, “Order, order!” in an average week?
    • Which words are most spoken in Parliament, and which have only become popular in the last five years?
    • What topics do people submit the most Freedom of Information requests about?
    • Just how often does a UK citizen get so fed up about dog poop that they take action?

    We reckon there are almost limitless stories in our data, waiting to be teased out. Some of them will be surprising, fascinating, or just plain funny. Some may even be potential front page news. So, we’ve invited journalists who have a particular interest in data, or indeed in any of the areas we work in, to come and have at it at our first ever mySociety Data Hackday.

    Not a journalist?

    Journalists aren’t the only ones with bright ideas, so if you’re reading this and there’s a burning question that springs to mind, leave a comment below. Given all these reams of data, what would you be looking for? We’ll add the best ideas to our list, and we’ll be reporting back on everything we find out.

    Actually, I am a journalist!

    There are still a few places, so if you’d like to attend, please drop us a line. Note: we will expect you to get stuck in! We will run the data, but you may be sifting through the results, looking for significant stories, and sharing your findings. Bring a laptop, and plenty of ideas.

    If you can’t attend, but really wish you could, let us know what data you’d like us to run, and we’ll add it to the list.

    ETA: Lanyrd page here.

    Image credit: Johan Nilsson

  9. FixMyStreet’s been redesigned

    FixMyStreet, our site for reporting things like potholes and broken street lights, has had something of a major redesign, kindly supported in part by Kasabi. With the help of Supercool, we have overhauled the look of the site, bringing it up to date and making the most of some lovely maps. And as with any mySociety project, we’d really appreciate your feedback on how we can make it ever more usable.

    The biggest change to the new FixMyStreet is the use of responsive design, where the web site adapts to fit within the environment in which it’s being viewed. The main difference on FixMyStreet, besides the obvious navigation changes, is that in a small screen environment, the reporting process changes to have a full screen map and confirmation step, which we thought would be preferable on small touchscreens and other mobiles. There are some technical details at the end of this post.

    Along with the design, we’ve made a number of other improvements along the way. For example, something that’s been requested for a long time, we now auto-rotate photos on upload, if we can, and we’re storing whatever is provided rather than only a shrunken version. It’s interesting that most photos include correct orientation information, but some clearly do not (e.g. the Blackberry 9800).

    We have many things we’d still like to do, as a couple of items from our github repository show. Firstly, it would be good if the FixMyStreet alert page could have something similar to what we’ve done on Barnet’s planning alerts service, providing a configurable circle for the potential alert area. We also are going to be adding faceted search to the area pages, allowing you to see only reports in a particular category, or within a certain time period.

    Regarding native phone apps – whilst the new design does hopefully work well on mobile phones, we understand that native apps are still useful for a number of reasons (not least, the fact photo upload is still not possible from a mobile web app on an iPhone). We have not had the time to update our apps, but will be doing so in the near future to bring them more in line with the redesign and hopefully improve them generally as well.

    The redesign is not the only news about FixMyStreet today

    As part of our new DIY mySociety project, we are today publishing an easy-to-read guide for people interested in using the FixMyStreet software to run versions of FixMyStreet outside of Britain. We are calling the newly upgraded, more re-usable open source code the FixMyStreet Platform.

    This is the first milestone in a major effort to upgrade the FixMyStreet Platform code to make it easier and more flexible to run in other countries. This effort started last year, and today we are formally encouraging people to join our new mailing list at the new FixMyStreet Platform homepage.

    Coming soon: a major upgrade to FixMyStreet for Councils

    As part of our redesign work, we’ve spoken to a load of different councils about what they might want or need, too. We’re now taking that knowledge, combining it with this redesign, and preparing to relaunch a substantially upgraded FixMyStreet for Councils product. If you’re interested in that, drop us a line.

    Kasabi: Our Data is now in the Datastore

    Finally, we are also now pushing details of reports entered on FixMyStreet to Kasabi’s data store as open linked data; you can find details of this dataset on their site. Let us know if it’s useful to you, or if we can do anything differently to help you.

    Technical details

    For the web developers amongst you – we have a base stylesheet for everyone, and another stylesheet that is only included if your browser width is 48em or above (an em is a unit of measurement dependent on your font size), or if you’re running Internet Explorer 6-8 (as they don’t handle the modern CSS to do this properly, we assume they’ll want the larger styles) using a conditional comment. This second stylesheet has slight differences up to 61em and above 61em. Whilst everything should continue to work without JavaScript, as FixMyStreet has done with its map-based reporting since 2007, where it is enabled this allows us to provide the full screen map you can see at large screen sizes, and the adjusted process you see at smaller resolutions.

    We originally used Modernizr.mq() in our JavaScript, but found that due to the way this works (adding content to the end of the document), this can cause issues with e.g. data() set on other elements, so we switched to detecting which CSS is being applied at the time.

    On a mobile, you can see that the site navigation is at the end of the document, with a skip to navigation link at the top. On a desktop browser, you’ll note that visually the navigation is now at the top. In both cases, the HTML is the same, with the navigation placed after the main content, so that it hopefully loads and appears first. We are using display: table-caption and caption-side: top in the desktop stylesheet in order to rearrange the content visually (as explained by Jeremy Keith), a simple yet powerful technique.

    From a performance point of view, on the front page of the site, we’re e.g. using yepnope (you can get it separately or as part of Modernizr) so that the map JavaScript is downloading in the background whilst you’re there, meaning the subsequent map page is hopefully quicker to load. I’m also adding a second tile server today – not because our current one isn’t coping, it is, but just in case something should happen to our main one – we already have redundancy in our postcode/area server MapIt and our population density service Gaze.

    If you have any technical questions about the design, please do ask in the comments and I’ll do my best to answer.

  10. Welcome, Mzalendo – Monitoring Kenya’s MPs and Parliament

    When TheyWorkForYou was built by a group of volunteer activists, many years ago, it was a first-of-a-kind website. It was novel because it imported large amounts of parliamentary data into a database-driven website, and presented it clearly and simply, and didn’t supply newspaper-style partisan editorial.

    These days dozens of such sites exist around the world. But today sees the launch of a rather-special new transparency site: Mzalendo, covering the Parliament of Kenya.

    Mzalendo (which means ‘Patriot’ in Swahili) has been around for a few years too, as a blog and MP data website founded by volunteer activists Conrad and Ory. However, over the last few months mySociety’s team members Paul, Jessica and Edmund, plus the team at Supercool Design have been helping the original volunteers to rebuild the site from the ground up. We think that what’s launched today can stake a claim to being a true ‘second generation’ parliamentary monitoring site, for a few reasons:

    • It is entirely responsively designed, so that it works on the simplest of mobile web browsers from day one.
    • All the lessons we learned from storing political data wrongly have been baked into this site (i.e we can easily cope with people changing names, parties and jobs)
    • Every organisation, position and place in the system is now a proper object in the database. So if you want to see all the politicians who went to Nairobi University, you can.
    • There is lots of clear information on how parliament functions, what MPs and committees do, and so on.
    • It synthesizes some very complex National Taxpayer’s Association data on missing or wasted money into a really clear ‘scorecard‘, turning large sums of money into numbers of teachers.

    The codebase that Mzalendo is based on is free and open source, as always. It is a complete re-write, in a different language and framework from TheyWorkForYou, and we think it represents a great starting point for other projects. Over the next year we will be talking to people interested in using the code to run such sites in their own country. If this sounds like something of interest to you, get in touch.

    Meanwhile, we wish Ory and Conrad the best of luck as the site grows, and we look forward to seeing what the first users demand.