Of Bikes and Books

At the start of 2016, for the first time in a long time, I made resolutions. 2 specific.

  1. Cycle 3000 km.
  2. Read 10 fiction books.

These resolutions were inspired by 2 things.

In 2015, my love of beer caught up on me and I tipped the scales at 225 on a 5’10” frame. Turning 50 this year, I needed to make some changes. I know that the standard resolution of “lose weight” was too general. I needed something specific. So, in addition to renting a rowing machine (which actually happened towards the end of 2015), in 2016 I got back into cycling on a regular basis.

I’ve always biked, but in recent years working at home more and my mountain biking taking a back seat to small kids, my mileage had taken a real hit. So I started 2016 with a goal of riding 3000 km. I thought it was an achievable goal. A tad under 60k a week. My plan was to ride into the office 2 days a week on 10 k routes, and then a longer ride on the weekend.

I used Strava to track most of my rides and, while I didn’t hit 3000, I am pretty happy with my Strava total.

There were times I didn’t use Strava, like weekends where I took on some singletrack trails with my son (who got into mountain biking in a big way this year which was fantastic as it re-ignited my passion for MTB, something I have not done since before I had kids).

All in, I figure the best I did was around 2300 km. Short, but I am still happy with that. And, despite a recent uptick in the weight, cycling this year has helped me stay under 200 lbs for most of the year.

Some of my Kindle library. Many samples waiting to dig into in 2017.

The second goal was inspired by David Wiley and Martin Weller. At the end of 2015, both wrote blog posts about the books they read in the previous year (and I see that, today, Martin has written one for 2016). As I read their posts, I realized that, while I read – non-fiction, reports, papers, research, blog posts, etc – I had really fallen off the fiction wagon. So I made a modest goal of 10 fiction books this year, far short of the impressive output that Martin managed. 48. Enough to make some lovely charts and do some analysis on.

This goal I met, again with help from my son who, at 10 and like his sister, seems to be developing a voracious appetite for fiction.

Here (in rough chronological order) is the fiction I read in 2016.

  1. Neuromancer William Gibson
  2. No Relation Terry Fallis
  3. Fool Christopher Moore
  4. Good Omens Terry Pratchett & Neil Gaiman
  5. High Fidelity Nick Hornby
  6. Little Brother Cory Doctorow
  7. Armada Ernest Cline
  8. Holes Louis Sachar (my sons favorite book of the year)
  9. The Dragonet Prophecy Wings of Fire book 1 Tui T. Sutherland
  10. The Lightening Thief Rick Riordan
  11.  The Hunger Games (book 1) Suzanne Collins

So, a couple notes about this list. There are some decidedly YA titles on this list. The last 4 are books that my son and I read together. I still read to him every night before bed and the final four books on the list (Holes, Dragonet, Lightening Thief and Hunger Games) were his choices. I almost thought I should not include them, except for the fact that I really enjoyed all 4. Holes was much richer and complex than I expected, and The Lightening Thief felt like a great way to introduce classic Greek mythology to a contemporary audience.

Despite having watched the movies and reading books 2 and 3 in the series, I had not read the first Hunger Games book. Reading it with my son at the same time I was reading the non-fiction Hillbilly Elegy and while the US election debacle was unfolding added an extra resonance to the plight of Katniss Everdean. District 12 as Appalachia in a pre-Panem America. So much about the novel has been topical this fall – the role of the media and manipulation, who controls the media, reality television, the plight of the working class, the excessive indulgence of the elite oblivious to the plight of working class until it is too late. The novel has been a source of rich political discussion with both my kids, who are both fans.

While Little Brother was also a topical read this year, by far my favorite book on the list was Good Omens. Smart and funny, it reminded me of the best absurdist satire of Vonnegut. I had never read either author and Good Omens proved to be an excellent way to whet my appetite for more from both Gaiman and Pratchett.

Disappointments were Armada and No Relation. While both Fallis and Cline had debut novels that I really enjoyed (in The Best Laid Plans and Ready Player One respectively), both of these newer efforts were weak and I struggled to finish them.

In addition to the Hillbilly Elegy, the other non-fiction title that made an impact on me this year was Quiet by Susan Cain. While I had it on my list for awhile, attending Educause in Anaheim this year where she keynoted was the impetus that spurred me to dig in, and I was happy I did.

A penny dropped for me while reading Queit in that, as I ws reading it, I realized that I have not been a good advocate for my introverted daughter with her teachers. Consistently year after year in the 7 years she has been in the public school system, her teacher assessments have always included the wish that she speak and participate up more in class. I have taken those assessments to heart and (high irony alert here for someone who considers himsefl quite introverted) tried to push her to be more participatory.

