How news outlets covered the State Department’s visa policy change

Posted on October 3, 2018 by Patrick Garvin

Under a new State Department policy that went into effect October 1, the United States will issue a G-4 visa to a partner of a staff member of US-based international organizations only if the couple is legally married. Among other organizations, this includes the United Nations, the World Bank, and the International Monetary Fund.

Per the State Department’s website: “Effective immediately, U.S. Embassies and Consulates will adjudicate visa applications that are based on a same-sex marriage in the same way that we adjudicate applications for opposite gender spouses.”

This has ramifications for anyone who worked for a US-based international organization and wanted to obtain a G-4 vis for a partner. But this has noticeable consequences for same-sex couples. In many countries, same-sex marriage is not permitted. Furthermore, there are some countries where same-sex relations are still illegal, and in some countries, punishable by death.

From an NBC News article:

For all new G-4 applications filed at the State Department after Monday, the same-sex partner must be a legally married spouse. For U.N. workers who are in relationships currently recognized by a G-4 visa but are not legally marriage, their partners will have 30 days after the new year to either get married or exit the United States.

David Pressman, who was the U.S. ambassador to the U.N. Security Council for special political affairs in the Obama administration, said the G-4 action is harmful in part because the United Nations is “composed of probably one of the most diverse workforces of any organization in the world.”

“If that’s how you advance equality between same-sex and opposite sex partners, then we have an enormous problem on our hands,” Pressman said. He described the policy as a “creative and cynical way to use the expansion of equality at home to vindictively target same-sex couples abroad.”

Here’s a look at how a handful of news outlets framed the issue. I’ve included screenshots of the headlines, as well as links to the articles.

First, the aforementioned piece from NBC News: U.S. to partners of U.N. LGBTQ staff: Get married, or get out

CBS News: U.S. says same-sex partners of UN staff will have to marry or leave

ABC News: Trump administration halts visas for unmarried same-sex partners of foreign diplomats

Washington Post: State Department changes visa rules for same-sex partners of foreign diplomats

New York Times: U.S. Bans Diplomatic Visas for Foreign Same-Sex Domestic Partners

Wall Street Journal: Trump Administration Halts Some Same-Sex Visas for Foreign Officials in U.S.

Los Angeles Times: U.S. stops issuing visas to same-sex partners of foreign diplomats unless they are married

CNN: US halting visas for same-sex partners of diplomats

New York Magazine: The U.S. Just Made Life Harder on LGBT Diplomats and U.N. Staff

And here are some headlines from LGBTQ-themed publications:

INTO: The Trump Administration Is Denying Visas to Unmarried Same-Sex Partners of U.N. Diplomats

them: The State Department Says Gay Diplomats Have To Marry Their Partners Or Leave

LGBTQ Nation: Trump administration will deny visas to same-sex partners of diplomats

The Advocate: Trump Reverses Clinton Policy, Strips Visas From Same-Sex Partners of Diplomats

Headlines have the challenge of distilling the essence of a story down to a few words while not giving away too much of the story. This story is a hard story to sum up in a short headline, because there are so many ways to frame the situation:

The State Department has a new policy affecting people who want G-4 visas
People who work for US-based international organizations who want visas for their partners will have to get married to get those visas
People who work for US-based international organizations who want visas for their partners will have to get married to get those visas, but there will be complications for some people
People who work for US-based international organizations who want visas for their partners will have to get married to get those visas, but same-sex couples face potential dilemmas that opposite-sex couples won’t face
UN workers who want to get G-4 visas for their partners will now have to marry their partners to get the visa
UN workers who want to get G-4 visas for their partners will now have to marry their partners to get the visa, even if they are in a same-sex couple and they live in a country where same-sex marriage is not legally allowed
UN workers who want to get G-4 visas for their partners will now have to marry their partners to get the visa, even if they are in a same-sex couple and they live in a country where same-sex relations are agains the law

Each of those statements is true, though some of them are descriptive and precise, and some are broader. Ultimately, the least clunky of them is that first one: “The State Department has a new policy affecting people who want G-4 visas.” But that fails to capture the totality of what’s happening, and what’s at stake.

Part of what makes it difficult to convey the news in brief, compelling and accurate language is that it’s difficult to refer to the people affected without being at least somewhat clunky. News organizations and the journalist who write for them have struggled on how to refer to couples in same-sex relationships. For years, “gay marriage” has been treated as interchangeable with “same-sex marriage,” and “gay couples” has been seen as acceptable to mean “same-sex couples.” This colloquial way of referring to same-sex couples is limited, though, as it implies something that we can’t know for certain: the orientations of the people in same-sex couples. In the US and other countries that permit same-sex couples to marry, the orientation of the couple is not a factor. The couples can comprise gay people, bisexual people, pansexual people, queer people, and so on. Even straight people.

