When it comes to Twitter names, you can of course use variants of your organization’s name, taking on a “Canada” or simply a “CA” to the end of your Twitter handle or using some other variant of your name. The thing to be aware of there however, is that when limited to posting 140 characters a too long Twitter handle can actually get in the way, particularly when others want to retweet your post and therefore include your @TwitterName in their post. (Also note that Twitter currently restricts names to 15 characters).

If your organization is not yet convinced about using Twitter, you may want to make a case for grabbing your name (or a reasonable variant of it), if it’s still available. Even if you don’t get to using it for a few months, you’ll want to secure it.

So what can you do?

Currently Twitter’s policy is to only release names that are registered by someone else if it is a trademark violation (see here for their word on this). They are talking about releasing accounts that have been inactive for at least 18 months at some point, but do not currently have a time frame in place for when they will do this. They, sadly, will not do it on an individual request basis either. (The official inactive user names policy can be found here).

TweetClaims offers a free service that will notify you when your name of choice becomes available (or a pro service for $20/year which will actually text message you as soon as your name becomes available).

Today week they produced the simple but to the point video below, that is making its rounds on the web through people’s Facebook and Twitter feeds as well, in support of the cause.

Will all of this win them $100,000? Hard to say, but the great thing is they had the tools ready to go when an opportunity like this arose. Applying for this $100K was not in their communications or fundraising plan for 2010, but when the Pepsi program was launched they were well positioned to take advantage of it and activate their supporters to boost their chances.

So much of effective communications and capacity building work is about seizing moments that are often not of your organization’s making. Whether it’s an online contest that might boost your profile or land you some serious donation funds, a change in government policy you didn’t see coming, or any other unforeseen event that requires immediate mobilization of your supporter base. Yes, we can all be over saturated with social media and it can be hard to figure out how your organization can really make the best use of the various tools available on a day to day basis, but building up a group of meaningful supporters, and ensuring you have access to channels to communicate effectively with them, can allow an organization to really capitalize on an opportune moment when it comes knocking.

Will Covenant House win $100,000? We’ll find out next week, but if you want to help you can vote here.

The friend in question is David Eaves, who has more trouble answering the question, “What do you do?” than just about anyone I know. He’s a prolific writer, public speaker and consultant who works in three areas of interest: public policy, open source, and negotiation. I never imagined those three things could overlap in such interesting ways until I met David & heard him wax poetic on subjects like open-source community management (bringing negotiation skills to online communities) and Government 2.0.

So there you go: You already know what David’s biggest communication challenge on his website is. It’s demonstrating what he does in a way that makes intuitive sense to people reading his popular blog. The previous iteration of his site was a pretty typical personal blog, with a long sidebar filled with links to this & that, and hardly a self-promotional word to be seen. It was a great demonstration of his brilliant mind at work, but a poor sales tool. (It didn’t even have a Contact page. I’m serious.)

Now, David isn’t really a sales-y kind of guy (in case the lack of a Contact page wasn’t your first clue), and he didn’t want his blog to transform overnight into the website equivalent of a flashing “Buy! Buy! Buy!” sign. He simply wanted to pare down the visual clutter, and make it easier for people who might want to hire him to know how to do that.

I took a simple approach: I interviewed David about the kind of work he does & organized it into three categories: public speaking, writing & consulting. The first two merited their own pages, and the third got folded into the About page (since his consulting services are a bit more amorphous & his consulting clients generally come to him via word of mouth). And the rest of the menu bar was filled out with a page of media appearances (since David appears frequently on television & radio as a commentator on current events) and a “What I’m Reading” page that lists some of the writing that’s inspiring his free-flowing pen (or rather, keyboard). (We hooked up the latter with his LibraryThing and Delicious accounts so that they can be kept up to date automatically, saving him the hassle of updating the page by hand.)

The design process posed an interesting challenge: David really liked his old minimalist, low-key blog design and didn’t want too radical a change. He also didn’t want the site to look too “designed,” because he feels that part of his brand is a kind of approachable, do-it-yourself style that doesn’t jive with anything too flashy or trendy. So I had to really rein myself in and keep it quiet, monochromatic, and simple. (I love simple design, but I didn’t allow myself any indulgences on this one.)

