Step 2: Make subfolders for different types of your work<\/h3>\n\n\n\n
Within your Work<\/strong> folder, make a subfolder for each flavor of project that you do. I have individual folders for Grants<\/strong>, Editorials, Non research <\/strong>(for blog posts and other miscellaneous work), and Research<\/strong>.<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\n\n\n Let’s say you are about to have your first meeting for a new research project studying the effects of Fro-yo vs. ice cream on cholesterol among adults. All of the relevant documents for your next research project will now be saved in the 001 froyo ice cream <\/em>folder, seen here:<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\n\n\n (You also had a good idea for a maple syrup study that you have also started simultaneously.)<\/p>\n\n\n\n What is the threshold to start a new numerically and descriptively labeled sub-subfolder? Mine is pretty low. If I think I have at least a marginally good idea and have started emailing folks about it, I go ahead and start a new folder. A PDF copy of those initial emails are often the first things that I save in that new numerically and descriptively labeled sub-subfolder. (I loathe MS Outlook but have to use it. Its search is terrible. Saving copies of important emails saves me some headache.)<\/p>\n\n\n\n What kinds of things are you going to save into these folders? That’s up to you. I recommend saving your literature searches, copies of relevant important emails, research proposals, and so on. I like to make sub-sub-subfolders with headings like Data and analysis<\/strong>, Manuscripts<\/strong>, PDFs<\/strong> (for relevant literature saved from your library’s journal subscriptions), and Presentations<\/strong>. You should probably number these folders to match the overall sub-subfolder number as well.<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\n\n\n Example: You finished all of your awesome dessert-related research and are starting to write up the main findings. You are going to start your first MS Word version of the first draft. I suggest naming it like this: “001 froyo ice cream main findings r00 v01.docx<\/em>“.<\/p>\n\n\n\n The r00 (that’s r zero zero) means that this particular draft has never undergone a major revision from a prior draft. The v01 (that’s v zero one) means that it’s the first version ever. You’ll email out a file titled:<\/p>\n\n\n\n 001 froyo ice cream main findings r00 v01.docx <\/em><\/p>\n\n\n\n …to your primary collaborator who will send back something with edits, they’ll probably save it as:<\/p>\n\n\n\n 001 froyo ice cream main findings r00 v01 BHO edits.docx<\/em><\/p>\n\n\n\n …which is nice but doesn’t help with your naming structure. Immediately save that to Work\\Research\\001 froyo ice cream\\Manuscripts\\<\/strong> as version 02, or:<\/p>\n\n\n\n 001 froyo ice cream main findings r00 v02<\/strong>.docx<\/em><\/p>\n\n\n\n Accept or refuse their edits and save that version as:<\/p>\n\n\n\n 001 froyo ice cream main findings r00 v03<\/strong>.docx<\/em><\/p>\n\n\n\n …then send this out to more collaborators. You’ll wind up going through somewhere between 5-20 (or more) manuscript versions before you are ready to submit to a journal. What’s nice about this system is that you’ll have no problems figuring out which version of a file you are getting edits on. Remember, at >5 collaborators, the probability of one co-author checking their email <1 time per month approaches 100%. You'll be working on the 10th version of your draft and receive an email from the slow reviewer with edits to version 03. Sticking to this scheme helps you figure out how to integrate their suggestions into the current version by tracking the intermediate changes.<\/p>\n\n\n\n Note: I suggest using two digits (v01<\/strong>-v99) for the revision and version numbers rather than starting with 1 digit (v1<\/strong>-v99). This helps keeping files in alphabetical-numerical order when sorting in your file explorer. Computers aren’t smart enough to figure out that v12 doesn’t come between v1 and v2.<\/p>\n\n\n\n For some reason, the New England Journal of Medicine<\/em> doesn’t accept your manuscript for publication after sending it out for review. Lucky for you, it was sent out for review and the reviewers gave you some high-quality feedback that will improve your paper. Now it’s time to start revision 01! When prepping it for the inevitable JAMA<\/em> submission, you’ll be working starting on revision 01<\/strong> and version 01<\/strong>, or:<\/p>\n\n\n\n 001 froyo ice cream main findings r01<\/strong> v01.docx <\/em><\/p>\n\n\n\n In the end, you’ll have a folder looking like this:<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\n\n\n Look at how pristine and well-organized this is!<\/p>\n\n\n\n Let’s say that you decide to write both a main findings<\/strong> manuscript and a subgroup analysis<\/strong> manuscript. How to stay organized? Just the 001 Manuscripts<\/strong> folder into two sub-sub-sub subfolders for each publication, with 001a<\/strong> for the main findings<\/strong> and 001b<\/strong> for the subgroup analysis<\/strong>. It’ll look like this:<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\n\n\n The naming scheme changes slightly as filenames will start with 001a<\/em><\/strong> instead of 001<\/strong>, like this:<\/p>\n\n\n\n <\/p>\n<\/div><\/div>\n\n\n\n I can’t stress this enough. Keeping your Work folder in a commercial cloud storage drive doesn’t count as backing things up. Dropbox only saves things for 30 days in their basic plan. If you aren’t actively backing up your data, you can safely assume it isn’t backed up<\/strong><\/em>. One dead hard drive in a non-backed up folder can mean months or years of lost work.<\/p>\n\n\n\n Remember to check your institution’s policies for determining your backup method of choice. If you are working with PHI, saving it on an unencrypted thumb drive on your keychain won’t cut it. If it’s okay with your data policies, I recommend buying a DVD-R spindle or a bunch of cheap thumb drives and setting a calendar date to write your Work<\/strong> folder to a different DVD-R or different thumb drive once per month (i.e., you should have this on a different thumb drive each month). Keep these in a locked, secured, fireproof area that is consistent with the policies of your organization. Better yet, keep them in multiple locked, secured, fireproof areas if possible. For bonus points, get an M-Disc DVD discs and compatible burner, which should be stable for >1,000 years, unlike the usual 10-20 years of conventional burnable DVD-Rs and CD-Rs.<\/p>\n\n\n\n Or, just speak with your friendly neighborhood IT professional about how your institution recommends backing up the data you are working with. Chances are that they have a server that they back up 3 times per day that you can just use for a modest price. It’ll be worth the sorrow of lost data and drafts.<\/p>\n","protected":false},"excerpt":{"rendered":" I’m not an organized person by nature. However, I’m the kind of guy that likes to implement systems to overcome problems. In medical school, I didn’t have any sort of structure for my projects and found it frustrating to find the most recent versions of papers, posters, and other writings. Here’s an approach that I … Continue reading Keeping your digital work organized<\/span><\/a><\/p>\n","protected":false},"author":4473,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[502555],"tags":[],"class_list":["post-48","post","type-post","status-publish","format-standard","hentry","category-productivity-and-organization"],"_links":{"self":[{"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/posts\/48","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/users\/4473"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/comments?post=48"}],"version-history":[{"count":14,"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/posts\/48\/revisions"}],"predecessor-version":[{"id":575,"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/posts\/48\/revisions\/575"}],"wp:attachment":[{"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/media?parent=48"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/categories?post=48"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.uvm.edu\/tbplante\/wp-json\/wp\/v2\/tags?post=48"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"\"](\"http:\/\/blog.uvm.edu\/tbplante\/files\/2017\/08\/folders.png\")
<\/figure>Step 3: Numerically and descriptively label each of your projects in its own sub-subfolder<\/h3>\n\n\n\n
![\"\"](\"http:\/\/blog.uvm.edu\/tbplante\/files\/2017\/08\/subsubfolder2.png\")
<\/figure>![\"\"](\"http:\/\/blog.uvm.edu\/tbplante\/files\/2017\/08\/subsubsubfolder2.png\")
<\/figure>Step 4: Name each item within your sub-sub-subfolders starting with the a) sub-subfolder name, b) a short descriptor of the thing you are writing, and c) ending with a revision and version number <\/strong><\/h3>\n\n\n\n
Using version numbers<\/h5>\n\n\n\n
Using revision numbers<\/h5>\n\n\n\n
![\"\"](\"http:\/\/blog.uvm.edu\/tbplante\/files\/2017\/08\/namingstructure-282x300.png\")
<\/figure>Step 4.5: Use trailing letters for projects with multiple publications<\/h3>\n\n\n\n
![\"\"](\"http:\/\/blog.uvm.edu\/tbplante\/files\/2017\/08\/split-manuscripts-folder.png\")
<\/figure>![\"\"](\"http:\/\/blog.uvm.edu\/tbplante\/files\/2017\/08\/main-findings-folder-254x300.png\")
<\/figure>Step 5: For the love of all things decent, regularly back up your Work folder!!<\/h3>\n\n\n\n