About filename conventions
Seems like an subject with endless possibilities, endless talk and actually pretty straight forward solution, only thing is that, there is not one solution and therefore becomes an argument rather than a tool. Of course our little egos do thrive on these thing, like talking football, anyone can talk yet very few have to prove they really understand what it is behind so what I am going to do instead of selling my personal approach is just outline an strategy and from then on, you do your own, which seems much more fair too as I do not know your needs.
Please make sure you read first My vocabulary so you can get a good reference on how and why I call these things as I do.
The reason of why we need a naming convention is pretty obvious, as teams working together become bigger than four, we start to realize we need to unify these so we don’t need to ask constantly where and how things are. Also on top of it later down the line we will realize the benefits of assuming certain name structure or template.
Well, my personal approach on everything is to divide things into their tiniest little components and understand the base so we can build on top, in this case of course this raises the question “What is inside the naming convention” and “Which information do I have to carry on the name” so it becomes really useful tool to communicate. After all that is the whole point.
Well, everybody, that is the real strength, no matter what is the convention, the strength is directly proportional to the people using it so as long as everybody uses it, it will be a good naming convention. Remember this is not like a religion where you have to believe blindly, this you can reason and argument with facts.
As you do with a cooking recipe where you mix little by little multiple ingredients to construct a sauce for example, the same thing can be said of a naming convention, and then my next step is to define these ingredients;
- Show name
- Sequence name
- Shot name
- Element name
- Subelement name
- Element version
- Subelement version
- Artist name
- Time stamp
Of course you can add yours, you can remove mine but nevertheless I am going to assume you have these to start. So imagine we want to use the Show Name, the Sequence Name, the Shot name the Element name and version, Description and you could build something like;
or if we feel the show really is implicit on the folder structure and is no need for too long names, then;
or if we consider that the artist is already registered on the filesystem, then we could clean the clutter further like;
or if we decide that show and sequence should be driven via folders instead of sequences then;
But not, we don’t want this last one as you will be having multiple shots 1 in your project, therefore there is the need to have certain things in your name, and clearly the sequence is vital so;
Seems like very good one but, what if we need to deal with sub-elements? Well, you get the gist so I will let you do it. Nevertheless we can now safely put a few convenient rules so we all play it even better
- We should shorten the final structure as much as possible, remember many software tools don’t like 250 characters.
- Also, we want to take advantage of the dumb linux/windows/osx filesystems so will set it up in such a way that ordering becomes system and human friendly, which means we want to use leading zeroes.
- We should also try to eliminate confusion between different numbers like shot number versus the version number by adding may be a single character in front to clarify.
- And of course we programmers will love a riggid enough structure so we can clearly parse the whole thing by separating every ingredient with a symbols that won’t be used anywhere else.
With this said, here is a possible solution and the one we use at The Mill.
Arguably this complies with these rules I mentioned before and from our last years of experience using it we have found we could do better by adding may be other things but due to the type of work we do, really that is so rare that will make the name even longer for no real reason so this is it for now. But what about the textures, animation, presets, etc..? well, isn’t it the same? you may want to avoid certain ingredients for these but truly it boils down to just this so i will let you try to figure out them by yourself.
4 Responses to “About filename conventions”
Leave a Reply