NOTE: This list represents only the pieces I authored. My colleagues Adam Glenn and Michele McLellan wrote several other posts. You can find everything on the News for Digital Journalists blog.

Most important post: March 14: Pew research points to mobile opportunities for local news, info. There’s a lot to learn from in this Pew report. I spotted these strategic implications:

• Attract more young people to your news brand. Tomorrow’s audience has to come from somewhere. The research indicates that news orgs could promote long-term growth of their local news market via mobile offerings.
• Native apps not really such a great revenue strategy. In fact, Pews numbers paint a pretty dismal picture for trying to generate much revenue from getting people to pay for content. Now, if news apps became more service-oriented, that could change the picture…
• Embrace the spectrum of mobile technology, not just smartphones. OK, Pew, didn’t look at this directly, but when you look at their numbers you can see that feature phones are a big part of the picture. And the news business mostly thrives based on audience size. Ignoring feature phones means leaving money on the table and alienating potential allies.

Other posts…

Feb. 22: Disaster news prep: Google Person Finder. I wrote this after the Christchurch, NZ earthquake but before the big Japan earthquake/tsunami. Goal here is to tell news orgs how they can leverage this tool by embedding it in their own pages. Also, if your region gets hits by a disaster, I tell how to ask Google to spin off a new instance of Person Finder. You can spin off your own instance, but it’s better to see if Google will do it first to avoid confusion.

Feb 28: Engaging tomorrow’s news audience today: Report. Research from the Newspaper Association of America takes a closer look at sub-groups within the youth demographic for news audiences. I’d like to see more research like this. More importantly, I’d like to see some evidence that news organizations are actually using this research in their strategies.

March 8: Knight Community Info Toolkit: Help make your community stronger with better info. Summary of a new planning tool for community activists. This is the kind of effort I’d love to see news organizations get involved in, but it’s interesting that the toolkit is not really intended for news organizations.

March 9: Knight names new VP of Journalism and Media Innovation: Michael Maness. Pretty significant shift of leadership at the Knight Foundation. It’ll be interesting to see what direction Maness wants to take Knight’s programs. Especially now that the Knight News Challenge is in its fifth and possibly final year. (It was originally intended as a five-year contest program.)

March 11: Texas Tribune, Bay Citizen win Knight grant to build open-source news platform. I’m curious about this project — especially whether it will build upon existing open-source platforms (hopefully WordPress rather than Drupal, if so), and what kind of mobile functionality, if any, it will include.

March 17: New York Times launches paywall — and why most news orgs shouldn’t. Most people who watch the media business are pretty down on this strategy. Frankly, I’m also pessimistic — although I suspect the Times may be able to pull it off, for a while, without really hurting its audience size or search visibility. But there are so many loopholes, and so few real benefits to paying subscribers, that I’ve got to wonder why they’re even bothering with this. It seems almost like a philosophical exercise. They should be putting these resources into offering services that they can sell, if you ask me. As for the vast majority of news orgs: Don’t try this at home. The Times is a very special case.

March 22: Why “data journalism” is good for the news business. My UK colleague Paul Bradshaw wrote an excellent analysis of the many ways that data-focused content (such as interactive databases) and services (such as APIs of metadata from a news org’s content) can help build a news business.

Today at the Knight Digital Media Center, I wrote about new advocacy/awareness tool from Sunshine Week: a model proclamation that news orgs and other activists/advocates can customize, publish, and challenge specific government officials and agencies to adopt. It gets into specifics, at least to some extent.

See: Sunshine Week shows how to call for open government

It’s a good start, but here’s what else I’d love to see from Sunshine Week…

I’d really love it if they called for no more pdf-format publishing of government documents with arcane meaningless titles and no useful metadata. (City of Oakland, are you listening? Nah, I didn’t think so….)

…OK, personally I’m skeptical of the value of proclamations, even ones that call for specific actions. What I’d really love to see from Sunshine Week is an online interactive database where people and groups could file public incident reports about specific examples of government opacity or obstructionism, so we can track this issue better.

See: Video will dominate mobile data traffic by 2015, forecast says