Similarly, this policy change affects anyone in a same-sex couple wanting a G-4 visa, whether they are gay, bisexual, pansexual, queer, etc. This might seem like hairsplitting and nitpicking, but there’s a good reason to pay attention to the language. From a traditional copy editor’s perspective, it’s more precise and accurate to say “same-sex couple” and “opposite-sex couple” than to say “gay couple” or “straight couple.” I can’t imagine too many people have written corrections for incorrectly identifying the sexual orientation of a couple who got married, but anyone who aims to be accurate — and correction-free! — should keep this in mind.

But beyond that, it’s more inclusive to say “same-sex couple,” because “gay couple” only speaks to gay couples. “Same-sex couples” includes so many more people. Bisexual people and others who identify as neither straight nor gay can feel erased or ignored if the default blanket description of “not straight” is just “gay.”

For similar reasons, the term “straight marriage” is also limited and inaccurate. There can be — and are — opposite-sex couples comprising people who don’t consider themselves straight.

Sign up for the LGBTQ+ Experiment newsletter here.

How to use Mr. Map Generator, a map tool for journalists

Posted on March 24, 2015 by Patrick Garvin

In a recent blog post about journalists using technology to make their lives and jobs easier, I mentioned that I created templates in Illustrator of the maps we use the most. I saved those as SVGs and then turned those SVGs into HTML. The heavy lifting was writing code for a map generator that would allow me to copy and paste spreadsheet data to color-code the maps for me. It took some time, but it paid off. It creates responsive maps that I can easily pluck onto the website, but I can also print-to-PDF those suckers and have the basis for the print version. People who have made vector maps will know that the “old way” of having to select each state/county individually to color-code it was a pain. And fraught with the possibility of introducing error.

Mr. Map Generator has maps of the US, Massachusetts and Boston. For this post, I’ll explain how to use the US map generator, though the concepts will be almost the same for the other map generators.

GETTING STARTED

1. We’ll start with a spreadsheet. I usually use a Google Spreadsheet or an Excel Spreadsheet. In our fake spreadsheet, we will pretend it’s a spreadsheet about the “Dawson’s Creek” finale, showing the percentage of people in each state who rooted for Joey to end up with Pacey, Dawson, or neither. Obviously, these are made-up numbers, because most people will agree that Joey should have ended up with Pacey. But for the sake of this exercise, we will pretend.

Format your data with state postal codes in the first column, state names in the second column, and data in however many columns you want, starting with the third column. You can download a zip for the responsive files here or if you just want to make a print map, download the Excel template here. Neither the postal codes or state names need to be in any order.

2. On the page of the US map generator, paste your data in the field that says, “Paste your data in this field.”

3. After pasting your data, click on the button that says, “Click here to select your data set.”

4. After you’ve done that, you’ll get a button that shows you the columns from your spreadsheet. In this scenario, as we’ve created a fake spreadsheet, our options are “Rooted for Joey ending up with Pacey,” “Rooted for Joey ending up with Dawson,” and “Rooted for neither Dawson nor Pacey.” For the sake of this exercise, I’ve clicked on those who “Rooted for Joey ending up with Dawson.” Which, of course, was not how it ended.

5. Step 5 allows you to select your color from the options of red, blue, a gold/yellow, green, and purple. Step 6 allows you to decide whether you want the map to have 2, 3, 4 or 5 colors, or to be a chloropleth where the smallest value is the lightest shade and the largest value gets the darkest shade.

6. In our case, we’ve opted to have four shades of red. The generator is designed to calculate your smallest value and your largest value, and then calculate the ranges in between those two values. I strongly suggest not leaving those values as is, for a variety of reasons:

Outliers that skew the ranges
Ranges that aren’t intuitive (6.1-11.6, 11.6-17.1, etc.)

7. Once you have selected your color and ranges, you can click a button to preview your map. Do that.

Here’s what your map will look like:

8. You’ll then have the option to generate your code. It will appear in a text box.

9. To make a web version, download these files if you didn’t already do so in the first step. Copy the code in the box above and paste it inside the file called code.js. Then open the HTML in a browser. You don’t have to edit or change any of the other files. When you upload it to your server space, you’ll need four files:

code.js
map.css
US-map.htm
US-responsive.js

10. You’ll need to add a key/legend on your own. If you inspect element on this page, you can copy the HTML you’ll need and can plunk it into US-map.htm before uploading it.

11. To use this to make a vector print map, right click and select “Print.”

12. In the print dialog box, select “Save as PDF.” I usually have it only save page 2 of the PDF, rather than saving the entire file.