The header is very similar to what he had before, but the menu bar was a new addition, making his “sales” pages more prominent. The sidebar got hugely simplified, to focus the visitor’s attention on what’s relevant & important rather than cluttering up the space with superfluous content.

But where I pushed David to be bold was in two areas:

1. The home page now features a single, complete post. This is rather unusual (though not unheard-of) for a blog, but it really allows the visitor to fully absorb one piece of content before moving on to the next. The previous post is highlighted in a box directly below the most recent post, to encourage further exploration of the site.
2. The pre-footer area is large & prominent, and directs traffic to recent posts, popular posts, the “sales” pages and to David’s various social media accounts (Twitter, Facebook, etc. etc.).

These two design decisions go hand in hand. If the home page housed five or ten posts, the pre-footer area would be virtually invisible, so it wouldn’t merit special attention. But in this case, once a reader has absorbed the content on the page they are reminded of the various options they have to read further. A lot of websites ignore the footer area, but when your site attracts voracious readers (as David’s does), it pays to reward them by allowing them to navigate the site from the bottom of the page as well as the top.

A lot of bloggers wear multiple hats and have little time to build stand-alone websites for each of their endeavours, and I think David’s site is a good example of a middle ground: he shares information about how to hire him without presuming that’s the goal (or desire) of every visitor, while maintaining a familiar blog interface to those who simply want to read his latest post. If a highly promotional website is outside your comfort zone, this site may hold some lessons for you. In particular, I think I managed to convince David to:

• Stop withholding information about your services from people who want to hire you.
• Always, always, always have a Contact page.
• Consider that bringing in a designer can be helpful even if you don’t want anything “designed.”

The purpose of the sprint was to try to teach some folk, like me, how to create and review a patch on the issue queue, in an effort to move things along with the release of Drupal7. I helped out a little by putting together a quick Google Docs presentation on how to install Drush. Drush is a handy command line tool for working with Drupal. One of it’s most popular features is the ability to download and enable core and modules very quickly.

Following that Yi Yang from FCV, with the help of Angie, walked us through the process of creating a patch and then reviewing a patch. I thought I’d post my notes from the session to help others out. I was totally confused about the process prior to Angie being a star and providing a simple list of steps to complete.

CREATING A PATCH

1. Download most recent version of Drupal 7: drush dl drupal-7.x --package-handler=cvs
2. hack core to fix the issue!
3. Go to your Drupal Root directory
4. Make the patch: cvs diff -up modules /path/to/file (optional) > 12345.patch (Compare my local version to CVS version)
5. Upload it to the issue queue
6. Reset your codebase: cvs up -dPC
7. Goto 2

REVIEWING A PATCH

1. Download most recent version of Drupal 7: drush dl drupal-7.x --package-handler=cvs
2. Optional: Download dreditor greasemonkey script
3. Find a patch
4. Download patch to your Drupal root directory
5. Apply the patch: patch -p0 < 12345.patch ('offset" is ok. "fuzz" is ok. FAILED is bad)
6. Test, test, test!
7. Review the code!
8. Post a comment, change issue status accordingly
9. Reset your Drupal code: cvs up -dPC
10. Goto 2

Big thanks to Audrey, Chris for the space and food and to Angie and Károly for their brains :)

Photos

NetSquared Camp is an unconference, and for those who aren’t familiar with that term, it’s an event where the agenda is entirely driven by the participants. So if you show up and speak up, there’s a very good chance that you’ll learn something that’s relevant to you. (You may also end up teaching others, since the participants also lead & facilitate the sessions.)

The list of suggested session topics is both wide-ranging and highly practical, and the organizers have set up a wiki where you can propose your own session ideas.

Perhaps best of all, the ticket price is by donation, with the suggested donation a very affordable $20. By the look of the RSVP list, interest is high, and as with all unconferences, the event’s success will depend entirely on who shows up — so please mark the date in your calendar and spread the word.

Here at Raised Eyebrow we’re very passionate about sharing what we know and building capacity within the nonprofit sector, so we’re very pleased to be a sponsor of NetSquared Camp Vancouver 2010. I’m looking forward to seeing how the agenda evolves.

I have a terrifying confession to make: Until very recently, I didn’t play video games.

