A sneak peek at new products and services being developed by the NPR Digital Media team

API Jan. 7, 2009

Tips and Tricks for Mix Your Own Podcast

We've had a positive reception to the Mix Your Own Podcast tool launched December 18. Here are a few tips to help you get more out of this new feature.

Every Story is an Episode

Our traditional podcasts, launched in August 2005, often combine multiple stories in a single podcast episode. For example, the Economy podcast has episodes that typically contain 4 stories, delivered on Tuesday and Friday. With Mix Your Own Podcast, each story appears as its own episode. Here is a Mix Your Own version of the Economy podcast. This allows you to download the stories as soon as the audio is available on NPR.org, and it gives you more control over what you want to listen to.

However, if you set up a podcast on a popular topic, you may get several episodes per day, so you may want to adjust your podcast software to keep more episodes available. In iTunes, this is done by selecting the Podcast Tab and then clicking the Settings button on the lower left. You may also want to set your software to download episodes more frequently so that you get timely news as soon as it is available. Here are some suggested settings.

Click to enlarge

 

Refined Search

Mix Your Own Podcast finds stories relevant to your interests in one of two ways. First, NPR categorizes stories in many different ways: the program on which the story was aired/published, topics associated with the story, the reporters of the story, musical artists featured in the story, and so on. You can use any of these pre-existing categories to build your podcast. In the Mix Your Own Podcast tool, pre-existing categories will appear as you type in the keyword field. You can select these categories by clicking on them.

Mix Your Own Podcast drop down

 

Second, your podcast can be based on free text searches of the content of stories. Originally, this search was done on any text content found on the web page for the story as well as the audio transcripts for the stories (if available). While comprehensive, this can find stories that are only tangentially related to your keywords. For example, if you entered "Cat" as your keyword, your podcast could include stories where a reporter used the phrase "Let the cat out of the bag." So, we have changed the way text search is used in Mix Your Own Podcast; now, we will only search the title and the summary of the story. This should provide more relevant stories for your podcast. This change took place automatically, so you don't have to make any changes to your podcast to take advantage of it. However, if you liked the full text search, see the next tip.

Mix Tool for Power Users

You can still use the full text version of search to build your podcast via the API Query Generator. Mix Your Own Podcast is built on top of the NPR API. Using the Query Generator, you can fine tune the criteria used to pick stories for your podcast. To use the Query Generator, you will need to sign up for a free API Key. Then, in the Query Generator, go to the "Fields" tab and select "Podcast" as your "Output Format". You can then use the other tabs to customize your podcast to your heart's content.

Click to enlarge

For example, if you preferred the full text search option for building your podcast, go to the "Control" tab, type in your search terms, and select "Full Content of Story" as the "Search Type".

Another example of what you can do with the Query Generator is controlling how your selection criteria are combined. In the Mix Your Own Podcast tool, we return stories that match any of your specified criteria. If you enter several categories, the podcast will contain stories that match at least one of the criteria. In technical terms, we call this a "Boolean Or" API query. Perhaps, though, you want to combine your criteria to get a more focused podcast that contains only the stories that match all of the category selections you have made. For example, if I wanted a podcast that contained only stories that were about both Technology and Politics, I would go to the Query Generator "Topics" tab, check both the "Technology" and "Politics" options, and then go to the "Control" tab and select the "And" option for "Boolean for IDs" option.

Click to enlarge

The end result is my Techlogy and Politics custom podcast.

We would like to hear how you are using the Mix Your Own Podcast tool. If you have created an interesting custom podcast, please post the URL in the comments section of this post.

--Harold Neal

comments () | | e-mail

 
Technology Jan. 5, 2009

The Station Finder Map with Driving Directions is Live on NPR.org

I am happy to announce the re-release of our Station Finder Map, including our Road Trip functionality. This version includes several features worth noting, as follows:

- It allows you to identify local NPR station based on zip code, city/state, station call letters or by broadcasting network.

- It allows you to identify local NPR stations along a driving route.

- It allows you to identify local NPR stations that can be heard at a specific address.

- For stations returned by the finder, you can view the station's coverage map, view more information about the station, and click through to the stations' group page within the NPR Community.

