Cross Platform Document Management Systems? 32
Alan asks: "I'm
looking for a way to do document management at the office. We have
windows people and linux people, some writing documents that are a few lines (developer notes for example) and others are full of charts, graphs, etc. Currently we have a file server that has shares
set up for the documentation, but it lacks any sort of revision
control, and with the salespeople writing in Microsoft Word there are
cross-platform issues. We were thinking of setting up an wiki or an everything-based site, but as it is
only text, it's not good enough for everyone. There is also the
matter of getting our master documentation (which is in PDF format)
accessable to everyone as well, possibly in an XML format that can be
imported into indesign or Pagemaker or something. There are lots of
solutions that work for different departments and different systems, but
it would be nice to have something that works for everyone."
Framebuilder (Score:2)
Re:Framebuilder (Score:2)
PVCS (Score:1)
or any one of a million other source/document control systems.
Document management (Score:1)
Downloading/saving files is done via HTTP (users can work via the same system at home).
That said, our company likes making our own wheels. In the end we find it's less work (especially on a simple project like this).
Xerox Docushare (Score:2, Informative)
It's web based, features access controls and revisions, HTML rendering of Office documents, and a lot of other nice things.
Best simple document management system I've seen that scales from small teams to large groups.
PDF for everyone? (Score:2, Insightful)
Document *sharing* (Score:3, Insightful)
Simple (Score:3, Interesting)
Here is the best system for managing documents, it's simple, yet very effective. The technology or database here is a matter of preference - let's address "business flow".
You need a single directory to store all of your documents - no subdirectories. The categorization should be held in the database. This makes for simple backups and not having to heavily integrate your application with the server's file system.
You should have 5 ways to access the files - categorical, by date, by "uploader", by type, and a search function that indexes the complete text held within each document. Verity has a very nice offering for indexing MANY different types of files.
All of the 5 different methods of access should be linked. For instance, if I am browsing categorically and I run across a documentation style I like in particular, I should be able to click a link that takes me to the "uploader" filter that will show me all the other documents that individual uploaded.
Another example is if I did a full-text search for "widgets 123" and had a long listing of documents, you should list the categories they reside in so the user can click that category and be taken to all of the documents in that category.
Two phrases should be at the top of every thought you have regarding this system:
Fully Integrated
Stupid dumb easy to use
Adam.
Re:Simple (Score:2)
Re:Simple (Score:1)
Here is a quick primer on database-driven categories. One table, three fields:
primary key parent key name
All of your root level categories would have a parent key of 0. Your subcategories would have a parent-key of whatever their parent categories primary-key is. You just need to write recursive SQL to traverse up and down the parent-child structure and it actually works quite well. All of the logic sits snuggly in your database.
Re:Simple (Score:2)
The more I think about it, the more I like your approach. The files can be indexed and organized into arbitrary structures, and the RDBMS does all the heavy lifting.
I'm I the only one who thought of this? (Score:2, Interesting)
(Or, alternatively, PDF, which is equally well supported. Though you lose the ability to browse the documentation off your favorite web browser.)
For revision control: Try CVS with SSH (instead of RSH) for updating. Cheap. Effective. Highly portable. Add a little script so that it automatically checks out the latest versions of whatever is checked in, and checks them out into a public place -- perhaps into your intra-web-server's (Apache's) directory.
For your sales people, add commands (batch or bash scripts) to create/checkin files to their windows explorer browser commands list... So they can easily update/checkin files using their winX click and drool interfaces... (But, of course, it only works for the "right" file types...)
Welcome to format hell (Score:3, Informative)
The problem is compatibility between applications. Every application has its own format -- in some cases even different versions of the same app can't share files.
The software vendors would like you to believe that their products solve this with "import/export" filters. Bullshit. I have never, ever seen such a filter that's suitable for everyday use. Some require a lot of skill to use. But most just fail to parse this element and that. So you get data loss ranging from minor formatting errors to suprise content loss.
The closest I can suggest to a total solution is to make everybody standardize on a small set of formats. There's a minimum of three, for plain text (and don't forget the Mac/Unix/DOS line break issue!), rich text, and graphics (possibly more than one). Easy enough to find standard formats for each these. The hard one is rich text, but not for any technical reason.
Technically it's simple. Settle on a widely-used rich text format and forbid everything else. If you don't care about the content-formatting dichotomy, LaTeX is a good candidate -- techies can use their favorite text editors, techno-muggles can use any number of WYSIWYG tools. (Being a technical writer, I would insist on XML, but that doesn't make sense for every organization.) Problem solved, right?
Wrong. If your organization is at all typical, you've got a lot of people who have an investment in their Word, Powerpoint, and Excel skills, and would quit if they had to start over. That's a social engineering problem, and I don't have a solution for it.
Re:Welcome to format hell (Score:3, Insightful)
Please work on your insults (Score:2)
I'd tell you how old I am if I thought you could count that high!
Zope (Score:3, Informative)
I've been looking at this lately and Zope is an ideal solution.
Zope can grok anything if you can find/write a product for it. It can also search it using ZCatalog.
I downloaded the MSWordDocument product and it kicks ass. When you stick a Word document into the Zope database it has it's own 'type.' When you access the document it will, by default, render it in HTML (thanks to wvware) and display it, with a bar at the top with a 'download' link that retrieves the original document. What makes this even cooler is that, since Zope can extract the text, ZCatalog can give you a search interface.
I built a simple system with search in about five minutes using the web interface and DTML tags. No lie.
There's a similar product for PDF files and if I make one for StarOffice files, it'll be useful at the place where I work.
To top it all of, Zope has built in versioning. You can even do diffs between arbitrary versions. It also has webdav support so that Windows users, with 'Web Folders' and Linux users, with davfs, can open and save files, with locking and everything as if they were local.
All the little stuff is already there, too. User accounts and login handling is native, you can attach metadata to anything, and you can write scripts in Python, Perl, or PHP.
Needless to say, I highly recommend it.
Adobe Framemaker is a tried and true solution (Score:1)