That may not be particularly appalling to many of you, but for someone in my industry, that’s pretty embarrassing. Game designers are an integral part of the interactive design community, and I’ve always felt an affinity with them, despite not really knowing their territory. In fact, one of my favourite blogs is written by Clint Hocking, a former creative director at Ubisoft (and high school friend of mine). But I have long been more than a little sheepish about publicly admitting to not having a clue about gaming, aside from what I’ve read on Clint’s blog.

That said, it’s always educational to be late on the uptake with a particular technology; as a web designer I feel like it can help me empathize with the people using my designs who might not spend even a fraction of the time I spend online. I’ve learned a few things from my experience that feel particularly relevant to the work we do with our clients.

First, I had valid reasons for not playing video games until now. I didn’t have access to a console; I didn’t feel like spending money on one until its value had been shown to me; I had seen a lot of games that didn’t appeal to my interests and sensibilities; and perhaps most fundamentally, I was so green that even working the controller was daunting to me — that is, the basics of navigation and control felt uncomfortable and clunky. All of these practical resistance points are also true for many website users; even now when those of us in the industry refer to ourselves as “veterans” and to the up-and-coming generation as “digital natives,” there are still huge swaths of people on the planet who simply don’t need to use the internet to get through their days — as my uncle Ken, a farmer & logger in Northern Ontario, reminds me regularly. For those people, the only thing that’s going to make them interested in the technology is for it to become relevant to their lives.

It wasn’t until I discovered a game that I truly fell in love with (more on that in a moment) that I became invested enough to want to work through my painful awkwardness with the controller and my hesitations about the financial investment. (I haven’t touched on the time investment required, which is significant — this was another fear I had about games, and one that proved well-founded as I have found myself losing all track of time while immersed in the gaming experience.) But once I found a game I connected with, the obstacles fell away and my desire to interact with the game overcame all resistance. Us web designers are fond of parroting the maxim that “Content is king,” but we haven’t always been good at practicing what we preach — this has been a good reminder to me that what’s inside really is what counts. And just as all websites aren’t created with equal amounts of attention to content, neither are all video games.

The game that stole my heart is Assassin’s Creed II, an action-adventure game set in Renaissance Italy. Your character is a young assassin from a noble family who is avenging a betrayal of his family — but it’s actually far more complicated than that. You’re actually a modern-day guy who’s been projected back into the body of this 15th-century assassin, and you’re trying to solve a mystery involving the Knights Templar that traverses centuries. In the process, you travel through the gorgeously-rendered streets of Florence, Venice, and points in between, running over rooftops, climbing church towers, dodging guards, exploring secret tombs, hiding in crowds, stealing treasure, and oh yes — hanging out with Leonardo da Vinci. There are puzzles to solve, swordfights, thieving missions, and even some economic development to manage in a small town where your uncle’s villa is located.

The premise itself appeals to me more than some other games, but the real genius of Assassin’s Creed II lies in its execution. Game designers clearly put an enormous amount of thought into human motivation, and there’s something in this game for just about anyone. The rewards that you earn over the course of the game are a mix of financial (good old-fashioned cash), status (your armour and weapons get progressively better — and pricier — as you progress), relational (you meet new characters & gain access to allies) and intellectual (solving puzzles). It’s been interesting to observe my responses to the various types of rewards and see how they correspond with my real-life predilections. I think the real hook for me has been the mystery-solving part, because it lends an over-arching mission and urgency to the game that I have only ever felt when reading a complex and layered page-turner of a novel.

I honestly never imagined that a video game could make me feel so immersed, and provide such a strong emotional connection. Now that I’ve had this experience I’m far more likely to explore the rest of the gaming world and see what else is out there. But it’s also got me thinking about the factors that shift behaviour and that motivate us — which makes me further resolved to focus my summer reading on those topics. I’ve picked up Switch and Made to Stick (both by Chip & Dan Heath) but I welcome other suggestions.

The CPRS award is a well-deserved honour. Covenant House’s blog is a great model for nonprofits who are looking to create more compelling blog content. Here are a few of the secrets of their success, as we see them:

