The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

209
Data Reality Check Henk van Ess [email protected] chairman WWW.VVOJ.NL Sunday, March 25, 12

description

Data driven stories are made by people. By designers. By reporters. By coders. Or even better, by all of them together in a team. Henk van Ess did al lot of data journalism projects with people he never met in person, through Skype and Go To Meeting. He also worked together in small teams in company. What is better? To do it in-house or outsource it? And what kind of person do you need? A fine researcher? A smooth talker? A good number cruncher? A great story teller? A brilliant designer/ GUI specialist? Fantastic communicator? All? In this deadly honest presentation Henk van Ess gives you all the gory details about what will happen if things go wrong. Who was responsible and why? What can we learn?

Transcript of The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Page 1: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Data Reality CheckHenk van Ess [email protected]

chairman WWW.VVOJ.NL

Sunday, March 25, 12

Page 2: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Andrew Lehren, NYT

Age of Data by Geoff McGhee Paul Bradshaw

Digital Diggers ProjectData Driven Stories Book

http://www.vvoj.nl

This year: a new book & site about data journalism

Sunday, March 25, 12

Page 3: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 4: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Let’s cut the crap

Sunday, March 25, 12

Page 5: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Let’s cut the crap

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 6: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 7: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 8: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 9: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 10: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Showing what is possible, not what is sensible

Sunday, March 25, 12

Page 11: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Showing what is possible, not what is sensible

Sunday, March 25, 12

Page 12: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 13: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Assembly line syndrom: no place for new workflows

Sunday, March 25, 12

Page 14: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:

Sunday, March 25, 12

Page 15: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:before

Sunday, March 25, 12

Page 16: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:

List of dangerous chemical companies

before

Sunday, March 25, 12

Page 17: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:

List of dangerous chemical companies

before

Sunday, March 25, 12

Page 18: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:

List of dangerous chemical companies

before

after

Sunday, March 25, 12

Page 19: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:

Adobe Captivate

List of dangerous chemical companies

before

after

Sunday, March 25, 12

Page 20: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Do you use tools like:

Adobe Captivate

List of dangerous chemical companies

before

after

Sunday, March 25, 12

Page 21: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

There are many new dedicated tools

Sunday, March 25, 12

Page 22: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

There are many new dedicated tools

Timeline the bad way

Sunday, March 25, 12

Page 23: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

There are many new dedicated tools

Timeline the bad way Timeline with Timeline 3D

Sunday, March 25, 12

Page 24: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

There are many new dedicated tools

Timeline the bad way Timeline with Timeline 3D

Sunday, March 25, 12

Page 25: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

There are many new dedicated tools

Timeline the bad way Timeline with Timeline 3D

This was done in 30 minutes

Sunday, March 25, 12

Page 26: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 27: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 28: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Mind boggling presentations.. leaving your mind boggled

Sunday, March 25, 12

Page 29: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Sunday, March 25, 12

Page 30: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The CoderThe ReporterThe Designer

Who was in charge and what went wrong?

Showing problems, not explaining them

Sunday, March 25, 12

Page 31: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

when no one is in charge (anymore)

Sunday, March 25, 12

Page 32: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

when no one is in charge (anymore)

empty pages

Sunday, March 25, 12

Page 33: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

when no one is in charge (anymore)

empty pages

Sunday, March 25, 12

Page 34: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

when no one is in charge (anymore)

broken databases empty pages

Sunday, March 25, 12

Page 35: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

when no one is in charge (anymore)

broken databases empty pages

Sunday, March 25, 12

Page 36: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 37: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Datajournalism is

Sunday, March 25, 12

Page 38: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Finding information

Datajournalism is

Sunday, March 25, 12

Page 39: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Finding information

Processing information

Datajournalism is

Sunday, March 25, 12

Page 40: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Finding information

Processing information

Presenting information

Datajournalism is

Sunday, March 25, 12

Page 41: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Put like that, it seems the job description for any reporter

Finding information

Processing information

Presenting information

Datajournalism is

Sunday, March 25, 12

Page 42: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 43: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

Sunday, March 25, 12

Page 44: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcher

Sunday, March 25, 12

Page 45: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talker

Sunday, March 25, 12

Page 46: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncher

Sunday, March 25, 12

Page 47: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncherA great story teller

Sunday, March 25, 12

Page 48: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncherA great story tellerA brilliant designer/ GUI specialist

Sunday, March 25, 12

