Standardize Name Document For Free

If you want to modify the above naming convention, observe the following three best practices. Consistency counts. Naming conventions must be consistent. ... Be descriptive. Whatever naming convention you go with, it should be descriptive. ... Designate version.

The number of characters of the name is restricted to 8 and the number of characters of the extension is restricted to 3. The total length of the name and extension is restricted to 30 characters (excluding the point and semicolon).

Files are listed in alphabetical order. If two file names do not have the same number of characters the shorter name is treated as if extended with spaces. This rule applies for both the name and the extension. If two files have equal names the file with the highest version numbers comes first e.g. AA.;2 before AA.;1.

Why use naming conventions? Naming records consistently, logically and in a predictable way will distinguish similar records from one another at a glance, and by doing so will facilitate the storage and retrieval of records, which will enable users to browse file names more effectively and efficiently.

How to develop naming conventions? Keep file names short but meaningful. Include any unique identifiers, e.g. case number, project title. Be consistent. Indicate version number where appropriate. Ensure the purpose of the document is quickly and easily identifiable.

A File Naming Convention (FNC) is a framework for naming your files in a way that describes what they contain and how they relate to other files. Developing an FNC is done through identifying the key elements of the project, the important differences and commonalities between your files.

Keep file names short and relevant. If using a date, use the format Year-Month-Day (four digit year, two digit month, two digit day): YYYY-MM-DD or YYYY-MM or YYYY-YYYY. Include a leading zero for numbers 0-9. Order the elements in a file name ing to the way the file will be retrieved.