File names can include:
Always document decisions on what components you will use, what acronyms mean, how the file names are structured. Consider including a README.txt file in the directory including all the documentation.
Examples of good file names:
Examples of poor file naming:
Example file structure and file-naming for general or research projects
This is just one of many ways to organize your files. Each project and collaboration will name and organize differently, and all are viable options as long as the structure is orderly, logical, and follows file naming conventions.
No matter what, be consistent with your organization and naming.
Beyond organizing your files for your own use over the course of your project, doing so according to broadly accepted standards helps aid in collaboration with colleagues, with citing your data, and sharing your published data down the road.
Why name your files consistently?
At the core of file naming conventions is the idea that your file names should allow all of your documentation and research to be sortable and accessible by various computer programs.
Organizing files in folders logically and systematically can help you locate and organize files and versions down the road.
First create a top-level folder whose name contains the project name or acronym and a date.
Within that top-level folder, project files can be organized by:
Questions? Contact firstname.lastname@example.org
Powered by Springshare.