Page 49: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncherA great story tellerA brilliant designer/ GUI specialistFantastic communicator

Sunday, March 25, 12

Page 50: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncherA great story tellerA brilliant designer/ GUI specialistFantastic communicator

“overlapping set of competencies drawn from disparate fields” http://bit.ly/nLlbYn

Sunday, March 25, 12

Page 51: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncherA great story tellerA brilliant designer/ GUI specialistFantastic communicator

You offer:“overlapping set of competencies drawn from disparate fields” http://bit.ly/nLlbYn

Sunday, March 25, 12

Page 52: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

To be more specific, you need:

A fine researcherA smooth talkerA good number cruncherA great story tellerA brilliant designer/ GUI specialistFantastic communicator

You offer:“overlapping set of competencies drawn from disparate fields” http://bit.ly/nLlbYn

Sunday, March 25, 12

Page 53: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 54: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 55: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 56: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 57: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Your problem

Data journalism is a “baggy monster of a field”5 tips for getting started in data journalism

http://www.poynter.org/how-tos/digital-strategies/147734/5-tips-for-getting-started-in-data-journalism/

Sunday, March 25, 12

Page 58: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

We can learn from Nokia, for once :

Go for teamwork!

Sunday, March 25, 12

Page 59: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The gory details

Sunday, March 25, 12

Page 60: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 61: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The problem

Sunday, March 25, 12

Page 62: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The problem

Reporters bored with Wikileaks

Sunday, March 25, 12

Page 63: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

WHY?

Most explosive documents were already published

Sunday, March 25, 12

Page 64: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

WHY?

Finding new leads in new documents was hard

Sunday, March 25, 12

Page 65: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 66: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Colleagues told me: ‘It isn’t worth our time’

Sunday, March 25, 12

Page 67: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Me, being shocked

Sunday, March 25, 12

Page 68: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

I said:

Me, being shocked

Sunday, March 25, 12

Page 69: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

I said:

If you don’t check this, who does?????Me, being shocked

Sunday, March 25, 12

Page 70: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How we started:

Sunday, March 25, 12

Page 71: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

No inhouse coders

How we started:

Sunday, March 25, 12

Page 72: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

No inhouse codersNo designers

How we started:

Sunday, March 25, 12

Page 73: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

No inhouse codersNo designersNo funding

How we started:

Sunday, March 25, 12

Page 74: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

No inhouse codersNo designersNo fundingNo technical infrastructure

How we started:

Sunday, March 25, 12

Page 75: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it ended:

http://cablesearch.org/?page_id=46

Sunday, March 25, 12

Page 76: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

So what happened here?

Sunday, March 25, 12

Page 77: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Text

www.cablesearch.org

Sunday, March 25, 12

Page 78: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it started

http://screencast.com/t/1scMTaBgZytF

Sunday, March 25, 12

Page 79: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 80: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Why did this succeed?

Sunday, March 25, 12

Page 81: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

Sunday, March 25, 12

Page 82: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

Sunday, March 25, 12

Page 83: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

For news beats

Sunday, March 25, 12

Page 84: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

For news beats

Sunday, March 25, 12

Page 85: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

For news beats

Sunday, March 25, 12

Page 86: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

For news beats

By tags, for specialist & background stories

Sunday, March 25, 12

Page 87: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problem

Why did this succeed?

For news beats

By tags, for specialist & background stories

Sunday, March 25, 12

Page 88: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problemSharing with public gave us great new ideas

Why did this succeed?

Sunday, March 25, 12

Page 89: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a problemSharing with public gave us great new ideas

Why did this succeed?

Sunday, March 25, 12

Page 90: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It solved a real problemCrowdsource!The Business plan paid for infrastructure

Why did this succeed?

Sunday, March 25, 12

Page 91: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Even more gory details

Sunday, March 25, 12

Page 92: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 93: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Volkskrant:

Sunday, March 25, 12

Page 94: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Volkskrant:

• Newspaper demanded tons of data about the state of elderly homes in The Netherlands

Sunday, March 25, 12

Page 95: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 96: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The response

Sunday, March 25, 12

Page 97: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The response

Sunday, March 25, 12

Page 98: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 99: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Volkskrant

Sunday, March 25, 12

Page 100: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Volkskrant• Pushed over and over again to get the

data

Sunday, March 25, 12

Page 101: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The response

Sunday, March 25, 12

Page 102: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Volkskrant• Invoked the freedom of information act

Sunday, March 25, 12

Page 103: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The response

