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: guide/bundle.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ This may include a copy of the author's files, and any additional files that the
24
24
- Dockerfile and Docker image, see [Ten simple rules for writing Dockerfiles for reproducible data science](https://doi.org/10.1371/journal.pcbi.1008316)
25
25
- ...
26
26
27
-
## Codecheck report with R Markdown
27
+
## Codecheck certificate with R Markdown
28
28
29
29
R Markdown has some nice features that are helpful for writing a report.
Copy file name to clipboardExpand all lines: guide/community-workflow-codechecker.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,17 +80,17 @@ Some further tips:
80
80
- Is the data and [software](https://content.iospress.com/articles/data-science/ds190026) FAIR?
81
81
1. Add **mandatory codechecker-contributed information** to the **`codecheck.yml`** file, see [spec](/spec/config/latest)
82
82
1. Wait for the article DOI.
83
-
1.**Deposit the CODECHECK report on _Zenodo_** using your own Zenodo account and following the [community curation policy](https://zenodo.org/communities/codecheck/curation-policy) (which is replicated here for convenience):
83
+
1.**Deposit the CODECHECK certificate on _Zenodo_** using your own Zenodo account and following the [community curation policy](https://zenodo.org/communities/codecheck/curation-policy) (which is replicated here for convenience):
84
84
-_Reserve a DOI_
85
85
- Add the DOI to the `codecheck.yml` file.
86
-
- Add the DOI to the `codecheck.pdf` CODECHECK report, which should include a full citation of itself.
86
+
- Add the DOI to the `codecheck.pdf` CODECHECK certificate, which should include a full citation of itself.
87
87
-_Files_
88
88
-`codecheck.pdf` (mandatory)
89
89
- Optional: You can add any material to this record that you see fit, especially things that helped you with your reproduction, i.e., the [CODECHECK bundle](/guide/bundle).
90
90
-_Communities_: Search for "codecheck" to add the record to the [CODECHECK community on Zenodo](https://zenodo.org/communities/codecheck).
91
91
-_Authors_: Add all codecheckers as authors.
92
92
-_Title_: `"CODECHECK Certificate YYYY-NNN"` (certificate number issued via the register ticket above, optionally you may add the submission's title).
93
-
-_License_: Use `Creative Commons Attribution 4.0 International` if you only upload the CODECHECK report, otherwise use `Other (Open)` or `Other (Attribution)` and document the licensing of the different parts in an _Additional notes_ field.
93
+
-_License_: Use `Creative Commons Attribution 4.0 International` if you only upload the CODECHECK certificate, otherwise use `Other (Open)` or `Other (Attribution)` and document the licensing of the different parts in an _Additional notes_ field.
94
94
-_Description_: Copy the summary of the check here.
95
95
-_Contributors_: Add the original authors as contributors (see Zendo Metadata form section "Contributors (optional)") with a suitable role (e.g., "Researcher").
96
96
- Add a _Relationship_ in metadata between the certificate and the original paper/submission.
0 commit comments