<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Scoop &#187; Presentations</title>
	<atom:link href="http://blog.thescoop.org/archives/category/presentations/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.thescoop.org</link>
	<description>Derek Willis' weblog on investigative and computer-assisted reporting.</description>
	<lastBuildDate>Sun, 05 Feb 2012 04:18:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>What We Don&#8217;t Know About Elections</title>
		<link>http://blog.thescoop.org/archives/2011/10/17/what-we-dont-know-about-elections/</link>
		<comments>http://blog.thescoop.org/archives/2011/10/17/what-we-dont-know-about-elections/#comments</comments>
		<pubDate>Tue, 18 Oct 2011 01:46:07 +0000</pubDate>
		<dc:creator>Derek Willis</dc:creator>
				<category><![CDATA[Data]]></category>
		<category><![CDATA[Journalism]]></category>
		<category><![CDATA[Presentations]]></category>

		<guid isPermaLink="false">http://blog.thescoop.org/?p=5631</guid>
		<description><![CDATA[If you happened to be at the recent Online News Association conference in Boston and happened to attend the session on covering the 2012 elections, then a good bit of this will be repetitive. Since there wasn&#8217;t a ton of time to expand on what I said, and I don&#8217;t want to leave the impression [...]]]></description>
			<content:encoded><![CDATA[<p>If you happened to be at the recent <a href="http://ona11.journalists.org">Online News Association conference in Boston</a> and happened to attend the <a href="http://ona11.journalists.org/sessions/innovative-ways-to-cover-the-2012-election/">session on covering the 2012 elections</a>, then a good bit of this will be repetitive. Since there wasn&#8217;t a ton of time to expand on what I said, and I don&#8217;t want to leave the impression that I&#8217;m critical of all election coverage, consider this the write-through.</p>
<p>First, I stand by <a href="http://twitter.com/#!/kzhu91/status/117273879105384449">what I said</a> about how little we understand about the way that elections are won or lost these days. It&#8217;s not that political journalism has strayed from its roots, or stopped covering important elements of a modern campaign. It&#8217;s that the elements of a modern campaign have changed, and as journalists, we have not kept pace.</p>
<p>You might respond that campaigns still involve quite a lot of stuff that we <em>do</em> understand, such as debates and visits to state fairs and town hall meetings. True. But the nature of media and technology has brought extensive changes to the electoral system, and I don&#8217;t believe that we as journalists devote enough attention to understanding those changes. Remember the <a href="http://www.wired.com/wired/archive/12.01/dean.html">Dean campaign in 2003</a>? Most of the coverage was on the, for then, staggering online fundraising managed by some doctor from Vermont. But that Wired piece I referenced had it right; Dean&#8217;s accomplishment was less a mastery of the Internet but a willingness to embrace its fundamental aspect: you give up some control by bringing other people in, and you gain a host of possibilities. You may, of course, choose badly or falter in some other way, but the lessons and possibilities are becoming clear. At the time, as a Web geek who loved politics, I felt that journalists couldn&#8217;t really explain the Dean campaign, because it was so alien to us. Today&#8217;s campaigns make me long for the simplicity of 2003.</p>
<p>But let&#8217;s stick with fundraising for a bit. Political fundraising can be hugely expensive, because campaigns need to amass large number of donors. Unless you&#8217;re the President, it&#8217;s hard to repeatedly gather the wealthiest Americans and have them fork over $2,500 or more for the pleasure of your company. So a smart campaign sticks with what works: direct mail is costly, for example, but it&#8217;s also effective. Telemarketing takes time and money, but it also works pretty well. Let&#8217;s not mess with the script too much. <a href="http://blog.optimizely.com/how-obama-raised-60-million-by-running-an-exp">But what if you <em>can</em> mess with the script</a>? Now it&#8217;s possible, even trivial, to experiment with Web site design or <a href="http://themonkeycage.org/blog/2011/08/23/rick-perrys-eggheads/">even advertisements</a> in order to gauge their effectiveness and improve upon them. President Obama had a <a href="http://www.youtube.com/watch?v=71bH8z6iqSc">Director of Analytics</a> for his 2008 campaign, and <a href="http://www.datashaping.com/jobs18843x.shtml">has been hiring data scientists experienced in predictive modeling</a>.</p>
<p>White men smoking cigars in cramped rooms making gut calls is how we&#8217;ve usually understood campaign decision-making. This? Whole new ballgame. Yes, there is still a mass audience that is shaped by the media and big events. But there are now thousands and thousands of &#8220;small&#8221; audiences &#8211; or rather, they always were there. Now campaigns can identify them and deliver precision messages to them. And they can find them online in different ways; an hour after <a href="http://twitter.com/#!/derekwillis/status/126084472666984448">posting on Twitter</a> about the Obama&#8217;s campaign use of Github, the <a href="http://twitter.com/#!/teddygoff">campaign&#8217;s Digital Director</a> was following me. And that&#8217;s the easy part.</p>
<p>While campaigns have a public presence that is mostly recorded and observed, the stuff that goes on behind the scenes is so much more sophisticated than it has been. In 2008 we were fascinated by <a href="http://www.jackandjillpolitics.com/2008/10/obama-launches-iphone-app-makes-everyone-a-campaign-worker/">the Obama campaign&#8217;s use of iPhones for data collection</a>; now we&#8217;re entering an age where campaigns don&#8217;t just collect information by hand, but harvest it and learn from it. An &#8220;<a href="http://www.targetpointconsulting.com/ToThePoint/2011/09/27/the-information-arms-race">information arms race</a>,&#8221; as GOP consultant Alex Gage puts it.</p>
<p>For most news organizations, the standard approach to campaign coverage is tantamount to bringing a knife to a gun fight. How many data scientists work for news organizations? We are falling behind, and we risk not being able to explain to our readers and users how their representatives get elected or defeated.</p>
<p>None of this is to say that we need to completely abandon our ways of covering elections. Horse-race coverage is and should be a part of campaign coverage, because in many respects elections are like horse races. Things can change rapidly, and small things can have big impact. We still should be on the ground, talking to voters, showing up at town halls and covering debates. We still need to show up and do the legwork.</p>
<p>But if we can&#8217;t appreciate, much less understand, what modern campaigns are doing to win elections, how can we hope to explain elections? If we don&#8217;t collect at least some of the information available to us &#8211; realizing that we can&#8217;t get our hands on everything that the campaigns do &#8211; we&#8217;ll miss the story. Elections will become even bigger surprises to us, and then how long will it be before readers start to ask whether we actually know the people and places we cover?</p>
<p>Surprises make the news. Some of my favorite stories from the 2004 presidential election are in <a href="http://www.amazon.com/One-Party-Country-Republican-Dominance/dp/0471776726">a book</a> by my friends Peter Wallsten and Tom Hamburger, then of the Los Angeles Times. Here&#8217;s <a href="http://www.latimes.com/news/opinion/commentary/la-op-hamburger25jun25,0,906381.story">one anecdote from the key state of Ohio</a>:</p>
<blockquote><p>One suburban African American woman in Ohio, for example, told us that though she tends to vote Democratic, she was deluged in 2004 with calls, e-mail messages and other forms of communication by Republicans who somehow knew that she was a mother with children in private schools, an active church attendee, an abortion opponent and a golfer.</p></blockquote>
<p>Think about what this kind of thing means. It means that we cannot assume that the campaign visible to the mass audience is the same campaign that&#8217;s being pitched to individuals and groups around the nation, and that winning coalitions can be built not just by harnessing large groups (unions, religious voters, etc.) but also by piecing them together in small units. President Bush&#8217;s margin in Ohio in 2004? <a href="http://www.nytimes.com/packages/html/politics/2004_ELECTIONRESULTS_GRAPHIC/">About 2.5 percent</a>. The only thing that I don&#8217;t like about this anecdote is that Wallsten and Hamburger&#8217;s book appeared nearly two years later. Is there any evidence that we as journalists have closed the gap since then?</p>
<p>To understand how elections are now being waged, we need to have as many of the tools as do the campaigns. We need to build our own storehouses of data &#8211; <a href="http://www.wakegov.com/elections/8data.htm">voter registration</a>, <a href="http://www.sos.georgia.gov/elections/voter_registration/voterhistory.asp">voter history</a>, Census, campaign finance, <a href="http://transition.fcc.gov/mb/audio/decdoc/public_and_broadcasting.html#_Toc202587585">advertisements</a> and more. We need to be able to tap into the rich stream of material that&#8217;s being created and disseminated every day. We need to be able to see the value in small data points that can lead to bigger things.</p>
<p>Elections are great stories. They deserve to be told from a position of confidence and knowledge. We have work to do.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thescoop.org/archives/2011/10/17/what-we-dont-know-about-elections/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>On Technical Challenges to Accessing Government Information</title>
		<link>http://blog.thescoop.org/archives/2011/03/28/on-technical-challenges-to-accessing-government-information/</link>
		<comments>http://blog.thescoop.org/archives/2011/03/28/on-technical-challenges-to-accessing-government-information/#comments</comments>
		<pubDate>Mon, 28 Mar 2011 17:40:55 +0000</pubDate>
		<dc:creator>Derek Willis</dc:creator>
				<category><![CDATA[API]]></category>
		<category><![CDATA[Data]]></category>
		<category><![CDATA[Presentations]]></category>

		<guid isPermaLink="false">http://blog.thescoop.org/?p=5601</guid>
		<description><![CDATA[If you&#8217;re in D.C. on April 12 and are interested in government records, you may want to consider attending the Media Access to Government Information Conference (MAGIC) being held at National Archives building on Pennsylvania Ave. I&#8217;ll be one of the panelists there, but don&#8217;t let that dissuade you; there are far brighter people who [...]]]></description>
			<content:encoded><![CDATA[<p>If you&#8217;re in D.C. on April 12 and are interested in government records, you may want to consider attending the <a href="http://www.archives.gov/ncast/news/events/magic.html">Media Access to Government Information Conference</a> (MAGIC) being held at National Archives building on Pennsylvania Ave. I&#8217;ll be one of the panelists there, but don&#8217;t let that dissuade you; there are far brighter people who will be there.</p>
<p>As part of our participation, panelists were asked to write a 1,000-word comment on the topic of their panel. Mine is &#8220;What are the common technical challenges journalists face in making sense of government documents and analyzing government actions, and how could those be overcome?&#8221; Faithful readers will know that I could probably go on for hours on this, but here is what I sent to the conference organizers (sans links):<br />
<span id="more-5601"></span><br />
I very much doubt that the conference organizers intended this, but the fact that our responses to these questions were requested in either PDF or MS Word formats is an excellent example of one of the technical challenges for journalists when dealing with government documents. So in the spirit of openness, I wrote this in Google Docs.</p>
<p>Both journalists and government employees who create and manage information need to know about more than the usual options for the collection and dissemination of information. Part of the technical failure rightly belongs to journalists &#8212; too often, we don’t ask or don’t know how to ask for information in a way that makes it easy to use. But far too often, government officials are either unaware of their format options or, more perniciously, all too aware and resort to distributing documents in, for example, a locked PDF.</p>
<p>I have been told many times that to release information in a format that would allow it to be copied is not the policy of a government agency. Those government agencies fail to understand what public information is. I also have been the recipient of records that clearly were stored in spreadsheet software but, for purposes of public release, have been printed out, scanned into images and stored as a PDF. Obfuscation and paranoia are not technical challenges, but they contribute to them, forcing journalists to acquire costly software or spend additional time overcoming an artificial roadblock.</p>
<p>This challenge is not due to deficiencies in software produced by any particular company but rather in the understanding of how information can and should be made available to citizens. To the greatest extent possible, government information should be made available in formats that allow its users to copy, sift and reorganize it as they please. In practice, this means favoring text-based and open formats over images, PDFs and closed formats. I am less concerned about how agencies store their data, as long as they are able to export it in common formats or reliable workarounds exist, but there are exceptions to this.</p>
<p>Map data, for example, is commonly stored at the government level in <a href="http://en.wikipedia.org/wiki/Shapefile">ESRI’s shapefile format</a>, which, from the point of view of a journalist, has advantages and disadvantages. ESRI is a large, well-known company with products in use at most government agencies that have geographic data, so it makes sense that GIS data would be provided in that format. But not all newsrooms, and certainly not all journalists, are able to obtain ESRI’s software or have access to someone who can easily convert from shapefiles to other formats, such as the <a href="http://code.google.com/apis/kml/documentation/kml_tut.html">KML standard</a> now owned by Google. <a href="http://www.google.com/search?sourceid=chrome&#038;ie=UTF-8&#038;q=filetype%3Akml+site%3Agov">Some government agencies</a> already produce useful geographic data in KML format, but many others could join that list.</p>
<p>Fixing this situation will require education of journalists and government employees of the benefits and ease of working with open formats. The benefits for journalists are apparent: faster access to information that they can immediately put to use. Training journalists is a time-consuming and inefficient process, but journalists must break out of the mindset that government information only comes in documents.</p>
<p>Doing so means that journalists need to become as comfortable interviewing data as they are interviewing people. The benefits for government may need some more time to explain, but they exist. The <a href="http://www.fec.gov/">Federal Election Commission</a> is a case in point.</p>
<p>Thanks to a commitment to maintaining stable, available and well-documented data, the FEC makes it possible for its users to obtain and analyze information when they want to, even on a late-night deadline. This isn’t new-fangled technology; the <a href="http://fec.gov/finance/disclosure/ftp_download.shtml">FEC’s FTP site</a> has been operating for years. But the agency operates as if it trusts its data users, not from a defensive standpoint. As a result, the FEC is rightfully seen as an agency that makes it possible for reporters to do their jobs, not as an impediment to that goal.</p>
<p>A more recent, but increasingly significant, technical challenge is that too many government agencies fail to make better use of the best information distribution platform they have: the Internet. In a digital age, some agencies continue to treat all records either as documents, or when they do make data available, it is done as a single dump. In many cases, journalists do not need an entire dataset; they are more likely to want to answer a single question or small set of questions. In those cases where government agencies make this possible, it is usually through a Web form of their own design &#8211; one which often is tailored to heavy users such as the regulated community.</p>
<p>Providing <a href="http://en.wikipedia.org/wiki/Application_programming_interface">Application Programming Interfaces</a> (APIs) to government data via XML or JSON feeds would make it possible for journalists and Web developers to take advantage of government data without having to download and process enormous files. And while adding an API will incur an up-front cost, it will also save agencies employee time handling requests that could be done computer-to-computer.</p>
<p>Yet such APIs are very rare in government, even though they would make it easier for users and journalists to combine disparate data, and would make it possible to build more useful applications from government data. We know this to be true, because in the absence of any meaningful government approach to disseminating legislative data, several outside organizations, including my own, have developed APIs to help spur the use and spread of congressional data.</p>
<p>But in order to do this, we have had to essentially reverse-engineer the <a href="http://thomas.loc.gov/">Thomas site</a> operated by the Library of Congress, writing fragile HTML parsers that can break should the LoC change the structure of individual pages. So, in order to answer anything beyond the most basic question on legislative matters, a journalist must either spend hours looking up information one page at a time or be able to write a computer program to parse those pages. There has to be a better way.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thescoop.org/archives/2011/03/28/on-technical-challenges-to-accessing-government-information/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>NICAR 08 Presentations</title>
		<link>http://blog.thescoop.org/archives/2008/02/28/nicar-08-presentations/</link>
		<comments>http://blog.thescoop.org/archives/2008/02/28/nicar-08-presentations/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 18:07:03 +0000</pubDate>
		<dc:creator>Derek Willis</dc:creator>
				<category><![CDATA[Presentations]]></category>

		<guid isPermaLink="false">http://blog.thescoop.org/archives/2008/02/28/nicar-08-presentations/</guid>
		<description><![CDATA[Here&#8217;s the PDF of the presentation used for the panel that Chase Davis of the Houston Chronicle and I did on programming for journalists. Chase, Matt Waite and I also did a panel on open source software for CAR. Here&#8217;s the handout.]]></description>
			<content:encoded><![CDATA[<p>Here&#8217;s <a href="http://www.forjournalists.com/media/programming_intro.pdf">the PDF of the presentation</a> used for the panel that <a href="http://www.car-chase.net/">Chase Davis</a> of the Houston Chronicle and I did on programming for journalists. Chase, <a href="http://www.mattwaite.com/">Matt Waite</a> and I also did a panel on open source software for CAR. Here&#8217;s <a href="http://docs.google.com/Doc?id=dspprdc_173dp3rcgm">the handout</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thescoop.org/archives/2008/02/28/nicar-08-presentations/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>SLA 2007 Notes</title>
		<link>http://blog.thescoop.org/archives/2007/06/11/sla-2007-notes/</link>
		<comments>http://blog.thescoop.org/archives/2007/06/11/sla-2007-notes/#comments</comments>
		<pubDate>Mon, 11 Jun 2007 20:53:09 +0000</pubDate>
		<dc:creator>Derek Willis</dc:creator>
				<category><![CDATA[Journalism]]></category>
		<category><![CDATA[Presentations]]></category>

		<guid isPermaLink="false">http://www.thescoop.org/archives/2007/06/11/sla-2007-notes/</guid>
		<description><![CDATA[This year&#8217;s Special Libraries Association conference was in Denver, and I was lucky enough to be asked to help present, along with Jeremy Milarsky, a day-long session for the News Division on June 3rd. The basic focus was on developing a &#8220;tech toolbox&#8221; for news researchers &#8211; expanding their skills further into the technology realm. [...]]]></description>
			<content:encoded><![CDATA[<p>This year&#8217;s <a href="http://www.sla.org/content/Events/conference/ac2007/conference/index.cfm">Special Libraries Association conference</a> was in Denver, and I was lucky enough to be asked to help present, along with Jeremy Milarsky, a day-long session for the <a href="http://www.ibiblio.org/slanews/">News Division</a> on June 3rd. The basic focus was on developing a &#8220;tech toolbox&#8221; for news researchers &#8211; expanding their skills further into the technology realm. You can see <a href="http://www.thescoop.org/downloads/sla2007.zip">two of my presentations</a>(zipped ppt slides) and <a href="http://docs.google.com/Doc?id=dspprdc_13gjxf34">a quick handout</a> on sites for learning about technology in general and some of the specific tools that Jeremy and I use.</p>
<p><span id="more-5047"></span></p>
<p>I&#8217;ve written before about <a href="http://www.thescoop.org/thefix/innovate-or-die/">the crucial role that news librarians can play in the life of the newsroom</a>, but it takes people willing to embrace the shift in attitude and habits that these new roles demand. We&#8217;ve got a core group of folks who want to learn &#8211; the folks who paid $300 for the session, some of it out of their own pockets, were eager to dive in. The next day we heard from news librarians who have completely turned their jobs upside down (not always voluntarily), but I&#8217;m not sure that it didn&#8217;t just frighten some of the attendees.</p>
<p>At the News Division&#8217;s business meeting it was great to hear Jim Hunter, the outgoing division chair, say that <a href="http://www.ibiblio.org/slanews/">the division&#8217;s website</a> was a key element in serving our members and attracting more. Hopefully there will be more news on that front soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thescoop.org/archives/2007/06/11/sla-2007-notes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Computers in Libraries Presentation</title>
		<link>http://blog.thescoop.org/archives/2007/04/16/computers-in-libraries-presentation/</link>
		<comments>http://blog.thescoop.org/archives/2007/04/16/computers-in-libraries-presentation/#comments</comments>
		<pubDate>Mon, 16 Apr 2007 18:58:52 +0000</pubDate>
		<dc:creator>Derek Willis</dc:creator>
				<category><![CDATA[Presentations]]></category>

		<guid isPermaLink="false">http://www.thescoop.org/archives/2007/04/16/computers-in-libraries-presentation/</guid>
		<description><![CDATA[Today I spoke at the Computers in Libraries conference in Crystal City, about creating browsable data with Django. My presentation is attached in PowerPoint and PDF formats.]]></description>
			<content:encoded><![CDATA[<p>Today I spoke at the Computers in Libraries conference in Crystal City, about creating browsable data with Django. My presentation is attached in <a href="http://www.thescoop.org/wp-content/uploads/2007/04/CILPresentation.ppt">PowerPoint</a> and <a href="http://www.thescoop.org/wp-content/uploads/2007/04/CILPresentation.pdf">PDF</a> formats.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.thescoop.org/archives/2007/04/16/computers-in-libraries-presentation/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

