Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Sakai
Score 8.7 out of 10
N/A
Sakai is an open source learning
management system provided by the Apero Foundation. The LMS provides what it
calls Core and Expanded Features. The Core Features encompass an integrated
tool set that is tested by the Sakai community members and is then included
with each new release. The tool set can be configured by: instructors,
students, research investigators and project leaders. The other set of tools, known as “Contrib
Tools” are specific to Sakai tools and innovations that are developed…
N/A
Pricing
Drupal
Sakai
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Drupal
Sakai
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Must contact vendor for pricing information.
More Pricing Information
Community Pulse
Drupal
Sakai
Features
Drupal
Sakai
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Sakai
-
Ratings
Role-based user permissions
8.174 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.6
69 Ratings
2% below category average
Sakai
-
Ratings
API
7.264 Ratings
00 Ratings
Internationalization / multi-language
8.160 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
Sakai
-
Ratings
WYSIWYG editor
6.171 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
00 Ratings
Admin section
6.878 Ratings
00 Ratings
Page templates
5.577 Ratings
00 Ratings
Library of website themes
5.568 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
00 Ratings
Publishing workflow
6.876 Ratings
00 Ratings
Form generator
6.472 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Drupal
6.5
77 Ratings
13% below category average
Sakai
-
Ratings
Content taxonomy
6.971 Ratings
00 Ratings
SEO support
6.272 Ratings
00 Ratings
Bulk management
6.367 Ratings
00 Ratings
Availability / breadth of extensions
6.570 Ratings
00 Ratings
Community / comment management
6.569 Ratings
00 Ratings
Learning Management
Comparison of Learning Management features of Product A and Product B
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
I've used Sakai to supplement my Public Speaking class. Public Speaking is very much a F2F type course, so I didn't use Sakai much for course content delivery. However, I did use it to post my syllabus, post my lecture slides, communicate any class announcements, and to conduct a final exam for the class. Building the final exam was very simple and I was easily able to swap out questions to vary it from term to term. Before I was a staff member and lecturer, I used Sakai as a student. My instructor used Sakai to varying degrees. I really appreciated it being the one-stop-receptacle for all-things class related. If I somehow lost an assignment instruction sheet, I could rely on it being posted there. For multimedia work it was lacking, at that time, but I know Sakai has been updated over time and I hope that part of it has improved. If I was ever frustrated by Sakai, it was because faculty used it in a piecemeal way. It's fine not to want to use the gradebook, but don't enter some grades and not others. It's wonderful to upload class documents to it; but don't do some and not others. Whatever way you're going to use Sakai, commit to it and use it well. Your students will thank you.
Sakai is flexible, providing a way for our customers (instructors) to customize their courses while staying in line with consistency and continuity of course design. This has allowed our courses to be far less cookie-cutter and stale. This is mostly accomplished through Sakai's LTI functionality and it's Lessons tool. This is particularly notable because not every course is the same, nor should it be. Our faculty and course developers can draw from OER resources, course text publisher assessment quiz banks and pull in content from sources from our library databases and services like YouTube.
Sakai is customizable, allowing us to pair it with our student information system to automatically create and track with student registration data - including adding new students and removing students who have elected to drop a course. The customization features also include being able to create course templates for individual schools or courses using specific tools or sequences of tools as well as a way to personalize content for students when they engage with each lesson.
Sakai is stable in the market. We have been using Sakai for almost 10 years and continue to see it improve; responding to changing trends in browser technologies, mobile platforms and accessibility requirements. Multiple programs offered over the years have been recognized by outside organizations like BestColleges.com for our programs and given high marks by students taking the courses offered in Sakai.
Sakai allows our faculty to inform it's continued evolution. We work closely with the developers, having a front seat to how things can work and function for our faculty. There have been multiple occasions where faculty ask, "Can Sakai do this?" and the answer is never "No."
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
Sakai is a good general learning management system - it is not leading edge but rather a stable system with standard learning management system features. It can be fairly easily customized and is fairly easy to learn from both student learning and faculty administrative vantage points. New paradigms for online learning though are emergent so the current field should also be investigated with competitors.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
When faculty are preparing courses from term to term, a portion of the content is static within a specific discipline. The time it takes to import past lessons into new versions of Sakai can be an inefficient use of my time. When I want to add new content and edit from the old content, it's reliant upon me to cut and paste the content from term to term rather than simply import and edit from a backup.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
Since Sakai is open-source their documentation is often lacking and support is absolutely needed onsite. Internal documentation is more important with Sakai than other services. The Sakai community is fun, passionate, engaged, and absolutely doing their best, but it's an uphill battle against the current market and trends.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
As an adjunct professor, I didn't pick Sakai for the university. I have experience with Moodle, Blackboard, eCollege, iBoard and now Sakai. I would have to say that Sakai is one of my all time favorite LMSs to use as it is very easy to navigate.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
Sakai makes it easy for students to monitor grades which puts their minds at ease.
Sakai makes it easy for teachers to assign and receive assignments from students.
Communication is one of the most important and one of the most taxing parts of an educational system. Sakai makes this process just a little bit easier.