Monday, October 31, 2011

The Art, Science, Skill & Craft of Datacasting Baseball


Datacasting is the process of capturing most game events into a software client, for the purpose of broadcasting the events online while also creating a record of the game. Several of my colleagues in other stats organizations do similar functions for other sports. My boss has said that he cannot overstate how difficult the job really is. Datacasting is an art, science, skill & craft; I'll show you how.

Preparing for the Game

Before the game starts, I get a lineup sheet and game notes from the media handouts and sit in my assigned seat in the front row of the pressbox (opposing team's media on my left, AP/STL on my right, OS just past that). I check the rosters in the software with the lineups on the media sheets, and IM roster changes to my tech support person at MLB.com. I then input lineups for the day, along with umps, the official scorer (OS), weather and wind.

The Game

Just before the game starts, as the team warms up on the field, I check the umps to make sure we have the correct lineup.

During the game, I write down then input every pitch, hit and substitute as they happen. When runners are on base, I look for blocked pitches, as well as the runner going on a pitch (rather than hit). On the handy graphic, I mark the spot on the field where the ball was played.

Pitches aren’t just balls and strikes, but call, swing, swing (block), bunt, foul, foul tip, foul bunt, missed bunt attempt, ball, blocked ball, intentional ball, pitchout.

Most of you know that each fielder has a number (pitcher 1 catcher 2 1B 3 etc etc).
Each play has a code. If it’s a single grounder to the center fielder, it’s S8/G. If it’s a grounder out to the shortstop, it’s 63/G (SS to 1B). A popout 6/P, a flyout is only the outfield 8/F. A sacrifice bunt is 31/SAC/BG.1-2 (batter thrown out on a bunt grounder to the first baseman to pitcher covering first; runner at first goes to second (1-2)). A groundout double play is 64(1)3/GDP (SS to 2B (runner from 1st) to 1B/ Groundout Double Play). Saw a lot of those this year!

Sometimes the OS determines a play (error or hit, play or no play (e.g., if a foul ball was catchable or not), so I wait while the OS reviews the play. The game continues (pitches, hits, etc), so I write while waiting for the answer, then input & catch up.

Post-Game

After the game is over, I input attendance and game time, and make edits as my MLB support person requests. Every pressbox has its own process for reviewing box scores; in St. Louis, my box score is printed for the OS to check, and I make changes if necessary. An overnight file is made from my file and submitted to various sports bureaus. (I’m a bit fuzzy on those details, if it’s my file or the OS sheet etc).  Yahoo is a client of MLB.com; here is a game I did for them http://sports.yahoo.com/mlb/boxscore?gid=310518124.

After reading this, you can imagine that I’d really appreciate a great pitcher’s duel, straight up substitutions, with an umpire that calls strikes and tips to his side rather than in front of his body!

Datacasting as an Art
Wikipedia: Generally, art is made with the intention of stimulating thoughts and emotions....The word art can describe several things: a study of creative skill, a process of using the creative skill, a product of the creative skill, or the audience's experience with the creative skill. 

I suppose the game itself is the actual art here, but I believe that my datacasting could well be described as art since it requires skill and exists (in my role with MLB) to satiate the baseball masses' desire to never be apart from their beloved teams (e.g., Red Sox fans).

Datacasting as Science
Wikipedia: In modern use, "science" is a term which more often refers to a way of pursuing knowledge, and not the knowledge itself. 

Interestingly, knowledge to a datacaster encompasses several elements: knowledge of the game and knowledge of the software.  My buddy Rollie says that the job wouldn't be hard if it weren't for the technology. He's right, I think.

Datacasting as a Skill and a Craft

Historically, there have been arguments about the divide between professions, trades, crafts, etc etc. The definition I use here combines them to some extent:  

A craft is a branch of a profession that requires some particular kind of skilled work. 
    Separately defined:
** A skilled worker has some special skill, knowledge, or (usually acquired) ability in their work ...While most (if not all) jobs require some level of skill, "skilled workers" bring some degree  of expertise to the performance of a given job.  
** A profession is a vocation founded upon specialized educational training,

I began training for the season in January, learning codes, and eventually moving on to the software. I was thankful for every hour I had trained, but learned much on the job; we were told that after about 20 games (1 season of work), we'd be comfortable. 

I was also warned that just because I'm good at my day job does not mean I'm good at datacasting. I observe classrooms and crunch numbers for a living, so many times I found myself wondering if I was bad at my day job, too.

How Roy Oswalt Became My #3 will provide a more entertaining and emotional examination of my experience. Hint: It involves significant pain, Vicodin and probably stubbornness. 

And yes, I know there are better sources than Wikipedia, but for this, it's sufficient. I'm saving the real deep stuff for the discussion of baseball's fourth wall.

No comments:

Post a Comment