- It is fully supported by our recently released Station Finder API.

We are very excited to have this feature back on the site and hope that it will help our listeners find NPR wherever they may go. In a later post, I will be providing a detailed technical explanation of how the Station Finder Map works.
--Daniel Jacobson

comments () | | e-mail

 
Editorial, Mobile, Social Media Dec. 31, 2008

Help NPR Plan Our Social Media Activities for the Inauguration

The presidential inauguration is less than a month away and the NPR social media desk is kicking it into high-gear to figure out how we can get all of you involved in our inauguration coverage. We're also looking for some techies who can help make it happen.

After our successful VoteReport experiment last month, in which we work with bloggers around the country and invited the public to submit reports on their voting experiences, we're hoping to do something similar for the inauguration. Some of our partners in the VoteReport project, including Dave Troy of Twittervision and mapping guru Andrew Turner, are volunteering again to help re-purpose the VoteReport tools for the inauguration. We've also got some new folks involved, including American University journalism professor David Johnson, and I'm sure others will come on board in the coming days and weeks.

Among the things we've got in mind:

Inauguration '09 citizen journalism iPhone app. Dave and his colleagues created an awesome iPhone app for VoteReport that allowed users to post audio and text reports online and have them plotted on maps, using the iPhone's GPS capability. We're thinking of adding on to this app so that it could also allow users to attach inauguration-related photos or perhaps even short video clips. One idea that was also suggested was to allow an iPhone user to save their reports on their phone and post them later, in case AT&T's data networks are jammed on January 20th. We're also thinking of giving users the ability to submit their email and phone number so NPR reporters can contact them in case we want to use their audio in one of our stories.

Mobcasting. During VoteReport, Dave set up a bank of telephone lines that allowed users to call in and record a voicemail about their voting experiences and have it posted for all to hear online. Given that not everyone participating in inauguration festivities will have iPhones, we want to do what we can to make sure that any phone line could be used by you to file a report from the field.

Twitter and tags. Many of our VoteReport participants used Twitter as their primary method of sending in reports, and we expect that to be the case for the inauguration. We're planning to track all Tweets that are tagged either #dctrip09 (for people road-tripping to DC) or #inaug09 (for Inauguration Day itself). We'll then be able to display all the tweets as they come in. People can also use these tags when they upload to sites like Flickr, YouTube, etc, so we can aggregate that content as well. (Though you shouldn't use the # sign when tagging on Flickr or YouTube - that's just a quirk of tagging on Twitter.) Of course, we'll have to encourage people to use those tags in order for them to work, so we'll need your help getting the word out.

Texting. For people who want to send a text message but don't have Twitter, we hope to have an SMS shortcode available. Fingers crossed.

