Not Every Child Is Secretly a Genius, an essay in The Chronicle of Higher Education by Chris Ferguson, is an excellent bubble-bursting treatise on the “multiple intelligences” education theories of Howard Gardner that have been so much in vogue over the last 20 years as to have become accepted as truth within the educational establishment.

As much as I’m not sure that Ferguson is completely right, I’ve never been altogether sure Gardner’s theories represented more than a hope that our minds work differently than they do. And this is the crux of Ferguson’s argument about multiple intgelligences:

It’s “cool,” to start with: The list-like format has great attraction for introductory psychology and education classes. It also seems to jibe well with the common observation that individuals have particular talents. More important, especially for education, it implicitly (although perhaps unintentionally on Gardner’s part) promises that each child has strengths as well as weaknesses. With eight separate intelligences, the odds seem good that every child will be intelligent in one of those realms. After all, it’s not called the theory of multiple stupidities.

It would be wonderful to live in a world where we were all equally capable of achieving greatness in something. Indeed I’d say that’s the bedrock of my educational philosophy to date, and a good part of the underpinning of how I approach the world.  But it’s good to be reminded that it’s a relatively recent model for intelligence, and one that might be based on a Utopian dream more than a practical reality.  As Ferguson writes:

That is the root of the matter. Too many people have chosen to believe in what they wish to be true rather than in what is true. In the main, the motive is a pure one: to see every child as having equal potential, or at the very least some potential. Intelligence is a fundamentally meritocratic construct. There are winners and there are losers. A relative doofus may live a comfortable life so long as his or her parents are wealthy. However, clawing one’s own way out of abject poverty is best achieved with a healthy dose of both motivation and “g.”

As much as it pains me, I’ve a feeling Ferguson might be right about all this, and I’m left with the question: what to do about the doofuses?

(Oh, and just to be clear: my child is secretly a genius)

As proof that there is an organization for everyone: Canadian Association of Ukrainians from Former Yugoslavia. Thanks to my father for the pointer.

In my old homebrew blogging system, I built in a function that let me enter references to articles in the Rukapedia but just surrounding an entry’s title in double square brackets: when the post was displayed to the public, the link would automagically get rewritten to become an HTML hyperlink. 

I didn’t want to have to go back and edit these posts and manually insert HTML links for Drupal, so I solved the problem by leaving this as they were and writing a simple Drupal Input Format filter called wikilinks.  It turned out to be really easy to do this.  Here’s how.

First, I created a new directory under the sites/all/modules directory in my Drupal installation called wikilinks.  Inside that directory I created two files: wikilinks.info and wikilinks.module.

In wikilinks.info I put the following information describing the module:

name = Wiki Links Filter
description = A filter to convert wiki links into HTML links to the wiki.
core = 6.x

 In wikilinks.module I put the following PHP code:

<?php
// $Id$

function wikilinks_filter($op, $delta = 0, $format = -1, $text = '', $cache_id = 0) {
  switch ($op) {
    case 'list':
      return array(0 => t('Wiki links'));

    case 'description':
      return t('Converts old-style wiki links to HTML hrefs to wiki.ruk.ca.');

    case 'prepare':
      return $text;

    case "process":
      $text = preg_replace("/\[\[(.*?)\]\]/","<a href=\"http://wiki.ruk.ca/wiki/$1\">$1</a>",$text);
      $text = str_replace("[indent]","",$text);
      return $text;

    default:
      return $text;
  }
}

The heavy lifting is done in this line:

$text = preg_replace("/\[\[(.*?)\]\]/","<a href=\"http://wiki.ruk.ca/wiki/$1\">$1</a>",$text);

The text that gets passed to the filter gets scanned and all instances of two square brackets followed by any number of characters followed by another two square brackes gets replaced by a hyperlink to http://wiki.ruk.ca/wiki/ followed by the term that was surrounded.

Once these two files were in place, I just visited Administer > Site Building > Modules, added the Wiki Links module, and then Administer > Site Configuration > Input Formats and clicked the Configure links for the “Full HTML” input format and checked the box beside “Wiki Links.”

Once all this was in place, all the old-style encoded links to the Rukapedia worked fine, with no conversion needed.

Oliver and I drove up to Rollo Bay this morning to take in the last day of this year’s Rollo Bay Fiddle Festival. We arrived just in time for the “Tune Writers Circle” in hall at Noon, and were entertained by the fiddle, banjo, piano and mandolin stylings of players like J.J. Chaisson, Brent Chaisson, Elmer Deagle, Anastasia DesRoches, and Mike Hall.

At 2:00 p.m. the afternoon concert started, and we stayed around for Courtney Hogan, the Queens County Fiddlers, Tim Chaisson, and another round of Mike Hall, who was the real highlight of the event for me.  Born in Saint John and honed in Cape Breton, Hall is a sharp player who’s obviously going places. We picked up his CD, A Legacy Not to Be Forgotten, and will look for him again.

By 3:00 p.m. Oliver was flagging — an 8 year old can only take some much fiddle — and so we took the long way home, up to Naufrage and along the north shore and over to Mount Stewart where we stopped in at The Trailside for a piece of cake and a chocolate sundae and a chat with the Doug Deacon.

