-
Notifications
You must be signed in to change notification settings - Fork 4
/
openScience.Rmd
248 lines (192 loc) · 10.5 KB
/
openScience.Rmd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
---
title: "Open Science"
---
```{r setup, include = FALSE}
knitr::opts_chunk$set(
echo = TRUE,
error = TRUE,
comment = "")
```
# Overview {#overview}
We, as a lab, value and strive to advance the mission of [open science](https://onlinelibrary.wiley.com/doi/10.1002/icd.2315) to improve the accessibility, reproducibility, and replicability of science.
As such, all lab members are expected to conduct research transparently and to promote reproducibility.
This includes, but is not limited to, [pre- or co-registering](#preregistration) studies, [sharing analysis scripts and data](#sharing), using [version control](#versionControl) (GitLab), submitting [preprints](https://psyarxiv.com) when submitting a manuscript to a journal, and providing support for other labs' attempts to replicate and reproduce our findings.
Our lab's template for projects on the [Open Science Framework](https://osf.io) (OSF) is located here[^1]: https://osf.io/4w9sv.
# Pre-Registration (or Co-Registration) {#preregistration}
There is a continuum of registration approaches.
Pre-registration involves publicly posting aspects of a study (e.g., study design, hypotheses, methods, materials, and analysis plan) before data collection begins.
Co-registration involves specifying aspects of your study after data collection starts but before analysis.
Post-registration involves specifying aspects of your study after after analysis has begun.
Pre-registration is often considered the gold-standard.
However, co-registration and post-registration are better than no registration.
Here are elements of a study that can be registered:
- study design
- hypotheses
- methods
- materials
- analysis plan
When analysis decisions are contingent upon prior steps that may influence which decision to take, the analysis plan can include decision trees (e.g., if X, then Y; if A, then B).
For example, you can specify how you would proceed if the measures do not demonstrate longitudinal factorial invariance, or how you would handle poorly fitting models.
# Sharing Data, Analysis Scripts, and Research Materials {#sharing}
## Data Dictionary {#dataDictionary}
For each study, we create a Data Dictionary.
A Data Dictionary is a metadata file that tells people the meaning of variables in the data file and how to interpret them.
### Style Guide {#styleGuide}
- Use Roboto font size 10
- Use an en dash (`–`; i.e., not a hyphen) to indicate a range:
- e.g., 1–18 (not 1-18)
- an en dash is technically correct; in addition, spreadsheets often read 3-7 as March 7th, but they correctly read 3–7
### Columns {#columns}
The Data Dictionary should have the following columns:
- Variable Name
- the variable name in the data file
- Form Name
- the instrument or measure that the variable comes from
- Human-Readable Variable Name
- a more easily readable version of the variable name
- Data Type
- the format of the values in the column (e.g., string, binary, integer, numeric, date, time, etc.)
- Variable Type
- whether the scale of measurement is nominal, ordinal, interval, or ratio
- Measurement Unit
- the conceptual unit that is being measured (e.g., seconds, level, count)
- Allowed Values
- the allowed values for a variable and (if possible), what conceptual level each value corresponds to (e.g., 0 = Male; 1 = Female)
- Description
- conceptual description of the variable
- Definition
- definitions of abbreviations, conceptual defintions of terms, mathematical definitions of how a variable is calculated, etc.
- Notes
- additional notes about the variable and how it is calculated
- References
- references for the measure and/or variable
#### Data Types {#dataTypes}
Data Types include:
- string
- include letters or other characters (and possibly numbers)
- factor
- categorical variable with letters and/or numbers
- binary
- 0/1
- integer
- whole numbers (never decimals)
- numeric
- numbers
- date
- `MM/DD/YYYY`; e.g., 06/24/2020
- time
- `HH:MM:SS` (e.g., 01:30:24), or `HH:MM` (e.g., 05:24), or `MM:SS`
- date-time
- `MM/DD/YYYY HH:MM:SS` (e.g., 06/24/2020 01:30:24)
#### Variable Types {#variableTypes}
Variable Types include:
- nominal
- distinct categories
- ordinal
- ordered categories
- interval
- ordered with meaningful distances
- ratio
- ordered with meaningful distances and an absolute zero
#### Measurement Units {#measurementUnits}
Measurement Units include:
- ID
- participant identification (ID) numbers
- count
- number of something (e.g., number of children in the household)
- group
- categories that reflect different groups (e.g., female vs male)
- instance
- nominal categories that do not reflect groups
- yes/no
- 0 = No; 1 = Yes
- ratio
- ratio of two variables (one variable divided by another variable)
- USD
- U.S. dollars ($)
- option
- categories that reflect participant's choice among multiple options
- location
- categories that reflect different locations
- state
- categories that reflect a status
- degree
- the degree of
- level
- the level of
- grade
- school grade
- date
- `MM/DD/YYYY`; e.g., 06/24/2020
- time
- `HH:MM:SS` (e.g., 01:30:24), or `HH:MM` (e.g., 05:24), or `MM:SS`
- date-time
- `MM/DD/YYYY HH:MM:SS` (e.g., 06/24/2020 01:30:24)
- milliseconds
- seconds
- minutes
- hours
- days
- months
- years
- percentile
- item
# Version Control {#versionControl}
We use [GitLab](https://research-git.uiowa.edu) for version control.
See our [lab's guide for using GitLab](https://devpsylab.github.io/DataAnalysis/git.html).
Our lab's template for GitLab repositories is located here[^1]: https://research-git.uiowa.edu/PetersenLab/Template.
# Preprint {#preprint}
When submitting a manuscript to a journal, also submit a preprint to [PsyArXiv](https://psyarxiv.com).
Combine the supplemental material and manuscript into one PDF file when posting.
# OSF {#osf}
The [Open Science Framework](https://osf.io) (OSF) is a website for hosting pre-registrations, data, analysis code, research-related materials, and pre-prints to improve replicability and reproducibility of findings.
For each paper project, create a new repository on the OSF and add the relevant contributors, including Dr. Petersen.
Our lab's template for projects on the Open Science Framework (OSF) can be found here[^1]: https://osf.io/4w9sv.
## Components {#components}
Create a component in the OSF project repository for the following components:
- Pre-registration (or Co-registration)
- Data
- Data Dictionary
- Analysis Code
- Research Materials
- Preprint
### Pre-registration {#osfPreregistration}
### Data {#osfData}
To help protect participant anonymity, it is important to anonymize participant IDs so their data cannot be stitched together across papers.
To anonymize participant IDs, use the following script and change the seed for every paper so that a given participant gets a different anonymized code each time.
[https://devpsylab.github.io/DataAnalysis/osf.html#anonymizedID](https://devpsylab.github.io/DataAnalysis/osf.html#anonymizedID)
### Data Dictionary {#osfDataDictionary}
For each paper project, we export a `.csv` file with the subset of the [Data Dictionary](#dataDictionary) variables used for that specific paper.
We upload that `.csv` file to the OSF.
The formatting of the Data Dictionary is described [here](#dataDictionary).
### Analysis Code {#osfAnalysisCode}
### Research Materials {#osfMaterials}
### Preprint {#osfPreprint}
## Create Anonymous View-Only Links for Anonymous Peer Review {#anonymousViewOnlyLink}
With your project open, go to Settings (top-right) → View-Only Links → Add.
Then check "Anonymize".
Then you can share that URL.
For detailed instructions, see here: https://help.osf.io/article/201-create-a-view-only-link-for-a-project (archived at https://perma.cc/AGJ9-V487)
# Manuscript Submission to a Journal {#journal}
Before submitting a manuscript to a journal, make sure to post the relevant materials on the [OSF](#osf), as described [here](#osf), and post the preprint, as described [here](#preprint).
When preparing a manuscript for submission to a journal, make sure to follow the Author Guidelines for each journal.
After finalizing the manuscript in accordance with journal guidelines and when you are ready to submit the paper to the journal (but before submission), post the [preprint](#preprint) on [PsyArXiv](https://psyarxiv.com).
Include the link to the preprint in the cover letter to the journal.
In the method section and on the title page, include the relevant OSF links to the pre-registration, data, data dictionary, analysis code, computational notebook, and research materials, etc.
For example:
> Hypotheses and measures for the School Readiness Study were pre-registered: https://osf.io/jzxb8.
> Hypotheses methods, and a data analysis plan for the present study were also pre-registered: https://osf.io/pny26.
> Data files, a data dictionary, analysis scripts, and a computational notebook for the present study are published online: https://osf.io/zs2bn.
In the manuscript submission, create and use [anonymous view-only OSF links](#anonymousViewOnlyLink) (for blind review).
In the preprint submission, use the general OSF links (not the [anonymous view-only OSF links](#anonymousViewOnlyLink)) that will become viewable when the manuscript is accepted for publication (i.e., when you make the OSF repo public).
# When the Manuscript is Accepted for Publication {#accepted}
When the manuscript is accepted for publication:
1. Let all of the authors know, and send them the full, (in-press) APA-style reference
1. Make the OSF repo public and [create a DOI link](https://help.osf.io/article/220-create-dois) for the repository that can be used for citing it
1. Submit the finalized, unblinded manuscript (and any tables, figures, and the supplement; with the public OSF link; removing any highlighting or tracked changes) to the NIHMS system: https://www.nihms.nih.gov/submission/create/
- After you submit the manuscript to NIHMS, send Dr. Petersen the NIHMS ID for the submission.
We are required to report published papers to funding agences.
1. Make sure the finalized, unblinded manuscript (and any tables, figures, and the supplement; with the public OSF link; removing any highlighting or tracked changes) is uploaded as an updated version of the [preprint](#preprint) on [PsyArXiv](https://psyarxiv.com).
# Adapting Open Science to Longitudinal Research {#longitudinal}
See our paper on adapting open science to longitudinal research: https://onlinelibrary.wiley.com/doi/10.1002/icd.2315
[^1]: Ask Dr. Petersen to give you access.