I use a few different tools and tricks to make Twitter work for me professionally.
The first thing I do is archive everything I tweet using ifttt.com and Evernote. I think it's useful to have a record of what I've said, just for later personal reference and so I can trace any useful things I might have said or shared and not bookmarked at the time. It used to be very straightforward to link Twitter and ifttt.com (ifttt stands for "if this then that" and is a service that lets you link triggers in one place with actions somewhere else), but sadly Twitter withdrew the ability to join the two directly. For the time being you can still use RSS feeds to suck Twitter content into ifttt. The RSS feed for any given user looks like this: https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=USERNAME, where you replace USERNAME with the obvious. Using this as the trigger it's straightforward to save all tweets to an Evernote note, which records their time and date and the tweet URL.
I also use ifttt to save tweets with certain content as bookmarks in Diigo. There's an option to do something only with RSS feed items that contain certain text, and I have triggers set up for certain hashtags such as #speccolls, #archives, #manuscripts and #libraryhistory. Whenever I tweet something with any of those tags the tweet is saved to Diigo with various tags of my choosing. I include the tag "tagme" so that I can find them all on Diigo later and add further specific tags as necessary. This is, unsurprisingly, the bit I am least good at. I need to make some time every week to tidy them up a bit.
I find interesting #speccolls content mainly from two Twitter lists I've set up: spec colls people and institutional spec colls. Every now and again I'll search Twitter users for appropriate new additions to the lists (as well as adding users I stumble across in every day tweeting). I don't follow everyone on these lists, but I keep the lists open in Hootsuite to keep an eye on what's going on, and retweet (with the hashtags mentioned above) what interests me.
Lastly, I use Scoop.it to draw together links connected to special collections. It's set up to catch my tweets with relevant hashtags (as mentioned above), as well as taking posts from a few special collections blogs. Then I choose the stuff that I want to include, add extra description, select a picture to show and add tags. I do this once a week at the weekend, and it takes surprisingly little time. It's a really good way to review what's been happening recently and to get a chance to read in more depth the things I might have skimmed over previously. Hopefully the links are useful for other people, too! I tried using paper.li to do something similar, but it's a completely automated process. I can see how that's useful in some situations, but for me it means I don't come face-to-face with things in the same way, and I didn't find it was picking up all the stuff I wanted it to. That latter could be fine-tuned with a little effort though, I'm sure.
Showing posts with label diigo. Show all posts
Showing posts with label diigo. Show all posts
Wednesday, 14 November 2012
Thursday, 24 May 2012
Behind the scenes at #cpd23: automating (some of) the registration process
A couple of weeks ago, I asked for thoughts about ways of automating the process of adding new subscriptions to a single RSS feed drawn from multiple sources. This was to try and streamline the process of managing registrations for 23 Things for Professional Development. I seem to have come up with something that works, albeit in a somewhat ungainly fashion, so I thought I'd write it up.
Here's a diagram of what's what. Red lines and text are manual steps done by the cpd23 team, and the blue lines and text are the automated bits. The yellow stars show the outputs that are intended for general use. If you can't see the image for whatever reason don't worry - I explain all the steps below.
The aims of the system are
Benefits of this system:
Here's a diagram of what's what. Red lines and text are manual steps done by the cpd23 team, and the blue lines and text are the automated bits. The yellow stars show the outputs that are intended for general use. If you can't see the image for whatever reason don't worry - I explain all the steps below.
![]() |
| Icons by Mysitemyway Design Team via iconfinder.com |
The aims of the system are
- to generate a tagged list of participants, so that participants and others can find blogs that interest them, based on geographical region and professional sector
- to create a feed of recent posts by participants to show on the cpd23 homepage
- to create a combined feed of all cpd23 participants' posts, to which anyone who is interested can subscribe
- Participants register their blogs using a Google Docs form (embedded into this blog post).The data submitted into a Google Docs form is stored in a Google Docs spreadsheet, which can be accessed and edited.
- Cpd23 team members manually visit each blog that is registered, and (if the link submitted is valid and the blog is a personal cpd blog) they add it to Delicious, including tags for place, sector, year and an alphabetical tag for the first letter of the blog title. (I use the handy Delicious bookmarklet for this.)
- Delicious provides scripts that power the 'recently signed-up' widget on the cpd23 blog, and the participants list on the participants page. There is a limit to the number of links that Delicious will provide (100 at a time), which is why the alphabetic tags are added to the bookmarks: the participants list is powered by a script for each letter of the alphabet.
- An ifttt task takes all new bookmarks added to Delicious with the tag '2012' and submits them to the Google Reader folder 2012. Where possible, Google Reader can automatically extract an RSS feed from the link given.
- Cpd23 team members periodically update the 'Participants posts' widget on the cpd23 blog, which runs using the Blogger blogroll widget. It's easy to add new subscriptions in the 2012 folder from Google Reader.
- Another ifttt task takes all new posts in the Google Reader 2012 folder, and bookmarks them in Diigo, adding the tag 'cpd23feed'. (It could bookmark them in Delicious instead, but I wanted to keep the Delicious account just for links to blogs, and not confuse matters by adding lots and lost of links to posts there).
- Diigo provides RSS feeds of users' tags, so an RSS feed of all new posts from cpd23 participants can be made available. The format of Diigo RSS feeds is: http://www.diigo.com/rss/user/[username]/[tag]
- And that's it.
Benefits of this system:
- It minimizes the number of manual steps - we only need to get involved at two points in the process
- It enables us to offer the 'added value' service of a combined RSS feed, on top of the Blogger blogroll and the tagged Delicious participants list.
- It relies on a lot of services running correctly
- Time lag: the ifttt tasks, and the feeds from Delicious and Diigo update periodically, so new blogs and posts aren't available everywhere immediately. The lag is usually up to an hour.
- Ifttt only recognises new tags, so if Delicious recognises a 2011 participant blog such that we're just adding a new 2012 tag to an existing bookmark that blog has to be added to Reader by hand.
- Google Reader doesn't always correctly find the feed of a link submitted from Delicious.
- The resulting RSS feed, because it's a feed of bookmarks not posts, only shows links and not post text. This really isn't ideal, but it's the best I could come up with.
Subscribe to:
Posts (Atom)