All of this was part of the 2009 edition of “trying not to completely miss summer on Prince Edward Island,” an effort that, so far, we’re doing pretty good at.

After I succeeded at getting my taxonomy into Drupal, my next task was to get 10 years worth of blog posts from my old homebrew blogging system into Drupal too.  In this regard the Drupal module Node Import was of great help, but a little massaging on the old posts was required before I actually did the import, for which I wrote a PHP script.

My script was quite simple: it took the existing blog posts from a MySQL table, did the massaging, and output them as a vertical bar-delimited ASCII text file ready for Node Import.  The “massaging” amounted to the following:

• I stripped the HTML tags from the post titles – just used strip_tags on this field.
• I escaped the vertical bars inside posts themselves – just changed all instances of | to \|.
• I created a “Taxonomy” field with a double-vertical bar-delimited list of taxonomy terms – for example Internet||Weblogs||Firefox.

Once my script ran on my archive of posts, I had an ASCII file that looked something like this:

"5487"|"2009-05-01 11:11:34"|"Post Title"|
<p>This is the post text in HTML.</p>"|"Internet||Blogs||Firefox"

The first field is the unique record ID on my old system, which I wanted to preserve in Drupal to make referencing old posts easier. The final step, once I had the ASCII file exported, was to run it through iconv to convert the character encoding from ISO-8859-1, used in my homebrew system’s tables, to the UTF-8 used by Drupal:

iconv -f ISO-8859-1 -t UTF-8 drupal-export.txt > drupal-export.utf8.txt

Now I was ready for Node Import.  In Drupal I went to Administer > Content Management > Import Content, clicked “New Import,” and then walked through the wizardy steps to define the import.  Some note on each of the steps:

• Step One
  
  • I selected “Story content type”, as this was the content type I decided to use for blog posts.
• Step Two
  
  • Remember that you have to “Browse” for the file, then click “Upload” to actually upload it before you go on to the next step.
• Step Three
  
  • Delimiter Separated Values
    
    • Record Separator Newline
    • Field Seperator Pipe (|)
    • Text Delimiter Double Quote (“)
    • Escape Character Backslash (\)
  • If you make the above selections and then click on the “Reload Page” button, you can see a preview of your import in the “Sample data” section of the page, and can get a quick visual indication of whether you selected properly.
• Step Four
  
  • I mapped each of my export file’s fields to the appropriate Drupal field.
  • I’d previously added a CCK field called “Previous Number” to hold the original blog post’s record number.
• Step Six
  
  • This is the step where you define the field settings you wanted applied to every post where no value appears for a given field in your export file.
• Step Seven
  
  • This is the most useful step of all: it gives you a preview of 5 imported items as they will appear once imported (and you can change “5” to a greater number using the “Number of records to preview” drop-down list at the top).  If posts don’t look right here, then they’re not going to look right when they import, so check the preview carefully for possible glitches.
  • If you find problems that require creating a new version of the ASCII file export, you can just click on the module’s “Back” button (not the browser’s) to go back to Step Two and upload another file; all the other choices you’ve made on on steps are remembered.

It took me about an hour of back-and-forth, looking at the preview of the import in Drupal, making tweaks to my export, uploading another version of the file, previewing again, and so on, to get things working properly; this was mostly working around peculiarities in posts on my old system, and didn’t have much to do with Drupal itself.

Once I was ready to launch the import itself it went quite quickly, and was done in under 30 minutes.  The result: more than 5,000 old blogs posts, mapped to a hierarchical taxonomy, in a new home in Drupal.

About a decade ago, back when Catherine and I had no Oliver, and thus had surplus time on our hands, we bought a canoe.  It is a nice canoe – nothing extravagant, but enough to knock around in the waterways of Prince Edward Island in.  We did not canoe extensively during our footloose time – a few trips in the West River, a rather bizarre attempt, with my brother Steve, to navigate the Morell River, and an unfortunate outing into the North River in the area surrounding a sewage outflow.  But we always had high hopes.

Those high hopes were diminished somewhat when Oliver arrived and our surplus time disappeared.  When Oliver was 3 years old we made some attempts at resurrecting our canoe lifestyle, but our initial personal flotation device trials resulted in a face-down-in-the-water Oliver, and so we were scared off.

This week, though, with summer speeding by and Oliver’s childhood advancing, I resolved to reapportion some of my summer time to getting the canoe up and running again.  

We started last night with a trip to Canadian Tire and the purchase of a wee paddle and a new PFD, followed by an hour-long session in the CARI Pool to insure that the PFD actually worked (it did!).

Tonight I dragged the canoe out of the carriage house, hosed it off, and assessed the wear and tear of 8 years among the skunks, cats and raccoons (in general, not to bad: some animal attempted to eat the styrofoam seats, but not too much damage was done, and the craft remains seaworthy).

Next on my list tonight: find a way of affixing the canoe to the roof of our 2000 VW Jetta.  When we first bought the canoe, Sporting Intentions sold us a $20 kit of nylon cord and styrofoam blocks that snapped on the canoe’s gunnels; they served us well, but were eaten by the aforementioned animals in the interim so needed to be replaced.

