Redefining Reusability…

January 16 3 Comments Category: E-Learning, SCORM


I received a [Google Alert](http://www.google.com/alerts/) this morning from [Al Moser's blog](http://elearningslam.blogspot.com/2008/01/thinking-about-scorm.html) where he basically states it’s time to blast our thoughts of reusability, in terms of reusing content objects into other contexts, and instead focus on reuse of content across learning environments. I urge you to read the original post, but let me riff on Mr. Moser’s thought:

The SCORM philosophy will work best if we go back to its original purpose which was to ensure that you could re-use existing (compiled) content from one LMS to another; not from one COURSE to another, or from one authoring tool to another. Right now they are caught between trying to ensure that a course will work well on any LMS (therefore, it pretty much has to be static) and the Web 2.0 concepts of content aggregation in real time from multiple sources (thereby breaking LMS-independence)

I must admit I’m a little torn on the subject, because I don’t think that reusability of content into different contexts is impossible. I think it’s very difficult to pull off without the use of some aids in the form of applications, tools, search technologies and rigid presentation standards, admittedly none of which are used together today. But I can picture it. Others pictured it. Claude Ostyn and Phillip Dodds even pictured it. If you can see it, I’m tempted to believe you can build it when it comes to digital technology.

However, in stating this which I think is in direct opposition to Mr. Moser’s thought, I definitely agree that getting the E-Learning community over the hump of reusability is important, and this notion of redefining reusability by coupling it with “interoperability” isn’t a fragmentary notion. At the big SCORM Technical Working Group meeting, one of the ideas batted around for what to do next was to consider which “ilities” were really relevant.

I agree that it’s near impossible to reuse content in different contexts where we’re at now. We still can barely get tools we use all the time to work all the time. I mean, jeez… I defined Articulate and Quizmaker as a standard for my organization. And guess what? If you have special characters in your Quizmaker assessment, it can break your suspend data on closing the content, and thus it makes it look to the LMS like you didn’t complete content, even though you might have. So you work though that one issue and maybe you inserted a special character into the title of your content — which ends up as an attribute in your Metadata and in your Manifest — and that breaks your content. You fix that, but decide to put in multiple Quizmaker assessments into an Articulate Presentation, but you don’t want to use any of the assessments as a determining factor towards completion — which after much testing you find out will never leave a student’s enrollments because of some weird issue with how Quizmaker assessments are leveraged in Articulate Presenter.

I don’t mean to go off on a rant on issues Articulate has in *Vendor X’s* LMS. But I want to highlight the issues I see in just getting content from the same authoring tool, with the same code base, working in one LMS in a consistent manner with other pieces of content authored in the same tools and deployed to the same environment with the exact same code base.

See, my point is that as difficult as my scenario above is — I’m not trying to mix my content in with content possibly produced by somebody else — possibly not even built with Articulate. Even using certified SCORM products isn’t good enough. Articulate IS certified. *Vendor X* **IS** certified. But that doesn’t mean they work together out of the box.

So maybe for slightly different reasons, I agree with Al Moser about reusability. Because, from my vantage point, we can’t even talk about reusability — even at a technical level, until we can address interoperability. And frankly, we can’t talk about interoperability until we finally settle on **compatibility.**

Because at the end of the day, you just want the content you buy or build to work in the system you support. And if you’re building the content, this should be a science, not an art.

  • Share/Bookmark

Related posts:

  1. FFL Podcast Production ramping up!
  2. Curriculum is Not the (Whole) Problem
  3. Virtual Patients
  4. LomPad = MetaData Generator

3 Responses

Write a comment
  1. this is definitely a topic that will follow us for years.

    as a guy that has to make somewhat cookie-cutter-ish (templatized) courses, using a CMS to manage media fragments that get reused in each course sounds great. but many of my instructional design peers, who generally work as contractors on projects for a number of different companies, don’t care as much about reusability; their focus is making that great knock-out one-of-a-kind course that really hones in on their instructional design concerns. custom graphics, custom interface, custom videos, none of which are meant to be used in other courses or for other clients.

    so where can we draw a line dividing the ranks between those whose main focus is reusable parts and the ability to import those parts into a multitude of courses and courseware systems, and those who’s sole care is making a “WOW” course that makes their client happy (while hopefully using quality instructional design principles), all the other stuff be damned?

    personally, i’m more inclined to say i want to make my course portable, with solid web standards and SCORM conformance. if i can reuse some of the content, great, but it’s low on the totem pole for me. i didn’t use to feel this way, but with the quick pace of shifts in technology, including file formats, i don’t want to spend my time worrying about whether the graphic elements i’m creating today are going to be compatible with courses that don’t exist yet. knowing my course will work as-is on any SCORM-conformant LMS is a pretty good feat in itself.

    what if a future course uses a color background on all of the pages, and my graphic has a drop shadow on a white background? i could spend a bunch of time trying to make transparent alpha PNGs that may or may not work with the future course, or i can just focus on my current needs. it’s a tough call. i guess my rule of thumb is: if i can do it quickly with minimal effort and it works with my current course, great. if not, screw it. :P

    philip 16 January 2008 at 8:48 pm Permalink
  2. All i know is i spend a ton of time integrating our template runtime into multi LMS and none of them do anything the same. One has an extra API that i have to use but not useful in any other lms, another likes to add spaces into datafromlms on import so my runtime freezes, others are scorm 1.2 and have different combos of the optional values supported.

    Then i see the clients having all kinds of tweaks like having a global lms specific star rating sco that you have to include in the manifest but obviously is useless in others. Then we can talk about how each lms chooses to interpret the sequencing rules-that’s a lot of fun.

    In the end i think it comes down to finances-companies like Chrysler opt to build their own LMS and use scorm as guidance but in the end don’t have any interest in sticking to it if it gets in the way of something they want. So you end up with content kingdoms at each company. For the content vendors working across these companies it’s absolute hell.

    And in the big picture i see little courseware crossing companies-if they pay for custom they want to own it. If they buy shrink wrap they want to customize it to the point that it’s custom anyways.

    ethan 18 January 2008 at 4:29 pm Permalink

Trackbacks/Pingbacks

  1. On Authoring Tools… - 22. Jan, 2008

    [...] content that any of the popular E-Learning tools on the market. And if you ever want to talk about reusability, there’s just about no easy-bake oven method available to make published Flash content look [...]