Opening the Irving K. Barber Learning Center

A few weeks ago, I was asked by Julie Mitchel if I would be able to speak at the opening of the Irving K. Barber Learning Center. She wanted me to...

A few weeks ago, I was asked by Julie Mitchel if I would be able to speak at the opening of the Irving K. Barber Learning Center. She wanted me to give a student’s perspective of what the Learning Center means to the students of UBC. I accepted, not really understanding what I was getting myself into. As the weeks went by subsequent meetings with Julie made me see that the ceremony was a lot more important than I ever could have imagined. For a great description of what the ceremony was actually about, Phillip Jeffrey wrote an excellent post here. I am still unable to express just how terrifying it was to speak after people like Professor Stephen Toope and Gordon Campbell. It went off pretty well though and I think my speech was well received. Pictures of the event (courtesy of Philip Jeffrey) can be found here. A video of it can also be found here (I talk right at the end).

It was an amazing experience and I feel so honored to have been a part of it.

Facebook Tip… make your profile more presentable

So after Looking at Mackenzie and Ciara’s Facebook profiles I saw that they both look much better than most people’s. The reason being that instead of having comma denominated lists like...

myFacebookprofile
So after Looking at Mackenzie and Ciara’s Facebook profiles I saw that they both look much better than most people’s. The reason being that instead of having comma denominated lists like “Interests: running, swimming, hiking, hockey…” they put them in an actual list form like so:

Interests:

Running

Swimming

Hiking

Hockey

Ciara even adds breaks using dashes. I did the same and now my profile is no longer a jumbled mess… yay!

In fact it looks so good I’ll just include it on my about page on this site.

My Vision for a Semantic UBC

This is my vision as for what we can do at UBC to create an expandable eduglu solution. Most content will be stored in a wiki. Our wiki will be extended...

This is my vision as for what we can do at UBC to create an expandable eduglu solution.

Most content will be stored in a wiki. Our wiki will be extended so that we can lock more sensetive pages for certain users.
In order to make our content semantic and to allow it to be remixed in ways that make sense we would use the SemanticMediaWiki plugin for our MediaWiki. A working example of this kind of wiki can be found here.This plugin allows users to define relationships between the article and its content. This data is then Collected and can be navigated in a semantic way. Lists are then also generated and dynamically maintained. For instance in Chemistry someone could define the property “has boiling point” for a certain element. The page for “is metal” will then contain all the elements that have a boiling point (like this example).

Once we have the Semantic MediaWiki the next step is to republish content from the wiki into other contexts. We are still working on exactly how to do this (what tools to use etc) but the basic concept is simple: Use some kind of feed to publish the content in another context (we will probably use WordPress as the new context for most of our services). Then periodically check the feed to see if it has been updated. If it has been updated, then update the republished content. This ensures that not only is content dynamic (like it should be) but it also means that it is searchable and that the server-breaking parsing of hundreds of feeds doesn’t happen all the time. Another step would be to build in a system whereby people who take feeds from the wiki are notified when the content changes (I know the watch page function does that already, but one time users that just wanted to quickly grab and republish some content would need to be informed of major changes to their content). This would create communities of watchdogs around more used content to ensure that vandalism is quickly curbed.

So that is the start. Content is dynamic and open on the wiki. It will be easy to grab content and republish it in other places. It will also have meta data that can used in the immediate term to navigate data and in the long term to drive applications like those created by the MIT simile project.

My essential Facebook Applications:

Here is a list of some of my favorite Facebook Apps: FriendFeed: Allows me to publish my life stream on my Facebook profile Boost: Boost is a Firefox add on that...

Here is a list of some of my favorite Facebook Apps:

FriendFeed: Allows me to publish my life stream on my Facebook profile

Boost: Boost is a Firefox add on that allows you to change the look and feel of Facebook. Adds a bunch of cool functionality like “download whole album” and showing full size images when you mouse over them.

Nexus: Creates a graph of your network. Really interesting to see how you are connected to other people and how connected they are to your friends.

FBcal: Generates an iCal file of your upcoming Facebook events and/or upcoming birthdays. Seeing as my Google Calendar plans my life, I don’t know how I’ve lived without this application for so long!

Today's realization:

Enej and I decided today that we need to start making this a reality at UBC: from digitalbazaar Still have no idea how. We will figure it out though. So here’s...

Enej and I decided today that we need to start making this a reality at UBC:

from digitalbazaar

Still have no idea how. We will figure it out though.

So here’s how:

Now for where!

Edugluing things together

so here is a mapping of my plan for a UBC content management strategy. It is designed to overcome two obstacles: 1) Content changes, therefore the content stored in repositories has...

so here is a mapping of my plan for a UBC content management strategy. It is designed to overcome two obstacles:

1) Content changes, therefore the content stored in repositories has to change and be updated when the source is updated. This is overcome by using a wiki (this has been Novak’s vision of content management for a while) that produces RSS feeds along with an aggregator like Feed WordPress that updates the repository when a feed gets updated (that feature is still buggy at the moment, but I will get to fixing that ASAP).

2) The second obstacle is the fact that RSS and JavaScript are not easily searchable (a must for a content repository or even an end user site). Republishing is a must until we find an easy way to index and search RSS and JSON.

So here is what it looks like (click on it for larger view):