Best Versioning Method

[Sara Levy]

I need to maintain two versions of our documentation in our Author-it library, which is something new for me. I first thought I would use this method: make a new book object for the new version of each guide, and, whenever I need to make a change to a topic, create a new version of that topic and make it the active version. I see that there is an alternative to create a duplicate of a topic object instead of a new version. 

If I should need to publish an old version of a doc at a moment's notice, I will need to switch which version of many topics is the active version. Will I have to do that separately for each topic, and do so from the folders view? i.e. locate each topic in the folders view and then select it, go the manage ribbon, and change the active version? And the same for all file objects? If so, that sounds like a nightmare. Is it therefore more efficient for me to work with duplicates, which will presumably have their own object code? Or is there a way to switch the active version of all topics in a book?

I am working with version Author-it 6.21

(I don't think I want to use variants for versioning.)

Thanks

[Eli Har-Even]

Hi Sara-

I would use variants for versioning, not versions. They are the only game in town if you want to maintain two releases with many docs per release. Variants have their quirks, but they allow you to work one book at a time rather than one topic at a time, which as you say, is not doable.

Eli

--
You received this message because you are subscribed to the Google Groups "Israeli Author-it Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to author-it-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Email secured by Check Point.