This weekend has been a busy one, so this weekend's blog post is a short one. But it's reflecting something that I've been thinking of doing for some time though.
File numbering schemes. Users spend hours and hours trying to figure out which one to use.
Is it better to use a sequential? One where the numbers have no meaning with regard to the files they're associated with?
Or is it better to create one where the file name has a meaning. A given portion of the file name tells the user this an assembly, or this component is made out of stainless steal, or is a custom part. The different meanings can go on forever, and are different from company to company.
In my own, personal file structure in Autodesk Vault, I've done what so many are guilty of doing. I've ignored it.
My own Vault file names are an example of what I'd tell someone not to do.
They have a mishmash of names. Most have some sort of meaning. Some are just names I threw in because I needed a name in a hurry.
Others are names that I changed with Vault's Rename command because I needed to make room for another file with the same name (I have "Enforce Unique File Names" checked).
|An example of my similar, but not consistent file names.|
I've wanted to clean that up. I would like more consistency in my file names. But I just haven't had the time or desire to create one.
So I decided to steal a number scheme from someone who's already created one. I'm going to use the one the FAA uses for their Air Worthiness Directives!
How does the FAA do it? They start with the year, then count which two week period in the year the document was issued. Then finally, number the documents in sequential order.
For example an Air Worthiness Directive numbered 2012-20-06 would mean the document was issued in the year 2012, in the 40th week of the year (20th two week period), and that it was the 6th document issued in that time.
I'm going to give it a try in my own Vault, and see how it works out! I'll use the file naming scheme, and for searching, I'm going to search for keywords and properties associated to the files.
|An example of the properties I've added. I'll probably adjust them, but it's a start.|
I'll keep you posted on how it goes. There will be benefits, there will be drawbacks. The real question is, which will outweigh which?
So what do you think? Are you a fan of meaningful, or non-meaningful file names?