14 Oct
2008
14 Oct
'08
12:58 p.m.
We envision using xwiki to manage 2 different parts:
1. A public one accessible to our customers only
2. A private one for internal use only
My question is the following: what is the best strategy to achieve a clean content
separation:
Space partitioning (i.e. one wiki, but 2 or more spaces)
or
wiki partitioning (i.e. separate wikis)
Space partitioning seems easier to set up, because only 1 wiki is needed. However, my
concern is the risk of having a sloppy employee inadvertently publishing an internal page
on the wrong space, i.e. on a public space. With the wiki partitioning scenario, I
don't even know if this is possible to set up xwiki so as to have several wikis while
running on the same code base. On top of that, I would like to have internal users being
able to search through a common index (public + private), while customers could only
search the public one. I don't know if that's possible at all with wiki
partitioning.
Has anyone of you guys experience with such a setup?
What are the pros and cons of each?
What would the experts / architects recommend here?
Thanks for the insights.
ALBAN SCHMID
CLIENT SOLUTIONS SPECIALIST
DIRECTOR, CHANNEL SOLUTION SERVICES
CBS Interactive - Channel
Tel: +41 21 943 03 86
Skype: albanschmid
Rte Industrielle 2 | CP 138 | 1806 St-Légier, Switzerland
CNETChannel.com
14 Oct
14 Oct
6:29 p.m.
New subject: [xwiki-users] Public vs. Private strict content separation - what's the best strategy?
Hi Alban,
We envision using xwiki to manage 2 different parts:
You can do both depending on your personal preference. Thanks to XWiki
Enterprise Manager (http://manager.xwiki.org/), XWiki makes it easy to run 2
wikis as part of the same farm on the same server, meaning that you could
have a shared user base and yet 2 different wikis. As for global search, you
can setup a global search on XWiki Enteprise Manager. Since search results
are rights-filtered, your users won't be able to see pages they're not
allowed to either way. In XWiki you'll need to create 2 groups (one for your
employees and one for your customers) and set rights for those groups at
either the space or wiki level depending on your choice.
Since you can set user rights and user interface preferences (skin color)
both at the wiki and the space level, those features don't affect your
decision much.
To summarize: both solutions should work out fine. If you're afraid of
having employee publishing stuff in the wrong place, you might want to setup
2 different wikis (they'll have their own URLs : http://wiki1.server.com/and
http://wiki2.server.com/ which is probably the key point in yoru use case).
Hope this helps,
Guillaume
> Thanks for the insights.
> ALBAN SCHMID
> CLIENT SOLUTIONS SPECIALIST
> DIRECTOR, CHANNEL SOLUTION SERVICES
> CBS Interactive - Channel
> Tel: +41 21 943 03 86
> Skype: albanschmid
> Rte Industrielle 2 | CP 138 | 1806 St-Légier, Switzerland
> CNETChannel.com
>
_______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://blog.xwiki.com/
1. A public one accessible to our customers only
2. A private one for internal use only
My question is the following: what is the best
strategy to achieve a clean
content separation:
Space partitioning (i.e. one wiki, but 2 or more spaces) or wiki
partitioning (i.e. separate wikis)
Space partitioning seems easier to set up, because only 1 wiki is needed.
However, my concern is the risk of having a sloppy employee inadvertently
publishing an internal page on the wrong space, i.e. on a public space. With
the wiki partitioning scenario, I don't even know if this is possible to set
up xwiki so as to have several wikis while running on the same code base. On
top of that, I would like to have internal users being able to search
through a common index (public + private), while customers could only search
the public one. I don't know if that's possible at all with wiki
partitioning.
Has anyone of you guys experience with such a setup?
Yep. We actually have experience with both of them.
What are the pros and cons of each?
What would the experts / architects recommend here?
15 Oct
15 Oct
1:57 p.m.
New subject: [xwiki-users] Public vs. Private strict content separation -what's the best strategy?
Thanks Guillaume,
That's very useful.
Regards,
ALBAN SCHMID
CLIENT SOLUTIONS SPECIALIST
DIRECTOR, CHANNEL SOLUTION SERVICES
CBS Interactive - Channel
Tel: +41 21 943 03 86
Skype: albanschmid
Rte Industrielle 2 | CP 138 | 1806 St-Légier, Switzerland
CNETChannel.com
-----Original Message-----
From: users-bounces(a)xwiki.org [mailto:users-bounces@xwiki.org] On Behalf Of Guillaume
Lerouge
Sent: Tuesday, October 14, 2008 6:30 PM
To: XWiki Users
Subject: Re: [xwiki-users] Public vs. Private strict content separation -what's the
best strategy?
Hi Alban,
We envision using xwiki to manage 2 different parts:
You can do both depending on your personal preference. Thanks to XWiki
Enterprise Manager (http://manager.xwiki.org/), XWiki makes it easy to run 2
wikis as part of the same farm on the same server, meaning that you could
have a shared user base and yet 2 different wikis. As for global search, you
can setup a global search on XWiki Enteprise Manager. Since search results
are rights-filtered, your users won't be able to see pages they're not
allowed to either way. In XWiki you'll need to create 2 groups (one for your
employees and one for your customers) and set rights for those groups at
either the space or wiki level depending on your choice.
Since you can set user rights and user interface preferences (skin color)
both at the wiki and the space level, those features don't affect your
decision much.
To summarize: both solutions should work out fine. If you're afraid of
having employee publishing stuff in the wrong place, you might want to setup
2 different wikis (they'll have their own URLs : http://wiki1.server.com/and
http://wiki2.server.com/ which is probably the key point in yoru use case).
Hope this helps,
Guillaume
> Thanks for the insights.
> ALBAN SCHMID
> CLIENT SOLUTIONS SPECIALIST
> DIRECTOR, CHANNEL SOLUTION SERVICES
> CBS Interactive - Channel
> Tel: +41 21 943 03 86
> Skype: albanschmid
> Rte Industrielle 2 | CP 138 | 1806 St-Légier, Switzerland
> CNETChannel.com
>
_______________________________________________
> users mailing list
> users(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/users
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://blog.xwiki.com/
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users
1. A public one accessible to our customers only
2. A private one for internal use only
My question is the following: what is the best
strategy to achieve a clean
content separation:
Space partitioning (i.e. one wiki, but 2 or more spaces) or wiki
partitioning (i.e. separate wikis)
Space partitioning seems easier to set up, because only 1 wiki is needed.
However, my concern is the risk of having a sloppy employee inadvertently
publishing an internal page on the wrong space, i.e. on a public space. With
the wiki partitioning scenario, I don't even know if this is possible to set
up xwiki so as to have several wikis while running on the same code base. On
top of that, I would like to have internal users being able to search
through a common index (public + private), while customers could only search
the public one. I don't know if that's possible at all with wiki
partitioning.
Has anyone of you guys experience with such a setup?
Yep. We actually have experience with both of them.
What are the pros and cons of each?
What would the experts / architects recommend here?
5912
days inactive
5913
days old
2 comments
2 participants
participants (2)
-
Alban Schmid -
Guillaume Lerouge