LMS Non-Negotiables

I listened in on the first town hall meeting for our USG LMS Transition Task Force on Thursday. There are 3 more town halls this week and a final one December 9th. It sounds like the task force is looking for what items are non-negotiable, extremely important, nice to have. Here are the non-negotiable items from the list. Here are my thoughts.

  • Security: Agree. Student data is critical information to keep away from those who ought not see it while giving access to those who should. I would include in this an audit log of administrative actions such as changing passwords, resetting virtual classrooms, or anything else which possibly could be abused.
  • Scalable: Agree. We’ve seen fantastic usage growth other the years. When I started with this project four years ago, we had only around 100,000 active users. We now approaching 300,000 active users. Even each user does more now than then. There is no reason we will see an end to usage growth.
  • Integrates with enterprise systems (i.e. Banner): Agree. There is a need for a relatively easy way to ensure the faculty and the students have accounts which are placed in the correct virtual classrooms. I’ve seen a desire for real-time integration. The Luminis Data Integration Suite always looked to cause more problems than it would solve.
  • 508 Compliance: Agree. Every user ought to be able to get the information in the class. However, to truly meet this I would think that would include fixing faculty uploaded content so that is accessible.
  • Don’t go backwards (features and functionality meet or exceed current functionality): Unsure. I’m not aware of an LMS option which meets every feature we currently have in Vista 8. The only way to meet this one is to negotiate which are the non-negotiable features.
  • Cross-platform and cross-browser support: Could not agree more. Most web sites I visit work in any web browser I choose. Vista 8 has limited supported operating system and browser combinations. Don’t forget the cantankerous Java Applets multiple versions of Java behave erratically and prior to Java 1.6.0_11 left in place older versions. Also sometimes new versions of Java suddenly do not work.
  • Ease of use and good user interface (student, instructor, administrator): Agree. More is not always better. I sense a frustration about a lack of efficiency accomplishing tasks.
  • Timely support and response: Agree. I understand this one to mean fix the problem in 1-2 weeks not a year plus.
  • Good communication regarding downtime: Unsure of the intent. Vista 8 has a pretty good announcements tool. Does it mean be more aggressive in telling the users when the system will go down next for a scheduled maintenance? I wonder if it means my organization (hosting) ought to take a firmer hand rather than continue to depend on the campuses in letting end users know.
  • Back up and restore capability (minimum 1 year – nice to go back farther)/archiving/back-up without significant downtime: Unsure of the intent. Our system backups are daily without any downtime involved. My best guess is it means something like a wiki history for all content and tools and maybe the whole virtual classroom. Should something bad happen the faculty member ought to be empowered to fix it and not depend on going to an administrator every time. While Vista 8 allows faculty to make their own backups, this was disabled to avoid performance issues. Also, the restore overwrites everything and not selective enough to ensure the faculty would not lose other data trying to retrieve something specific. Imagine losing 10 weeks of work in order to retrieve an accidentally deleted file. (Administrators have unintentionally done this.)
  • Ability to bring in guests to the system (i.e. collaboration): Agree. In a bricks-and-mortar classroom, the faculty can just ask a guest to come to the right room in a building. With Vista, the virtual classroom is more like a fortress requiring the faculty member to complete some kind of paperwork/memo to get an id so the guest can pass through security.

For those of you in similar searches, does this list look similar to yours? What would you add?

Some things I am surprised are not non-negotiable.

  • Better grade book: The existing one in Vista 8 is cumbersome, especially the grade calculator. A key use of the LMS is for students to understand their performance in the class. However, keeping up with the calculated grade at any given point is a lot of work for the faculty.
  • Reporting and analytics: The faculty, advisors, and tutors need to know which students are having difficulty.  Department heads and deans need to know which instructors are failing to spend enough effort teaching a class. People composing budgets need to know how much the LMS and auxiliary software are used.
  • Administrator becomes another user: Similar to *nix’s “su – user”, some problems only become apparent when using the correct account. Rather than change the password, take a look, and give the user the new password, administrators need an easier way of reviewing.
zv7qrnb

Tags: , , , , , , , , , , ,

  • http://kylemackie.ca Kyle Mackie

    Agreed with all your points above (including your second “surprised” list). I’d add a couple specifics:

    – integration with final grades systems
    – integration with library e-reserve systems
    – connection with or fully-integrated ePortfolio tool.

    • http://www.ezrasf.com/ Ezra S F

      Thanks, Kyle. I agree all three are very important. My oversight with the integration with enterprise systems item was not fully developed to cover all the cases. I think all three of your suggestions fall under that item. Also, I’m thinking the description is a poor one. Really it ought to be something like “integration with external systems”. Vista 8 has the System Integration API by which developers can create PowerLinks or connect to the API in order to facilitate password-less logins (single sign-on) and transfer of important data. The difficulty has been the approach taken by us, those hosting, is to only work on the integrations with external systems we will use/run. Vendors of library e-reserve systems, ePortfolios, publisher web sites, etc. and even our clients were more than welcome to make a PowerLink or use the APIs. However, without us being experts, these integrations fizzled. There is a strong desire for more integrations with all kinds of things.

%d bloggers like this: