It doesn’t always have to be text. A smart mixture of written and graphic content is recommended to overview information and quickly absorb knowledge. Markus Glaser, CEO of Hallo Welt! GmbH, explains the possibilities of visualization in the BlueSpice enterprise wiki.
It is crucial for organizations that the documentation in their wiki is stored in a comprehensible and revision-proof manner. BlueSpice MediaWiki now supports you in the balancing act between traceability and data protection. Against the background of the General Data Protection Regulation (GDPR), we have revised our enterprise wiki software with regard to the protection of personal data.
The GDPR defines a number of basic rights that are also relevant for BlueSpice MediaWiki users:
- Information: Users have the right to know what data about them is stored in the system.
- Data portability: Users must be able to extract the data stored on a platform and transfer it to another system.
- Correction, erasure or blocking: Users may request or arrange for their data to be corrected. They may also request the deletion or blocking of access to their data.
- Forgetting: It must be possible to cancel the linking / assignment of data to individual users.
- Consent: Users must be able to give their differentiated consent to the storage and use of their data.
Continuing our comparison of BlueSpice MediaWiki and Confluence – with a short summary.
In this second part we concentrate on those functions aimed more at power users and administrators than at normal users. (Read here part 1 of our comparison)
BlueSpice and Confluence differ significantly in how they deal with metadata. Continue Reading
In this two-part article, we give a detailed comparison of the wiki top dog MediaWiki and Confluence.
We already wrote a few words about MediaWiki and Confluence some years ago. At that time, we wrote about the main objections to MediaWiki.
That article is still worth reading and remains largely valid. Ultimately the key argument then was that the choice of tool did not depend only on features, but also on the concept behind the software. This is a timeless truth.
However, MediaWiki does not need to fear a direct feature comparison. Importantly, the enterprise distribution BlueSpice has already decided the feature question in my view. This can be seen on our newest internal feature-comparison table, published here and offered for free download:
- Feature Comparison BlueSpice and Confluence 2017.xlsx
- Feature Comparison BlueSpice and Confluence 2017.ods
This publication is a good chance to detail the differences and similarities of the two projects comprehensively and systematically. Continue Reading
The installation of wikis and quality control of the wiki software is still generally done by hand. Obviously, this increases the costs for the customers. And the software producers do not find this repetitive work much fun either. Continue Reading
With BlueSpice 3, we replace the previous VisualEditor with the MediaWiki VisualEditor, which some people will already know from Wikipedia. This leads to questions, for example: Why are we changing now? What potential does the editor have? And what is the situation with real-time editing? Continue Reading
Everything used to be simple: database queries for structured data and full-text search functions were conceived separately. But that is now history. In new search engines, metadata can be searched for much more selectively. These new possibilities blur the distinction between a database query and a search function. What does this mean for the technological development of wikis? Continue Reading
We are currently fitting out the new Version 3 of BlueSpice with a new search engine. So this is a good opportunity to explain what actually happens in a search engine and why we have decided to make this change. Continue Reading