Sunday, March 25, 12

Page 104: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Volkskrant• They kept pushing

39

Sunday, March 25, 12

Page 105: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 106: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

After one year

Sunday, March 25, 12

Page 107: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

After one year Finally. Succes!

Sunday, March 25, 12

Page 108: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

After one year Finally. Succes!

Sunday, March 25, 12

Page 109: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 110: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

A cd full of data

Sunday, March 25, 12

Page 111: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

A cd full of data

Sunday, March 25, 12

Page 112: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

A cd full of data

Sunday, March 25, 12

Page 113: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 114: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

• 270.000 questions• 320.000 answers• Devided in 9 categories • More then 12 subcategories

Sunday, March 25, 12

Page 115: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Overwhelmed by data:• 270.000 questions• 320.000 answers• Devided in 9 categories • More then 12 subcategories

Sunday, March 25, 12

Page 116: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 117: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Minor detail: all 4500 forms are PDF

Sunday, March 25, 12

Page 118: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Minor detail: all 4500 forms are PDF

Sunday, March 25, 12

Page 119: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Minor detail: all 4500 forms are PDF

Sunday, March 25, 12

Page 120: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 121: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 122: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 123: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 124: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

So what now?

Sunday, March 25, 12

Page 125: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

So what now?

Sunday, March 25, 12

Page 126: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It’s 2012. Don’t despair

Sunday, March 25, 12

Page 127: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It’s 2012. Don’t despair

Sunday, March 25, 12

Page 128: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

It’s 2012. Don’t despair

Sunday, March 25, 12

Page 129: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Anatomy of a projectI posted the pitch for the project:

“Need coder for converting 4500 PDF’s”

Sunday, March 25, 12

Page 130: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

One minute later

Sunday, March 25, 12

Page 131: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The Whole World Is Bidding

Sunday, March 25, 12

Page 132: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

And Bidding

Sunday, March 25, 12

Page 133: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

And Bidding

Sunday, March 25, 12

Page 134: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The result was:

Sunday, March 25, 12

Page 135: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The result was:• Over 60 programmers wanted to convert the

data into Excel and Web (MySql) for a price of $100 -$3000

• Choose the ones that are in the top 300 (out of 200.000 coders) to avoid surprises

Sunday, March 25, 12

Page 136: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Topcoder for $500

Sunday, March 25, 12

Page 137: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Out of 9 projects

Sunday, March 25, 12

Page 138: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Out of 9 projects

• 8 were a success• 1 was a miserable failure • Total number of publications: 7, 1 pending

Sunday, March 25, 12

Page 139: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Don’t forget

Always 2x coders for the same jobPerfect Pitch is ParamountDataminded reporter should do the pitch

Sunday, March 25, 12

Page 140: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Project lessonsHire coders, don’t become oneDo get the concepts behind data mining so you can instruct the coder Outsource smaller projects can be done

Sunday, March 25, 12

Page 141: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Back to the Volkskrant

Sunday, March 25, 12

Page 142: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The first job was done in 5 days

Sunday, March 25, 12

Page 143: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The first job was done in 5 days• PDF converted to normal text

Sunday, March 25, 12

Page 144: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Other steps:

Sunday, March 25, 12

Page 145: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Other steps:

• Text converted to Excel• Excel converted to MySql• Search engine for reporters enabled

them to ‘Google’ data of the homes - later used as public search

Sunday, March 25, 12

Page 146: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

FINALLY SOME ANSWERS

Sunday, March 25, 12

Page 147: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

• How many homes have financial troubles?• How many aggressive people caused

trouble?• How many actions of non-medical

employees were not backed up by a doctor?

• Which elderly home is the best/worst?

FINALLY SOME ANSWERS

Sunday, March 25, 12

Page 148: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Unexpected questions:

• Why are homes with a high mortality rate?• Why are homes with a sickness absence

of 15-20% ?

Sunday, March 25, 12

Page 149: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Results

• Two lead news stories on the front page• A special section about the best/worst

homes• ‘Top 300’ on the web for consumers:

where do I put daddy away• A lot of goodwill

Sunday, March 25, 12

Page 150: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The lessons:

Sunday, March 25, 12

Page 151: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The lessons:

• 1.Datamining is the start of the project, not the end

• 2 Reporters write the story• 3 Public comments on story - new stories

Sunday, March 25, 12

Page 152: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 153: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

School dataThe 2x 500 euro Solution

Sunday, March 25, 12