1. Stories, stories, stories: On the House personalizes youth homelessness and the challenges that contribute to it.  By telling youth stories, for example the story of 13-year John, On the House helps helps educate prospective donors and volunteers as well as building stronger community among existing constituents.
2. Gratitude is infections: Covenant House posts letters they receive from donors (with permission) to their Donor Stories.  In the story Thank You, a donor wrote to give thanks for the call they received during Covenant House’s “thank-a-thon.”  In Feel Good Friday, Joanne wrote to explain how much it meant to her to be able to teach her children about giving to Covenant House Vancouver.
3. Self-promotion is more palatable when it’s surrounded with great content: On the House has a few asks and some promotion mixed in, such as Christmas is Coming.  Coupled with youth stories, it seems only natural that Covenant House should be asking for support to help these kids.
4. Show, don’t tell: Some of the most powerful posts are contributed by the youth Covenant House Vancouver serves: poetry, artwork, and prose tell the reader more than a third-person story ever could.  For example Gratitude for Donated Hockey Sticks, in which two youth thank you letters are reprinted.
5. Share your challenges: The blog content stays interesting because there’s lots of variety. Posts, like Youth Privacy Versus Good Communication, explore internal challenges Covenant House staff face every day, lending a human face to the organization and breaking down barriers between the staffer who’s writing and the reader.

Congratulations to Michelle Clausius and Kristy Hayter who have done an amazing job of bringing On the House to life. If you have minute, check out On the House.  The posts are often funny, informative, inspiring, and/or heartbreaking.  They’re compelling and worth the read.  Kudos to Covenant House for helping to give these talented young writers a voice.  Also, thanks for the important insights on the issues of youth and homelessness.

• What is CKAN?
• CKAN’s API
• The Foundation
• The Build
• Theming
• Homepage Chart

Caching

API calls are expensive. There’s no doubt about that. Particularly when you’re returning large amounts of data. To avoid any issues of the CKAN API being exhausted from requests and to ensure that the site remained responsive, I decided to leverage Drupals caching mechanisms and pretty much cached everything I could, within reason. The Chart, Tag Cloud, Tag lists, Ministry lists, All Packages list and all individual packages are cached. The issue with caching on this site is that if a package gets updated on the CKAN instance, we need to know about that on our Drupal site immediately and then clear the appropriate caches so that the most recent data can be retrieved.

For caching I created a table called ‘cache_ckan’, that stores everything I need. To create this table I used the schema of the existing cache table and put that in my .install file in my module directory.

/**
 * Implementation of hook_install().
 */
function ckan_install() {
  drupal_install_schema('ckan');
}
 
/**
 * Implementation of hook_uninstall().
 */
function ckan_uninstall() {
  drupal_uninstall_schema('ckan');
}
 
/**
 * Implementation of hook_schema().
 */
function ckan_schema() {
  $schema = array();
  $schema['cache_ckan'] = drupal_get_schema_unprocessed('system', 'cache');
  return $schema;
}

Whenever this module is enabled this schema will be run and the table will be created.

What is stored in the ckan_cache table?

There are various items stored in the cache table.

1. The Homepage chart data
2. Tag lists
3. Ministry lists
4. List of all datasets

Let’s take the list of all packages as an example. I covered how I implemented the paging in my previous post. As this list is paginated it’s important that every page be cached to improve the speed of the site. As the paging mechanism is already implemented it’s just a case of creating a cache table entry (ckan:all{page-number}) for each page, and then checking for it’s existence when loading the page.

if(($cache = cache_get('ckan:all'.$page, 'cache_ckan')) && !empty($cache->data)) { // If cached data exists for this page...
	$results = $cache->data;
} else {
	$ckan = ckan_ckan();
 
	$start = 0;
	$items_per_page = variable_get('ckan_items_per_page', 4);
	if($page) {
		// If we're in a page, we need to set where to start the list
		$start = $page * $items_per_page;
	}
 
	// Set the offset to the number of records in
	$offset = $start;
	// Limit to the number of items per page 
	$limit = $items_per_page;
 
	try {
		$results = $ckan->advancedSearch(array('groups' => 'canadagov', 'all_fields' => '1', 'offset' => $offset, 'limit' => $limit));
	} catch (Exception $e){
		return $e->getMessage();
	}
 
	// If the API call worked
	watchdog('ckan', 'Called CKAN API for list of all packages');
    	cache_set('ckan:all'.$page, $results, 'cache_ckan');
}

