It's all about the answers!

Ask a question

RTC for document management?


N Z (3622026) | asked Nov 09 '11, 11:57 p.m.
Is anyone using RTC for document management.

Any practical advice on how to manage document workflows, document versioning, RTC access (web vs clients) and any other information which might be relevant.

8 answers



permanent link
Geoffrey Clemm (30.1k23035) | answered Nov 10 '11, 7:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A couple of differences between using RTC for document management and
using RTC for source code management would be:
- You would commonly use the Web UI to access your documents, rather
than an IDE such as Eclipse or Visual Studio.
- You wouldn't be using the build component.

Cheers,
Geoff

On 11/10/2011 12:08 AM, nz wrote:
Is anyone using RTC for document management.

Any practical advice on how to manage document workflows, document
versioning, RTC access (web vs clients) and any other information
which might be relevant.

permanent link
Sebastien Hadjifotis (21) | answered Nov 10 '11, 9:23 p.m.
Further elaboration on our requirement is that the document has a lifecycle/workflow. Simple document status could be draft->review->approve.
The document has a version identifier that is associated with it: eg. 0.1 0.2 ... 1.0.
The checkout/checkin cycle promotes the document to a new version.

So how are people handling this simple document management scenario?

Cheers,
Sebastien

permanent link
Geoffrey Clemm (30.1k23035) | answered Nov 10 '11, 11:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In RTC, the document states are maintained by a work item that you would
associate with the changes you are making to the document.

Cheers,
Geoff

On 11/10/2011 9:38 PM, sebastienhadjifotis wrote:
Further elaboration on our requirement is that the document has a
lifecycle/workflow. Simple document status could be
draft->review->approve.
The document has a version identifier that is associated with it: eg.
0.1 0.2 ... 1.0.
The checkout/checkin cycle promotes the document to a new version.

So how are people handling this simple document management scenario?

Cheers,
Sebastien

permanent link
Christophe Lucas (8624847) | answered Nov 11 '11, 5:15 a.m.

permanent link
Sebastien Hadjifotis (21) | answered Nov 13 '11, 7:35 p.m.
Thank You

I have seen and read this article .. but it simply leans on using RTC for document file management. We need details on how RTC can be used to address the document versioning and workflow.

WRT using work item for workflow .... would appreciate some feedback on RTC being used in an actual site that has addressed our requirements and can provide specific details.

permanent link
Sebastien Hadjifotis (21) | answered Nov 15 '11, 7:30 a.m.
Has anyone done any work around document management using RTC?
Keen to see what other people have implemented.

Cheers,
Sebastien

permanent link
Sebastien Hadjifotis (21) | answered Nov 29 '11, 1:51 a.m.
So is no one is using RTC to manage documents then?

Cheers,
Sebastien

permanent link
Christophe Lucas (8624847) | answered Dec 21 '11, 4:41 a.m.
Further elaboration on our requirement is that the document has a lifecycle/workflow. Simple document status could be draft->review->approve.
The document has a version identifier that is associated with it: eg. 0.1 0.2 ... 1.0.
The checkout/checkin cycle promotes the document to a new version.

So how are people handling this simple document management scenario?

Cheers,
Sebastien


Sebastien, couldn't you:
- create a custom work item type called e.g. 'Documentation' or 'Documentation_Task'
- apply the draft->review->approve workflow to this custom WI type
- use this WI type to create/update new/existing documents, e.g. 'Create Vision.doc' Documentation_Task
- associate to this WI all File Deliver activities, with comments at each deliver, i.e. add a comment (cf. 3.a of 'Share and manage documents through the Rational Team Concert 3.0 Web UI' https://jazz.net/library/article/361)
- on this WI type, re-enforce an Approval and/or Review cycle
?

By using this (i.e. associating the workflow to a 'Documentation' work item vs. to a 'document' as per your requirement), you would not only have a 'Revision' history of your File, but also 'Approval/Review' checks, and your Documentation related work could be tracked as all other WIs in Plans, Queries, Reports etc

Your answer


Register or to post your answer.