Administering several individual wikis is technically intricate because all too often, a confusing “wiki chaos” develops, which is difficult to take care of. In this area there is already a concept which has proved itself: the wiki farm.
Several wikis can be created, archived or deleted quickly and easily by using a wiki farm. When creating wikis, the user has the option to create an empty wiki or to clone what is known as a “master wiki”. Such a master wiki can be already filled with content (e.g. handbooks), or contain files and configuration data, all of which can be transferred and supplied.
From a technical point of view, by using the farm concept, one can provide several wikis with just one wiki installation. The wiki software is only installed and saved once on the server and all the wikis use this installation together.
We have had an increasing number of enquiries from customers over the last few years for whom the best possible solution is provided by a wiki farm. Many have the problem that a single wiki is no longer sufficient, because they need to reflect the most differing topics, languages and permissions concepts. In such cases, we always recommend the use of several wikis via our wiki farm solution.
Why does one need several wikis?
By providing several wiki instances within one organisation, we can ensure that data and permissions structures are absolutely separated. While access to information can be controlled within a wiki by assigning permissions for separate namespaces, this harbours risks and gaps. The basic software MediaWiki does not recognise the regulation of access by namespaces and presents loopholes which an experienced user might make use of. On top of this, there is the risk of errors creeping in when permissions are assigned, making data available for non-authorised users. This can have fatal consequences, particularly in divisions with sensitive information like personnel, research and development or management.
Creating new individual wikis is also especially useful in project management. In general, projects with wikis can be excellently organised and monitored by including, structuring and keeping up to date the content of the project or data like the points of contact and costs, schedules and milestones or the current status and the to-do list. The security obtained by separating the data makes it possible to share a project wiki with, for example, external service providers or customers, so you can work together and exchange ideas without risk. When a project is concluded, then the wiki can be archived so that the information and data can be made available again if needed at a later time.
Single wikis are not intended to implement multilingualism. There are differing concepts around for solving this, but using separate wikis for each language is still the most elegant and cleanest option (see Wikipedia). This is an indispensable requirement for companies working across the globe, which can be optimally fulfilled with WikiFarm. BlueSpice even has its own special features here. Linking individual articles in different languages is done with InterwikiLinks. In such cases, BlueSpice automatically adds a menu for navigating between languages (see fig. 1).
Because multilingualism is just as much a hot topic and just as involved as before, we will devote a blog entry just to this topic so we can give more detail.
How does a wiki farm pay off?
So that the creation and maintenance of a number of wiki instances can be managed quickly and simply, there are farm solutions with which organisations and users can practically “host” as many single wikis as they want.
We have developed the technical basis of the BlueSpice farm solution a great deal further, and tailored and optimised it with a view to the individual use-cases of our customers. Not only MediaWikis, but also BlueSpices can be administered by the solution.
The great advantage of using a wiki farm is that the systems are simpler to maintain, which reduces the costs. Patches, updates and upgrades are only carried out in a single system but are available in all wikis of the farm.
Wikis with a limited “lifespan”, like project wikis, are better organised in a wiki farm: if there are processes and tasks that occur again and again, they can be put in a prefabricated structure in the master wiki and content which repeats can be populated. As soon as one needs to, one can clone this wiki so the project can begin immediately. After finishing the project documentation, the wiki is archived in such a way that it is no longer active. The information contained within it, can still be recalled at a later date.
Farm management is configured to be very clear (see fig. 2). Along with a description, keywords can be assigned to individual wikis. The list of wikis can be sorted, filtered and grouped according to different criteria. This makes all wiki instances simple to keep an eye on, and redundant wikis and unused relics can be avoided.
Putting together the biggest advantages of a BlueSpice WikiFarm, we have:
- 1 click installation for new wiki instances
- Very little effort needed to update and upgrade
- Provision of standardised content via master wikis
- Data security because content and rights can be separated
- The clear presentation, sorting and filtering of wikis
If you would like to create and manage several wiki instances in the twinkling of an eye, WikiFarm is exactly the right solution for you. Even when operating just a second (Media)Wiki, the software’s architecture and administration interface save time and costs.