This method is very simple and very effective. It means the pages load lightning fast and only one page of data at a time is retrieved.

How does the cache get cleared/updated

Datasets/Packages change all the time on the CKAN instance, so how do you make sure that the Drupal site has the most current data. This module has two ways of managing that.

1. Using hook_form to redirect to CKAN

As the CKAN nodes on Drupal are created on the fly and hold very little information, there is really no need to access the EDIT form for these nodes. Whenever an admin user clicks the edit tab on the node, they are automatically redirected to the appropriate CKAN package editing screen. hook_form is called to retrieve the form that is displayed when one attempts to “create/edit” an item. For CKAN content types, the user is redirect to the CKAN instance.

/**
 * Implementation of hook_form
 *
 * Redirect the user to ca.ckan.net package edit screen on edit
 */
function ckan_form(&$node, $form_state) {
  if($node->type == 'ckan') {
  	drupal_goto('http://ca.ckan.net/package/edit/'.$node->body);
  }
}

When the CKAN form is submitted, CKAN then redirects back to the Drupal site and calls a specific URL that tells Drupal to call CKAN again to get the package information and populate the node. To clarify, the process is

1. Redirect http://www.datadotgc.ca/node/X/edit to http://ca.ckan.net/package/edit/{name of X}
2. On save of CKAN Package, redirect to http://www.datadotgc.ca/{special_url}/{name_of_X}
3. Load the node with {name_of_X}
4. Call CKAN to get the (updated) data for Package {name_of_X}
5. Save the node with updated data

Using Cron and an Atom Feed

CKAN provides an Atom feed of recent updates to the Packages. Cron checks this feed every time it runs. If the feed has changed since the last cron run, then we know there have been updates and we clear all of the caches.

/**
 * Implementation of hook_cron()
 *
 **/
function ckan_cron() {
	// Get the md5sum of the current atom feed
	$current_feed = trim(md5_file('http://ca.ckan.net/revision/list?format=atom'));
	watchdog('ckan', 'Current feed md5: '. $current_feed);
	// Retrieve the previously stored md5sum
	$previous_feed = variable_get('ckan_atom_feed_md5', $current_feed);
	watchdog('ckan', 'Previous feed md5: '.$previous_feed);
 
	// If there have been changes
	if($current_feed != $previous_feed) {
		watchdog('ckan', 'ATOM feed has updated, clearing caches and deleting nodes');
		// Flush all the caches
		cache_clear_all('*', 'cache_ckan', TRUE);
  	        // Set the previous feed md5
		variable_set('ckan_atom_feed_md5', $current_feed);
	}
}

Tag cloud creation

I borrowed some code from the Tagadelic module to achieve the tag cloud

/**
 * Build a tag cloud based on the settings provided
 *
 * @return	String	A themed list of weighted tags
 */
function ckan_tag_cloud() {
	// If there is cached data
	if(($cache = cache_get('ckan:tags', 'cache_ckan')) && !empty($cache->data)) {
		$results = unserialize($cache->data);	
	} else {
		$ckan = ckan_ckan();
		$results = $ckan->getTagCount();
		watchdog('ckan', 'Called CKAN API for tag cloud');
		cache_set('ckan:tags', serialize($results), 'cache_ckan');
	}
 
	// Let's sort them by weight first off
	foreach ($results as $key => $row) {
    $tag[$key]  = $row[0];
    $weight[$key] = $row[1];
	}
	array_multisort($weight, SORT_DESC, $results);
 
	// Now let's get the top X number of tags
	$results = array_slice($results, 0, variable_get('ckan_tagcloud_total', 40));
 
	// Now build the tags
	$tags = ckan_tag_build_weighted($results);
	// Sort them
	$tags = ckan_tag_sort($tags);
	// Theme them
	$output = theme('ckan_weighted_tags', $tags);
	return $output;
}
 
/**
 * Theme function that renders the HTML for the tags
 * @ingroup themable
 */
function theme_ckan_weighted_tags($tags) {
  $output = '';
  foreach ($tags as $tag) {
    $output .= l($tag['name'], 'data/tag/'.$tag['name'], array('attributes' => array('class' => "tagcloud level".$tag['weight'], 'rel' => 'tag'))) ." \n";
  }
  return $output;
}

