Tag Archives: Data journalism

Developers and journalists forging common ground

Back in April 2009 I listened as a group of bloggers at the G20 protests in London sent in reports using the new Audioboo iPhone application. The rules of the game are clearly changing fast, I thought.

The application allows users to record and upload high-quality sound files in an instant. In the same way that a photo of a plane floating in the Hudson river circumvented traditional channels and made its way around the world online, journalists (including Guardian staff) and bloggers on the ground were able to instantly upload reports on the unfolding activity with the immediacy and colour of front-line reports. I happened to be home ill that day and listened to the action with fascination. Then a contact from ABC News in the States contacted me via Twitter asking me if I knew any of the reporting bloggers and to pass on the direct number of the ABC newsroom. It was quick, energised and direct, and I was immediately hooked.

On the surface, the domain of the journalist and the developer seem poles apart. Journalists trace and shape stories, uncover information, and on a good day bring hidden truths to light. Developers build tools, marshal data and on a good day make the impossible possible. But a convergence is taking place that will ultimately rewrite the rulebook for both camps. Journalists have long been sifting and filtering forbidding mountains of data, looking for a story in the noise. Now they are going further, familiarising themselves with the tools to cohere and present this data, adapting to remain relevant in the new digital space. Developers in turn are doing far more than pushing data around. With rich social media tools and networks available to all, they are starting to report, telling stories with code and changing the way people in the online world relate, work and communicate. It’s a vast social experiment taking place in the production environment of the real world.

Back in March of this year, a small group of developers and journalists met in a pub in Islington to explore this overlap between coding and journalism in an intensely pragmatic fashion – the former teaching the latter the rudiments of web programming over a few beers. Ruby In The Pub was born.

A few days before, I overheard an online conversation between Joanna Geary of the Times and self-proclaimed ‘relapsed blogger’ James Ball. They were discussing the possibility of starting a regular event to get developers and journalists together. They touted Ruby as a possible language and with a speed typical of events incubated in social media circles the venue was sourced and the date decided.

As a Ruby developer (with the penchant for the odd beer) I immediately decided to attend and offer whatever support I could. The first event was warm and freestyle in nature, and the second drew a significantly larger group to the Shooting Star in Spitalfields, including the lead developer of the New York Times. One whole side of the pub was taken over by laptops and energised conversation. Due to the spotty wifi, I hardly managed any teaching at all, but became engaged in a wider discussion around journalism, the digital arena, and the changing media landscape.

Like that difficult third album, the next meet-up will probably define the future of this freestyle session. Ideas will gain traction, people will gravitate to familiar faces or pick up on projects that have been discussed. Karen Barber of Audioboo will be in attendance and has already taken up my offer of help on a project she has been kicking around for a while. We’ll get a drink, sit down, and start building it, responding to feedback from newbies and experienced hackers as we do so. Along the way, the communication channels between both sides will be strengthened and clarified and, what with all the activity on Twitter around the event, feelers of energy will spread out and spark up satellite meetings.

In fact, this has already happened. Paul Bradshaw, a journalist who teaches the MA in Online Journalism at Birmingham University, has already activated the wonderfully-named Ruby Tuesday up North and hopefully we’ll see a lot more. In a series of regular posts I will attempt to cover the process as it unfolds, as well as looking at the wider interface between word and code.

There’s no end to this journey, it’s a vibrant buzz of collaboration and exploration. Why not join us?

Working with coders to maximise readership

Bringing coders and journalists together is one of the big issues in newsrooms today, causing many journalists to think about how much coding knowledge they should invest in.

The problem is that coding is an enormous subject that many of us simply don’t have time for. It requires thousands of hours of hard work and dedication. For this reason having coders work alongside journalists in the newsroom will always be the best solution: having experts next you in the office is the most effective way of learning on the go.

Last January I attended Journalism.co.uk’s news:rewired event where one discussion generated particular interest amongst attendees. Cynthia O’Murchu from the FT described how they used developers to create infographics on a piece entitled ‘Oil and Gas Executives: Are they worth it?’.

Taking complex data like this and turning it into easily understood visual information, otherwise known as data mashing, is the practice for which today’s journalist will most likely be required to delve into design and coding. So as well as the ability to write and communicate, journalists are going to have to acquire a certain flair for design and some practical technical understanding, even if we don’t turn into full blown coders ourselves. So where is a good place to start?

3i = Immersive, Interactive, Intuitive

These are three words we hear a lot working in technology journalism: immersive, interactive and intuitive. They represent areas in which journalists will do well to excel, especially given the imminent arrival of the iPad and other tablet computers. Touchscreen computing creates a childlike desire to delve into a webpage and explore information like never before, and it will be the publishers producing the right kind of content that will have the heavy traffic.

The general election has been great for this kind of rich content. For the first time we’ve all been able to interact with that famous swingometer on the BBC’s website, while live blogging appeared to be firing on all cylinders during the hung parliament negotiations.

Working with designers and coders to create these apps is great if you have the budget, but obviously we don’t all work for the Guardian or the BBC. So getting some basic understanding of how to go about doing these things is going to be a good career move for many journalists.

From a design perspective, Adobe Fireworks is a great image and graphics software programme. It is perfect for beginners looking to start creating their own basic infographics. Similar to Photoshop, but smaller and more instinctive, it is useful for creating web optimised visual data in both vector and bitmap formats.

