>5. Upload it, using the same File:xxxxx name as the original document
>(assuming you remember it) 6. Panic, when you realize someone else
>uploaded the same document a few minutes before you did, and you just
>wiped out their changes without realizing.
Now, wait just a second here, correct me if I'm wrong, but if the"someone
else" of whom you write did indeed upload the same document a few minutes
before you did, then their changes are not "wiped out" but, are nicely
captured in a previous version of the same file, under the same file name.
Agree, it's not a good solution for heavy traffic, but if you have just a
few users who are mostly downloading... I just recently created a Semantic
MediaWiki installation for a customer who wanted a shared calendar (Semantic
Results Formats) and a Document Repository for a quick set up that would
only last a few months.
I think we did a nice job-- we took the 'upload file' out of the Monobook
skin and added a tool bar to upload documents to certain "portal" pages.
Using Semantic MediaWiki and Semantic Forms, we created forms & templates
that allowed uploads (with filename auto completion from existing filenames)
that tagged the file with the right properties to make the 'Image:' pages
show up on the "portal" pages where the files are listed. I'm feeding the
query results to templates using the collapsable tables css from
en.wikipedia/wiki/MediaWiki:Common.css to create a microsofty folder-type
view that seems to resonate with the users.
Agree, it's not ideal and it's not a CMS. But, I run a wiki farm, not a web
hosting service. All things considered, I'm pretty happy with the result.
I can't do the inverse with a CMS-farm. ...I can't also use it as a wiki.
The magic combination for all the enterprise 2.0 needs seems to be the
combination of MediaWiki and Semantic MediaWiki (+Semantic Forms and
Semantic Results Formats).
I appreciate the links to o3spaces, alfresca, and opencms, tho. Those look
like long-term solutions for customers that need solutions that persist.
-CW