View Full Version : File naming conventions
mwilson
2006-06-19, 05:51 PM
Could i get your ideas on file naming conventions
Thanks
Mike
rkmcswain
2006-06-19, 06:13 PM
See [ https://tsc.wes.army.mil/products/standards/aec/2_0_Std/volume1.pdf ]
Jeepin
2006-06-19, 06:27 PM
Could i get your ideas on file naming conventions
Thanks
MikeYou might want to put what industry you are working in.
robert.1.hall72202
2006-06-19, 08:40 PM
Ask your customers/end user what they use to identify the files.
Wouldn't it be nice to know exactly what file to pull up when
someone asks a question?
Finding a file asked for as "XYZ" would be easy to find if it
was actually labeled as "XYZ".
Bad example:
Go find the "XYZ" design.
Oh, it is the "GM Door", finally found it!
H-Angus
2006-06-20, 08:46 AM
Could i get your ideas on file naming conventions
Thanks
Mike
Were an Architectural firm and we file them by drawing number followed by a brief description, for example:
832.L.301-Proposed Layout
832.S.401-Proposed Sections
832 = Job Ref.
L/S/A = Layout/Section/Detail
301/401 = Drawing sheet No.
Each job will have its own folder which will include the following subfolders:
Survey - Contains original measured survey
OS - Contains original Ordinance Survey map
Sketch - Contains sketch designs
Planning - Contains Planning drawings
Building Regulations - Contains Breg submission drawings
Construction - Contains construction drawings
Scans - Contains images referenced in drawings
These subfolders often vary a little depending on the job, for example a tender set might be included.
Doodlemusmaximus
2006-06-20, 09:13 AM
Quite offten found that most firms tend to over-complicate the filing system, some going over board on long file names <client job number>/<our job number>/<type of job>/<type of drawing>/<tender etc>/then finally drawing number.
I've been trying to get every thing simplified but to no avail. some even put all this on then a discription of the drawing as well. Thats what the drawing register is for, not to have really long file names. If they need to put a discription on the drawing why don't they just use the properties for this.
Everything will be in sub folders so why not just stick with the drawing number.
Thats my two pennies worth
Mike.Perry
2006-06-20, 09:29 AM
Hi
Might be worth a browse...
A feeler - Intelligent Alpha-Num Filenames
Have a good one, Mike
Jeepin
2006-06-20, 11:46 AM
Quite offten found that most firms tend to over-complicate the filing system, some going over board on long file names <client job number>/<our job number>/<type of job>/<type of drawing>/<tender etc>/then finally drawing number.
I've been trying to get every thing simplified but to no avail. some even put all this on then a discription of the drawing as well. Thats what the drawing register is for, not to have really long file names. If they need to put a discription on the drawing why don't they just use the properties for this.
Everything will be in sub folders so why not just stick with the drawing number.
Thats my two pennies worthOurs is as simple as Survey, Site, Grading, Drainage, Utilities, Profile Xsec, Layouts, Basin Map. I agree w/ Beldin about long file names, I reserve that for a properly set structure of files in MS Explorer.
mom of 3
2006-06-20, 12:52 PM
Unfortunately, sometimes our naming/numbering depends on the client. I'm in civil, & our sheets are generally C.XX (C - civil, the "X"s are numbers), BUT, sometimes the client want something different. As for the sheet names, Demo, Grading, Site - etc.
H-Angus
2006-06-20, 01:01 PM
Heres an example.
I don't think this can be described as over complicated in any way IMHO.
If a client phones and starts talking about a drawing and you want to open it on your screen, they could either give you a drawing number or simply say the site plan, either way it wouldn't matter because both are in the file name.
Or similarly you may want to open a particular floor plan without having to lookup drawing numbers on a register.
I'm not saying this is the best way for everybody, but we've found it's the best way for us.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.