13. I then open that PDF in Illustrator. Using the white arrow, I select everything I want to delete. I delete until all is left is the shapes of the states.

14. Once I’ve deleted the extra parts from the PDF, such as text characters, I have only the map left. I then plug that into a Globe template file. I’ve done enough of these that I have a starter file with the state labels in place.

If you see yourself making a lot of these, having an Illustrator template with a layer of labels is not a bad idea.

“Should journalists learn code?” Well, what exactly do you mean by “code”?

Posted on March 18, 2015 by Patrick Garvin

There have been many blog posts and articles that pose what has become a divisive question: Should journalists learn code?

There’s a lot of passion in the comment sections on these posts, but I’ve wondered if we’re all on the same page as to what the question means.

“Should journalists learn code?”

What do we mean by “code”? Do we mean HTML and CSS, which are markup languages? Or do we mean languages such as JavaScript and jQuery? Or do we mean Ruby? Python? C++? Journalists who don’t know what they don’t know might be tempted to lump everything together, but they’re not all the same.

What do we mean by “learn”? Do we mean learn everything until we are masters? Do we mean learn enough to be proficient? Do we mean that we should learn some of the basic concepts so we can follow conversations with our colleagues about projects?

Does this mean everyone should learn the same skills? Should reporters, editors, developers, photographers and graphic artists all learn the same programs and languages? Should they all be proficient at an expert level?

“Should journalists learn code?” will mean different things to different journalists, and the anxiety that question brings with it also brings valid concerns. Many journalists equate that question with completely changing their job. Some could think of it in terms of web galleries and managing assets on a web site. Some have told me they think of code as high-level computer programming and thus think of it as losing any aspect of reporting or editing in their jobs to instead solely write code. Others have not-unfounded worries that some newsrooms could farm out more work to fewer people. In other words, they muse, if journalists have to take on more work, and even different kinds of work, how can they do any of it effectively?

These are the concerns of many journalists, and thus we have been asking the wrong question all this time. There’s a better question to ask than “Should journalists learn code?”

The better question to ask is, “How can journalists use technology to be better at their jobs and to make their jobs easier?” A follow-up question can be, “How can markup and/or coding languages help journalists be better at their jobs and to make their jobs easier?”

These two questions are intentionally open-ended, and hopefully have a much more positive spin to them. It doesn’t imply changing your job or having to learn MIT-level technology. “Technology” doesn’t have to necessarily mean “code.” Any journalist who’s used Excel or Google Refine has used technology to make his or her job easier.

This question does not have any one right, binary answer, because each journalist will need different technologies for different reasons based on what his or her job is. As a person who makes interactive graphics, it behooves me to stay on top of the best practices for jQuery and JavaScript. But I don’t expect our metro columnists to feel the same need to master jQuery and JavaScript. They might scrape data, clean up spreadsheets or use coding languages with their reporting, because that can make their job easier.

“Should journalists learn code?” makes people defensive. They get their guards up and lose track of the ways they can mine data and use it to make their projects richer.

Here are examples of how I’ve integrated technology into my workflow to make things easier for me:

*When making bar charts in Illustrator, I never manually type the data values for the bars. I copy the chart, and modify that copy so that the text of the values appear. I ungroup that chart and voila, I have labels without me having to risk typing a typo.

*We tend to make a lot of color-coded maps, so I created templates in Illustrator of the maps we use the most: US, Massachusetts towns, Boston neighborhoods, etc. I saved those as SVGs and then turned those SVGs into HTML. That was just a few clicks and typing of lines. The heavy lifting was writing code for a map generator that would allow me to copy and paste spreadsheet data to color-code the maps for me. It took some time, but it paid off. It creates responsive maps that I can easily pluck onto the website, but I can also print-to-PDF those suckers and have the basis for the print version. People who have made vector maps will know that the “old way” of having to select each state/county individually to color-code it was a pain the ass. And fraught with the possibility of introducing error.

*When working on web projects, I almost always use spreadsheets. Lately I’ve used Google spreadsheets so that reporters and editors can make changes. I then use Mr. Data Converter to turn that spreadsheet into a JSON and then write the JavaScript/jQuery that will cycle through that data and write out HTML for me. I do that rather than having to copy and paste things, because it’s ultimately easier and because copying and pasting things into divs leaves the possibility of pasting in the wrong place.

You might sense a theme in those three examples: All three of them are processes I’ve adopted so as to minimize or eliminate errors. Cutting down on errors is good for us, our bosses, our readers and our sources. It’s good for everyone. Using technology to help me do that was worth any of the effort I put into it. It also taught me skills that allowed me to help colleagues in ways I hadn’t been able before.

