Easy setup of a wiki-based knowledge management system using Tiki | |
Link to event: https://fosdem.org/2019/schedule/event/collab_tiki_wiki_knowledge_base/ Abstract: I will demonstrate an easy and fast way of configuring Tiki Wiki CMS Groupware for the purpose of having a central repository for a knowledge base. I will also explain how to manage permissions for various use cases, how to separate different topics, how to access stored knowledge. Full Description This presentation will start with a minimal Tiki site and show how to build structures of pages and file repositories.
I will show how to configure permissions for a publically visible and editable knowledge base, or separate knowledge bases which are restricted to groups of users and invisible to others, or intermediate scenarios with groups of editors and groups of read-only viewers. I will show the basics of how to make the knowledge acessible, searchable, navigatable and allow comments from people who can only view it. HOWTO
We start with a real-life Tiki website right after the installer was run. Nothing special except I put my email in Sender email field because I want people who get automated notifications to reply to me in an easy way. |
Setting Tiki | |
I did the demo on a local VM http://fosdem.alsawiki.com You need to adapt links shown below to your own site. |
Special for the FOSDEM presentation: theme trick | |
I set a different theme for admins than normal users to make it clear if it's an admin's view or a user's view for the people who watch the vidéo. Settings → Groups → Admins Now admin views are mostly white and anonymous browsing or normal users are grey. |
General Tiki improvements | |
I set a number of configurations which make sense for our use case or are required for the site to perform as we want. activate features http://fosdem.alsawiki.com/tiki-admin.php?page=features
General configurations http://fosdem.alsawiki.com/tiki-admin.php?page=general&cookietab=3
Look & Feel Copy to clipboard
Admin Wiki
Recap
Preference wiki url scheme set (Preference name: wiki_url_scheme) |
Set up global permissions | |
Recap
Global permissions: Reload user browser: Lost access to everything, as expected. |
Reorganise modules and HomePage | |
For the benefit of visitors. HomePage Copy to clipboard
Remove list of authors. Edit HomePage |
Set Modules | |
Settings → Modules Move login module from top to left Add Since last visit to right section Add Search module to right (with more time, it might be nicer in top section but detailed placing requires CSS) Restrict Menu 42 module to Admins Reload user browser: View the site for Anonymous users (not logged in) |
Create a new workspace for AACMEE Corp (aacmee) | |
Totally fictitious Corporation, don't sue! 😊 |
Create category aacmee | |
Uncheck Apply parent category permissions |
Create group aacmee | |
|
Set Group permissions for category aacmee | |
"Categories" → "Admin Categories" → aacmee (spanner) → Permissions Select group aacmee for display. All permissions are set for group aacme
Recap
Object permissions for the category aacmee (ID 1): aacmee: tiki_p_blog_post (blogs) |
Create user account Vile Fox | |
"Admin Users" → fill
(no self-registration, only professional contacts known beforehand here) Set him in group There won't be a confirmation mail (this is a demo running on a VM). Force validation as admin (right-hand spanner for user) Log in and set the password for Vile Fox |
Create file Gallery aacmee | |
First create a projects file gallery to keep things orderly.
Group Monitor: aacmee |
Create blog aacmee day-to-day interventions | |
Description: Tasks performed for AACMEE Corp. This is for keeping track of day-to-day interventions
Categorize: aacmee → Save → Note number NNN Group Monitor: aacmee |
Create custom module | |
So as to let users and yourself find their way. Admin → Modules Name: Custom menu aacmee Data: Data template Copy to clipboard Data already replaced with values you get if you start from scratch and follow the above instructions Copy to clipboard → Create Click Assign → Assign Edit again (double click) Exit Modules |
That's it | |
You can add other customers and other companies and they won't see each other. |
Extensions and improvements | |
Please remember that more communication channels does not necessary lead to better communication. As an example, a small addition to the above would be to create a bug tracker for a customer/project. This would be done just like adding the blog or the file galleries above. Yet, in 8 years only a single customer of mine wanted to communicate using a bug tracker. If you feel constrained by the end result of the above and you would like full control of forms, processes and such, you can have a much more elaborate site and more customisation using Tiki's trackers feature (which really stands for our inbuilt database/forms system). But that's off-topic. |