Better Document Management:
Novell Teaming 2 - Document Management for the Masses
By Ken Baker
Novell Connection Magazine - October 2009
Here's an excerpt:
When you first take a look at Novell Teaming, it’s likely because you want a better way for your users to collaborate and share information with their peers. As you dig in and start to use it yourself, you’ll get even better insight on the value it delivers such as the ability it gives you to generate great ideas; then share, act and preserve them; and then leverage those ideas for other projects. Spanning all three of these value areas, Novell Teaming includes document collaboration/management capabilities that enable users to better manage the lifecycle of the content they create.
Novell Teaming delivers basic document management for the masses that is easy to use, effective and inexpensive.
It should be noted upfront that the document management capabilities in Novell Teaming are not on the grand scale that you would find with a comprehensive and expensive document management platform. Rather, Novell Teaming delivers basic document management for the masses that is easy to use, effective and inexpensive. Perhaps more important is that Novell Teaming enables you to move from the inefficient, error-prone, but often-used e-mail attachment-based document-management scheme to a more efficient and easy-to-use paradigm with version control, access control, histories and powerful workflow capabilities.
Managing the Document Lifecycle
E-mail was never really designed as a tool for content creation, but we use it that way all the time. You create a document and e-mail it out to your team members for review. Hours or days later, you receive five or so e-mails back, all with updated versions of your document attached. You then spend hours sorting through and consolidating the edits and comments. When there are conflicts, you have to decide which edits trump other edits, then hope you guessed correctly. If you don’t want to do the guesswork, you often must have a conference between team members just to sort out the conflicts. The further you go down the revision path, the more complex the problems become. For instance, you might be on your fifth round of edits when you receive an e-mail attachment full of significant edits, but they’re all based on the first version of the document. What do you do then?
Read the article here
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.