Subdivisions of a wiki

In large companies, a wiki will have to handle multiple subjects, not related to one another. The initiator of a project might want to have some separation between his pages and the rest of the wiki1.

Reasons

  1. Restrict acces rights (who can read, who can write?)
  2. Limit search and navigation to his pages (FindPage, TitleIndex, WordIndex, RecentChanges...)

  3. Different default presentation style or logo

ACL's could be used for point 1., but would have to be managed by the users for each of their pages (too dangerous and too complex).

Wiki farms could answer to all the points; each wiki would have different configuration files and of course the search and navigation would be limited to one wiki.

But

Large wiki farms have many disadvantages:

Solution

New sub-wiki feature:

IMHO it would make more sense to discuss this single features needed seprately.

Additionally there are some general questions:

Alternative 1

Extention of the wiki farm model:

Alternative 2

Multiple UnderlayPages (see also MultiLang):

What is needed here is not underlays but overlays. Pages from different wiki are visible within one other wikis but are edited in their original wiki.

Alternative 3 - facets

Have one big wiki, where subwiki is a facet. For example, each page in a wiki can belong to multiple subwikis, or groups. In this alternative, there is actually one big wiki that you can filter by your needs, or is being filtered for your by your access control rights.

Currently moin does not have a way to add meta data, but we work on it (see MetaData and MetaDataInMoin). Here is an example for wiki meta data:

{ { {
#!meta
Wiki: RedWiki
Wiki: BlueWiki
...
} } }

Now with meta data search, or filtering, you can do a partial search. You can also assign users to pages by meta data and like.

For example, we can have a facet browsing device, like FacetBrowsingTheme, that let you filter information you see in the wiki. Or a search menu that let you search in all wikis or only in one.

Having one big wiki will solve automatically the user management, and save lot of duplication of pages.

We wait for your comments about these alternatives.

-- JeanJacquesKahn 2005-03-15 12:23:02

This last one seems the most elegant because it satisfies the funcionality needed with a powerful resource (MetaData) that is being developed right now and serves also other purposes. I vote for it, no doubt. -- EduardoMercovich 2005-03-15 16:01:34

  1. Twiki has this feature for quite some time and it's a plus for big organizations. (1)

MoinMoin: FeatureRequests/CorporateWiki/SubWikis (last edited 2007-10-29 19:10:04 by localhost)