The web is to our culture now what water is to a fish. If we ignore the basics of how the web works, we do so at our own peril. The more tools we have in our toolbox, the more our projects will benefit. A reporter who pores over public records could do well to understand how to scrape data from web sites. That same reporter could benefit from knowing how to clean up data, either through Excel or Google Refine.

Given the choice between two equally talented writers, I would bet news organizations want people who can do more with the web, not less with it. It’s going to be hard to find a journalism job posting that doesn’t want someone who has at least a basic understanding of general web concepts. No, that does not mean that reporters will need mastery understanding of HTML, CSS and JavaScript to get a job. But if the reporter is going to be working with designers and developers who will take that reporter’s story and turn it into a web presentation, shouldn’t the reporter at least have a broad understanding of what those people do? The reporter doesn’t need to know how to do those other jobs, but should at least know some of the challenges, including that the way a web page looks on a desktop is not necessarily how it looks on a mobile phone.

Reporters are good at researching the processes and terminologies of the organizations they cover, whether it’s a basketball team or a school board. A good tech reporter doesn’t have to be able to build the technology he’s covering, but he at least should be able to know enough to follow along when talking to sources and then be able to explain the important parts to readers. We should have that same mindset in our newsrooms. A reporter and a developer working on a big web project together will have different roles on that project, but they should at least communicate what they need from each other and how they can help each other most effectively.

How it appeared in the newspaper vs. online: Movie psychopaths

Posted on January 26, 2014 by Patrick Garvin

In today’s Ideas section of The Sunday Globe, Boston Globe Graphics Editor (and my boss) Chiqui Esteban put together a graphic examining psychopaths from the movies. The graphic accompanies a Q&A with psychiatry professor Samuel Leistedt, who watched 400 movies, identified 126 psychopathic characters, sorted them into four broad clinical categories, and released his findings last month.
Click the image below to see a larger version.

As people would walk by our desks and comment on how cool the graphic was shaping up to be, we would tell them, “Just wait till you see how this plays online.”

The print graphic was able to include images of just some of the characters, but for the BostonGlobe.com version, we had images for each of the 126 characters in Leistedt’s report. Online, Chiqui created a sortable datable where users could sort between type, gender and primary/secondary. Additionally, he added a slider, allowing users to isolate the time frames.

Additionally, I added a link to a PDF of today’s Ideas page so that users how the piece ran in print. In my gay marriage project for BostonGlobe.com, I’ve been including PDFs of Boston Globe front pages as a way of playing up BostonGlobe.com’s archiving potential. When possible, I’ve tried to include links to past projects, whether those links are to other web projects or PDFs of newspaper pages.

This web version of the psychopaths graphic benefitted from Chiqui’s knowledge from past projects. He has done lots of good web graphics making use of sortable databases that show or hide an array of variables:

As you can see, the web version has a different feel to it from the print version. But that’s OK. That’s going to be true for most graphics that have both print and web components, because of a few variables:

The print versions are constrained by whether the page is color or not. The web version, of course, can appear in a golconda of colors. In this case, the use of colors allowed us to color-code the four types of psychopaths that Leistedt included in his survey. In a quick glance, you can see the variety.
The total print version can be seen at once. But on the web, the interactive can’t be seen all at once, as the user will scroll and/or click to see more.
Whether you’re reading the newspaper in downtown Boston or Newton or all the way out in Maine, you’ll see the graphic at the same size on a page that has the same dimensions. The web version, of course, varies based on the size of your screen.
The print reader can’t sort, click, show or hide any of the information presented to him/her. But the user of the interactive graphic can have all of those options.
Because you can see photos with all 126 characters, the user can get a more complex view of the variety of psychopathy in the movies.
The option to not sort is just as important as the option to sort. This list includes quite a disparate list, ranging from Don Corleone to Chucky to Patrick Bateman to Thelma and Louise to Bonnie and Clyde. That covers a lot of ground, and I think we’re doing a service to the readers by giving them the options to see it all at once while also giving them the options to only see the subcategories. In print, we’d have to make that decision for them. But if they’re on a desktop or a mobile device, they can decide for themselves with their mouse or their finger.

This ran in The Sunday Globe Ideas section, which reports on ideas, people, books, and trends that would be of interest to intellectuals. It covers lots of ground, and has allowed us to do lots of great graphics. One of my favorite graphics for Ideas was a chart I did showing how Harry Potter and other fantasy characters used Joseph Campbell’s hero myth archetypes.

Go check out Chiqui’s graphic here. Check out Chiqui’s portfolio here.

How BostonGlobe.com’s gay marriage interactive graphic came to be

