You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-7Lines changed: 9 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,7 @@ Overview
24
24
|- study.Rmd # executable Rmarkdown for this study, if applicable
25
25
|- Makefile # executable Makefile for this study, if applicable
26
26
|- study.Rproj # RStudio project for this study, if applicable
27
+
|- datapackage.json # metadata for the (input and output) data files
27
28
28
29
How to use
29
30
----------
@@ -40,13 +41,14 @@ Key concepts and goals
40
41
----------------------
41
42
42
43
See [Noble 2009] for a full description of and argument for the principle template structure. Some concepts and goals that guided this work:
43
-
* There is a folder for the raw data, which do not get altered, or intermixed with data that is the result of manual or programmatic manipulation. I.e., derived data is kept separate from raw data, and raw data are not duplicated.
44
-
* Code is kept separate from data.
45
-
* Manuscript production output is kept separate from everything else.
46
-
* There is a scratch directory for experimentation. Everything in the scratch directory can be deleted at any time without negative impact.
47
-
* There should be a `README` in evey directory, describing the purpose of the directory and its contents.
48
-
* There is a top-level `Makefile` or [Rmarkdown] file that documents the computational study in executable form. Those files may call out to other `Makefile`'s or `.Rmd` files in subdirectories.
49
-
* The template structure should have no special software or skill prerequisites to install. Specifically, deploying the template structure should not require installing git, or using the command line.
44
+
* (Good) There is a folder for the raw data, which do not get altered, or intermixed with data that is the result of manual or programmatic manipulation. I.e., derived data is kept separate from raw data, and raw data are not duplicated.
45
+
* (Good) Code is kept separate from data.
46
+
* (Better) Manuscript production output is kept separate from everything else.
47
+
* (Good) There is a scratch directory for experimentation. Everything in the scratch directory can be deleted at any time without negative impact.
48
+
* (Better) There should be a `README` in evey directory, describing the purpose of the directory and its contents.
49
+
* (Best) There is a top-level `Makefile` or [Rmarkdown] file that documents the computational study in executable form. Those files may call out to other `Makefile`'s or `.Rmd` files in subdirectories.
50
+
* (Best) There is a formal metadata descriptor at the root of the package that describes all the important input and output data files.
51
+
* (Meta) The template structure should have no special software or skill prerequisites to install. Specifically, deploying the template structure should not require installing git, or using the command line.
0 commit comments