'R' was appointed as Managing Director of P mart Limited recently. During the meeting of the Board, he desires that all agenda files should be sent by email encrypted by password. He also desires that to protect the file

The following are best practices for file naming. The File names should: Be unique and consistently structured; Be persistent and not tied to anything that changes over time or location; Limit the character length to no more than 25-35 characters; Use leading Os to facilitate sorting in numerical order if following a numeric scheme '001, 002, 010, 011... 100, 101, etc.' instead of '1, 2, ... 10, 11 100, 101, etc.'; Contain a file format extension; Use a period followed by a file extension (for example, '.tif', '.jpg', '.gif', '.pdf', '.wav', '.mpg'); Use lowercase letters. However, when a name has more than one word, start each word with an uppercase letter for example, 'File_Name_Convention_001.doc'; Use numbers and/or letters but not characters such as symbols or spaces that could cause complications across operating platforms; Use hyphens or underscores instead of spaces; Use standard date notation (YYYY-MM-DD or YYYYMMDD); Avoid blank spaces anywhere within the character string; and Not use an overly complex or lengthy naming scheme that is susceptible to human error during manual input, such as 'filenameconventionjoesfinalversioneditedfinal.doc'. The strength of a folder and file naming convention is dependent on the proposed naming structure and the quality and quantity of the data elements chosen to build it. It should be of no surprise that for any business activity there is always an ideal naming structure. However, any structured naming convention that attempts to be all encompassing may result in overkill and unwieldiness.