1. How academics are using Wikidata to look for links between legislative behaviour and the biographies of Members of Congress

    Earlier this year, we were fortunate enough to be contacted by Brian Keegan, Assistant Professor in Information Science at the University of Colorado Boulder, who specialises in the field of network analysis.

    Brian and his team were planning to mine the official biographies of every legislator published by the Library of Congress – going back to the first Congress in 1789 –  and add the information as structured data to Wikidata. Having heard of our involvement with  WikiProject Every Politician, they wanted to understand more about contributing.

    The research team, which included professors from the Libraries, Political Science and Information Science departments, planned to combine this biographical data with more common data in political science about voting and co-sponsorship, so that interesting questions could be asked, such as “Do Ivy League graduates form cliques?” or “Are medical doctors more likely to break with their party on votes concerning public health?”. Their hypothesis was that the biographical backgrounds of legislators could play an important role in legislative behaviours.

    However, the first big step before questions could be asked (or SPARQL queries made) was supporting undergraduate students to enter biographical data for every member of Congress (going right back to the first) on Wikidata. This has not generally made it into the datasets that political scientists use to study legislative behaviour, and as students began to enter data about these historical figures, it quickly became apparent why: non-existent nations, renamed cities, and archaic professions all needed to be resolved and mapped to Wikidata’s contemporary names and standardised formats.

    Nine months on, the team and ten undergraduates have revised over 1,500 Wikidata items about members of Congress, from the 104th to the 115th Congresses (1995-2018) and the 80th– 81st Congresses (1947-1951), which is 15% of the way through all members dating back to the first Congress in 1789!

    They started running SPARQL queries this summer.

    Joe Zamadics, a political science PhD student who worked on the project explained the potential of combining these data:  “One example we tried was looking at House member ideology by occupation. The graph below shows the ideology of three occupations: athletes, farmers, and teachers (in all, roughly 130 members). The x-axis shows common ideology (liberal to conservative) and the y-axis shows member’s ideology on non-left/right issues such as civil rights and foreign policy.  The graph shows that teachers split the ideological divide while farmers and athletes are more likely to be conservative.”

     

    The team are keen to highlight the potential that semantic web technology such as  Wikidata offers to social scientists.

    For the full Q + A with Brian and Joe see the mySociety Medium post. 

    Photo by Jomar on Unsplash

     

  2. Open data on elected Politicians and the power of community

    You may remember that thanks to a grant from the Wikimedia Foundation, mySociety has been working to support increasingly authoritative data on the world’s politicians, to exist on Wikidata as a key part of developing the concept of the Democratic Commons.

    And, this summer mySociety welcomed two members of staff to support with the community work around both Wikidata and the Democratic Commons. In May, I (Georgie) joined in the role of ‘Democratic Commons Community Liaison’ and in late June I was joined by Kelly, mySociety’s first ever ‘Wikimedia Community Liaison’… and it’s about time you started to hear more from us!

    I’ve been climbing the learning curve: exploring the potential moving parts of a global political data infrastructure,  finding out how the communities of Wikidata and Wikipedia operate, attempting to take meaningful notes at our daily meetings for the tool the team developed to improve political data on Wikidata and making sense of the complexity in creating interface tools to interpret the political data already in Wikidata. Oh, and supporting a “side-project” with Open Knowledge International to try and find every electoral boundary in the world (can you help?).  

    And if you are in any of the relevant open Slack channels (what is Slack?), you may have seen my name on the general introduction pages, as I have been shuffling around the online community centres of the world — off Wikidata Talk that is — trying to find  the people interested in, or with a need for, consistently and simply formatted data on politicians, but who aren’t already part of the Wikidata community.

    That’s because, the issue the Democratic Commons seeks to address is the time-consuming business of finding and maintaining data on politicians, work that we suspect is duplicated by multiple organisations in each country (often all of them having a similar aim), that is slowing down delivering the stuff that matters. This has certainly been mySociety’s experience when sharing our tools internationally.

    And the solution we propose  — the Democratic Commons — is that if people and communities worked together to find and maintain this data, it would be better for everyone…  ah the paradox of simplicity.

    Update on efforts to support the Democratic Commons concept

    With each interaction and conversation that we’ve had about the Democratic Commons with partners, we’ve continued to learn about the best role for us to play. Here are some initial actions and thoughts that are shaping the work; please feel free to comment, or even better,  get involved  🙂

    Making sure the concept is a good fit through user research
    We have set a goal to carry out user research on the concept of the Democratic Commons. So far, we have lined up calls with campaign staff  (who are interested in using and supporting open political data through their UK campaigning work) and journalists in Nigeria (who have expressed a need for the data) and I am lining up more calls — if you have a need for or can contribute political data, let’s talk.

    Bringing the Open Data/Civic Tech and Wiki communities together?
    From my experience to date, the Civic Tech and Wiki communities appear to operate quite separately (I am very open to being proved wrong on this point!).

    I am just getting started within the Wikidata/ Wikimedia communities (that’s more for Kelly) but on the Open Data/ Civic tech side,  there are questions about data vandalism and the potential to trust the data from Wikidata, arguments on the benefit of using Wikidata (especially where you already have a lot of useful data) and on whether there is a need to invest time in learning SPARQL, the query language that allows faster retrieval and manipulation of data from databases.

    Misconceptions are not unusual in communities online or offline, but it is a gap that our work focus, communications and tools hope to help close. If you have ideas on blogs, video tutorials or articles to share to read around these concepts, please get in touch.

    Working openly in existing global communities (off Wiki)
    We are aware that, off-Wiki mySociety is leading the work to develop the Democratic Commons, however, we know that we need to be delivering this work in the open for it to be owned by other people outside of mySociety, and finding the right homes to talk about it (off Wiki) has been important.  In order to work openly, we have a shared #DemocraticCommons Slack channel with mySociety and Code for All; see ‘Get involved’ below to find out how to join the conversation.

    We also plan to document the learning involved in the process through blog posts and documentation, to be uploaded publicly.

    And, supporting local communities to develop, where possible
    A global network such as Code for All is very useful in supporting a concept like the Democratic Commons, however, the bulk of need for the data will likely be country-specific. Together with our partners and collaborators, we are exploring what is needed and how to support local communities:

    • Through the remainder of our Wikimedia Foundation Grant, we are supporting community events and editathons: in Lebanon with SMEX, in France with newly formed organisation F0rk, and in Spain with Wikimedia España.
    • Some groups we are working with, such as Code for Pakistan, plan to set up a channel on their Slack instance and use their Whatsapp community to discuss the data use and maintenance.  
    • In my own country, the UK, we are talking to mySociety’s community and collaborators to understand how the Democratic Commons could benefit organisations and work in practice here. If you want to be involved in this work, please contact me.
    • We are listening to understand what support is needed with collaborators in the global South, as we’re well aware that it is a lot to ask people to work on a voluntary basis and that adequate support is needed. I hope we can share the learning and use it to shape any future projects that may emerge.

     

    How to get involved in the Democratic Commons?

    • Contribute to the Wikidata community: If you are Wikidata user, or keen to learn,  visit the Wikidata project page on political data. If you need guidance on tasks, do feel free to add to the Talk page to ask the community, or get in touch with Kelly, our Wikimedia Community Liaison: kelly@mysociety.org.
    • Join the conversation on Code for All Slack:  If you would like to join the Slack conversation, join here: https://codeforall.org/ (scroll down and find the ‘Chat with us’ button).
    • Look for electoral boundary data: We are working with Open Knowledge to find electoral boundary data for the whole world. See more about that here.
    • Keep up to date and subscribe to our Medium blog: Sometimes these Democratic Commons posts are a bit too in-depth for the general mySociety readership, so for those who are really interested, we plan to share all we are learning here.
    • Share the concept with contacts: Please share the message on your platforms and encourage potential users to take part in research and get involved. We recognise that our view  — and reach — can only be anglo-centric, and we’d so appreciate any translations you might be able to contribute.
    • Tell us (and others) how you think you would use the data: This can’t just be about collecting data; it’s about it being used in a way that benefits us all. How would the Democratic Commons help your community? We would love people to share any ideas, data visualisations, or theories, ideally in an open medium such as blog posts.  Please connect with Georgie to share.
    • Something missing from this list? Tell us! We’re @mySociety on Twitter or you can email georgie@mysociety.org or kelly@mysociety.org .

    Image: Toa Heftiba

  3. A data refresh for Collideoscope

    As Zarino explained in his recent blog post, we’ve recently spent time talking to road safety advocates and cycling groups, as we prepare for some big improvements to Collideoscope.

    This has resulted in a shortlist of the tickets we’ll be working on, which you’re welcome to browse (and comment on, though this requires a GitHub account).

    Collideoscope, like many mySociety projects, is a website of two halves. On the one hand, it invites those involved in a cycling collision or near miss to contribute information to a database; on the other, it provides an output of all that aggregated data for planners, researchers, campaigners and anyone else who will find it useful.

    We’ll shortly be making some changes to the site so that its purpose and functionality are crystal clear; but in the meanwhile the next important step was to import the most recent batch of STATS19 data.

    STATS19 is the form the police fill in when road accidents are reported, lending its name to the dataset released annually by the Department of Transport. We include this data on Collideoscope alongside our users’ reports: we just take the reports which refer to cycling incidents, and with this latest update we’re now displaying everything from 2013 up to 2016, the most recent data available.

    That means, when you browse the site, you can see at a glance how many incidents have occurred in a specific area, not just from our users but from the primary national accident database too. Just click the checkbox (‘show reports from the Department of Transport’) at the top of the page to include them on the map.

    So that’s our most recent bit of housekeeping; now watch this space for some bigger changes to Collideoscope.

    Image: Charisse Kenion

  4. Help us find the world’s electoral boundaries

    We, and Open Knowledge International, are looking for the digital files that hold electoral boundaries, for every country in the world — and you can help.

    Yeah, we know — never let it be said we don’t know how to party.

    But seriously, there’s a very good reason for this request. When people make online tools to help citizens contact their local politicians, they need to be able to match users to the right representatives.

    So head on over to the Every Boundary survey and see how you can help — or read on for a bit more detail.

    Data for tools that empower citizens

    If you’ve used mySociety’s sites TheyWorkForYou — or any of the other parliamentary monitoring sites we’ve helped others to run around the world — you’ll have seen this matching in action. Electoral boundary data is also integral in campaigning and political accountability,  from Surfers against Sewage’s ‘Plastic Free Parliament’ campaign, to Call your Rep in the US.

    These sites all work on the precept that while people may not know the names of all their representatives at every level — well, do you? — people do tend to know their own postcode or equivalent. Since postcodes fall within boundaries, once both those pieces of information are known, it’s simple to present the user with their correct constituency or representative.

    So the boundaries of electoral districts are an essential piece of the data needed for such online tools.  As part of mySociety’s commitment to the Democratic Commons project, we’d like to be able to provide a single place where anyone planning to run a politician-contacting site can find these boundary files easily.

    And here’s why we need you

    Electoral boundaries are the lines that demarcate where constituencies begin and end. In the old days, they’d have been painstakingly plotted on a paper map, possibly accessible to the common citizen only by appointment.

    These days, they tend to be available as digital files, available via the web. Big step forward, right?

    But, as with every other type of political data, the story is not quite so simple.

    There’s a great variety of organisations responsible for maintaining electoral boundary files across different countries, and as a result, there’s little standardisation in where and how they are published.

    How you can help

    We need the boundary files for 231 countries (or as we more accurately — but less intuitively — refer to them, ‘places’), and for each place we need the boundaries for constituencies at national, regional and city levels. So there’s plenty to collect.

    As we so often realise when running this sort of project, it’s far easier for many people to find a few files each than it would be for our small team to try to track them all down. And that, of course, is where you come in.

    Whether you’ve got knowledge of your own country’s boundary files and where to find them online, or you’re willing to spend a bit of time searching around, we’d be so grateful for your help.

    Fortunately, there’s a tool we can use to help collect these files — and we didn’t even have to make it ourselves! The Open Data Survey, first created by Open Knowledge International to assess and display just how much governmental information around the world is freely available as open data, has gone on to aid many projects as they collect data for their own campaigns and research.

    Now we’ve used this same tool to provide a place where you can let us know where to find that electoral boundary data we need.

    Where to begin

    Start here  — and please feel free to get in touch if anything isn’t quite clear, or you have any general questions. You might want to check the FAQs first though!

    Thanks for your help — it will go on to improve citizen empowerment and politician accountability throughout the world. And that is not something everyone can say they’ve done.

    Image credit: Sam Poullain

  5. Using mySociety data to explore the representation of women

    A key part of mySociety’s research agenda is understanding how Civic Technology is (or isn’t) helping under-represented groups in society access government services and their representation. In 2015 we released a report  Who Benefits from Civic Technology, that explored variations in usage of Civic Tech in various countries and demographics. You can read or download it here.

    In this blog post I’m going to talk a bit about how we’ve internally tried to apply our data to understanding the under-representation of women in politics and as users of our services, as well as some interesting things that external researchers have found using our data.

    EveryPolitician

    Our EveryPolitician dataset contains information on current (and in some cases historical) politicians for a large number of countries around the world. For a large number of representatives, this includes gender information.

    However, a key problem of international comparisons of the representation of women is, as Miki Caul points out, that it “overlooks the fact that individual parties vary greatly in the proportion of women MPs within each nation”. Similarly, Lena Wängnerud argues “cross-country studies tend to miss variations between parties within a single system. Variations in the proportion of women to men are even greater across parties than across nations”.

    Fortunately, this is exactly the kind of problem that an international dataset like EveryPolitician is well placed to examine – on Thursday we’ll be using a new mini-site to explore the gender and party information contained in EveryPolitician to give a sense of the international picture and the party-level differences within each country. Stay tuned! Or you can download the data yourself (there are APIs for Python, Ruby and R) and try and beat us to it.

    TheyWorkForYou

    TheyWorkForYou makes it easy to search through the history of what has been said in Parliament, and we make the data (based on the Hansard dataset but more consistently formatted) freely available to download. As essentially a download of a very large amount of text, getting insights from this dataset is a bit more complicated, but potentially very rewarding.

    Jack Blumenau has a paper based on TheyWorkForYou data using language to analyse whether appointing female ministers changes how other female MPs participate in debates. Looking at “half a million Commons’ speeches between 1997 and 2017, [he demonstrates] that appointing a female minster increases the participation of women MPs in relevant debates by approximately one third over the level of female participation under male ministers” – and that “female MPs also became more influential in debates under the purview of female ministers […] female ministers respond in a systematically different fashion to the speeches of female MPs.” In this case, influence is a measure of whether the language an individual used is then taken up by others, and this kind of analysis shows how the TheyWorkForYou dataset can be used to demonstrate not just counts of how many women were in Parliament, but the substantive effects of women holding office on the political process.

    As Myf talked about yesterday, TheyWorkForYou’s Commons content now extends back to 1918, and so includes every speech by a female MP ever made. We hope this is a useful resource for anyone interested in exploring the history of the representation of women in the UK and have plans for a small project in the upcoming months to show in a simple way how this data can be used (please sign up to our mailing list if you’re interested in hearing about this when it’s completed).

    TheyWorkForYou data can either be accessed through an API, or downloaded as formatted XML files.

    FixMyStreet and WriteToThem

    Understanding the under-representation of women is important across our services. Where men and women are experiencing different issues and concerns, imbalances in access (or use of access) potentially lead to differences in resource allocation.

    The majority of reports on FixMyStreet.com are reported by men – but to make things more complicated, it’s not just that women make fewer reports, but women report substantively different kinds of reports.

    Reka Solymosi, Kate Bowers and Taku Fujiyama investigated FixMyStreet reports and found (by determining gender from names of problem reporters) that different kinds of reports are more likely to be reported by men and women – they suggest that at “first glance it appears that men are more likely to report in categories related to driving (potholes and road problems), whereas women report more in categories related to walking (parks, dead animals, dog fouling, litter)”.

    If different kinds of reports are differently gendered, this complicates thinking about how to improve how women use the website – as potential users are having substantially different experiences of problems in the real world well before they interact with the site. We have to engage with the nuance of this kind of finding to understand how to redress issues of access to services.

    We’re currently in the process of extending this kind of analysis to our other service. For WriteToThem, we’ve learned that while the majority of people using the service to write to MPs are male (around 60%), this picture is different depending on the level of government – for instance the gender balance for people writing to councils is pretty close to 50/50.

    As part of this, we’re investigating whether having the same gender as their representative makes people more likely to make contact. This has some interesting preliminary findings, and we hope to have more to say about this towards the end of the year.

    Our research in this area is ongoing, and we’re keen to help people use our data to investigate under-representation – especially where you have expertise or knowledge that we don’t. If you’d like to discuss potential uses of the data please get in touch, or sign up to our mailing list to hear about future research releases.

    Image: Theresa May’s first PMQs: © UK Parliament/Jessica Taylor (CC by-nc/2.0)

  6. Celebrating National Democracy Week

    Excuse us while we just finish hanging this bunting…

    Yes, wave the flags and toot those vuvuzelas: it’s National Democracy Week, a new initiative to celebrate the democratic process and encourage democratic participation.

    And thanks to some extra-curricular work by one of the mySociety team, we’re now able to celebrate it in a quite exceptional way. Longstanding  developer Matthew has used his own free time to import historic House of Commons debates from 1919-1935 into our parliamentary site TheyWorkForYou. With this work, he’s extended the site’s value as an easy-access archive of parliamentary activity even further.

    You can check it out now by visiting TheyWorkForYou, searching for any word or phrase, and then sorting the search results by ‘oldest’. Or, pick any MP active during 1919-1935 and search for them to see every speech they made in Parliament.

    Please let us know if you find anything of interest! For developers who use TheyWorkForYou data to power their own sites and apps, the extended content will also be available via TheyWorkForYou’s API.

    “No one sex can govern alone” – Nancy Astor

    This is the first National Democracy Week, and it has taken, as its theme, the anniversary of women’s suffrage: as you’re sure to have heard by now, 2018 is the centenary of (some) women getting the vote* in the UK.

    We wanted to celebrate by highlighting some of the big milestones of women’s participation in Parliament, but there was just one problem.  TheyWorkForYou only contained House of Commons debates as far back as the 1930s — while, for example, the maiden speech of Nancy Astor, the first woman to speak in Parliament, was in 1920.

    So it’s a big deal that Matthew’s imported this early data into TheyWorkForYou, and we’re all the more grateful because he did so on his own time. It’s something we’ve wanted to do, but not had the resource for. You can now browse, search or link to Commons debates right back to 1919, and find not just women’s contributions, but a whole wealth of historic parliamentary content. Result!

    What you can enjoy this week

    We’re going to take this opportunity to highlight, through a week-long series of posts:

    • Tomorrow, our researcher Alex will be highlighting some of the ways people have used our data and APIs to explore issues of gender and representation and describe some of our future plans in this area. This also gives us the opportunity to point out where you can access all our lovely, juicy data, should you want to do something similar yourself.
    • Finally, as a weekend bonus, we’ll be blogging on the various organisations which support women within our own sphere of Civic Tech.

    We’ll add the links in for each day’s content as it goes live.

    Since our sites TheyWorkForYou and WriteToThem in the UK, our activities with the Democratic Commons, and the support we give to partners in other countries are all, at heart, aiming to make democratic participation easier, we are, of course, all over this event. We hope you’ll enjoy the week!


    *We can have another celebration in 2028 for the remaining women.

  7. mySociety Data Portal

    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!


    Image: Ash Edmonds (Unsplash)

  8. New insights for councils, on FixMyStreet

    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.

  9. TheyWorkForYou and leaves of absence: it’s all about priorities

     

    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.

    You can see just how long we’ve had this issue open, and that it has had some thought, in our development ticket here (related tickets are also here and here).

    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

  10. GLOWing the extra mile

    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.

    Five of the countries (Croatia, Greece, ItalySlovenia 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.

    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.

    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.

     

     

    Photo by Margo Brodowicz on Unsplash