dealing with project development file clutter
dealing with project development file clutter
(OP)
I inherited a project that several people had worked on in the past, and the design had gone thru several major changes.
A network folder named "current version" was the working folder and had all the development parts and assemblies in it and some analytical models too. Some files were named as part numbers, and many had descriptive names.
When I began I saved the newest version of the assembly with sub assemblies and all parts on a separate drive before I started finalizing parts and assemblies and assigning part numbers and making dwgs and BOMs. Our released parts models' file names are strictly part numbers.
Now I need to put my nearly finished stuff somewhere for public access while the final parts drawings are in the process of being released into Source Safe.
I'd like to move the contents of that entire "current version" devopment folder down a few levels as "development models" and reload the top level with my parts and assemblies and drawings.
The pack and go feature would work OK for previous assemblies, but moving the slew of development and analysis parts etc while maintaining associations and correct part numbers look like a major nightmare. But I don't think I will be able to even rename the "current version" folder to something less authoratative sounding without creating big problems.
Right now I think my best bet is to simply leave the "current version" folder as-is, and place my final version in it's own carefully named folder at the same level.
Any suggestions?
A network folder named "current version" was the working folder and had all the development parts and assemblies in it and some analytical models too. Some files were named as part numbers, and many had descriptive names.
When I began I saved the newest version of the assembly with sub assemblies and all parts on a separate drive before I started finalizing parts and assemblies and assigning part numbers and making dwgs and BOMs. Our released parts models' file names are strictly part numbers.
Now I need to put my nearly finished stuff somewhere for public access while the final parts drawings are in the process of being released into Source Safe.
I'd like to move the contents of that entire "current version" devopment folder down a few levels as "development models" and reload the top level with my parts and assemblies and drawings.
The pack and go feature would work OK for previous assemblies, but moving the slew of development and analysis parts etc while maintaining associations and correct part numbers look like a major nightmare. But I don't think I will be able to even rename the "current version" folder to something less authoratative sounding without creating big problems.
Right now I think my best bet is to simply leave the "current version" folder as-is, and place my final version in it's own carefully named folder at the same level.
Any suggestions?






RE: dealing with project development file clutter
Better yet, why not copy it to a CD or DVD and delete the original.
RE: dealing with project development file clutter
You may want to use a top-level drawing to do this instead of an assembly, but I think you have options to include related drawing files when you do the File > Save As gig.
Jeff Mowry
www.industrialdesignhaus.com
Reason trumps all. And awe transcends reason.