File Naming Standards - Summary / recommendations

 Appears to be consensus that file naming

  • be consistent
  • should not use special characters (" # % * : < > ? / \ |)
  • should not use spaces (spaces will be converted to the characters "%20" in hyperlinks)
  • should not separate words in file names with underscores or dashes (underscores "_" or dashes “-“)
  • should use capitals instead of periods and spaces 
  • should use date format YEAR / MONTH / DAY - ISO 8601

There is no consensus on 
  • use version numbers in file names (versioning may be available automatically in Google and/or Sharepoint - viewing history)
  • use of underscores instead of periods and spaces 

Worthy idea
  • include naming convention in data management plan (and commonly used docs - i.e. agenda - for quick reference) 

Recommendation 
450 / folders / files 
  • folders
    • meeting
      • 20210314_450AgendaMidterm
    • listening
      • 20210101_CT2Chapt6Quizv02 
    • speaking 
    • reading 
    • writing 
    • administration
      • 20211010_Syllabusv03
      • 20211010_CourseOutlinev03
    • assessment
file names (sample)
  • 450/meeting/20210314_450AgendaMidterm
  • 450/listening/20210101_CT2Chapt6Quizv02
  • 450/administration/20211010_Syllabusv03
  • 450/administration/20211010_CourseOutlinev03
file name (sample) 
  • 450/meeting/450AgendaMidterm
  • 450/listening/CT2Chapt6Quizv02
  • 450/administration/Syllabusv03
  • 450/administration/CourseOutlinev03


Notes
  • version history may be redundant if done in Google docs (version history can be labelled in the doc)
  • date of document may be redundant if done in Google docs (automatically done in doc) - could be labelled Mastery 

Comments

Popular posts from this blog

File Naming Strategies - List of articles

File Naming Standards - Notes (University of Maryland Baltimore)

Micro learning - 5 minute desk exercises (example)