Easy setup of a wiki-based knowledge management system using Tiki | |
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.
This presentation will start with a minimal Tiki site and show how to build structures of pages and file repositories.
I will show the basics of how to make the knowledge acessible, searchable, navigatable and allow comments from people who can only view it.
|
Table of contents | |
HOWTO
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 | |
|
Special for the FOSDEM presentation: theme trick | |
Settings → Groups → Admins
Now admin views are mostly white and anonymous browsing or normal users are grey. |
General Tiki improvements | |
activate features http://fosdem.alsawiki.com/tiki-admin.php?page=features
Copy to clipboard
Recap
Preference wiki url scheme set (Preference name: wiki_url_scheme)
|
Set up global permissions | |
Recap
Global permissions:
|
Reorganise modules and HomePage | |
For the benefit of visitors. HomePage Copy to clipboard
Edit HomePage |
Set 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 | |
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 | |
(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 | |
|
Create blog aacmee day-to-day interventions | |
Description: Tasks performed for AACMEE Corp.
This is for keeping track of day-to-day interventions
→ Save → Note number NNN Group Monitor: aacmee |
Create custom module | |
So as to let users and yourself find their way.
Admin → Modules
Create new custom module
Name: Custom menu aacmee
Title: aacmee
x ← Must be wiki parsed.
Data:
Copy to clipboard |
That's it | |
You can add other customers and other companies and they won't see each other. Yet you can communicate with them and changes trigger email notifications. |
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). That's more complex than the above, but also way more powerful. Yes, if you want more control than a plain blog, you can rewrite the blog feature using trackers. Same for file galleries. But that's off-topic. |