e-Literate

Present is Prologue

Tag: Campus-Technology

  • LMS Market Updates, Dec 2015

    There seems to be a series of news and analysis on the LMS higher education market worth summarizing.

    Major Adoption News

    I posted last weekend about University of Phoenix (UoP) and their LMS. UoP is well-known for being the biggest user of a homegrown LMS for well over a decade, but in the past several years they rolled out “Classroom”, an entirely new adaptive-learning based design. In a major strategic change, UoP is abandoning this effort and moving to a commercial provider.

    What we can now confirm at e-Literate is that the “learning platform” selected by the University of Phoenix is Blackboard Learn Ultra. This is the cloud-based redesign of Learn that Michael and I have described in several posts. Even with the University of Phoenix’s reduced enrollment, I consider this news to be the most important new client acquisition for Blackboard since at least 2011.

    Today Campus Technology reported that Stanford is moving to adopt Canvas as their campus-wide LMS. Previously Stanford was a founding member of Sakai, with its implementation called CourseWork.

    The university has been piloting Instructure Canvas since the 2014-2015 academic year. The vice provost for teaching & learning (VPTL) said in a statement that about 80 percent of faculty in the pilot reported being “very or somewhat satisfied” with the new platform; even more students (94 percent) found it “very or somewhat easy” to use.

    Alongside the pilot, two Stanford schools had already adopted the application independently. The Graduate School of Education moved to Canvas in 2013-2014, and the Graduate School of Business did so in 2014. Both adoptions were considered successes.

    During this school year, the migration was accelerated. Some 300 classes switched to Canvas. And the plan is to migrate the remaining 4,200 classes still using the legacy LMS software over the next academic year.

    (more…)

  • What You Can Do About the Blackboard Patent, Part I

    A number of people have commented to me that they wish that they could make a difference in the Blackboard patent fight. In the process, they usually imply that I have some power that they don’t. The thing is, I’m not a decision-maker at my university, I don’t run an Open Source project or professional association, and I’m not in a position to hire an army of lawyers. Basically, I’m just a guy with a blog. If I can make a difference then you can too.

    Here’s something really simple that you can do at your university, regardless of what your role is and regardless of what LMS you use (Even if it’s Blackboard!): (more…)

  • Good Open Source for Higher Ed Article

    Campus Technology has strong backgrounder on Open Source that could be useful for educating your stakeholders. It covers the basics–and a few not-so-basics–in very clear, simple terms. In the latter case, I’d like to highlight just three of a handful of fine points that the article brings forward. First, one critical strategy to consider is “aggregating support costs across institutions so that ongoing costs of running the software can be shared.” In other words, the more organizations can collaborate on support, the better Open Source generally looks in terms of total cost of ownership. The economy of scale reduces the significance of any support cost differentials that may exist. Second, the future value of Open Source on campus is really going to be unlocked via loose coupling:

    A typical workflow within a college eLearning environment today might look something like this: A faculty member creates a Microsoft Word or Microsoft PowerPoint document as the basis for a student assignment. The faculty member uploads the document into the Blackboard Content Repository and makes it available to her students through the Blackboard Course Management System. Students create their own Microsoft Word documents and submit them to the faculty member, still within the Blackboard environment. The student also saves a copy of the assignment and submits it to his LiveText ePortfolio system. All of these interactions may be accessed from a university portal application, or they may each require a separate entry and authentication scheme.

    Now consider an alternate workflow. The faculty member uses OpenOffice to author the assignment and saves it to what appears to be a network drive on the faculty’s desktop. In reality, the network drive is the faculty’s space in a Fedora-driven content repository � providing functionality such as version control and collaborative access. The Fedora system also serves as a universal document repository from which content is drawn into the Sakai course management system. As the student completes the assignment and uploads it into Sakai, the student’s work is automatically added to the Fedora repository, where it can be referenced from OSP (the ePortfolio system integrated within Sakai), or through collaboration tools used in conjunction with other students.

    This is very much the vision that inspires the LMOS.

    And the final point I want to highlight is actually a reference to research by my colleague Patrick Masson. Pat was interested in making the point on the Sakai discussion lists that, if Sakai (or any particular Open Source project) wants to get broader adoption, they need to foster broad conversations about the value proposition of Open Source in general across various stakeholder communities within potential adopting institutions. He came up with a clever rough-cut metric of comparing the co-occurrence of the phrases “open source” and “information technology” on a university’s web site to that of peer institutions.

    These are just the three points that resonated the most with me; there’s a lot more in the article.

  • Blackboard by the Numbers

    Update: Welcome, Chronicle readers. Since it wasn’t made clear in the Chronicle’s reference, I’d like to point out that the paper I’m quoting was written by Jim Farmer, who is the Coordinator of Georgetown University’s new Interoperability Center, formerly the Sakai SEPP Community Liaison and project administrator for the uPortal project. Jim has pretty impressive credentials across the board, including having served as the CIO for the Cal State University system. You can find his full bio here.

    Sorry I’ve been incommunicado for a while. There’s been lots of stuff going on, both professionally and personally (including a new grandbaby).

    Anyway, I’m going to make it up to you with a special treat. Jim Farmer has a fantastic analysis of how much it costs Blackboard to make a sale, what that means to their overall business model, and how that compares to the cost-per-sale of a commercially marketed open source software product and the cost for community-building the Open Source uPortal project. Some of it may be slow going if you’re not familiar with financial analysis, so I’m going to unpack a few of the good parts and speculate a bit on the implications.

    (more…)