CodesYou may have noticed that the other abbreviations list contains abbreviated field names, with the data following the abbreviation. Oftentimes you may wish to code other data with shots.
One system I developed employed the use of status codes on all our quicktime takes, so that in addition to knowing what take it was, we knew the level of refinement. Here are some status codes that could modify (and hence follow) your take name:
ANM 2D Animatic with audio
BLK Playblast Maya Blocking
RUF Rough Composition
STD Submitted To Director
STE Submitted To Editor
TCB Take Accepted, Could Be Better
TCF Take Considered FinalOf course, use of these codes requires the ability of the supervisor to review the shot and rename the file with the correct code. Use your imagination and perhaps you can come up with a set of codes that sort properly and reflect the revision loop you use.
LegibilityOne important corollary to abbreviations and consistency is to improve legibility, the ability to distinguish between letters and hence read the file name. Note in example 3 that the text string for reel, “rl” is hard to read when next to a 1. for this reason, try to avoid lower case “l” in abbreviations and codes.
To help with legibility, I kept the client name lowercase and made the show abbreviation all caps. . ou could, if you don't use client names, help by making the show name lower case or switch and make the client all caps – just make a rule an follow it consistently:
Asset Management 101 – part 7: Essential Rules of File Naming 9 - Use Project identifiers