The catch: Thank to lax net neutrality rules passed by the FCC last December, wireless carriers are free to charge users extra for any kind of mobile content they choose — even if it’s available for free via wired connections.

I wrote more about this for the Knight Digital Media Center at USC site: US Census upgrades American FactFinder tool, new data coming soon | Knight Digital Media Center.

singlesmap

*Livestock statistics not included

Seriously, this interactive singles map is fun. I just wish there was a poly version!

Thanks to Allan Jenkins for the pointer.

Recently I wrote about how a Los Angeles Police Dept. geocoding data glitch yielded inaccurate crime maps at LAPDcrimemaps.org and the database-powered network of hyperlocal sites, Everyblock.

On Apr. 8, Everyblock founder Adrian Holovaty blogged about the two ways his company is addressing the problem of inaccurate geodata.

1. Latitude/longitude crosschecking. “From now on, rather than relying blindly on our data sources’ longitude/latitude points, we cross-check those points with our own geocoding of the address provided. If the LAPD’s geocoding for a particular crime is significantly off from our own geocoder’s results, then we won’t geocode that crime at all, and we publish a note on the crime page that explains why a map isn’t available. (If you’re curious, we’re using 375 meters as our threshold. That is, if our own geocoder comes up with a point more than 375 meters away from the point that LAPD provides, then we won’t place the crime on a map, or on block/neighborhood pages.)
2. Surfacing ungeocoded data. “Starting today, wherever we have aggregate charts by neighborhood, ZIP or other boundary, we include the number, and percentage, of records that couldn’t be geocoded. Each location chart has a new “Unknown” row that provides these figures. Note that technically this figure includes more than nongeocodable records — it also includes any records that were successfully geocoded but don’t lie in any neighborhood. For example, in our Philadelphia crime section, you can see that one percent of crime reports in the last 30 days are in an ‘unknown’ neighborhood; this means those 35 records either couldn’t be geocoded or lie outside any of the Philadelphia neighborhood boundaries that we’ve compiled.”

These strategies could — and probably should — be employed by any organization publishing online maps that rely on government or third-party geodata.

Holovaty’s post also includes a great plain-language explanation of what geodata really is and how it works in practical terms. This is the kind of information that constitutes journalism 101 in the online age.

(NOTE: I originally published this post in Poynter’s E-Media Tidbits.)

According to Nieman Lab, “Media Cloud is a massive data set of news — compiled from newspapers, other established news organizations, and blogs — and a set of tools for analyzing those data.

Here’s what Berkman’s Ethan Zuckerman had to say about Media Cloud:

Ethan Zuckerman on Media Cloud from Nieman Journalism Lab on Vimeo.

Some of the kinds of questions Media Cloud could eventually help answer:

• How do specific stories evolve over time? What path do they take when they travel among blogs, newspapers, cable TV, or other sources?
• What specific story topics won’t you hear about in [News Source X], at least compared to its competitors?
• When [News Source Y] writes about Sarah Palin [or Pakistan, or school vouchers], what’s the context of their discussion? What are the words and phrases they surround that topic with?”

The obvious use of this project is to compare coverage by different types of media. But I think a deeper purpose may be served here: By tracking patterns of words used in news stories and blog posts, Media Cloud may illuminate how context and influence shape public understanding — in other words, how media and news affect people and communities.

This is important, because news and media do not exist for their own sake. It seems to me that the more we learn about how people are affected by — and affect — media, the better we’ll be able to craft effective media for the future.

(NOTE: I originally published this article in Poynter’s E-Media Tidbits.)

You can upload your dataset to Many Eyes and apply various visualization types to that data — kind of like using filters on images in Photoshop. You can customize your display.

Many Eyes is a useful tool not just for publishing information, but also for analyzing information to see what the story might be, or where the anomalies are.

Here’s an interactive visualization I just created:

Earlier on Poynter’s E-Media Tidbits I wrote about how you can use some Many Eyes tools like word tree for document analysis.

Many Eyes meet the New York Times: On Oct. 27 NYTimes.com launched its Visualization Lab, where anyone can create and share visual representations of selected datasets and information used by Times reporters.

Many Eyes is just one of the projects from IBM’s Visual Communication Lab.