Page 154: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

What ifYou want to report on a regular basis on the same

subject?

Sunday, March 25, 12

Page 155: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Spidering or custom programming ?

Roughly 7500 records in two spreadsheets

Sunday, March 25, 12

Page 156: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done

Brin codes identify school

http://functiemix.minocw.nl/resultaten.aspx?criteria=1&type=1&brin=00AH

Sunday, March 25, 12

Page 157: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done: securing school codes

List of BRIN codes

ScreenScraper

BuildURL

Req.Page

GetPage

Build Report

Sunday, March 25, 12

Page 158: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done: Building URL (from list)

List of BRIN codes

ScreenScraper

BuildURL

Req.Page

GetPage

Build Report

Sunday, March 25, 12

Page 159: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done: Request web page

List of BRIN codes

ScreenScraper

BuildURL

Req.Page

GetPage

Build Report

Sunday, March 25, 12

Page 160: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done: Get & parse web page

List of BRIN codes

ScreenScraper

BuildURL

Req.Page

GetPage

Build Report

Sunday, March 25, 12

Page 161: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done: Build report

List of BRIN codes

ScreenScraper

BuildURL

Req.Page

GetPage

Build Report

Sunday, March 25, 12

Page 162: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

How it was done: REPEAT until done

List of BRIN codes

ScreenScraper

BuildURL

Req.Page

GetPage

Build Report

Sunday, March 25, 12

Page 163: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 164: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider

Sunday, March 25, 12

Page 165: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage

Sunday, March 25, 12

Page 166: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time

Sunday, March 25, 12

Page 167: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate

Sunday, March 25, 12

Page 168: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate• - Not tedious, no insult to intelligence

Sunday, March 25, 12

Page 169: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate• - Not tedious, no insult to intelligence• Legal ramifications

Sunday, March 25, 12

Page 170: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate• - Not tedious, no insult to intelligence• Legal ramifications

– Always be respectful of your source

Sunday, March 25, 12

Page 171: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate• - Not tedious, no insult to intelligence• Legal ramifications

– Always be respectful of your source – You can’t copyright facts

Sunday, March 25, 12

Page 172: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate• - Not tedious, no insult to intelligence• Legal ramifications

– Always be respectful of your source – You can’t copyright facts– You can copyright how facts are presented

Sunday, March 25, 12

Page 173: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Things to consider• Creates competitive advantage• - Saves time• - More accurate• - Not tedious, no insult to intelligence• Legal ramifications

– Always be respectful of your source – You can’t copyright facts– You can copyright how facts are presented– Don’t make yourself conspicuous

Sunday, March 25, 12

Page 174: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

LessonsBuild once, use often

Generic & important: zip code / geodata / feedback

Sunday, March 25, 12

Page 175: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The 300 euro project

Sunday, March 25, 12

Page 176: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess

digital digging: converting data

Source: Funda

Technique: ‘datascraping’

Makelaars manipuleren woningaanbod ROTTERDAM, 3 JAN. NVM-makelaars en huizenverkopers manipuleren met te koop staande huizen, door ze een paar dagen van de markt te halen en daarna als nieuw aan te prijzen. De afgelopen drie maanden is dat over heel Nederland verspreid meer dan 2.700 keer gebeurd

Sunday, March 25, 12

Page 177: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 178: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

• Script was written to download the data of more then 300.000 houses during three

months

• The results were put in an Excel file.

• Reporters browsed manually for anomalies

Sunday, March 25, 12

Page 179: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Results

Sunday, March 25, 12

Page 180: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Results• Two frontpage stories• 1 Appendix• Higher circulation

Sunday, March 25, 12

Page 181: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Nice, but..

Can’t you do it cheaper?

Sunday, March 25, 12

Page 182: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

The 0 euro-projects

Sunday, March 25, 12

Page 183: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

european databases

Sunday, March 25, 12

Page 184: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Creative thinking

Sunday, March 25, 12

Page 185: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Creative thinking

• What databases are there online in Europe?

• Hmm, there is a register of all people who attended meetings, a presence register.

Sunday, March 25, 12

Page 186: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess

So what??• What can you do with such a register?• Study which members are there and which not• Study which countries are more absent than others• How big is the effect if certain members of countries

aren’t voting at all?• In reality some countries have more influence then

you would expect from the actual number of seats

Sunday, March 25, 12

Page 187: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess

CAR: do try this at home! The Netherlands has

more power

