{"id":199,"date":"2025-11-27T12:56:31","date_gmt":"2025-11-27T17:56:31","guid":{"rendered":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/?post_type=chapter&p=199"},"modified":"2026-03-01T21:27:48","modified_gmt":"2026-03-02T02:27:48","slug":"folder-organization","status":"publish","type":"chapter","link":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/chapter\/folder-organization\/","title":{"raw":"Folder Organization","rendered":"Folder Organization"},"content":{"raw":"

Previous Lesson<\/a><\/h4>\r\n

Lesson 6 of 17<\/h4>\r\n

Consider how you name and organize your folders. It is a good idea to keep a readme file in a top-level folder that describes what is in each folder (see the readme section<\/a> in this module as an example).<\/h3>\r\n
\r\n

You might create a readme that explains how you organized your data into folders and which file-naming conventions you use.<\/p>\r\n

ABOUT READMES<\/strong><\/a><\/p>\r\n\r\n<\/div>\r\nRather than storing the same file in multiple locations, consider using file shortcuts (Windows) or aliases (Mac). Using shortcuts or aliases allows a document to appear in more than one folder without having to create and maintain multiple copies.\r\n\r\nNote: A\u00a0folder structure<\/strong><\/span>\u00a0may also be referred to as a\u00a0directory structure<\/strong><\/span>.\r\n\r\n \r\n\r\nIt is useful to plan a file hierarchy structure before you start your project. One way to do so is to sketch it out on a whiteboard (or use the worksheet in Activity 3.1<\/a>). You will want to consider how you will group or categorize your data in ways that make sense for you and your team as you access and use data throughout the project. As you plan your folder hierarchy, it can also be useful to consider who requires access to the different files. Do all team members require access, and do they need both read and edit access to the files? Some folders may only need to be accessible to a principal investigator or certain team members. Consider whether you want a deep or shallow hierarchy; lots of nested folders increases the depth of the hierarchy. You can also create templates you can reuse from project to project if you work with similar data types or methodologies so that data is stored in similar ways across your projects.\r\n

Next Lesson<\/a><\/h4>","rendered":"

Previous Lesson<\/a><\/h4>\n

Lesson 6 of 17<\/h4>\n

Consider how you name and organize your folders. It is a good idea to keep a readme file in a top-level folder that describes what is in each folder (see the readme section<\/a> in this module as an example).<\/h3>\n
\n

You might create a readme that explains how you organized your data into folders and which file-naming conventions you use.<\/p>\n

ABOUT READMES<\/strong><\/a><\/p>\n<\/div>\n

Rather than storing the same file in multiple locations, consider using file shortcuts (Windows) or aliases (Mac). Using shortcuts or aliases allows a document to appear in more than one folder without having to create and maintain multiple copies.<\/p>\n

Note: A\u00a0folder structure<\/strong><\/span>\u00a0may also be referred to as a\u00a0directory structure<\/strong><\/span>.<\/p>\n

 <\/p>\n

It is useful to plan a file hierarchy structure before you start your project. One way to do so is to sketch it out on a whiteboard (or use the worksheet in Activity 3.1<\/a>). You will want to consider how you will group or categorize your data in ways that make sense for you and your team as you access and use data throughout the project. As you plan your folder hierarchy, it can also be useful to consider who requires access to the different files. Do all team members require access, and do they need both read and edit access to the files? Some folders may only need to be accessible to a principal investigator or certain team members. Consider whether you want a deep or shallow hierarchy; lots of nested folders increases the depth of the hierarchy. You can also create templates you can reuse from project to project if you work with similar data types or methodologies so that data is stored in similar ways across your projects.<\/p>\n

Next Lesson<\/a><\/h4>\n","protected":false},"author":2543,"menu_order":6,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-199","chapter","type-chapter","status-publish","hentry"],"part":184,"_links":{"self":[{"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/chapters\/199","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/wp\/v2\/users\/2543"}],"version-history":[{"count":7,"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/chapters\/199\/revisions"}],"predecessor-version":[{"id":744,"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/chapters\/199\/revisions\/744"}],"part":[{"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/parts\/184"}],"metadata":[{"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/chapters\/199\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/wp\/v2\/media?parent=199"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/pressbooks\/v2\/chapter-type?post=199"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/wp\/v2\/contributor?post=199"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.bccampus.ca\/rdmoer\/wp-json\/wp\/v2\/license?post=199"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}