Posted on December 2, 2013 by Patrick Garvin

Today is the first day that Hawaii allows same-sex marriage. The state was the 16th to approve allowing gay marriage, and becomes the 15th to begin performing them. Illinois’ state legislature approved same-sex marriage a few days before Hawaii, but that law won’t go into effect until summer of 2014.

For the last four months, I have been editing and updating this BostonGlobe.com interactive graphic about the history of same-sex marriage in the United States. In short, there’s a sticky navigation that stays with you when you scroll through the timeline, show maps and tallies that change as states allow gay marriage, ban gay marriage or allow civil unions or domestic partnerships. The timeline includes links to archived stories, copies of bills and statutes, and PDFs of past Globe front pages.

The landscape as of 1996:

As of the 2004 election:

As of today, when Hawaii becomes the 15th state to allow same-sex marriage:

This sticky bar is just part of the graphic, of course, as the timeline is what triggers the changes in colors.

—————————

HOW THIS STARTED

I conceived this project right after the Supreme Court ruled on Proposition 8 and the Defense of Marriage Act. In the days that followed, we had many stories about what impact these rulings could bring. These stories usually included maps that more or less looked like this:

Those maps can be tricky to read, because they cram five different types of states into one map:
*States allowing gay marriage
*States allowing civil unions or domestic partnerships, but not gay marriage
*States banning gay marriage by constitutional amendment
*States banning gay marriage by constitutional amendment, but allowing civil unions or domestic partnerships
*The default states, not identified, which have no constitutional reference to gay marriage

These maps are helpful to glean the overall splintering of the issue, and can be used to parse out laws state by state, but are still busier than need be. I wanted was something easier to read, and after talking with Boston Globe AME for Design Dan Zedek, I decided three separate maps would work best. But even then, I thought the map alone didn’t show how much the map has changed over time.

To truly get at the heart of the story, I thought, we needed three interactive maps that changed over time.

It was late June and I set myself an August 1 deadline. I picked that date because that’s when Rhode Island and Minnesota would begin performing same-sex marriages.

So, I set to work on a variety of tasks:
*Researching gay marriage laws and milestones, both on national and state-by-state levels
*Compiling links of past stories on the milestones, both to add to the timeline and to CQ the dates I had found
*Compiling photos from those events
*Building the framework for this responsive graphic using jQuery, JavaScript and CSS
*Testing it to see where it broke
*Refining, revising, refining and more revising

As I revised this, former Boston Globe Graphics Director Javier Zarracina was very helpful in giving me advice on tweaking the design. He was also very accommodating in giving me the time to work on this project.

—————————

HOW THIS EVOLVED

I reached the August 1 deadline.

For the Metro section of the paper that day, Boston Globe Assistant Design Director for News Robert S. Davis conceived a tease graphic that could anchor the page and promote the online graphic:

Once I launched this on August 1, I would update this whenever new developments occurred. The summer and fall of 2013 saw a bunch new developments, of course, as federal agencies and state agencies began changing policies to be inclusive of married same-sex couples. I ended up having more than 100 events on the timeline. Thus, per the suggestion of Robert Davis, I divided the news stories into “key events” and “other.” The page now loads with only the key events, but the sticky nav with the maps includes a link to click that shows all the events.

This project has spawned the most unwieldy-looking Excel file I’ve ever used:

I mean, just looking at that gives me a headache.

—————————

HOW THIS TECHNICALLY WORKS

Using Shan Carter’s great resource, Mr. Data Converter, I turned that beast of an Excel file into a JSON file. The jQuery reads that and appends a main div on the page with a div for each event, including nested divs for the headline, the text, the photos, the captions and the links.

The maps are SVG, taken from a template that Chiqui Esteban created for our department. When the timeline is scrolled through, the color and tally changes are triggered by div IDs when those IDs are near the top of the screen.

—————————

HOW I FIND STORIES FOR THE TIMELINE

The obvious ones — “Illinois to approve gay marriage,” for example — present themselves. The less obvious ones come from the AP wire, Google searches and a great app that has been invaluable in this process.

Zite functions like Google News in that you can have personalized categories for your news feed. Furthermore, it lets you give a story a “thumbs up” or “thumbs down,” like Pandora.

I check Zite throughout the day, particularly on its feed for “Same-sex marriage.” It often has things that are on my radar, but it has also allowed me to find stories that I wouldn’t have known were coming.

Gay news blogs have also been invaluable. I never source a gay news blog, but I will often follow their links to news sources that I can source: The Associated Press and other newspapers. In the same vein, Twitter has also been a good way to find stories. The #gaymarriage hashtag brings up a lot of opinions, but it has helped me find stories in other states.