Using the CKAN Search API for all lists

Ok, so what’s this all about? CKAN has some nice API calls like /api/rest/package/PACKAGE-REF that return a list of Packages. However these return the name/id of the Package ONLY. In our case, for our listings, we wanted other data, such as the tags attached to the Package as well as a brief description.

The only way to get this data was to do a search API call /api/search/package and pass some extra parameters, in this case all_fields=1 and department={name of Ministry}.

all_fields=1 tells the search to return all Package fields, not just the name/id; just as is if you called /api/rest/package/PACKAGE-REF.

department={name of Ministry} tells the search to return all packages that have a department of {name of Ministry}. The lovely folks at CKAN added this functionality for us on request.

What does this look like, well it’s pretty simple really. Call the advancedSearch() function. Pass it a few parameters and it returns you all the data you need. Here’s the function itself:

public function advancedSearch($parameters){
	foreach($parameters as $key => $value) {
		$querystring .= $key .'='. urlencode($value) .'&';
	}
	$results = $this->transfer('api/search/package?'. $querystring);
	if (!$results->count){
		throw new CkanException("Search Error");
	}
	return $results;	
}

And here is that function being called for the list of Ministry Packages. The offset and limit are for the paging mechanism:

// Call the function
$results = $ckan->advancedSearch(array('department' => $ministry, 'all_fields' => '1', 'offset' => $offset, 'limit' => $limit));

There’s a lot more functionality in this module, more than I can go through in a blog post, even 5 posts. If you’re trying to integrate Drupal with a CKAN instance and are not sure where to start then please leave a comment and I’ll get back in touch.

Information about the program and the one page application form are available on the Ministry website: http://www.aved.gov.bc.ca/workplace_training_program/welcome.htm

In brief the eligibility requirements are:

• Business or organization (non-profit organizations are eligible) with less than 50 employees (this number would not include volunteers).
• Been operating for more than a year.
• Apply the funding to training which will “help improve productivity” and/or “support the introduction of new equipment, technology or work process”. Your new CMS should be eligible as a new technology which will also help improve productivity.
• You must have not already applied for the grant.

The grant offers:

• Up to $1,500 per employee for training costs
• An organizational maximum of $5,000

Please note that training for Owners is not eligible for the grant, however, we have been unable to ascertain whether or not Executive Directors are excluded (there is no language that says so, and the Ministry has been slow to respond).

The program is in place until January 31, 2011.

Please note, this is a one time grant so if you feel there is other training to which you could better apply this grant, then we would advise you to not apply for the grant for your website training.

Of course Raised Eyebrow can not guarantee that your funding will be approved, but the training we provide to our clients as a part of a website redesign or a new development project does fit into the criteria of the program. We are in no way affiliated with this program, we simply want to make our clients aware of it as we are conscious of the limited resources that many of our clients operate under.

More information:

• Download the One Page Application Form (PDF)
• Questions and Answers on the Ministry website (PDF)

The old editor, used for editing custom HTML templates was pretty picky.  It reminded me of Microsoft Word, in that you might press return once and get a huge gaping hole in your layout. Or press backspace once and the entire design would disappear. Undo was a most used feature.  And often the remedy was to extract the source and fix things up in Dreamweaver, combing through line by line.

That said, I’ve always liked Vertical Response because I like the management interface, including the list manager, and after gaining enormous popularity, they are still offering their service FREE to nonprofits, which is awesome for many of our clients.

So recently I logged into Vertical Response and made a copy of a campaign and got the prompt “NEW: Copy to New Canvas Editor.”  I ticked the box and this opened the newsletter in the new editor and it was a beautiful transformation.

My favourite improvement is the Format drop-down, which allows you to apply paragraph styles defined in the CSS by simply highlighting text and choosing a style from the drop-down.  Prior to this you would have to copy a few characters from a paragraph with the formatting you wanted, paste it in the desired location, and then edit it.  So this was a big improvement.

Another plus is the tick box that allows you to automatically generate a text-based version of the email.  This prevents the need to carry content changes in two versions of the email.

If you are still using the old editor, give the new one a try.