Maps, maps, maps. Thanks to the hard work of Andrew, Dave and others during VoteReport, we managed to pull together some pretty snazzy maps of all of this user-generated content as it came in. We plan to do the same for the inauguration, particularly in the week leading up to it, so we can track content submissions from people all over the country as they make their way to DC. One thing I'm hoping we can pull off is tapping into all those users with iPhones, since the GPS capability will make it possible to plot each person's route, see how far they've traveled and explore what they've uploaded. For January 20th itself, we're thinking about setting up a hyperlocal map of DC itself, so you can observe everyone's submissions over the course of the day, no matter where they happen to be around the National Mall. This might be the toughest thing to do in the project, particularly for content that's not submitted with GPS metadata. (Using zip codes as geolocators, for example, won't work to well when zoomed in at the street level.) So we may put together a series of DC-specific tags (#ellipse, #washmonument, #lincolnmemorial, #airandspace, etc) to make it easier to identify who's doing what where. Journalism students from American University will also be volunteering to cover the inauguration throughout the city, so we'll be highlighting their activities on the map as well.

Of course, all of this is going to be one big, messy experiment, particularly given the fact that many mobile network providers are forecasting serious congestion and possible outages due to the huge numbers of people using their phones simultaneously. Nonetheless, we think it's worth the effort, given how many people are planning to be involved in the inauguration. There are going to be lots of stories to tell that week, and we want to give you the tools to help share those stories.

Lastly, we'd love your help building this project. We don't have many resources to pull this off, and everyone is volunteering their time to do this. Dave and Andrew are tech geniuses, for sure, but they can't do it alone given the limited time between now and January 20th. So we're looking for some techies who can back them up. Our biggest need is for iPhone app developers who can help them repurpose the VoteReport app and get it in the App Store as soon as possible, so people will be able to install it prior to their roadtrips to DC. We'll also need some Rails, Google Maps and Javascript gurus. If you're interested in helping, please post a comment below and describe what skills you can bring to the table, and we'll be in touch with you soon. If you're on Twitter, you can also send me a note at @acarvin.

As for everyone else reading this post, we'd love your feedback. Does this seem like a worthwhile effort? Is there anything you liked or disliked about VoteReport that we should take into consideration? Are there any specific features or requirements we should try to work into the project? Please let us know what you think.

-- Andy Carvin

comments () | | e-mail

 
Editorial, Social Media Dec. 31, 2008

An Unruly Comment Thread? It's Probably The Trolls

I had a long conversation with a colleague of mine about how easily comment threads can go sour. She said every community manager begins with a pleasant view of their online preserve, a view that values democracy, free speech and an open market place of ideas.

Then, after countless episodes of rants, name calling and non sequiturs (it's people like you who will soon have us living in a Nazi wonderland ruled over by a leader who makes Hitler look like a caring social worker), your ideals are dashed.

Where do these meandering, senseless rants come from? Trolls, people who say just about anything to get a rise out of others. Don't get me wrong, I think for the most part, we have a very strong let-the-community-sort-itself-out ethos. We welcome pointed comments from all points of view. We just ask that they also be constructive and substantive.

Trolls, however, are community members without convictions, arguing a point just to see the other person go red. They turn perfectly interesting threads into festering cesspools of resentment.

We've talked about what to do with them. We've stepped in and asked posters to stop breaking the discussion rules. We've blocked scads of comments, and even a few community accounts. Eventually, we came to the obvious conclusion that the only thing that will move this conversation forward is to ask the community to ignore them.

So, here's a new community rule: Do not "feed" the trolls. We encourage community members to report abuse by trolls. But we also ask that you not engage with trolls in the comment threads. Reacting to their provocations is exactly what they want.

If we see you feeding a troll, we will remove both the troll's comments and your responses.

I messaged with a few community members about implementing this new rule and the reaction was mostly positive. But everyone had one question: How do you define a troll?

I think I've already given some definition to the concept of a troll. But community member Peter Wilbur added a bit more: "I think of it," he wrote in an e-mail, "as someone who doesn't engage others in a discussion, who posts irrelevant comments, or who goes off on the same rant no matter the topic."

In some ways, a troll is like the person at the party who's a little too drunk and picks a fight with everyone. He (or she) is the one who makes things so hostile that everyone avoids a gathering as soon as they see him on the guest list.

Our oft-stated principle is that we want the NPR.org community to be home to a civil conversation that avoids insults, vulgarities and unsubstantiated conspiracy theories. We ask for first and last names during the registration process because we want users to remember that behind our funny avatars and strong views are real human beings.

Trolls tend to hide behind the anonymity of the Internet to make community interactions less human. So, from now on, let's ignore them.

-- Eyder Peralta

comments () | | e-mail

 
Editorial Dec. 30, 2008

Going To D.C. For Inauguration Day? Tell Us About It!

If you're planning to make the trip to the nation's capital to watch President-elect Obama take the oath, we'd like to hear about your plans. No matter if you're coming by car, by foot, by boat or plane -- we want your story. If your inauguration trip has particularly special meaning for you or your community, tell us that, too.

Tell us your plans in the comment area below, or e-mail us at homework@npr.org. We may even contact you to find out more!

Note: This post was originally published on Dec. 19 and then republished on Nov. 3 so that comments could remain open beyond the normal seven-day limit.

comments () | | e-mail

 
API Dec. 18, 2008

API Upgrade : Mix Your Own Podcast and Other New Features/Content

Today we have some exciting new API enhancements to share with you, including Mix Your Own Podcast, a new extension that offers users an infinite number of ways to customize NPR podcasts. Here are more details about Mix Your Own Podcast as well as some of the other features and content that we launched:

Mix Your Own Podcast
Prior to this release, the API offered only streaming formats of our audio content, including Windows Media, Real Audio, and progressive download MP3. These formats were supported by a Terms of Use that required API users to stream the audio from our servers, preventing them from downloading the audio. With today's launch, however, the API now allows users to slice through the NPR.org archive to create custom podcast feeds based on virtually any aggregation (or combination of aggregations) in the API. To learn more about this, go to the NPR Podcast Directory.
Due to various current constraints, the only real exception here is that users will not be allowed to create full-show podcasts of Morning Edition, All Things Considered, Weekend Edition Saturday or Weekend Edition Sunday. However, all stories from these and other programs will be available to create any other podcast mashup in the system.

Station Finder API. With this release, we are also offering access to our Station Finder API. This API will allow users to pass in zip codes, city/state, station call letters or latitude/longitude information, and we will return a list of stations that can be heard in that location. The station results also include key information about the stations, including links to their home page, schedule page, audio streams, RSS feeds, podcasts, station logo and more. Because the system also has station stories from some of these stations (and more of this content will become available in the coming months), you will be able to, for example, search for a zip code, identify the stations in that zip code, then find all of the stories from all of the stations returned. Over the coming months, more station content will be made available through the API.

New Content: Fresh Air and StoryCorps. With this release, we are also making available the full archive of Fresh Air and StoryCorps. For Fresh Air, we will be explosing over 10,000 stories (and counting) dating back to 1993. The StoryCorps offering will include about 200 stories (and counting) dating back to 2005.

Query By Asset Type
Now you can query the API to get stories that contain a particular type of asset. For example, you can filter your query to only get stories that contain images (useful if you are building a slideshow application, for example), or stories with audio, or stories with long-form text. To use this new feature, append &requiredAssets=image to your query string and you will get only stories with images. The other allowed values for this parameter are audio and text. You can combine these filters with a comma-delimited string (&requiredAssets=image,text,audio). This new feature will be added to the documentation and the Query Generator in the next week or so. This feature does not work yet with API queries based on free-text search.

We are excited about this new release and view it as the next step in our continued effort to open up our content to the world.
--Daniel Jacobson

comments () | | e-mail

 
API Dec. 8, 2008

API Usage

As mentioned in my previous post about metrics, we have identified quite a few different usages of the API. These implementations range from incorporating NPR stories on member stations' web sites to widgets created by developers in the public. Below are some of the more interesting or comprehensive uses that we have found.

NPR Member Station Implementations

Minnesota Public Radio Program Archives

North Country Public Radio

Oregon Public Broadcasting

KGOU

SouthEast Public Radio

WAMC

Hearing Voices Widget

KJZZ - NPR Simile Timeline


Public User Websites, Widgets, and Applications

Reverbiage Widget

Axiom Stack iPhone Site

KDE Desktop NPR Audio Player

NPR Backstory Twitter Mashup

RubyNPR - A code wrapper in Ruby

All Tweets Considered

NPR Song of the Day Widget for Mac OSX Dashboard

NPR Audio Search Box FireFox Plug-In

If you have created something using the API and it is not included in this list, please let us know about it by adding it in the comments of this post.
--Daniel Jacobson

comments () | | e-mail

 
Social Media Nov. 25, 2008

'Blade Runner' And The Beatles Define The NPR Community

Some things are predictable. Anyone could have guessed that The Beatles would be among the top-10 favorite bands of the NPR community. (For the record, it's number two, behind Radiohead.)

tag cloud, music NPR Community: Most popular music wordle.com
 

But other things are surprising: The science fiction film Blade Runner is the second favorite after the classic romance Casablanca.

These are the things we know after digging through some of the favorites you listed in your NPR.org profiles. Above is a crude tag cloud of the community's favorite music. Below is another based on listed hobbies. (Click on the image to get an enlarged version.)

tag cloud, hobbies NPR Community: Most popular hobbies. wordle.com
 

We're learning lots -- the most listed area of expertise? Music. Favorite program? All Things Considered. Favorite book? The Hitchhiker's Guide to the Galaxy -- and after the jump we've compiled two top-10 lists. Did any items on the list surprise you?

-- Eyder Peralta

Continue reading "'Blade Runner' And The Beatles Define The NPR Community" »

comments () | | e-mail

 
API Nov. 24, 2008

API Decisions : Metrics

When we launched the API back in July, we had some ideas as to how to gauge success from a metrics perspective. Some of those success measures were around adoption by member stations, others we based on total number of registrants, and others were based on number of requests. That said, having one of the first comprehensive content APIs, it was hard to determine what the actual numbers meant. In our first few weeks, we had over 300 registrants. Was that good? We think so, but it is hard to know. We know that many of those registrants were member stations, many were developers in the public, and some percentage were people who registered simply to take a look at what they just read about in an article somewhere. After one month, we exceeded 1,000,000 requests to the API itself. We were pretty confident that number was a good one, but again, we had no real basis of comparison.

Despite the challenges in figuring out what our numbers mean, we do believe that our usage and registration numbers (published most recently two weeks ago in my last post) are a strong indication of success for the API.

Another challenge is how to actually get our metrics. While our goal is to encourage the re-use of our content, we obviously want some way to measure success. There are several key ways that we have baked into the system to allow us to see how the API is being used. Keep in mind that there is no 100% way to know how many eyes are seeing the content, only how people are implementing it, and in some cases, on which websites, blogs or applications people are seeing the content that came from the API. The primary methods are as follows:

* Since all audio must be served from NPR servers (based on our Terms of Use), we are able to tag the audio accordingly, indicating that the request originated from the API.

* All requests to the API require an access key. This helps us identify trends in usage of the API at the key level, in addition to at much higher levels.

* For each request in the system, we will be outputting a log to our servers that includes the request, the API key used in the request, and the stories/assets that were returned. Over time, we will be able to see trends of use, most popular requests, most commonly distributed stories, etc.

* For any rich-content request to the API (ie. text elements that contain HTML), we have included a 1x1 pixel image that is served from NPR servers (which is an industry standard approach for capturing metrics online) and passes information back to our logs. This will help us identify some of the places where NPR content is appearing when it has been cached by the website, blog or application.

Like I said, this is not the complete picture, but these approaches result in metrics that do give us a good indication as to how the API is getting used and by whom. With that in mind, these numbers only have weight if they translate into real-world consumption of the content. In my next post I will highlight some of the more interesting implementations and usages that we have heard about in the marketplace.
-- Daniel Jacobson

comments () | | e-mail

 
Editorial Nov. 24, 2008

Mining Web Chats for Radio Reporting

A few weeks ago I did a Web chat on whether the government should bail out the Detroit auto business. That 35-minute exercise continues to pay dividends to our listeners on the air. NPR has one of the smartest audiences in America. But, until now, I didn't appreciate what an extraordinary resource they are for reporters like me.

Not only was the chat interesting, but we got over 100 comments. Many of the comments were from people who either had connections to the auto business or actually worked in the industry. (Nothing like talking to people who actually know what you're trying to report on.) :-) So after we did the Web chat, I began contacting some of the people who had commented.

Within a day, I was able to put together a radio story entirely based on sources from the Web chat. These were terrific sources with lots of knowledge whom I would have never been able to find by old reporting methods, like calling around. I also read some of the comments on All Things Considered and Talk of the Nation.

Now, I'm moving on to a story about car dealerships. One of the people who commented on the Web chat runs an advertising company whose clients include hundreds of dealerships. He's putting me in touch with some of his clients, some of whom, I imagine, will also soon be on the air.

In short, the Web chat has been a great way to find new sources and also get in touch with the people who ultimately support our work: the listeners.

-- Frank Langfitt, NPR Labor/Workplace Correspondent

comments () | | e-mail

 


   
   
   
null


 

About Us

Ever wanted to peer under the hood and learn about the inner workings of the NPR website? Have we got a blog for you, then. Here at Inside NPR.org, the NPR Digital Media team will keep you up-to-date on digital products and services we're developing, including social networking tools and our media player. For more info, please see our FAQ and our discussion rules.

 
 

Search Inside NPR.org

 
 

Contact us

Got a question or comment you want to send to us privately? Use our contact form.

 
 
 

Browse Topics

Services

Programs