Making a Wiki for my lab group (in Off-topic)
October 23 2007 3:56 PM EDT
My advisor wants our lab to have an internal wiki in order to make information we have available to all group members. I have been chosen to make this wiki, but am not sure what software to choose or where to start. An suggestions from the community are welcome, but I would prefer to hear from people who currently use an internal wiki.
Things my wiki must be able to do easily:
Store .pdf files and Endnote libraries for all our our literature (background stuff for various projects)
Store slide presentations that will be used to educate future group members
October 23 2007 4:08 PM EDT
That's not a wiki, that's a document management system...
October 23 2007 4:34 PM EDT
He is obsessed with the 'buzz word' wiki. If a document management system is what we need can you refer me to one? I'll just name it 'wiki.'
October 23 2007 4:38 PM EDT
We have several MS Sharepoint sites in our company. Pretty easy to setup and maintain.
Here is one using LAMP: http://en.wikipedia.org/wiki/KnowledgeTree
I don't know if there are many others in this sphere, as it's a big "money maker" for lots of people.
October 23 2007 6:28 PM EDT
I have a friend who just installed Plone for his department. The other big open-source ones are Drupal and Joomla.
All of them are a fair amount of work to customize. My friend went with Plone primarily because it has by far the best security record.
Plone is pretty sweet once you get up and running, but thats the tricky part.. At my last job, they had Plone setup to do some CMS stuff, but the client it was setup for didn't get how to use it (even though I found it surprisingly easy to use). And besides that it had stability issues with the plone deamon staying awake.. But it might have just been all the customizations we did to it.
This thread is closed to new posts.
However, you are welcome to reference it
from a new thread; link this with the html
<a href="/bboard/q-and-a-fetch-msg.tcl?msg_id=002FsS">Making a Wiki for my lab group</a>