This reading summarizes best practices for file naming, organization, and storage.
![This image is a white circle with a gray outline and green check mark at the center to check off a bulleted list item.](https://i0.wp.com/d3c33hcgiwev3.cloudfront.net/imageAssetProxy.v1/FlzPQrx9TNKcz0K8fXzS4Q_94483f00dbdf4c33a715424f9c9846f1_checkmark.png?w=1020&ssl=1)
Best practices for file naming conventions
Review the following file naming recommendations:
- Work out and agree on file naming conventions early on in a project to avoid renaming files again and again.
- Align your file naming with your team’s or company’s existing file-naming conventions.
- Ensure that your file names are meaningful; consider including information like project name and anything else that will help you quickly identify (and use) the file for the right purpose.
- Include the date and version number in file names; common formats are YYYYMMDD for dates and v## for versions (or revisions).
- Create a text file as a sample file with content that describes (breaks down) the file naming convention and a file name that applies it.
- Avoid spaces and special characters in file names. Instead, use dashes, underscores, or capital letters. Spaces and special characters can cause errors in some applications.
Best practices for keeping files organized
Remember these tips for staying organized as you work with files:
- Create folders and subfolders in a logical hierarchy so related files are stored together.
- Separate ongoing from completed work so your current project files are easier to find. Archive older files in a separate folder, or in an external storage location.
- If your files aren’t automatically backed up, manually back them up often to avoid losing important work.
![](https://i0.wp.com/smartitsoft.com/wp-content/uploads/2021/09/image-2-1024x605.png?resize=1020%2C603&ssl=1)
Source: https://www.coursera.org/learn/data-preparation/supplement/fLKJI/organization-guidelines