After reading Quiet, I realized that I have been so wrong and it isn’t my daughter who I should be coaxing to change It’s not often that I have read a book where I can see such a clear connection between the book and my life, but Quiet was one of those books that has made me change my attitude.

Oddly, no books about cycling. Come to think of it, I don’t think I have ever read a book where cycling is the main theme or subject. Hmmmm. #2107Resolution. That and this.

Photo: Cyclists Manifesto by Richard Masoner CC-BY-SA

 

Setting up Public Channels in Kaltura Mediaspace

Part of my work at BCcampus is to co-administer a provincial shared service of Kaltura with my colleagues at BCNET and UBC. Kaltura is a suite of tools for hosting and streaming media. Mediaspace is the YouTube like front end for Mediaspace. Because of that, BCcampus has access to some of the Kaltura tools for our own business uses and, for the past couple weeks, I have been mucking around with our new Kaltura Mediaspace instance.

In general, I find Kaltura a beast. It is complex, and there are multiple layers of administration to go thru depending on the tools you want to use. It is powerful, no doubt, and has some wonderful features. But likely not a system you want to tackle off the side of your desk to fully grok how it works and, just as important, fully maximize a fairly sizable institutional investment.

At any rate, I have been making some progress on setting up our Mediaspace site. You can take a look. Keep in mind it is being built in real-time and not fully configured and setup. But for now, I have some basic branding in place and a few channels with some content set up.

One task that I was failing at was creating public channels. I was able to make channels and add videos to channels, but could not seem to make those channels publicly visible unless you had an account. Every time someone would click on the Channels link, they would be taken to a log in screen. For an organization that does open work, having closed channels was a no go.

So, after poking around, I went back and did what i should have done in the beginning, which is RTFM. Or, in Kaltura’s case, RTFM’s. Started here, which led me here and here and here and here. Here and here. A bit over here. Some stuff from this 23 page PDF here.

Ok, well, you get the idea and why I say complicated. Oy! And no where could I find the damn setting to make a channel public.

Finally, in a brief 30 second conversation with my colleague Jordi at UBC, I found the setting. In the Mediaspace admin area, there is a setting called supportPublicChannel that needs to be enabled.  That was it. One little setting. Click that and, boom, public channels.

 

Man, there it was. Right there in the Channels section of the administration console. Hours of pouring thru technical support documents & Google searches on how to enable public channels and the problem was solved in 30 seconds by talking to Jordi.

There were a few steps I did before this that I’ll add in here just in case others are struggling. This info is specific to those in the BC Kaltura Shared Service, which is an on prem instance of Kaltura. If you are not in the shared service, this may not work for you. The other caveat is that I have been working on this off the side of my desk for a couple of weeks now, along with other config issues with Kaltura and Mediaspace and, because I don’t have the awesome discipline of CogDog to document and share on an incremental basis, may be incomplete and missing stuff (and let’s just pause here and acknowledge just how fantastic CogDog is at documenting the technical work he is doing knowing that there are very likely others out there struggling with the same thing).

But, to the best of my memory, here is what I did prior to making that final switch above.

When you log into your KMC and go to Categories, you should see a MediaSpace category already set up as part of the initial system wide configuration. Under channels, I have created 2 channels – EdTech Demos and SCOPE

On the MediaSpace category, the entitlement (what Kaltura calls permissions) are open. These can be overridden at lower categories.

 

Drilling down to the next layer, Channels, I have set default channels to be Private.


When someone creates a new channel, they may want to work on it before making it open. When you create an actual channel, you will need to override this setting, as this screenshot of the actual SCOPE channel shows. In this case, I have overridden the Channel defaults and made the content privacy no restriction, while adding a restriction on who can actually add content to the category (only the channel administrator).

.

In the Mediaspace admin area, when I create a new channel, I now have an option to make it a Public channel.

So, this was a spot that I was getting confused at because, until I flicked the supportPublicChannel option on, I was not seeing the Public radio button. But I was seeing the Open radio button. So, when I clicked Open, I thought that would make the channel, uh Open. But no. In Kaltura, Public and Open are different concepts and it wasn’t until I enabled the supportPublicChannels switch that the public radio button option became available during my channel setup. Clicking that button made the channel publicly viewable without people having to log in.

Now, when I upload a video, I can publish it to multiple channels, including the open and public ones.

 

Like I said, this is likely missing out a bunch of other steps I have done along the way to enable public channels on our Mediaspace instance. But for those of you in the KSS struggling with setting up public channels – supportPublicChannel was what finally did it for me. Thanks Jordi!