My company is in process of upgrading the intranet site presently running on SharePoint 2003. As part of this exercise, we are trying to weigh out MediaWiki against SharePoint 2007.
We seem to be heading to a mixture of the two. The main reason why we are not able to rule out SharePoint 2007 is a) File Uploading in MediaWiki isn't that good b) MediaWiki doesn't have features like Calendar, Task List etc., which are needed in our intranet. We could have Wiki as the main backbone, with connections to SharePoint 2007, where needed.
What we are not sure is how effective is the connection between MediaWiki and SharePoint 2007 and whether there are any issues in this interface. Any advice and suggestion from the vast experiences of this community will be highly appreciated.
Thanks in advance.
Offline
Blending Sharepoint and Medaiwiki is a none trivial task. Architecturally they are very different and use very different underlying engines. Depending on your level of integration you are looking for, you may want to consider developing an API to help like across.
You may also consider doing some additional research on extending the capabilities of Mediawiki. I have a Mediawiki instantiation (1.12.0) with a full up calendar, message board, etc. There are also an extension for task list; a good starting point is www.mediawiki.org.
Best of luck!
Offline
(I know this thread is somewhat old, but in case someone else is having the same considerations...)
One of things to consider is of course how to get a consistent user interface. In case of MediaWIki/Sharepoint integration, I would suggest using the Sharepoint-look-alike skin for MediaWiki that is available at http://www.rilnet.com/en/skins/
We developed it with the integration usecases in mind. It's available for Drupal too, so you can have the same look for all these three systems (Sharepoint, MediaWIki and Drupal).
Regards
// Samuel Lampa
Last edited by SHL (2009-01-14 03:45:54)
Offline
We have a SharePoint Connector that works with our enterprise wiki, Confluence. We developed it because so many customers had said that they use both products. Essentially, it allows you to create content (or upload a document) in one tool, and access it or search in in the other one, and visa versa. The idea is that you can work in your favorite tool, but not miss out on content created in the other application by a another user in a different part of the organization.
Confluence: http://www.atlassian.com/software/confluence
SharePoint Connector for Confluence: http://www.atlassian.com/sharepoint
Offline
bugmenot wrote:
It is very interesting for me to read that article. Thanks for it. I like such topics and anything that is connected to them. I definitely want to read a bit more soon.
More stuff available at http://www.bendsoft.com and http://blog.bendsoft.com
Offline
You are not logged in.