Very cool Dan! My only suggestion would be to create a top-level README file describing the directory structure (and possibly referring back to your script's URL), or print that out to the screen for the user to create their own file or append to their own.
The shell experts will probably want to add a little error-handling. At minimum, the script should probably turn clobbering off before writing to files. On Tue, Feb 3, 2015 at 4:59 PM, Daniel Chen <[email protected]> wrote: > Ever since Ivan showed Noble's PlosONE article [1] at the Harvard > workshop, I began to follow the template and teach it in workshops. > > I created a quick bash script [2] since I just started another project, > and thought it'd share with everyone. The code isn't pretty, but it does > the job. Improvements welcome! > > And hopefully it'll be a less barrier to entry for people to setup project > folders after they attend a workshop. > > > [1] > http://journals.plos.org/ploscollections/article?id=10.1371/journal.pcbi.1000424 > [2] https://github.com/chendaniely/computational-project-cookie-cutter > > > - Dan > > _______________________________________________ > Discuss mailing list > [email protected] > > http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
