The Scoop

  • Home
  • Projects
  • About The Scoop
  • Fixing Journalism
  • Medill Links
  • Departments
    • API
    • Apple
    • Asides
    • Broadcast
    • Campaign Finance
    • Car Tools
    • Code
    • Data
    • DIY
    • django
    • Fed Data
    • FOIA
    • General
    • IRE
    • Journalism
    • Local Data
    • Mapping
    • Miscellany
    • NonGov Data
    • Online
    • Paper Trail
    • Presentations
    • Public Records
    • Python
    • Rails
    • Ruby
    • SLA
    • Social Network Analysis
    • Sports
    • State Data
    • Teaching
    • Work
    • XML
  • Subscribe via RSS

Player-by-Player

August 6th, 2007  |  Published in Journalism  |  1 Comment

Continuing with adaptations of Facebook for journalism, yesterday I was reading a story in the Columbus Dispatch about an Ohio State football recruiting class that had just one player left in the program. Newspapers report on the comings and goings of college athletes, particularly in the high-profile sports, but we do so in a piecemeal fashion: either it’s a notebook item or the subject of stories like the one in the Dispatch. The writer was able to contrast the lone guy from the 2003 class with the 16 fifth-year seniors on last year’s team, but shouldn’t we (and the public) know how common it is to have that many (or few) fifth-year seniors?

Here’s an idea: databasing recruiting and subsequent player actions will give fans a resource to answer questions and track their favorite players, while also providing the paper with the ability to spot trends over time and compare classes and even schools with much greater ease. Every action (oral commitment, signing, enrolling, playing, starting, getting injured, getting suspended, getting kicked off the team) would be recorded in a database. Yes, it requires some work on the front end, but it’s a great reference with multiple uses for stories, for the Web, for syndication even. And it’s not like this work is beyond us – heck, the Dispatch compiled a listing of the Class of 2003 for its story. That’s a start, but it’s not the best way.

Unless, of course, news organizations are happy to have their sports fans get better stuff from blogs and recruiting services. Me, I’d rather compete.

Responses

Feed Trackback Address
  1. Doug Haddix says:

    August 17th, 2007 at 5:21 pm (#)

    Derek,
    That’s a really good idea. I’ve relayed it to my handlers here at The Dispatch. Given Buckeye Nation’s insatiable appetite, a database tracking all of the key events with players and recruits would be useful in a lot of ways.
    Thanks,
    Doug Haddix, projects editor

Leave a Response

Recent Comments

  • Seth Lewis on Lost in the Weeds
  • Reporters' Lab // News algorithms already exist – and that’s good on The Programmer-Reporter
  • Eric Mill on On Legislative Data Transparency
  • (19:19 06-02-2012) Noticias más populares de #opengov en las ultimas 24 horas | Tuits de Software Libre on On Legislative Data Transparency
  • (15:05 06-02-2012) Noticias más populares de #opengov en las ultimas 24 horas | Tuits de Software Libre on On Legislative Data Transparency

Recent Posts

  • Lost in the Weeds
  • Our Mark Knoller Problem
  • The Programmer-Reporter
  • Investigating House Freshmen Voting Patterns
  • On Legislative Data Transparency

Linking Out

  • Mapping America — Census Bureau 2005-9 American Community Survey - NYTimes.com
    holy crap
  • Backbone.js and Django | joshbohde.com
  • ProPublica
  • Geoff: GeoJSON Feature Functions for JavaScript
  • Introducing Spanner: From Documents to Linked Data Apps—Clark & Parsia: Thinking Clearly
  • A performance lesson on Django QuerySets | Seek Nuance
  • http://www.post-gazette.com/pg/03001/1108747-209.stm
  • CBC News - Canada - Database: Canadian cables in WikiLeaks
  • Federal prosecutors likely to keep jobs after cases collapse - USATODAY.com
  • Strata Gems: Explore and visualize graphs with Gephi - O'Reilly Radar


©2012 The Scoop
Powered by WordPress using the Gridline Lite theme by Graph Paper Press.