Hey, all,
Thanks for your quick and fantastic responses! I am loving this list. :)
I take the excellent point about looking at whether this is the right tool for the job. However, the decision to use a wiki comes out of two consultant recommendations to use a wiki and reactions to a failed Sharepoint intranet installation (dating to around 2000) that people hated because it required use of proprietary software, in that case, Microsoft FrontPage. Moreover, the specific decision to use MediaWiki was vetted through all of the proper channels, and no one raised any objections.
Thanks again, everyone!
Nina
Nina McHale, MA/MSLS Assistant Professor, Web Librarian Auraria Library http://library.auraria.edu/~nmchale/ Facebookhttp://www.facebook.com/profile.php?id=672599042 Twitter: ninermac Serving the University of Colorado Denver, Metropolitan State College of Denver, and the Community College of Denver 1100 Lawrence Street Denver, CO 80204 303-556-4729
A more multi-platform friendly (and free/open source) competitor to Sharepoint would be Alfresco, which cooperates very well with MediaWiki, if you want to consider supplementing the wiki with an ECM...
Ben
Sent from my iPhone
On Apr 28, 2009, at 1:45 PM, "McHale, Nina" Nina.McHale@ucdenver.edu wrote:
Hey, all,
Thanks for your quick and fantastic responses! I am loving this list. :)
I take the excellent point about looking at whether this is the right tool for the job. However, the decision to use a wiki comes out of two consultant recommendations to use a wiki and reactions to a failed Sharepoint intranet installation (dating to around 2000) that people hated because it required use of proprietary software, in that case, Microsoft FrontPage. Moreover, the specific decision to use MediaWiki was vetted through all of the proper channels, and no one raised any objections.
Thanks again, everyone!
Nina
Nina McHale, MA/MSLS Assistant Professor, Web Librarian Auraria Library http://library.auraria.edu/~nmchale/ Facebookhttp://www.facebook.com/profile.php?id=672599042 Twitter: ninermac Serving the University of Colorado Denver, Metropolitan State College of Denver, and the Community College of Denver 1100 Lawrence Street Denver, CO 80204 303-556-4729
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
SharePoint has changed TREMENDOUSLY since 2000.
We use both MediaWiki and SharePoint at my job. Each has its strengths and weaknesses. We use the wiki for general knowledge and SharePoint for documents.
SharePoint is a much more complex product than MediaWiki however. Don't install it unless you are prepared to hire an in-house SharePoint expert or two. Any PHP programmer can learn to be a MediaWiki admin, given time, but SharePoint administration requires a deep background (in SharePoint) to do well.
DanB
McHale, Nina wrote:
Thanks for your quick and fantastic responses! I am loving this list. :)
I take the excellent point about looking at whether this is the right tool for the job. However, the decision to use a wiki comes out of two consultant recommendations to use a wiki and reactions to a failed Sharepoint intranet installation (dating to around 2000) that people hated because it required use of proprietary software, in that case, Microsoft FrontPage. Moreover, the specific decision to use MediaWiki was vetted through all of the proper channels, and no one raised any objections.
Thanks again, everyone!
I hate Sharepoint with a passion. However, I realize that it's better at what _it_ does (being a document repository) than MediaWiki is. For most "documents" though, being simple text online and immediately editable like the wiki model seems a better solution to me. If there were some extension that allowed cooperation between MediaWiki and Sharepoint, letting each do what it is good at, that would be fantastic. I'm not even sure what that would look like, though.
Tim
mediawiki-l@lists.wikimedia.org