Have a look at this infographic from the Guardian on MPs expenses for an idea of what you can aspire to.

Code breaking

Stepping up to the next level and actually developing your own web applications gives you a problem experienced by every newbie developer starting out today: which languages do you learn first?

The good news in that most web development languages today share similarities, so tackle one and you’re going to find the next one much easier. It’s a bit like learning European languages; the more you understand the easier it becomes to make relevant connections.

HTML and CSS are your basic starting points, giving you colours and structure. If you want things to start sliding across the screen and getting interactive then J-Query and PHP (the web’s top scripting language) are the next ones to move onto.

As for getting your content on mobile phones, that is a whole other ball game.

John Hillman is the editor of PC Site which reviews and compares laptops and software. Follow him on Twitter: @JohnjHillman. Read his first post for the Journalism.co.uk editors’ blog at this link.

Poynter Online: How to get data from websites ‘without programming skills’

It’s not enough to copy those numbers into a story; what differentiates reporters from consumers is our ability to analyse data and spot trends. To make data easier to access, reorganise and sort, those figures must be pulled into a spreadsheet or database. The mechanism to do this is called web scraping, and it’s been a part of computer science and information systems work for years.

It often takes a lot of time and effort to produce programs that extract the information, so this is a specialty. But what if there was a tool that didn’t require programming?

Michelle Minkoff offers a simple guide for journalists who want to learn how to scrape data from websites, but don’t know how to start, using OutWit Hub – an extension for the Firefox browser.

Full post at this link…

Yesterday Journalism.co.uk attended a Digital Editors Network meeting to discuss data for journalism and journalists – more to follow on Journalism.co.uk

#dendatameet: Digital editors meet to discuss data and journalism

Journalism.co.uk is at the Digital Editors Network’s spring meet-up today discussing how news publishers can access useful sources of data and make the most of them
Here’s the line-up:

  • Martin Belam, the information architect in the Guardian’s web development team;
  • Paul Bradshaw, author of the Online Journalism Blog;
  • Jueditorially and commercially.
    lian Tait, an organiser of the FutureEverything conference who’s working to make Manchester the UK’s first OpenData City;
  • ProPublica reporter Olga Pierce and news application developer Jeff Larson will discuss the process of building layered data stories at the Pulitzer Prize-winning investigative news site.

The event is sponsored by Northwest Vision & Media and the School of Journalism, Media & Communication at the University of Central Lancashire and full details are at this link, but you can follow tweeted updates in the liveblog below:

Currybet.net: Journalists need to think like programmers

Following on from the recent ‘do journalists need to code’ debate on this blog and elsewhere, Martin Belam argues the answer is both yes and no.

[J]ournalists don’t all need to be able to write program, but the ability to think like a programmer is an invaluable skill.

For example, being able to spot the difference between a small technical change that has a big impact on story-telling, and what appears to be a small change but which has a hugely expensive technical impact, is an essential skill for someone setting the requirements for changes to a website or a CMS.

Full post at this link…

#ge2010: Times experiments with news and polls tracker

As part of its election coverage the Times attempted to chart the relationship between the news agenda, represented by Times reports and articles, and the political parties’ perfomances in the polls.

It looks like this:

And works like this:

Each bubble in the above graph is a news story. Its size reflects the number of comments it received on our site, and its position (on the y axis) indicates the number of recommendations the story received. (The basic idea here is that, the higher and larger the bubble, the more ‘important’ the news story, assuming that larger, more important stories tend to get commented on and recommended more.) Colours show to which party a story relates. The lines show (depending on the tab) either Populus polling results, or the number of seats the parties were predicted to win during the campaign based on Ladbrokes odds, which are used elsewhere on the site.

Online Journalism Blog: Visualising data – tools and publishing

The fourth part of a series of drafts for Paul Bradshaw’s forthcoming book on data journalism looks at tools for visualising data and how to publish those visualisations. A great round-up of the tools available, how best to use them and what type of datasets they work with.

Full post at this link…

Editor&Publisher: New AP regional investigative teams will boost CAR and data journalism

The Associated Press (AP) is creating four regional investigative teams to support its staff across the US with “reporting and presentation resources”, in particular by using journalists with expertise in computer-assisted reporting (CAR), Flash interactives and access to public records.

Now, any reporter in a region who has an idea for a story that requires high-level data analysis will have a partner. If an editor has an idea for a project that lends itself to an interactive map or another data-driven multimedia project, they can work with the team. When a big, breaking story happens anywhere in the country, we’ll tap the region’s I-team [the name given to the newly created teams] to begin digging into public records and inspection reports while the story is still developing, not days after the fact.

Full story at this link…

MediaShift: Why news organisations should use ‘linked data’

Director of the Media Standards Trust Martin Moore gives 10 reasons why news organisations should use “linked data” – “a way of publishing information so that it can easily – and automatically -be linked to other, similar data on the web”.

[Moore’s recommendations follow the News Linked Data Summit and you can read more about the event at this link.]

It’s worth reading the list in full, but some of the top reasons include:

  • Linked data can boost search engine optimisation;
  • It helps you and other people build services around your content;
  • It helps journalists with their work:

As a news organisation publishes more of its news content in linked data, it can start providing its journalists with more helpful information to inform the articles they’re writing. Existing linked data can also provide suggestions as to what else to link to.

Full post at this link…