Author-it [was: Single Sourcing tools]

[Christine Leisgen]

Dear Marie,

 

I guess you are right, I think the problem is that you cannot access the
same project file by multiple authors in Flare, and therefore reuse of
topics is either limited or more difficult to set up. [I have not tried
it though, if somebody else knows it's possible, please correct me.]

 

I guess the access control (who "wins" if the same file is changed at
the same time) is done automatically by the server in Ait?

 

Best regards, Christine

 

 

Message: 13

Date: Fri, 14 Sep 2007 08:05:55 -0700 (PDT)

From: "M. Palmieri" <mailinfodd-wrt at yahoo.com>

Subject: Author-it [was: Single Sourcing tools]

To: techwr-l at lists.techwr-l.com

Message-ID: <923040.63786.qm at web82308.mail.mud.yahoo.com>

Content-Type: text/plain; charset=iso-8859-1

 

Dear Christine,

 

Thanks for the additional information.

 

It seems that the ability of multiple authors to

access Flare files stored in a source control server

is different than the use of shared topics in

Author-it.

 

What I have observed in Author-it is that a topic (or

part of a topic) can be placed on a shared directory,

and then 2 or more authors can drag and drop the topic

into one of their TOCs. If the shared topic is

changed, the changes are propagated to wherever the

topic is used in multiple authors? table of content

structures. There is not a check-in/check-out process.

 

Of course it seems that shared topics need to be

planned for carefully, and from what I understand some

users recommend giving a limited number of authors

access to the shared topics. Authors using shared

topics could discuss in their team what kind of change

is needed to a shared topic before a change is

actually made.

 

The benefit seems to be that once content for a shared

topic is decided on, the content is consistent no

matter what author uses it.

 

Best regards,

Marie