mySociety services produce a lot of useful (and interesting!) data. Over the years we’ve often made components or the results of mySociety services available through APIs (like our MapIt service) or as open data to download (such as our EveryPolitician data).
What we haven’t been good at is showing you the full breadth of what we have available, or how component parts can be used together. Sometimes we find users of one aspect of mySociety data being unaware of other relevant datasets.
To fix this problem, we’ve created a new data portal – data.mysociety.org – to bring all the data we publish into one place. From the politicians of Albania to data about all ministerial and parliamentary roles UK MPs have held, everything can be found on one site.
Our research team will also use this site to publish supplementary materials to papers and blog posts that might be of use to others (such as a lookup table for the different codes used for UK Local Authorities). So we plan to keep adding data whenever we can!
FixMyStreet sends users’ street reports to councils across the UK.
But if you’re one of the staff that receives these reports, you might sometimes wish for more insights: which issues are most commonly reported in your area? What’s a bigger problem, dog fouling or potholes? How quickly do reports get fixed, and how does this compare with other councils’ performance?
To make it easy to discover the answers to all these questions, we’ve just rolled out a new stats dashboard on FixMyStreet — and it’s free to access if you work for a council.
Council staff can now view and download information that answers questions such as:
- How many FixMyStreet reports have been made in your area across various time periods?
- How many reports have been made in each category?
- What are the average times between reports being made and being marked as fixed, and how does this compare to other councils?
- Which categories of report are most common within your area?
- Which categories of report does FixMyStreet send to your council, and which email addresses does it use?
From this exclusive area, you can gain a more in-depth understanding of how FixMyStreet is being used in your area, while also getting a taste of the fuller functionality available with FixMyStreet Pro.
So, if you work for a council, head over to the dashboard page now, and start exploring.
@TheyWorkForYou – @EmmaReynoldsmp is saying that you refused to note that she was on maternity leave next to her voting record? Is that true? Is that something that is under active discussion? it seems to penalise female MPs as it stands https://t.co/7FfPFLY2EP
— Simon Burall (@sburall) February 1, 2018
TheyWorkForYou refusing to note that an MP was on maternity leave? Wait, that doesn’t sound like us…
TheyWorkForYou has one main aim: to make it extremely easy to see what’s going on in Parliament. To that end, we publish debates, voting records, and all sorts of details about MPs such as their job titles, expenses, and even which words they use most often.
Sometimes, interpreting all of these facts needs a little context. Case in point: when an MP is off on extended sickness or maternity leave, the number of speeches and votes they make will, of course, go down. There are many little exceptions like this, in fact: for example, my own MP was, for a while, a teller, meaning that he counted votes and was not normally allowed to vote himself. As you’d expect, this had quite an effect on his voting tally.
Now, the trouble with these exceptions is that they’re not easy to code. Most of TheyWorkForYou’s data actually comes from Parliament itself: they provide all the day’s debates, for example, as XML code, which our automated scripts pick up and publish out in the nice, readable format you see each morning on TheyWorkForYou. That’s how we’re able to publish such a large quantity of content on so many MPs: if TheyWorkForYou was compiled editorially, it’d require a far larger staff than we have.
So in fact, when Emma Reynolds got in touch to ask that we note her maternity leave on TheyWorkForYou, we didn’t refuse. Rather, we told her the truth: that it was a tricky issue that would require a manual bit of coding, but we’d add it to our development list and hopefully get to it.
And that’s what we did. The trouble is, our development list is long, and we’re constantly having to make decisions about what to prioritise. This ticket is now a few years old (Ms Reynolds was not the first to ask for a note on her record to explain special circumstances) and it hasn’t yet risen to the top of the list above bug fixes and other more urgent additions. TheyWorkForYou is currently unfunded, so of course, projects which have funding and expectations/deadlines attached to that funding take priority.
Note: In retrospect, we recognise that the advice below is not strictly relevant to this post. While we do very much need funding, and also do very much encourage anyone with coding skills to come and help out with our backlog, these two solutions would not alleviate the main obstacle to the issue above, which is that the required data isn’t output by Parliament. So, feel free to read on if you like, but with that in mind. mySociety CEO Mark Cridge put out a series on tweets on Friday which clarify our thinking; you can see those here.
Until we’re able to prioritise this piece of work (or any other that our users/MPs would like to see), there are a couple of solutions.
Ask for Parliament to add such information to their output
As mentioned above, most of TheyWorkForYou’s content is automated, so if there were a data source to show that an MP was on a leave of absence, we could easily pick it up and include it on their page. We’ve asked an MP’s office about this but they replied:
We are not aware of any official source of information about an MP taking leave of absence.
From our point of view, this would be far preferable to a manual solution, which would rely on MPs getting in touch themselves to let us know when exceptions applied. This would almost certainly lead to a situation where some did, and some didn’t, meaning the information could look more accurate than it really was. Many researchers use our outputs, so we wouldn’t want this to become the foundation of a study on MPs’ leaves of absence!
Be the change you want to see
OK, that’s a bit of a hippy-esque maxim, but in this case it’s quite apt.
A small job like this would not take very long or cost very much — the reason we haven’t yet managed it isn’t because it’s a massive piece of work, but because there are so many other pressing tasks.
An MP (or anyone) who wanted to see a new feature could help by making a donation. If you specify that it is for a particular addition to the site, we’ll get back to you to discuss how viable that is, and how we can make it happen.
Or do it yourself! Like most mySociety projects, TheyWorkForYou runs on Open Source code. That means that, if you have development skills, you are very welcome to fork the code and make a pull request for whatever improvements or additions you like. We’ll gratefully merge in any that fit with the site (have a chat with us first to make sure everyone’s on the same page).
If you’re not a developer (say, for example, you’re an MP), you could even contract one to do this for you.
We hope that’s cleared things up a bit. We’re not out to demonise MPs who take maternity leave, honest. And we’ve lodged an official request for a correction from the Times.
Image: Erik Lundqvist
As you’ll remember from our previous blogpost, the Global Legislative Openness Week — AKA GLOW — provided us with a great opportunity to support events and spread the word about our ambitious Wikidata project with groups around the world.
In the end we sponsored nine events (in Slovenia, Sweden, Croatia, Bulgaria, Italy, Greece, Spain, Wales and, amazingly, Nepal) and sent representatives to support seven of them in person. This meant that Tony, the lead for the EveryPolitican project, had an interesting 10 days getting the most out of budget airlines and managing to attend six of the events. He would have liked to have made it seven but EasyJet don’t go to Nepal! Also special thanks to Lucas who represented the project in Greece and Bulgaria taking a little of the pressure from Tony.
— OBC Transeuropa (@BalkansCaucasus) November 27, 2017
Five of the countries (Croatia, Greece, Italy, Slovenia and Spain) moved from very little or no coverage of political data in Wikidata to our two-star (or better) indicator — this is a (very) rough guide to how good the data is in a country; we are tracking what information already exists for the primary house of a national legislature which you can learn more about on our Wikidata project page. Wales was already a ‘three-star’ country and the others are coming along nicely.
— Open Knowledge NP (@okfn_np) December 1, 2017
We couldn’t be happier with the response and contributions made to the Democratic Commons by the participants — and we’re extremely keen to do more events early next year, collaborating with Wikimedia communities to make this happen. If that sounds interesting take a look at our original blogpost about the events and get in touch if it seems up your street.
Ahora @tmtm nos introduce al wikiproyecto @everypolitician, toda la info aquí >> https://t.co/8w1EhNNd9Q ¡En esta sesión vamos a añadir los primeros datos españoles! @mySociety @medialabprado pic.twitter.com/NyKX3AVmLG
— Wikimedia España (@wikimedia_es) November 29, 2017
All in all these events really felt like a culmination of all the learnings and activities undertaken in the project so far. The strides we have taken in understanding the best way to model this kind of data in Wikidata and the tools that have been built are what made it possible to make such a big impact in each of the countries in just a day or two. Not all of these lessons were easy to learn but they are really starting to pay dividends now.
We really want to keep this momentum up and build even more relationships with Wikimedia communities who are interested in contributing to the Democratic Commons in their countries so I can’t reiterate it enough – please do get in touch if you would like to get involved.
One more thing
If you’ve read this with great interest to the very end, then you are just the sort of person who we’re looking for! We currently have a vacancy for a Political Researcher to help us kickstart this kind of work in up to 100 countries, supporting our ambitions in the Democratic Commons project. See the job description here.
Earlier this month, Mark laid out the concept of a Democratic Commons for the Civic Tech community: shared code, data and resources where anyone can contribute, and anyone can benefit.
He also talked about exploring new models for funding the kind of work that we do in our Democracy practice at mySociety.
For many years, our Better Cities work has been proof of concept for one such model: we provide data and software as a service (FixMyStreet, MapIt, Mapumental) to paid clients, the revenue from which then funds our charitable projects. Could a similar system work to sustain our Democracy practice?
That’s the hope, and with Facebook who we first worked with during the UK General Election in June, providing the data that helped people see and connect with their elected representatives, we’ve already seen it in action.
This kind of project is positive on multiple levels: it brings us an income, it brings the benefits of democratic engagement to a wider audience than we could reach on our own, and it contributes data back into EveryPolitician and Wikidata, that everyone can use.
The UK election was only the first for which we did this work: we’ve gone on to provide the same service for the French elections and more recently for the rather more eventful Kenyan ones — currently on hold as we await the re-run of the Presidential election next month. And now we’re doing the same for the German elections, where candidate data is being shared this week.
As we’re learning, this is definitely not one-size-fits-all work, and each country has brought its own interesting challenges. We’re learning as we go along — for example, one significant (and perhaps obvious) factor is how much easier it is to work with partners in-country who have a better understanding of the sometimes complex political system and candidates than we can ever hope to pick up. Much as we might enjoy the process, there’s little point in our spending days knee-deep in research, when those who live in-country can find lists of candidates far more quickly, and explain individual levels of government and electoral processes far better.
Then, electoral boundaries are not always easy to find. We’ve used OpenStreetMap where possible, but that still leaves some gaps, especially at the more granular levels where the data is mainly owned and licensed by the government. It’s been an exercise in finding different sources and putting them all together to create boundary data to the level required.
Indeed, that seems to be a general pattern, also replicated across candidate data: at the national level, it’s easy to find and in the public domain. The deeper you go, the less those two descriptors hold true. It was also at this point that we realised how much, here in the UK, we take for granted things like the fact that the spelling of representatives’ names is usually consistent across a variety of sources — not always a given elsewhere, and currently something that only a human can resolve!
What makes all the challenges more worthwhile, though, is that we know it’s not just a one-off push that only benefits a single project. Nor is the data going straight into Facebook, never to be seen again.
Much of what we’re collecting, from consistent name data to deep-level boundaries data, is to be made available to all under open use licenses. For example, where possible we can submit the boundaries back to OpenStreetMap, helping to improve it at a local granular level across whole countries.
The politician data, meanwhile, will go into Wikidata and EveryPolitician so that anyone can use it for their own apps, websites, or research.
There are also important considerations about how this type of data will be used and where and when it is released in the electoral process; finding commercial models for our Democracy work is arguably a more delicate exercise than on some of our other projects. But hopefully it’s now clear exactly how a project like this can both sustain us as a charity, and have wider benefits for everyone — the holy grail for an organisation like us.
At the moment it’s unclear how many such opportunities exist or if this is a one-off. We’re certainly looking for more avenues to extend the scope of this work and keen to hear more ideas on this approach.
Your contributions help us keep projects like EveryPolitician up and running, for the benefit of all.Donate now
mySociety was built on its Democracy practice, a pioneer in providing simple- to-use tools that demystify the democratic process, allow citizens to understand how decisions are being made on their behalf and ensure that their voices are heard by elected representatives.
We’ve been on a long journey, from the early days of FaxYourMP which eventually became WriteToThem, to our pivotal TheyWorkForYou service which has both stretched the ambitions of Parliament in the UK and led us to develop similar services in Kenya, South Africa and beyond.
Amidst all of this has been our ongoing push to better standardise and make accessible more Open Data on politicians around the world; initially through our Poplus and Pombola projects, but more recently – and with more success – through our EveryPolitician service which has blossomed into a remarkable dataset of almost 4 million datapoints on over 72,000 politicians in 233 countries and territories.
Despite these successes I don’t think we’ve yet sufficiently cracked the challenge at scale of enabling more organisations to monitor and report upon the work of more politicians in more countries. We need to do something about that.
One of the principles that has always underpinned mySociety is that we carry our work out in the open, freely available for others to use. But, as is common with many Open Source projects, we do most of the development work ourselves internally. While community contributions are very welcome, practicality has dictated that more often than not, these are more commonly directed to raising tickets rather than making changes to the actual code.
Unchecked, this situation could lead to us being too internally focused; on developing everything ourselves rather than recognising where we can achieve our objectives by supporting other projects.
Fortunately our collaboration with Wikidata, announced earlier this year, suggests what promises to be a clear way forward to scaling up the impact of our work: we recognised that EveryPolitician could only become sustainable at scale as part of a wider community effort if we want our data to be used more widely.
By contributing to what we’ll call the Democratic Commons — a concept of shared code, data and resources where anyone can contribute, and anyone can benefit — we can help build and strengthen core infrastructure, tools and data that allow other democracy organisations and campaigners to hold their own governments to account.
This was notably put into practice for the snap General Election in the UK in June, where rather than build something new ourselves we directly supported the work of Democracy Club in their efforts to source candidate data and ensured that our existing services like MapIt, TheyWorkForYou and WhatDoTheyKnow were easily accessible for other campaigning and democracy organisations to put into use.
More recently we’ve established a commercial partnership with Facebook to provide them with accurate and independent lists of candidates and elected representatives matched to their relevant Facebook profile pages for the UK, French and Kenyan elections.
There’s a wider benefit to this kind of commercial work, beyond its being a useful source of additional revenue for mySociety. More importantly, it will allow us to feed the data that we source back into the Democratic Commons. It can contribute to EveryPolitician and Wikidata, and even improve boundary data internationally through OpenStreetMap, which in turn powers our own Global MapIt service.
Why is this important now?
Well, it’s not just the rather obvious observation that working with other people is a good idea. The reality is that we need to face the fact that our Democratic practice is just not fully funded, and, as with WhatDoTheyKnow.com, at best we’ll need to consider how more of our services in the UK can be run and directly supported by volunteers and the wider community.
At worst it’s quite possible that we’ll be forced to close some of our popular UK services and restrict the further development of our democracy work internationally.
In April next year we come to the end of our six-year grant agreement with the Omidyar Network who have given us tremendous support over that time. This will leave a substantial hole in our core funding and it’s one reason why we’ve been so diligently focused on developing appropriate new commercial services like FixMyStreetPro and WhatDoTheyKnowPro.
Without sufficient unrestricted core funding — that is, funding which can be applied wherever in the organisation it is most needed — we need to rely much more on specific project funding wherever we can find it. In most cases, however, this project funding comes with its own set of tasks to deliver, and there’s a tendency to want new shiny things, rather than supporting the maintenance of our existing projects. This is especially true of our Democracy work which relies more heavily on grant funding than commercial alternatives.
Sensibly directing our own work more towards contributions to external projects is also a hedge, should we need to find new homes for our services or shutter them for the time being.
In the meantime we’ll be speaking to more funders who we hope might recognise the importance of supporting and building the essential infrastructure of the Democratic Commons, but in the event that isn’t forthcoming we’ll do what it takes to ensure our work to date continues to have some value and impact.
As we start to map out a path to a sustainable future for mySociety and its community, I’d appreciate all thoughts on where we go next with this — after all, we can’t do this without your help.
Millions of people reached for their phone on June 9, and checked Facebook for the result of the UK General Election.
Now, you may or may not be one of those people yourself, but there’s no disputing that many of us turn to social media as our primary source for big news. Through the night, Facebook was a place where we could express feelings about the results as they came in, share news stories and ask questions: it gives us a rounded view of an event like an election, quite unlike any you’ll receive from traditional media.
And the morning after, those logging in to Facebook may have seen something like this — an invitation to follow your newly-elected or re-elected MP and other elected representatives, from local councillors to MEPs:
We’re glad to say that mySociety has been working alongside Facebook to help make this happen.
Reaching people where they are
mySociety has a mission to make democracy more accessible for everyone, and via our websites TheyWorkForYou and WriteToThem, we serve and inform more than 400,000 UK citizens per month.
That figure has, as we’d expect, spiked in the last few weeks as people rush to check their MPs’ track records, all the better to cast an informed vote; but all the same, we’re well aware that 400,000 users is only a small proportion of the country’s electorate.
What’s more, our research has consistently shown that our services don’t adequately reach the people that need them most: our typical user is male, reasonably affluent, well-educated, older and white — I mean, we’re glad to be there for everyone, but generally speaking this is a demographic that can inform itself quite readily without any extra help.
That’s not a problem Facebook has, though, with their 32 million UK users. 75% of them log in on a daily basis, and almost half are under the age of 30*.
That’s why we were so keen to join forces with the Facebook Civic Engagement team, to help this large online audience see who their representatives are today.
Facebook for engagement
You may not have been aware that Facebook has a dedicated political engagement team — unless you came to TICTeC this year, of course, in which case you’d have seen a walkthrough of the extensive research that’s gone into their election offerings globally — but if you use Facebook at all, and if you’re in a country that has recently had an election, you’ve probably seen some of their work.
Over the last few weeks in the UK, people on Facebook were alerted to each stage of the electoral process. They were invited to check who their candidates were and what they stood for; offered a reminder to vote and provided information on where and how to do so; and finally, encouraged to share the fact that they had voted, tapping into the proven peer encouragement effect.
mySociety behind the scenes
Thanks to our experience running TheyWorkForYou and WriteToThem, plus the support we receive from Commercial Evaluations and their Locator Online service and our involvement with Democracy Club’s WhoCanIVoteFor.co.uk, we have access to accurate and up-to-date data on candidates and representatives at every level, from local councillors up to MEPs, and including MPs — all linked to the relevant constituencies.
In all, this totaled around 23,000 people. What we needed to discover was how many of them were on Facebook — and could we accurately link our records to their Facebook pages?
Working together with Facebook, we built an admin tool that displayed likely pages to our team, on the basis of names, locations and the really giveaway information, such as ‘Councillor’, ‘MP’ or the constituency name in the page title. Some representatives didn’t have individual pages, but ran a party page; those counted too (and of course, a fair proportion of representatives have no Facebook presence at all).
While our tool filtered the results reasonably well, it was still necessary to make a manual check of every record to ensure that we were linking to the correct representative, and not, say, someone who happened to have the same name and live in the same town. We needed to link, of course, only to ‘official’ pages; not representatives’ personal pages full of all those things we use Facebook for on a day-to-day basis. Those holiday snaps, Candy Crush results and cat memes won’t help constituents much: what we were looking for was the kind of page where constituents could message their reps, find out about surgery times, and get the latest news from their constituency.
Now of course, until the results came in, no-one knew precisely which candidates would be MPs! So a small crack team of mySociety people worked through Thursday night to do the final matching. It was a very long night, but we hope that the result will be an awful lot more people following their representatives, and so quite effortlessly becoming more politically engaged, thanks to a platform which they already visit on a regular basis.
Last you heard from from the EveryPolitician team we were talking about integrating EveryPolitician more deeply with Wikidata.
Here’s a quick update on what to expect in the coming months and a note on how you can get involved – we are going to need a lot of help!
Before we can make headway on a deeper integration, there are some pretty foundational pieces of the puzzle we need to put in place.
Some key data is missing, and you may be surprised to discover that it is pretty basic stuff. Take a look at this for example:
This is from a report we have generated to highlight gaps in the links between items. Notice how not even all of the offices have been filled in on the country page, let alone who occupies those offices?
This is the type of foundational data we are hoping to get in place over the next little while, and you can help…
How you can get involved
Over the coming weeks we’re going to be conducting a few experiments in public and trying to get data into Wikidata. We’ll need as much help as we can get!
The experiments will focus on using Wikidata to attempt to answer some questions we find interesting and see how we can expose gaps and inconsistencies in the data. In doing this, we’ll be pointing to specific reports we have generated and asking you to help us fill in the gaps.
Our first question will be:
“What is the gender breakdown of heads of government across the world?”
We’ll be blogging about the investigation over on Medium. The first post is already there:
Keen to dive straight in? Help us fill in the blanks you see in this report! If you are familiar with Wikidata, you will probably be able to get started straight away, but there are also tips and pointers in the Medium post if you want a bit more guidance.
You can get notified of the challenges to complete the data as soon as they are published by following the EveryPolitician bot on Twitter.
Want even more details on our plans?
We should also mention that we’ve updated our proposal to the Wikimedia Foundation to make a couple of things clearer about the problem we are trying to solve and our proposed solution (the proposal is still being reviewed). If you are interested in the nitty-gritty, that’s the best place to get the full overview of what we are planning.
This week, we heard from a user whose MP’s agent had threatened to take him to court if he shared an image, showing TheyWorkForYou data, on social media. Here’s what we think of that.
Available to all
Prior to an election, you’ll see all sorts of messaging trying to turn you towards, or against, specific candidates — some from political parties, some from independent campaigning groups, and some just from individuals who feel strongly.
At mySociety, we’re non-partisan: we strive for neutrality in our websites and services, and they are available to everyone, no matter which part of the political spectrum you are on. We won’t tell you how to vote; we will, however, present the facts and give you the tools that allow you to make up your own mind.
When we looked into the image our user had wanted to share, we found that there are many similar images, generated from a single source, using TheyWorkForYou voting data to highlight the voting records of Conservative MPs in marginal seats. Here’s what they look like:
And for political balance, here’s an image with a similar intent, highlighting a Labour MP’s voting record (but not from this election, sorry: we have been unable to find anything more up to date, but feel free to send us any you’ve seen and we’ll add them to this post):
We have no problem with our data being shared in this way, so long as the wording is unchanged, and the source is credited (as clearly it hasn’t been in our latter example). Adding the source benefits everyone, because while top-line statements like these are, of necessity, brief in a shareable image, they are backed up on TheyWorkForYou with links to the actual votes that substantiate them.
As we say, this data is available to anyone, and TheyWorkForYou covers every MP, so there’s no unfair political advantage being gained here. The votes are statements of fact; and indeed there may well be people looking at a list like that and finding that, actually, they quite agree with everything on the list, in which case the image would be having the opposite effect from that intended.
If you read our blog post from yesterday, you’ll know that we’ve recently introduced Facebook and Twitter share buttons to make it super-easy to share any MP’s votes. So, in short: share our stuff. That’s part of what it’s for.
And yet, the user we mentioned had been told by someone working on behalf of the MP’s campaign that he would be ‘taken to court’ if he shared such an image, as it was ‘based on unreliable data’.
All of our voting analyses are based on the official data put out by Parliament, and we do our utmost to ensure that they are fair: while much of TheyWorkForYou’s content is published out via automated processes, we recognise that voting data is too subtle and sensitive to manage in any way other than manually. That’s why all our voting information is painstakingly compiled by hand, in a process we’ve described previously in this post.
MPs do occasionally contact us to question the wording of certain voting topics, and we are always happy to explain how we arrived at them, and improve them if we agree that the votes have been misrepresented.
We would be quite happy to hear directly from the MP in question and to discuss any information which they perceive as inaccurate: we note that their voting page has been in place on TheyWorkForYou since August 2015 (it has been viewed by over 5,500 people, 67 of them from within the Houses of Parliament) and in that time we have not been contacted with any query.
TheyWorkForYou makes politics accessible for everyone. Your donations help us.Donate now
In order to make debates and votes a bit easier to find, understand and share, we’ve recently introduced some new features on TheyWorkForYou.
What am I looking for?
Our users frequently write to us to say that they can’t find a specific vote on TheyWorkForYou — and that’s often because descriptions of votes in the media, or in conversation, don’t reflect the way they are referred to in Parliament.
The official record, for example, will not bring you a vote titled ‘Snooper’s Charter’, ‘Bedroom Tax’ or ‘Brexit’: you’ll have to know enough to search for the ‘Investigatory Powers Bill’, ‘Social Tenants Deemed to Have Excess Bedrooms’, or ‘Exiting the European Union’.
So we’ve put in place a few different ways to find the content that matters to you.
99% of the time when people ask us where to find a particular vote, it’s something that happened in the last few days, or at most, weeks.
So now, you’ll see a new ‘Recent Votes‘ tab in the main TheyWorkForYou menu, which leads to a page listing the last 30 votes:
If you’ve entered your postcode on the homepage (or your browser cookies remember you from previous visits), you’ll also see your own MP’s stance under each vote, like this:
There’s one important point about this page: it only contains those votes for which we currently have policy lines — that is to say, the votes we include on MPs’ pages. That’s because they are the ones for which we already have a plain English description. Fortunately, these are almost always the ones that people are most interested in.
If you want to find a vote that isn’t on this page, you can always look on Public Whip, which is where the raw voting data that feeds TheyWorkForYou comes from.
If you click through from any of those listings, you’ll get a page dedicated to that particular vote.
Here you’ll see something that we know is important to many of our users, set out nice and clearly: the ‘division’, ie which MPs voted for and against, who was absent and who abstained.
Again, if you’ve entered your postcode on the site, you’ll also see how your own MP voted, in the top section of the page:
But even better, if what you’re most interested in is your own MP’s position in a specific vote, you’ll get this version of the page when you click through from their voting record — as clear as we can make it:
So that’s all fine and dandy for people who think in terms of MPs and votes. But for a long time, we’ve wanted to explore ways to make parliamentary content more welcoming for complete political newbies.
We’ve been meeting with groups of young people around the UK to find out more about how they access politics, and one finding is that they think in terms of issues. Politics comes through the lens of topics like ‘the NHS’, ‘the environment’ or ‘Brexit’.
For that reason, we’ve created topic pages like this one, which gather together a lot of relevant and immediate content, showing how your MP voted, how all relevant votes went, debates and a chance to sign up for email alerts:
We’ll be adding more of these as time goes on.
Easier to share
The final feature we’ve introduced was a direct result of observing the way that you, our users, share our content on Facebook and Twitter.
We started collecting examples of where people had made a screenshot of voter records in order to make a political point, and we soon saw that this was a very common thing to do, especially at key points like the current run-up to the General Election, or a party leadership campaign.
To save you the bother of making and saving a screenshot, we’ve now added these share buttons at the foot of each section of votes on MPs’ pages:
That’s it for now, but this is all part of a rolling program of improvements, so do feel free to feed back with any related features you’d like to see.