Alas I’ve had no luck replacing them: there are plenty of kayak carriers in the stores of Charlottetown, but nobody but Sporting Intentions sells canoe carriers, and they’ve “gotten away from the styrofoam system” and all they have to offer is a $400 Thule system that, while it’s beautifully designed and snaps right into the Jetta, is overkill for what will likely be a weekend outing or two this summer (I should add that the Sporting Intentions salesperson was super-helpful, both in selling me on the virtues of the Thule, but also in pointing us to good spots to put in).

So as of this writing I’m still searching.  Canadian Tire is selling styrofoam “pool noodles” for $1.99 each and I’m pretty sure I could adapt them for the job, add $20 worth of tie-down straps and have something that would safely get the canoe into fresh water.

Times a wasting and the snow will be here soon, so I’d better be quick about it.

Suggestions welcome.

Finally, after being euphemistically known as an “entertainment centre,” and unofficially referred to as a “racino,” the casino in Charlottetown is being renamed to what it is: a casino.

There have been rumblings of discontent within the cultural intelligentsia of Charlottetown for the past few months about the donation, that last night became public, by developer Richard Homburg of $2 million to the Confederation Centre of the Arts, and the resulting renaming of the Centre’s Main Stage to Homburg Theatre.

While their are myriad reasons to call this donation into question, the foremost, to my mind, is the simple vanity of it all.

Selling off naming rights is a well-established institutional practise, and one the Centre has used before in smaller ways without outcry.  But Prince Edward Island is a special place, a place that treats vanity as a serious sin, punishable by suspicion and long term just-out-of-earshot scorn. 

On the Island, it’s fine to be successful, you’re just not supposed to show it off.

That Homburg appears to have ridden into Charlottetown, decided to remake the city in his image (complete with large HOMBURG signs slapped on everything that doesn’t move), and then, in a vainglorious coup de grace, paid to have the cultural heart of the city renamed after him, is vanity the likes of which we’ve never seen before.

While it’s hard to argue with Homburg’s generousity, to my eyes the impulse is tarnished by this self-idolatry.

My old homebrew blogging system used a hierarchical set of categories to tag posts.  It looked something like this:

• Technology
  • Apple
    • Steve Wozniak
  • Backup
  • Barcodes
    • UPC

And so on.  When I migrated the blog to Drupal, I needed a way of getting this set of categories out of the old system and into Drupal. Here’s how I did it.

First I created a new Drupal Vocabulary (Drupal-speak for “set of categories”) called “Topics” and then I looked in the drupal.vocabulary table to find that the vocabulary had a record number – or vid – of 5.  I noted this for later.

The old system’s categories were stored in a MySQL table that looked like this:

CREATE TABLE `categories` (
  `number` int(11) default NULL,
  `name` char(75) default NULL,
  `parent` int(11) default NULL,
)

For each category there was a number, a name (like “Apple”) and the number of the parent category, if any.  While there are various ways of importing categories into a Drupal “taxonomy”, none of them exactly fit the bill for me, so I decided to go the “write a PHP script to do it” route.

First I selected all of the categories, in numerical order (because I wanted to make sure that parents appeared before their children):

SELECT number,name,parent from categories order by number

For each of the categories I inserted a record into the Drupal term_data table:

INSERT into drupal.term_data (vid,name) values (5,'" . addslashes($name) . "')"

In then retrieved the tid (or “term ID”) value:

select LAST_INSERT_ID() as tid

and noted this for later use should I need to identify the ID of this category should it be a parent to a child encountered later.  I then also inserted a record into the term_hierarchy table, using a value of either 0 (zero) for categories with no parent, or the tid value for the parent, noted earlier, for this with a parent:

INSERT into drupal.term_hierarchy (tid,parent) values ($tid,$parent)

Put it all together and the code looks something like this:

$query = "SELECT number,name,parent from categories order by number";
$result = MYSQL_QUERY($query);
$howmanyrecords = MYSQL_NUMROWS($result);

$currentrecord = 0 ;

while ($currentrecord < $howmanyrecords) {
    $number = mysql_result($result,$currentrecord,"number");
    $name = mysql_result($result,$currentrecord,"name");
    $parent = mysql_result($result,$currentrecord,"parent");

    $query2 = "INSERT into drupal.term_data (vid,name) values (5,'" . addslashes($name) . "')";
    $result2 = MYSQL_QUERY($query2);

    $query2 = "select LAST_INSERT_ID() as tid";
    $result2 = MYSQL_QUERY($query2);
    $tid = trim(MYSQL_RESULT($result2,$currentrecord2,"tid"));

    $tids[$number] = $tid;

    if ($parent <> '') {
        $parent = $tids[$parent];
    }
    else {
        $parent = 0;
    }

    $query2 = "INSERT into drupal.term_hierarchy (tid,parent) values ($tid,$parent)";
    $result2 = MYSQL_QUERY($query2);
   
    $currentrecord++;
}

The end result was a 788-term vocabulary, with hierarchy preserved, in Drupal, ready to attach to the posts I would import next.