—————————

WHAT’S NEXT
What’s next is that I’ll keep updating this as gay marriage news continues to happen. Naturally, you’ll need to check BostonGlobe.com to see the updates.

A look at the Boston Globe’s Boston Marathon bombing infographics

Posted on April 22, 2013 by Patrick Garvin

This past week, the graphic artists and page designers at the Boston Globe did some great work to explain what happened at the Boston Marathon and during the manhunt. I was out of town for much of the week, so I only worked on a few graphics. The great graphic work from the Globe this past week was a huge effort by colleagues James Abundis, David Butler, Robert S. Davis, Chiqui Esteban, Kevin Golden, graphics director Javier Zarracina and assistant managing editor Dan Zedek.

Here are some of the graphics produced this past week. To see larger versions, click on any images.

——

Graphics director Javier Zarracina put together this map Monday, the day of the bombings, for Tuesday’s paper. This is not pointed due north, but rather due southwest, for perspective.

——

Here’s a slightly zoomed-out view of the finish area, showing a little more detail.

——

Here’s the area that was treated as a crime scene the days after the blast:

——

For Sunday’s paper, we ran vignettes of people who had been at and near the finish line when the bombs went off. The map shows where they were, and what happened to them after the explosions. This was part of a special “Terror at the Marathon” section designed by Robert S. Davis.

There were several reporters on this, as the gang byline at the bottom shows. It took some coordination to plot who was where, and then to triple-check all of it. David Filipov and Steve Wilmsen served as the main point persons on this, and were key to producing this map.

To read the story, click here.

To see Chiqui Esteban’s interactive graphic of this map, click here.

——

For Wednesday’s paper, James Abundis put together this in-depth look inside the medical tent that was turned into a functional triage unit. Click on the image to see more. Lots of detail in this graphic.

To read the story, click here.

——

As more detail about the actual bombs emerged, James Abundis put together this graphic.

——

How the manhunt unfolded Friday:

——

As details emerged about the Tsarnaev brothers, attention turned to their journey from Kyrgyzstan to Cambridge.

——

Again, it must be said that the great graphic work from the Globe this past week was a huge effort by colleagues James Abundis, David Butler, Robert S. Davis, Chiqui Esteban, Kevin Golden, graphics director Javier Zarracina and assistant managing editor Dan Zedek.

Pi Alley, responsive design and 140 years of The Boston Globe

Posted on March 4, 2012 by Patrick Garvin

One hundred and forty years ago today, on March 4, 1872, The Boston Daily Globe published its first edition.

A lot has changed since that first issue: For starters, the word “Daily” has dropped from the name.

In looking back on the paper’s history and how the newspaper industry has changed, I’m reminded of one of my parts of Boston: Pi Alley. Particularly, I’m reminded of how it supposedly got its name from typesetters.

There are a few stories. According to the web site for the Pi Alley Garage:

As downtown Boston evolved from a residential to commercial area by the end of the 19th century, the name of this alley evolved from the names of local landowners to one more descriptive of the area. Many small restaurants set up shop in the alley to serve the area’s workers. A staple in many of these places was meat pies, often ordered by colorful names such as “Cat Pie” earning the alley the name “Pie Alley.”

In the days that Washington Street was home to most of the city’s newspaper printing plants, many of the printers and typesetters frequented a tavern in the alley called the “Bell in the Hand” In their haste to get refreshments, newspapermen would often drop pocketfuls of mixed up, loose type (called “pi” in the printing business) on the ground, leading to the name “Pi Alley.” Today, the alley continues the tradition of small businesses serving the people who work in the area, as well as the many tourists and visitors.

There is a sign in Pi Alley that repeats those stories almost verbatim. I took a picture one night as photographic proof for a friend who dismissed the newspaper connection as bullshit.

The newspaper is no longer downtown and thus no longer near Pi Alley, but I think of the Globe every time I walk through that neighborhood. Not that I don’t think of the Globe anyway; it’s what brought me to Boston.

It’s a news organization of which I am proud to be a part. I could list 140 reasons why, but that would read like a sloppy love letter written by some infatuated teenager. Indeed, I am infatuated with the Globe, and there are many reasons. The newspaper’s Pulitzer-winning coverage of abuse in the Catholic church was instrumental in exposing abuse in parishes across the country. When I first got here, I would pass some of the reporters who worked on those projects and feel like the freshman walking by Johnny Football Hero, although those reporters were much nicer than Johnny Football Hero.

Late last year, the paper launched BostonGlobe.com, a subscriber-only site. It is responsive, meaning it resizes based on the user’s browser and platform. This responsive design sidesteps the need for individual apps for each device. Whether you’re on an iPhone, a Kindle, a P.O.S. with Internet Explorer or even R2-D2, you can read BostonGlobe.com.

