Quotes from
James
Sangster with my responses interspersed (these are intended
to be constructive suggestions for how to respond to these issues
in typical discussion with "senior management"; been there, done
that, got the tee-shirt...):
Moodle does not have the user base that WebCT does
and it can be argued that it's not as tested and therefore not as
reliable.... that can be over come, especially in the academic
arena.
It is very hard to get reliable figures for the "user base" of
either WebCT or Moodle. I think is is certainly fair to say that
the Moodle user base is substantial, and growing very
rapidly; sometimes (as in my own institution) at a direct
reduction in WebCT.
More importantly, the suggested inference that Moodle is
(therefore?) less well tested is very questionable. I think the
software methodology and business model has a much greater impact
on software reliability than the crude size of the user base. I
believe it is well established now (?) that agile software
development (with a very rapid deploy-test-repair cycle)
generally delivers significantly more reliable and robust
software. The open source approach makes this even more
effective by providing a very diverse, and usually rather active,
test audience.
From my own experience I can say that WebCT is generally a
well engineered and reliable package (better than most); but
Moodle is certainly at least as solid.
The full-blown support for moodle isn't available
for moodle as it is for WebCT. This is almost a total
show-stopper for us. We're very spoiled with the high-end WebCT
support. We call them and they fix it.
Well, we buy support from moodle.com and the service to date
has been absolutely amazing - significantly better that anything
I have ever experienced in the closed-licence software business. And
it's a lot cheaper to boot! But there is no surprise there: the
open source business model precisely supports vigorous
competition on service quality. As I say, we're very happy with
moodle.com, but if it should
ever falter we have a number of other outfits who would be only
too delighted to bid for that business. Try saying that for any
closed-licence software product. Open source is software consumer
heaven.
Migration of existing content is a major issue as
well. We have over 40 highly-developed fully online courses that
support "advanced" WebCT features like selective
release. Migration of that content has to be planned and
resources for that need to be allocated.
That's a real and genuine problem; which flows directly from
your original selection of a closed-license software platform.
You are locked into that vendor. That is the point of the
business model. Great for vendors (especially if they can achieve
a "dominant market position") and a disaster for consumers.
The strategic challenge for your organisation is whether to
"dig deeper" (by continuing to design even more such courses on
that platform - basically locking in to the current platform even
harder), or to jump ship now. Of course you
will have to take a significant hit to do so: that is the price
for future flexibility. But the longer you wait, the higher that
price will get. The fact that it is already high is therefore a
poor rationale for keeping going...
Moodle doesn't
(to my knowledge) support WebCT epacks (pre-formulated WebCT
courses available for adoption direct from major
publishers). Perhaps SCORM supports that but I havn't really
looked into things as of yet in that area.
Again, this is a serious issue, with no simple answer. The
first thing to understand is that e-Packs are primarily about
using the VLE as a (primitive) Digital Rights Management
device. So, as has already been mentioned, there is a high
incentive for the publishers to support any VLE which attains
significant market share. Given the current momentum behind
Moodle, I would think there is a good prospect of ePack
publishers beginning to support it in the near future.
I should also say that, in my own institution, while we played
with some ePacks on WebCT, we did not find any of appropriate
quality and relevance that we really wanted to adopt them. Of
course, this is a very dynamic and discipline specific thing, so
your mileage may vary.
Out current fall back position is that if any Faculty member
really does want to adopt ePack material, then that will be done
by linking to external hosting of the ePack. This is offered, at
no extra charge, by the leading ePack publishers. The linkage
would normally be embedded within a "shell" Moodle course, so there
is some superficial integration. Of course, you
don't get any "deep" integration (e.g., into the gradebook).
But, at this moment in time, this is a reasonable compromise. It
is certainly a straightforward response to the claim (sometimes
touted) that adoption of Moodle is simply incompatible with use
of ePacks. It is not.
Hope this helps. Good Luck!