Folder and File Naming Restriction's

Folder Naming Convention Implemented

  • Minimum Length: 5 characters
  • Maximum Length: 50 characters
  • It may not end with any special characters, including a periodNumbering Folders:
  • Pad Numbers with Leading Zeros: Use leading zeros for numeric values to maintain proper order (e.g., 001, 002 instead of 1, 2).
  • Separate Sections with Delimiters: For clarity, use hyphens, underscores, or spaces to separate numeric and alphabetic parts.
  • Consistent Case for Letters: Stick to uppercase or lowercase letters throughout the structure.
  • Avoid Special Characters: Limit special characters to prevent compatibility issues across systems.
  • Categorize Logically: If applicable, organize folders into parent-child relationships based on categories.

Guidelines:

  1. Use meaningful and descriptive names that convey the folder's content or purpose.
  2. Avoid special characters, spaces, or symbols that may cause issues with different operating systems or applications.
  3. Consider using camel case or underscores for multi-word folder names (e.g., "projectFiles" will be "project_files"). The upload process will remove invalid characters and add underscores.

File Naming Convention Implemented:

  • Minimum Length: 5 characters
  • Maximum Length: 100 characters

Guidelines:

  1. Use a combination of letters, numbers, and, if necessary, underscores or hyphens.
  2. Include relevant information such as the project name, date, and brief description to make the file easily identifiable.
  3. Avoid using special characters that cause compatibility issues. If used, the system will strip during upload.

Examples:

  • Good file name: project_report_2023Q1_final.docx
  • Example to avoid: document!!!.pdf

Automation:

You will experience checks and validations during the folder and file creation process for automated enforcement of these standards in your Vault Room app. If a user tries to create a folder or file that does not adhere to the specified naming convention, the app should provide a clear error message explaining the requirements or have corrected invalid uses.