Source: EU: database, available in 20

languages

Sunday, March 25, 12

Page 188: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Elaborate work..

Sunday, March 25, 12

Page 189: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Healthcare regulators

Sunday, March 25, 12

Page 190: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Sunday, March 25, 12

Page 191: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Sunday, March 25, 12

Page 192: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Tuchtcollege voor de Gezondheidszorg

Sunday, March 25, 12

Page 193: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Verdicts against doctors• Uitspraken van het CTG• <http://www.tuchtcollege-gezondheidszorg.nl/recent_files/recent.htm>De meest

recente uitspraken<http://www.tuchtcollege-gezondheidszorg.nl/recent_files/recent.htm>

• <http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/huisarts.htm>Uitspraken over huisartsen en basisartsen<http://www.tuchtcollege-

gezondheidszorg.nl/huisarts_files/huisarts.htm>• <http://www.tuchtcollege-gezondheidszorg.nl/specialisten_files/

SPECIALISTEN.HTM>Uitspraken over medische specialisten<http://www.tuchtcollege-gezondheidszorg.nl/specialisten_files/SPECIALISTEN.HTM>

• Uitspraken over psychiaters<http://www.tuchtcollege-gezondheidszorg.nl/psychiater.htm>

• <http://www.tuchtcollege-gezondheidszorg.nl/tandarts_files/Tandartsen.htm>Uitspraken over tandartsen<http://www.tuchtcollege-

gezondheidszorg.nl/tandarts_files/Tandartsen.htm>• <http://www.tuchtcollege-gezondheidszorg.nl/verpleegkundigen.htm>Uitspraken

over verpleegkundigen<http://www.tuchtcollege-gezondheidszorg.nl/verpleegkundigen.htm>

• <http://www.tuchtcollege-gezondheidszorg.nl/verloskundigen.htm>Uitspraken over verloskundigen<http://www.tuchtcollege-gezondheidszorg.nl/verloskundigen.htm>

• <http://www.tuchtcollege-gezondheidszorg.nl/apotheker.htm>Uitspraken over apothekers<http://www.tuchtcollege-gezondheidszorg.nl/apotheker.htm>

Sunday, March 25, 12

Page 194: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Total chaos•

2005.009 en 046<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.009%2520en%2520046.htm>2005.012<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.012.htm>2005.013<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.013.htm>2005.014<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.014.htm>2005.015<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.015.htm>2005.016<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.016.htm>2005.017<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.017.htm>2005.018<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.018.htm>2005.019<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.019.htm>2005.020<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.020.htm>2005.032<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.032.htm>2005.033<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.033.htm>2005.034<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.034.htm>2005.055<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.055.htm>2005.109<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.109.htm>2005.110<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.110.htm>2005.151<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.151.htm>2005.152<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.152.htm>2005.155<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.155.htm>2005.178<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.178.htm>2005.211<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.211.htm>2005.223<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.223.htm>2005.224<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2005.224.htm> 2004.005<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.005.htm>2004.012<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.012.htm>2004.014<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.014.htm>2004.021<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.021.htm>2004.022<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.022.htm>2004.023<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.023.htm>2004.024<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.024.htm>2004.025<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.025.htm>2004.026<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.026.htm>2004.027<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/2004.027.htm>2004.028<http://www.tuchtcollege-gezondheidszorg.nl/huisarts_files/

Sunday, March 25, 12

Page 195: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Sunday, March 25, 12

Page 196: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Step 1: download the site

Sunday, March 25, 12

Page 197: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Sunday, March 25, 12

Page 198: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Step 2

Sunday, March 25, 12

Page 199: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Step 2• Download a desktop

search tool

Sunday, March 25, 12

Page 200: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Sunday, March 25, 12

Page 201: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Step 3

Sunday, March 25, 12

Page 202: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Step 3 Start typing questions as you do in Google

Sunday, March 25, 12

Page 203: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Sunday, March 25, 12

Page 204: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

11/20/08  12:51  Henk  van  Ess11/20/08 12:51 Henk van Ess [email protected]

Like this:

Sunday, March 25, 12

Page 205: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

DIFFERENCES BETWEEN COURT RULINGS

Sunday, March 25, 12

Page 206: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

DIFFERENCES BETWEEN COURT RULINGS

Coverstory

Sunday, March 25, 12

Page 207: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12

Page 208: The Gory Details Of Datajournalism: what went wrong and who was responsible by Henk van Ess

Sunday, March 25, 12