As you probably know doing ResearchBuzz is not my real job; I love it but “love” and “pays the electric bill” are sometimes quite a ways apart.
However I have been consciously working to become more efficient in my information gathering and writing (you may have noticed that the daily ‘Buzz has been a lot more consistent since last December) and I have been trying to set aside more time to write.
That came to fruition this month when I wrote my first article in a long time. It was for IT World and it’s called How to make a Facebook Page RSS list in 6 easy steps. You can read it here (it’s free):
If you use Facebook for resource gathering, Facebook’s throttling of how many Page posts reach fans can be very frustrating. In the article I outline a way to turn your “Liked” Facebook pages into a set of RSS feeds that you can easily monitor without worrying about what Facebook is going to decide to put in your newsfeed.
I hope you like it. And I hope I get the opportunity to write more articles like this.
Have you heard of IFTTT? It’s available at http://ifttt.com. Pronounced “ift” (like “lift” without the l), IFTTT is a free Web tool that uses channels to easily automate Web tasks. You can get a basic overview at https://ifttt.com/wtf but the premise is really simple — you choose a trigger (like a new item on an RSS feed, someone tagging you on Facebook, someone following you on Twitter, etc.) and in response to that trigger you can choose an action (automatically following a new Twitter follower page, sending Facebook-tagged photos of you to Dropbox, storing your Tweets in an Evernote account, etc.)
At first glance it looks simple and somewhat limited, because there are only so many triggers and actions. But as I spent a lot of time playing with it (I’m using it to automate a bunch of stuff at work) I realized that it could help me solve one of those annoyances that’s been bugging me for a long time, and that is keeping up with The Flickr Commons.
The Flickr Commons is a group of about five dozen institutions and repositories from all over the world that have come together to make some of their collections’ visual content available online without copyright. Group members include the New York Public Library, NASA, the National Archives of Norway, and the National Library of Scotland. So you can imagine there’s tons of great material there.
Unfortunately I couldn’t find a way to look at the latest Commons photographs in toto. I could look at individual institutions and follow them through an RSS feed; I could search Commons content; I could not find a way to look at the latest Commons stuff. I did not want to have to monitor 60-odd feeds. I wanted all the latest Commons content in one place.
IFTTT to the rescue!
IFTTT and RSS Feeds
IFTTT lets you pull content from RSS feeds as one of its triggers, which is probably what I do the most with it, as there are countless RSS feeds out there. Each institution participating in Flickr Commons has an RSS feed of the latest photographs added to its content.
I grabbed an RSS feed from one of the Flickr Commons members and started messing with it. Since an image thumbnail shows up in the feed, I tried grabbing the image and sending it any number of places, like Picasa and Dropbox. I wanted to make the photographs available publicly and I wanted to have an easy way to go to the original image if I saw something I liked and wanted to look at more closely (remember, the RSS feed has only a small image and not the full-sized photograph.) Picasa didn’t allow me to append enough information and Dropbox didn’t allow me to delineate the images enough.
So finally I ended up using Flickr itself — specifically, my own photostream.
Setting Up IFTTT
The IFTTT trigger/response sets are called recipes. So my recipe trigger was new content in one of the Flickr Commons institutional feeds. (I had to set up about 60 recipes, which was the most tedious part of this whole business.) If you want to play along at home and have an IFTTT account, I shared my recipe at https://ifttt.com/recipes/52593.
The action was to take the content from the institution’s feed and put it in my own Flickr photostream. But that wouldn’t be enough because there’s only so much good I’d get from a random image – I’d also want to know where it came from and where I could go to see larger versions of the image. So in addition to just moving the image over, the recipe also puts the source of the image and a link back to the original image in the description. There’s also an option to create new tags for each image as well — remember that because I’m going to come back to it later.
The Harvest on My Photostream
So I set up umpty-zillion recipes based on RSS feeds from Flickr Commons institutions let them run, and within a day I started having images automatically post to my Flickr photostream at http://www.flickr.com/photos/taracal/.
The URL in the description is not clickable from the galley page, but it is clickable on the individual picture’s page.
So what do I have now? Now I have a constantly-growing group of photos from the Flickr commons as my very own photostream, but in addition I have an RSS feed of all the latest content posted to Flickr Commons (via my account’s RSS feed on Flickr.) And with IFTTT, I can take that feed and do something else with it. In this case, I set up IFTTT to send me an alert via the iOS notification Pushover whenever the RSS feed updated. This came in handy when a picture of Queen Elizabeth came through on my iPhone and I was able to immediately text it to my anglophile friend Dee.
I had no hesitation in setting up these RSS feeds of visual content to aggregate on my own photostream because the Flickr Commons is just that — a Commons — and violating copyright was not a concern. Besides, I made sure that each description sourced the original image and linked back to it, trying to ensure that nobody thinks I’m the creator/keeper of these images.
If the aggregation of thumbnails, with clear attribution and links back to original content, could be considered fair use, I would really like to go further with this. There are so many institutions using Flickr. If you do just a simple people search for State Library you’ll find all kinds of goodies.
With IFTTT you could take the RSS feeds of the institutions in which you’re most interested and start a flow of thumbnails to your own Flickr stream, but more than that, you could give all pictures from that group of institutions the same tag and start creating your very own repository.
For example, I could go through Flickr’s people search and find North Carolina organizations — the NC State Archives, the Museum of Natural Sciences, the North Carolina State Library for the Blind, etc. I could set each of these up with an IFTTT recipe to send new content to my photostream, and tag each item as it’s added with not only the photo’s description but also with a unique tag of my own — maybe NCGROUPRB (something that probably isn’t replicated elsewhere on Flickr.) Then I just let it run. What I’m doing here is creating my very own Flickr subset from lots of different sources, in this case photographs from North Carolina organizations and institutions. (You could do this with any other topic you can imagine that can be found in the people search — state fairs, national museums, or even cooking schools!) When searching this collection, I could use incredibly general search queries (school, food, etc.) along with my unique tag and have success in finding images relevant to my context because I had narrowed down the searched pool of images in advance via the IFTTT image aggregation.
This setup isn’t perfect — IFTTT limits how much you can extract from a given RSS feed — but I’m having a lot of fun with my newly aggregated feed of Commons content and looking at a lot more pictures. If you find this useful and end up doing your own Flickr mini-content-curation project, let me know in the comments!
If I never update this blog again, blame Sunlight Labs. I read their latest blog post and now I can’t… stop… playing… with… Scout.
Scout, at https://scout.sunlightfoundation.com/, is an alerts service which gives you updates on federal and state legislation, as well as speeches in Congress and Federal regulations. Federal legislation I’ve found all sorts of tools for, but when I was poking around for a place to get state legislative updates last year, I had a heck of a time — it was pretty much hit and miss and seemed to depend a lot on what state you’re in.
Scout starts out looking like a search engine so I did a simple search for “solar power”. The results page lets your break down your search results into several sections: bills in Congress, speeches, in Congress, state bills, and federal regulations. Choosing one of these allows you to do a little more delineation; for example, choosing to look at bills in Congress lets you choose what stage they’re at (passed, vetoed, etc.) and choosing state bills allows you to specify particular states.
Information in the search results is minimal; looking at solar energy bills in Montana provides brief information on the three bills that were returned, but additional information and the full text of the bill is no more than a couple clicks away. Similarly, searching for the number of times the word goofy has been used in congressional speeches (apparently former senator Byron Dorgan likes that word a lot) provides a brief context of the speech in the search results but the original speech is only a click away, with additional clicks to the source and the original GPO transcription with all its Green Acres references intact.
So the searching is good but the alerting is great. To use alerts you’ll need to have an account (it’s free) and if you want to get SMS alerts you’ll have to verify your phone number (Scout sends you a text and you enter the verification code from the text.) To set up alerts just do your searches. For every search result you’ll see a blue “Create Alert” button above the search results. Click that to save an alert.
All your alerts will be gathered in one spot, and you can edit them there to specify whether you want your alerts by text, e-mail, or not at all.
I immediately set up several alerts for state legislation; hopefully this’ll be easier for me to keep up with what’s going on in my state than what I’m using now, which is a couple of push notifications and lots of manual review. Thanks, Scout!
In what observers (well, me anyway) are calling a long-overdue move, Twitter has announced (http://blog.twitter.com/2012/07/simpler-search.html) several enhancements to its search engine. One of them has me a little leery, one of them has me absolutely thrilled, and the other ones I’ll have to try. Here’s a rundown on what’s new.
Search Autocomplete: According to Twitter, autocomplete is supposed to make search suggestions for you as you type. Which sounds great (and I love to get an idea of what people are searching for) except I couldn’t get it to work. I tried two different browsers (Chromium and Firefox) and made sure I was logged in, and nada. Even typing things like Justin got me no auto-complete suggestions. Maybe it’s not available at the moment?
Spelling Corrections: This is the one I’m leery about; Google already “corrects” your spelling even when you’re properly spelling what you want! I did a search on Twitter for appple; Twitter gave me lots of results for apple but also included at least one result for appple; as long as what I actually searched for is still in there I’m fine with it. (Interesting trick: looking at the “Top” results gave me tweets for both appple and apple. Looking at “all” results gave me tweets only for appple. All = Verbatim?)
Results with Real Names and User Names: Here’s the way Twitter describes it: ” When you search for a name like ‘Jeremy Lin,’ you’ll see results mentioning that person’s real name and their Twitter account username.” That’s nice. But I also like that I can do a search for “Museum” and get Museum Twitter results at the top of the search page, something I don’t remember from before. It also worked for the phrase “state library,” which is going to come in handy because of…
Restricting results to people you follow: You can now get results just from people you follow. Which means I can do my searches for things like database and archive and collection and not get a pile of spam. And oh look! This search supports special syntax, so I can search people I follow for filter:links and just see what people I follow are pointing to without the chatter. Aahhhhhh. Now if could only get that sent to me once a day as a list….
Of course, with that in mind I need to find more great folks to follow. Got a suggestion? Leave a comment or send me an e-mail!
This weekend the first annual Hopscotch Music Festival is taking place in Raleigh. Over a hundred bands, parties, and general downtown rocking out for four days.
I work for one of the sponsors so I wanted to keep track of the festival, pictures of the events, news coverage, and so on. To do so I set up several information traps that I’ll use just through this weekend and then expire. It was an interesting exercise so I wanted to share with you what I did.
There’s already been plenty of news coverage so I knew there would more during the festival. Hopscotch is an unusual enough word that I was able to use the query hopscotch location:nc at Google News and get almost all relevant results. (Remember, the location: syntax restricts results to media within a specific state. I might miss a few items, but on the other hand I’ll get really targeted results.) I picked up the RSS feed and put it in my reader.
Finding relevant blog posts was a bit tougher. I tried Technorati but a search for hopscotch got only six results total and most of them were not relevant. Searching Google Blogs for hopscotch found a lot more content and a little spam; still, the results were clean enough that the result feed went in my reader.
I couldn’t find a search interface for Bloglines, and Blogdigger had no results at all. Icerocket had plenty of results but there was a serious relevance problem. Narrowing down my search to “Hopscotch Music (I didn’t want to add another word as I wasn’t sure if people would refer to it as “Fest” or “Festival”) brought me a good set of results, and I added that RSS feed to my reader.
Hopscotch has tags devoted to it and of course you can do some geographic searching with Twitter. But despite the fact that I can do some narrowing of my Twitter search, I did not want to trap for just the hashtag #hopscotch. If I did that, I would be flooded with a lot of less-useful content, like tweets for people who arrive at venues, or leave, or so forth. So I decided to trap for multimedia content.
Searching for #hopscotch yfrog and #hopscotch plixi and #hopscotch twitpic will clue me in to pictures taken at the festival and quickly put online. Those queries went into my RSS feed reader after I saw they were already producing good results even though the festival started just this afternoon. (I’m writing this Thursday night.) I’m testing another query, hopscotch http -yfrog -twitpic, to pick up all the tweets with links that aren’t pictures, but at the moment those are mostly Foursquare checkins.
(These traps are only going to be active for three days, so I probably won’t abandon any of the traps before the end of the festival. But if I were building these traps to keep them for a long period of time, I’d pay careful attention to what my RSS feeds were producing and quickly dump any that were providing spammy or useless results. I only have so much time to review what I’m picking up.)
Looking at the pictures on Twitter reminded me that Flickr might be getting images of Hopscotch as well. A test revealed that hopscotch was currently working okay as a search term, with lots of band pictures and only one irrelevant result. So that went in the feeder too. (For information on how to make keyword-based RSS feeds for Flickr, check out my article.)
That was Quick
Setting up this set of traps only took about twenty minutes. I skipped a lot — didn’t get into discussion forums, for example, didn’t try to trap Facebook, and didn’t expand my news story search beyond what Google offers. But I feel this’ll give me a good overview of what’s going on a feedback from a wide variety of attendees. I’ll try to do a followup article next week about what I found and what I’d do differently next time.