Skip to content

Commit e58755f

Browse files
committed
Adds template datapackage.json metadata descriptor.
Also adds entry for metadata descriptor file.
1 parent ecf590b commit e58755f

File tree

2 files changed

+38
-7
lines changed

2 files changed

+38
-7
lines changed

README.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,7 @@ Overview
2424
|- study.Rmd # executable Rmarkdown for this study, if applicable
2525
|- Makefile # executable Makefile for this study, if applicable
2626
|- study.Rproj # RStudio project for this study, if applicable
27+
|- datapackage.json # metadata for the (input and output) data files
2728

2829
How to use
2930
----------
@@ -40,13 +41,14 @@ Key concepts and goals
4041
----------------------
4142

4243
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.
5052

5153
Acknowledgements
5254
----------------

datapackage.json

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
{
2+
"title": "Data package for study NAME OF STUDY",
3+
"name": "name-of-study",
4+
"license": "CC0-1.0",
5+
"contributors": [
6+
{
7+
"name": "Firstname Lastname",
8+
"email": "youremail@example.com"
9+
}
10+
],
11+
"resources": [
12+
{
13+
"path": "data/raw/rawDataFile1.csv"
14+
"name": "Name of data file 1",
15+
"format": "csv"
16+
}
17+
{
18+
"path": "data/clean/cleanDataFile1.csv"
19+
"name": "Clean version of Name of data file 1",
20+
"format": "csv",
21+
"sources": [
22+
{
23+
"path": "data/raw/rawDataFile1.csv"
24+
}
25+
],
26+
}
27+
],
28+
"datapackage_version": "1.0-beta.10"
29+
}

0 commit comments

Comments
 (0)