- Logging In
- Access Levels
- Workflow Tasks
- Website Guidelines
- Help Videos
- Files and Folders
- Upload Files
- About Navigation
Working with files and folders
UND naming conventions
Names should be concise. Words should be separated by hyphens. Initials or abbreviations that are not commonly used by external users should be spelled out or avoided. Only lowercase letters, numbers, and hyphens should be used.
Good file naming examples:
Poor file naming examples:
- myexamplewebpage.pcf (words not separated)
- upacalendar.pcf (upa abbreviation is not clear. Also, it may not be needed unless there are multiple calendars in the same folder)
- inforeq1112.doc (name not clear)
- dsc200384702938.jpg (image from camera or other source not renamed)
Why this naming convention?
- The type of file is more easily identifiable than a long string of letters.
- The URLS will look better and be easier to read in browsers.
- Browsers understand these characters.
- Search engines can parse (distinguish) words which are separated by dashes but cannot parse words that are separated by underscores or CamelCase.
- We have some automated systems (breadcrumbs and local nav titles) that rely on the dashes to parse the filename into text on a page.
*In filenames that contain dates the four digit year should come first, then the two digit month, and finally the two digit day (if a day is absolutely necessary). This will also help with organization of files and folders as future items are added.