that is exacly my problem. I (as a developer) can use subversion to
store and version my documents. Together with tortoiseSVN it is also an
elegant solution, that you can teach to non developers. But I'm missing
the workflow/lifecycle behind it.
How do you publish a document from a "draft" state into an "executive"
state. Naturally you can copy the file into a folder named "executive"
but still this is quite complex, since most of the documents stand for
themself. Perhaps a handfull of documents together will form a project,
but most of them are standalone. documentA at version 1.0 has nothing to
do with documentB at version 1.0. Grouping different documents into a
label folder doesn't make any sence. It feels like a multiproject setup
for documents, but with a common directory structure.
How do you revoke a document, so that anybody can follow this step easily.
I have to admit, that I don't have a real set of requirements that I
need to have fullfilled. I'm looking for solutions and simply storing
the documents into subversion is a good first step. But we more and more
have the problem that we need to distinguish between a published
versions and drafts, that we need to have access to older published
documents and that we need to see in an easy way the state of a document.
Other features like access control, full text search and easy one step
integration into the explorer are nice to have features. If you look for
example at the Xinco DMS, this kind of setup is probably the most
secure, it is also approved by the FDA, but the overhead to edit a
document is quite high.
So I'm looking primarily for
* recipies, how one could structure subversion in order to fullfill
basic DMS feautures.
* tools that can support these recipies
marc gonzalez-carnicer schrieb:
> You are right. I was describing just a "kind of" DMS that somehow
> suited my needs.
> 2007/6/26, Clemens <firstname.lastname@example.org>:
>> Excuse me, but in my opinion this does not mean DMS. If you want real
>> DMS the system has also to be able to maintain a document's lifecycle
>> that normally is very different than that from e.g. sources.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 28 19:53:29 2007