Even if you’re in Pi Alley.

————

To download the first front page, click here.

To see a gallery of Globe pages, click here.

To read Louis M. Lyons’ piece that marked the centennial in 1972, click here.

Coverage of the final Border War basketball game between Missouri and Kansas

Posted on February 26, 2012 by Patrick Garvin

Yesterday was a historic day for fans of Missouri and Kansas, as the two universities’ men’s basketball teams faced off in what is ostensibly the last of their meetups in the historic Border War rivalry. Mizzou is leaving the Big 12 Conference and will play with the SEC next season. Coaches and officials at the University of Kansas have said Kansas will not play Missouri out of conference. KU basketball coach Bill Self even said, “The majority of Kansas fans don’t give a flip about playing Missouri.”

When the teams played their last football game against each other in November, Mizzou won the game and the distinction of winning most of the football games between the two teams.

————

THE LAWRENCE JOURNAL-WORLD
Lawrence, Kan.

The University of Kansas’ hometown paper stripped a photo of victorious fans celebrating the “grand finale” of the “epic border battle.” Not that these fans “give a flip.”

————

THE HUTCHINSON NEWS
Hutchinson, Kan.

————

THE TOPEKA CAPITAL-JOURNAL
Topeka, Kan.

Here’s a close-up of that photo:

So, Bill Self, when you say that Kansas fans “don’t give a flip” about playing Mizzou, what fans are you talking about? These guys seem to give pretty much of a flip.

As they should. Their team was behind and then Mizzou blew a 19-point lead. That’s flip-worthy.

————

THE KANSAS CITY STAR
Kansas City, Mo.

This was pretty fitting play for the Kansas City Star, the biggest daily newspaper between Lawrence and Columbia.

It pains me to see that photo of smiling Jayhawks celebrating. But that’s a great photo, showing a majority of beakers… giving a flip.

————

THE COLUMBIA MISSOURIAN
Columbia, Mo.

What a heartbreaking photo by Andrew Mitchell of The Missourian, showing Missouri guard Michael Dixon on the court after the game. With the Jayhawk mascot in the background, even.

————

THE COLUMBIA DAILY TRIBUNE
Columbia, Mo.

The other daily paper in Columbia picked a slightly less heartbreaking photo, though the disappointment is still apparent.

————

THE ST. JOSEPH NEWS-PRESS
St. Joseph, Mo.

The News-Press does a good job picking above-the-nameplate photos. They used a variation of the Dixon scene. This photo shows more of the Jayhawk mascot than the Missourian photo, but it makes sense: St. Joe is a lot closer to Lawrence than it is to Columbia, so News-Press readers aren’t necessarily reading this outcome as heartbreak.

————

As a Missouri native and Mizzou alum, I can’t overstate how big this rivalry is. Games against KU were as important to Mizzou sports as the “Battlestar Galactica” episodes when you found out the identity of another Cylon. To Mizzou fans, Kansas was the rival among rivals. Kansas is the Cavil among the other Cylons. If the Big 12 were “The X-Files,” Kansas was Cancer Man among the Syndicate, foiling Mizzou’s Mulder and Scully. Watching Mizzou beat KU was like watching the trailer scene in “Kill Bill” when Darryl Hannah gets what she has coming.

I could come up with dozens more pop culture references, but you get the point: This was a big deal, about which we gave a huge flip.

As you can see, I’m pretty hacked off about that Bill Self comment. A friend of mine who used to cover the rivalry for a radio station put it pretty aptly: “He can say that, but I sure don’t ever see Kansas fans making ‘Muck Febraska’ T-shirts.”

Touche.

Florida Times-Union piece brings change — before it runs

Posted on February 21, 2012 by Patrick Garvin

A Florida Times-Union investigation of Jacksonville Transportation Authority bus drivers led to three employees losing their jobs and four bus drivers being suspended. Three of those drivers have been reinstated, though they could still face some punishment.

Newspaper investigations into public agencies result in firings and changes, but in this case, the moves happened in the week before the piece was even published.

Transportation reporter Larry Hannan wrote in Sunday’s piece:

JTA Executive Director Michael Blaylock said he was unaware of the background problems until the Times-Union investigation began. He promised major changes.

“I have to accept full responsibility for this,” Blaylock said. “And the [JTA] board expects me to fix it.”

What there is to fix: The Times-Union investigation found there were JTA drivers who were cited for driving with suspended licenses while continuing to drive buses. Additionally, 258 of 330 drivers had a total of 1,276 criminal and driving violations, including domestic battery, child abuse, driving without a valid license and writing bad checks.

