Skip to main content
Social Sci LibreTexts

5.5: Distributed, Collaborative or Open-source reporting

  • Page ID
    305692
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    The concept of distributed reporting is a form of transparency for a news organization. Traditionally, readers only learn about stories a news organization is working on when the articles are finished and published. While it is customary to keep a story idea secret to prevent the competition from running with the idea, the distributed reporting model requires a news organization to go public with a story idea early in the reporting process.

    The reason? To allow readers to assist in the reporting of the story.

    In December 2006, The Cincinnati Enquirer tapped the power of distributed reporting to gauge compliance with a new smoking ban. Here’s how the paper’s investigative and enterprise reporter, Gregory Korte, described it in his blog:

    “Whether you’re a smoker or non-smoker, you probably want to know which bars, restaurants and bowling alleys are complying with Ohio’s new ban on smoking — and which are ignoring it until the state posts new regulations.

    And we’d like to tell you. But with 1,488 bars and restaurants in Hamilton County alone (that’s just counting the liquor licenses), it’s hard to get around to all of them.

    It’s a good example of why The Enquirer, like all Gannett newspapers, is embarking on an experiment in what we call ‘crowdsourcing.’ We’re asking you to help us report the story by telling us what’s going on in all those places we can’t get to.”

    During the 2006 Elections, The Cincinnati Enquirer invited readers to report voting problems they experienced at their polling places. Dozens of readers called or e-mailed to describe the irregularities and The Enquirer presented the problems on a Google Map on its Web site (http://www.cincin natidatadesk.com/pages /voter.html).

    clipboard_e87ec857efdec8af073925f428e01e21c.png

    While the terms used to describe it are new, the practice itself has been around for many years. The Spokesman-Review in Spokane, Wash., began using distributed reporting in 2001 with a database of e-mail addresses — something it called a “reader network” — to correspond with readers while reporting stories. This model has been copied by newspapers everywhere and used effectively in many situations, especially when looking for sources to interview on a specific topic or feedback or reaction to a current issue in the news.

    Most reader networks were started with e-mail addresses from readers who had contacted the newspaper, either by sending a letter to the editor or asking a reporter about a news story. Through its Web site, a news organization can also build the database by advertising the network and inviting readers to join.

    Minnesota Public Radio excels at this with its Public Insight Journalism initiative (http://minnesota.publicradio.org/your_voice/). By collecting as much information as possible, the news organization can slice the network several different ways and target specific subsets of the list for certain queries. People who live in a particular ZIP code, for example, or sports fans.

    Ken Sands, who pioneered the practice in Spokane, highlights two ways the use of an e-mail network differs from traditional audience feedback such as letters to the editor or person-on-the-street interviews.

    clipboard_e5384f786ca55c0dc463a5ea55fa1f65b.png

    For more examples of how to use an e-mail database for distributed reporting, see Ken Sands’ article at: http://www.kcnn.org/modules/using_e_..._to_jumpstart_ your_newsgathering/

    “One, the interaction occurs before publication, during the information-gathering process; and, two, by actively reaching out to people, you get a different, broader reaction than you do by waiting for people who are compelled by passion to contact you,” Sands wrote for the Knight Citizen News Network (www.kcnn.org).

    Some newspapers now have more than one reader network. It can make sense to create and manage separate contact databases for education stories (if you need direct contact to teachers) or business stories (if you need to get feedback from local business leaders only).

    The concept is going national (and/or global) too. In 2006, New York University professor Jay Rosen and others launched NewAssignment.net, a sort of clearinghouse for open-source reporting projects produced by teams of volunteers. Craig Newmark (of craigslist fame) contributed $10,000 to help launch the project.

    “In this sense it’s not like donating to your local NPR station, because your local NPR station says, ‘Thank you very much, our professionals will take it from here.’ And they do that very well,” Rosen wrote on his blog PressThink. “NewAssignment says: Here’s the story so far. We’ve collected a lot of good information. Add your knowledge and make it better. Add money and make it happen. Work with us if you know things we don’t.”

    At a time when news organizations are looking for ways to build brand loyalty, getting readers and viewers to participate in the news process can help.


    This page titled 5.5: Distributed, Collaborative or Open-source reporting is shared under a CC BY-ND 4.0 license and was authored, remixed, and/or curated by Mark Briggs via source content that was edited to the style and standards of the LibreTexts platform.