# Part 3 - Folder Organisation ## 3a. Relevance:

? Why does folder organisation matter to me and my collaborators?

BEFORE:

With a cluttered desktop like this, it can be difficult to see what’s where, and hard to stay organised.

"Desktop Chaos" by TU Delft Library - Education Support is licensed under CC BY 4.0

AFTER:

With an organised system of folders, it's easier to locate exactly what you need.

"Desktop Harmony" by TU Delft Library - Data Analysis Team is licensed under CC BY 4.0

A system of sub-folders helps you organise items into more intentional and manageable categories. This will make it possible to find elements more easily and save you time in the long run, especially during big projects. Just like with file naming conventions, it’s important to **consider your folder structure in advance**. Your folders will be determined by what kinds of information you will collect and what you (and your collaborators, if applicable) eventually want to do with the data. **Your folder structure will depend on your project: there is no single right folder structure.**

? Why does folder structure matter in programming?

Will you use code and scripts to analyse research data? Well-organised folders will give you a much more efficient way to summon and work with specific data sets. For example, you may want to use a ```for-loop``` command or a ```glob``` to summon all the data housed in a folder. These commands work best if the data has already been sorted into clearly named folders. ## 3b. Folder Rules of Thumb:

? What are effective systems to organise the folders for my project?

Watch the video to learn about how to create a basic **hierarchical folder structure** for a project, in which folders are organised from most general to more specific.

Attribution: TU Delft Library Education Support & TU Delft Research Data & Software (CC-BY)

Check your understanding: Answer the True or False questions to check your understanding of the rules of thumb for folder organisation.

## 3c. Common Folder Pitfalls: The following video segment was created by the Ghent University data stewards. Watch the video to review best practices for folder organisation and to learn about three big pitfalls to avoid with folder organisation and naming.

Attribution: Ghent University (CC-BY)

Let’s elaborate on the three pitfalls mentioned in the video and demonstrate with examples. ### Pitfall #1: Too deep folder structure: the sub-sub-sub-sub-sub-sub-folder dilemma The video clip from the University of Ghent mentioned avoiding too many sub-folders. If getting there takes too many clicks, it may not be the most efficient way of working. The goal should be to make it easy and fast for you and your collaborators to navigate through all the folders of a project. An intentional, not-too-deep folder structure makes the components of your project more findable. For projects involving code or script, issues might also arise with trying to access a file via the command line if the folder structure is very deep. Check your understanding of pitfall #1:

### Pitfall #2: Too many files in one folder If you are working with files “manually” without using script or code, beware of folders getting too full. Repeated scrolling is not a good use of your time. If a single folder gets so full that you cannot easily see the files in it, consider making another folder or another sub-level of folders. This will re-organise large numbers of files into smaller, more manageable chunks so you can navigate to the file(s) you need more quickly. Please note: Full folders are not a problem for projects with folders containing data files that will be read primarily by code or scripts. In these cases, a folder might contain thousands of files. What really matters, then, is how well the files have been named and categorised. ### Pitfall #3: Overlapping or redundant folder names. As mentioned before, it’s a good idea to create a root folder and give it the name of the specific project. Within that root folder, all sub-folders should have their own unique and recognizable names, just like you saw earlier in the video about Folder Rules of Thumb. Otherwise, it can quickly get very confusing. Check your understanding of pitfall #3:

## 3d. Process what you've learned about folder organisation: Scenario: Nikola Vukovic is a Neuroscientist from the University of California San Francisco. To stay organised during his research, he has established this hierarchical folder structure. The folder structure reflects the key elements of his research projects: NVukovic Folder Structure

Folder structure. From "Setting up an organised folder structure for research projects" by N. Vukovic, n.d. (http://nikola.me/folder_structure.html). Reprinted with permission.

? How does this folder structure match Nikola's work flow?

- When Nikola puts his folder structure into action, “ProjectFolder” would actually be given his specific project’s title. - Nikola usually applies for and receives grants to conduct his research projects, so he likes to include a Project Management sub-folder. - He uses a sub-sub-folder for Proposals where he saves his project plan and grant application requirements. - Finance also gets its own sub-sub-folder because Nikola needs to track the funding and expenses for most projects. - Since his research tends to deal extensively with human research subjects, Nikola makes a habit of dedicating a sub-folder to Ethics governance. - Within that, he includes one sub-sub-folder for ethics forms and another for approvals. Nikola offers further insights into his established folder structure on his website. If you are interested in learning more, you can visit: http://nikola.me/folder_structure.html Check your understanding: Based on the visual outline of Nikola's folder structure, take a quiz about where you would find different types of files.