folder structure

[David Spreadbury]

Tim,
I would expect that the concensus will be to create the folder structure that fits your way of thinking and what will work for your documents.
 
Initially I would gather all of the relevant pieces into a clean structure and Bruce Foster's Archive is the tool to collect and assemble all of the pieces.
 
One gotcha you are going to run into is cross-references. A nice thing about Archive is that it fixes them during it's slight of hand. Very useful tool that, for me anyhow, has more than paid for itself. I think it is still going for $20, but don't hold me to that.

If you feel the need, then move the product specific stuff to sub-folders in the archived tree.
 
Then you will have to rebuild all cross-references to the specific stuff manually. Links to graphics should be okay, but if graphic links to the specific stuff do break, fixing the first one should fix all for that specific product.
--- On Tue, 5/18/10, Tim J. Slager <TSlager at isdcorporation.com> wrote:


From: Tim J. Slager <TSlager at isdcorporation.com>
Subject: folder structure
To: "framers at lists.frameusers.com" <framers at lists.frameusers.com>
Date: Tuesday, May 18, 2010, 3:41 PM


I inherited a book with chapters and files in a complex directory structure. We are changing from one version-control software to another, so now would be a good time to change the folder structure.

The complex structure makes it difficult to check out all the files in a  book at once. It seems to me that it would be easier to have files that are common across products in a common files folder, and to have all the rest of the .FM files for each product/FM book in a single folder, with images in an adjacent folder.

I am wondering if there are recommendations for file structure, and what are the gotchas I'm likely to encounter if I move things around.

Thanks. tims

Tim Slager | ISD Tech Pubs | 616.494.1373