Utilize Name Document For Free

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 space in a filename can cause errors when loading a file or when transferring files between computers. Common replacements for spaces in a filenames are dashes (-) or underscores (_).

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.

Class names should be nouns, in mixed case with the first letter of each internal word capitalized. Try to keep your class names simple and descriptive. Use whole words-avoid acronyms and abbreviations (unless the abbreviation is much more widely used than the long form, such as URL or HTML).

What is an example of a good naming convention? Good naming examples include: [Project number] - Data Use Agreement - [Title of research project] Approval - Change to employee travel policy - February 2014.

5 best practices for file naming conventions Keep file names short, but meaningful. Make use of consistent, relevant elements. Avoid special characters and spaces. Document and share the file naming convention. Logical file organisation.

The file name describes, at a glance, what the document is about, making it easier to browse files more effectively and efficiently.