The newspaper’s investigation began after a passenger was run over and killed downtown by a JTA bus in October.

Here’s how the story was played in this past Sunday’s Times-Union. Click for a larger view.

On the inside:

The main Jedi behind this investigation is Larry Hannan, the Florida Times-Union’s transportation reporter. He previously worked at News-Herald in Ohio and the Naples Daily News in Florida.

On Tim Wakefield, oldest active player in Red Sox history

Posted on February 19, 2012 by Patrick Garvin

On Friday, Boston Red Sox pitcher Tim Wakefield announced he’s retiring after 19 seasons in the major leagues, 17 of which were with the Red Sox.

Wakefield got his 200th career win this past season. Of those 200 wins, 186 were with the Red Sox. Sports Jedi Luke Knox put together this chart showing Wakefield’s wins and how he stacks up with other Sox players.

Indeed, among Red Sox pitchers, he’s high on many leader lists, right up there with Cy Young and Roger Clemens.

There’s another distinction that Wakefield earned in the 2011 season: he became the oldest active player in the history of the Boston Red Sox, including the time when the team was called the Boston Americans in the early 1900s. On Tuesday, May 10, 2011, Tim Wakefield was 44 years, 281 days old, a day older than Deacon McGuire was when he played final game for the team in 1908.

It seems like a nitpicky distinction, but it’s one I will remember, because it was the topic of one of my first enterprise graphics at The Boston Globe. Click for a larger view.

When I first got to the Globe in November 2010, I knew I wanted to learn more Flash. And I knew I wanted a project about the Red Sox. And I know that for both, the man to talk to was Daigo Fujiwara, who knew Flash and Red Sox baseball very well. He has his own baseball sites and even hosts a Red Sox podcast.

In talking with him, I mentioned Jamie Moyer, whom I had just seen mentioned in an article as being the oldest player in major league baseball in the 2010 season. A few years behind him in age was Boston Red Sox pitcher Tim Wakefield. I went home and did some research on Baseball-Reference.com, and found that there had been other Sox players who played at the age of 44. But a comparison of birthdays showed that none of them had been as far into 44 as Tim Wakefield. Some time into the upcoming 2011 season, Tim Wakefield would become the oldest Red Sox player in the history of the team.

I told my boss that this might be a fun project to work on in my down time at work when I didn’t have any other pressing projects. That is, if he thought people would be interested. “Almost anything Sox-related gots lets of traction in this town. People will definitely be interested.”

So, using Baseball-Reference.com, I created a spreadsheet. I noted the youngest and oldest player of each season, dating back to the days when the team was The Americans. Additionally, Baseball-Reference determines the average age of every player on the team, so I included that as well. It was a tedious task, going through each page for each season, looking through their rosters. But a pretty cool data table was shaping up.

When finished, I plugged the data into Illustrator’s graph tool, showing the youngest, oldest and average ages per season. The nut graph was that there were no noticeable trends. Carl Yastrzemski played for a bit when he was 44, but was a younger 44.

Throughout the winter of 2011, when I had no more dailies or short-term projects on my plate, I would turn to this project, and how we would present it online. Using the Actionscript from projects I had worked on with Daigo, I created a template for what the Flash version would be. I turned the Excel spreadsheet into an XML file that fed into the Flash file. While the print version had been a static version of the chart, the Flash version would allow the user to roll over each year and see the oldest and youngest players. My boss, David Schutz, suggested I include photos of each player. The aforementioned Luke Knox directed me to some old Red Sox press guides, which is where I found the bulk of the photos.

So, by the end of April, this thing had come together in bits and pieces over a period of several months. On Tuesday, May 10, the day that Wakefield became the oldest active Red Sox player, we ran the graphic in the sports section of The Boston Globe, and this interactive went live on Boston.com.

To this day, it’s one of my favorite things I have ever done, especially at The Globe. Of course, by the time Tim Wakefield was the age I am now, he had already won 56 games in the majors.

Not bad. Indeed, not bad.

Patrick Garvin: Blog

Tag Archives: newspapers

How news outlets covered the State Department’s visa policy change

How to use Mr. Map Generator, a map tool for journalists

“Should journalists learn code?” Well, what exactly do you mean by “code”?

How it appeared in the newspaper vs. online: Movie psychopaths

How BostonGlobe.com’s gay marriage interactive graphic came to be

A look at the Boston Globe’s Boston Marathon bombing infographics

Pi Alley, responsive design and 140 years of The Boston Globe

Coverage of the final Border War basketball game between Missouri and Kansas

Florida Times-Union piece brings change — before it runs

On Tim Wakefield, oldest active player in Red Sox history