ninja-forms
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114simple-custom-post-order
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114wp-mail-logging
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114health-check
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114updraftplus
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114rocket
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114North-West University features three locations, with the furthest over 200Km away from Potchefstroom where IT maintains their servers in two data centers. In October 2017, the university introduced a successor to the once-innovative network drive: a modern collaboration platform consisting of Nextcloud and Collabora Online. Today we publish a case study examining the challenges and how Nextcloud and Collabora Online were chosen.
\n<\/p>\n
The North-West University IT department has to deliver solutions that fit with what a new generation of students and employees are used to.<\/p>\n
The IT world has changed in such a way that if the institution, albeit a university, a company or any other organization, does not cater for the needs of their employees, those employees will just go and find these solutions on their own.<\/p><\/blockquote>\n
Noted Hans Erasmus, Infrastructure Architect at the university. He elaborates that this can be a \u00ab\u00a0cause of chaos,\u00a0\u00bb forcing IT departments to \u00ab\u00a0keep up with the technology.\u00a0\u00bb This prompted a search for a solution that would bring data back under control of IT, providing the benefits of syncing and collaboration while reducing complexity and protecting the security and integrity of data.<\/p>\n
People want to be mobile, and they want their data to be as well. Above everything else, it seems that end users want their data with them at all times, and obviously safe as well. Hence, a locally hosted cloud solution.<\/p><\/blockquote>\n
\nownCloud 9 (…)<\/em> had big technical problems<\/p><\/blockquote>\n<\/div>\n
After trying a number of Enterprise File Sync and Share solutions, including Proof-of-Concepts with two other open source solutions (ownCloud and Seafile) and a proprietary solution, the team concluded these were too limited in terms of platform support, maturity and scalability. It was decided to go for Nextcloud. As Hans noted, \u00ab\u00a0the architecture for NC is laid out well\u00a0\u00bb, making the technical side of implementing it easy.<\/p>\n
Adding Collabora Online<\/h2>\n
One of the first things users asked after the University implemented Nextcloud was: \u201cDoes this mean we can now edit files online? Or work on them simultaneously?\u201d Hans:<\/p>\n
Unfortunately initially the answer was no. But as the service became more popular and more users started working on it, the need grew and it became apparent this is something we would need to implement. Hence, Collabora Online.<\/p><\/blockquote>\n
The most used feature, Hans noted, is the \u00ab\u00a0available anywhere\u00a0\u00bb aspect:<\/p>\n
Working on a document at work, going home, and keeping on going where you left off. The feedback we get is that Nextcloud helps a lot with sharing stuff effortlessly with other people in the organization.<\/p><\/blockquote>\n
Control over the data was a primary concern and deciding factor in opting for Collabora Online:<\/p>\n
Why not use Google docs you might ask? Well, some laws prohibit us from keeping certain types of data in \u201cthe cloud\u201d. It is not allowed outside the boundaries of our country. Data security is therefore key. We needed a solution which could be hosted on premises, where we have total control of the data.<\/p><\/blockquote>\n
Happy users thanks to a Nextcloud Subscription<\/h2>\n
Hans noted the users are very happy with the solution:<\/p>\n
Because they are familiar with products like Google Docs etc, the concept of having stuff in the \u201ccloud\u201d and accessing it through a web browser was not unfamiliar to them. Initially they had some questions about a few functional things, but we sorted those out quickly enough. The product itself is very intuitive (IMHO) so spending a little time on it is all that is necessary to understand how it works.<\/p><\/blockquote>\n
As there are serious demands placed upon the IT departments, they opted for a Nextcloud Subscription to ensure quality and performance of the service.<\/p>\n
Our systems department is working closely with your technical department to resolve any issues that come up. We try to keep the major updates\/upgrades to a minimum to reduce the downtime on this service. Our pilot has expanded to include researchers who needs a safe haven for their large data sets. This means that already we\u2019re held accountable for the uptime of the service.<\/p><\/blockquote>\n