https://github.com/aaronpeikert/worcs
Rstudio project template and convenience functions for the Workflow for Open Reproducible Code in Science (WORCS)
Science Score: 13.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
○codemeta.json file
-
○.zenodo.json file
-
✓DOI references
Found 1 DOI reference(s) in README -
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (18.1%) to scientific vocabulary
Last synced: 9 months ago
·
JSON representation
Repository
Rstudio project template and convenience functions for the Workflow for Open Reproducible Code in Science (WORCS)
Basic Info
- Host: GitHub
- Owner: aaronpeikert
- License: gpl-3.0
- Language: HTML
- Default Branch: master
- Homepage: https://osf.io/zcvbs
- Size: 18.8 MB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 0
Fork of cjvanlissa/worcs
Created about 6 years ago
· Last pushed over 1 year ago
https://github.com/aaronpeikert/worcs/blob/master/
# WORCS[](https://cran.r-project.org/package=worcs) [](https://r-pkg.org/pkg/worcs) [](https://lifecycle.r-lib.org/articles/stages.html#maturing) [](https://github.com/cjvanlissa/worcs/actions/workflows/R-CMD-check.yaml) [](code_of_conduct.md) [](https://bestpractices.coreinfrastructure.org/projects/3969) The Workflow for Open Reproducible Code in Science (WORCS) is an easy to adopt approach to ensuring a research project meets the requirements of Open Science from the start. It is based on a good enough philosophy, prioritizing user-friendliness over exhaustiveness. It can be used either in absence of, or in parallel to, existing requirements for Open workflows. It can also be enhanced with more elaborate solutions for specific issues. ## Where do I start? For most users, the recommended starting point is to [read the paper, published in Data Science](https://content.iospress.com/articles/data-science/ds210031), which introduces the WORCS workflow, explains the underlying tools, and illustrates how the `worcs` package can be used to create a new project that follows the workflow. The workflow is illustrated below; the [workflow vignette](https://cjvanlissa.github.io/worcs/articles/workflow.html) describes each step in detail.
## Installing the package Before installing the package, please read [this vignette](https://cjvanlissa.github.io/worcs/articles/setup.html), which explains how to set up your computer for `worcs` (using the CRAN version). If you know what youre doing and you wish to install the development version of the `worcs` package from GitHub instead, you can use: ``` r if(!requireNamespace("remotes")) install.packages("remotes") remotes::install_github("cjvanlissa/worcs", dependencies = TRUE, update = "never") ``` ## Citing WORCS You can cite WORCS using the following citation (please use the same citation for either the package, or the paper): > Van Lissa, C. J., Brandmaier, A. M., Brinkman, L., Lamprecht, A., > Peikert, A., , Struiksma, M. E., & Vreede, B. (2021). WORCS: A > Workflow for Open Reproducible Code in Science. Data Science. Data > Science, vol.4, no. 1, pp.29-49. DOI: 10.3233/DS-210031. ## About this repository This repository contains the following: 1. An R-package called `worcs`, with convenience functions to facilitate the WORCS workflow. 2. In the subfolder `./paper`, the source files for the paper describing the WORCS workflow. The repository serves two functions: To allow users to install the `worcs` package, and to allow collaborators access to the source code for the package and paper. ## Repository structure | File | Description | Usage | |:--------------|:--------------------------------|:----------------| | \_pkgdown.yml | YAML for package website | do not edit | | DESCRIPTION | R-package DESCRIPTION | do not edit | | LICENSE.md | Project license | do not edit | | NAMESPACE | R-package namespace | machine-written | | README.md | Read this file to get started! | do not edit | | README.Rmd | R-markdown source for readme.md | human editable | | worcs.Rproj | RStudio project file | do not edit | | docs/ | Package website | machine-written | | inst/ | RStudio project template files | human editable | | man/ | R-package documentation | do not edit | | paper/ | WORCS paper source files | human editable | | R/ | R-package source code | human editable | | vignettes/ | R-package vignettes | human editable | ## Contributing and Contact Information We are always eager to receive user feedback and contributions to help us improve both the workflow and the software. Major contributions warrant coauthorship to the package. Please contact the lead author at
, or: - [File a GitHub issue](https://github.com/cjvanlissa/worcs) for feedback, bug reports or feature requests - [Make a pull request](https://github.com/cjvanlissa/worcs/pulls) to contribute your code or prose By participating in this project, you agree to abide by the [Contributor Code of Conduct v2.0](https://www.contributor-covenant.org/). Contributions to the package must adhere to the [tidyverse style guide](https://style.tidyverse.org/). When contributing code, please add tests for that contribution to the `tests/testthat` folder, and ensure that these tests pass in the [GitHub Actions panel](https://github.com/cjvanlissa/worcs/actions/workflows/R-CMD-check). ## Acknowledgements The worcs logo is inspired by the Open Science Badges by the Center for Open Science (CC-BY-4.0), and makes use of the gear, services, gears, preferences, settings icon, made by MD Badsha Meah from www.freeicons.io (CC-BY-3.0).
Owner
- Name: Aaron Peikert
- Login: aaronpeikert
- Kind: user
- Repositories: 15
- Profile: https://github.com/aaronpeikert
GitHub Events
Total
- Push event: 6
- Create event: 1
Last Year
- Push event: 6
- Create event: 1

## Installing the package
Before installing the package, please read [this
vignette](https://cjvanlissa.github.io/worcs/articles/setup.html), which
explains how to set up your computer for `worcs` (using the CRAN
version).
If you know what youre doing and you wish to install the development
version of the `worcs` package from GitHub instead, you can use:
``` r
if(!requireNamespace("remotes")) install.packages("remotes")
remotes::install_github("cjvanlissa/worcs", dependencies = TRUE, update = "never")
```
## Citing WORCS
You can cite WORCS using the following citation (please use the same
citation for either the package, or the paper):
> Van Lissa, C. J., Brandmaier, A. M., Brinkman, L., Lamprecht, A.,
> Peikert, A., , Struiksma, M. E., & Vreede, B. (2021). WORCS: A
> Workflow for Open Reproducible Code in Science. Data Science. Data
> Science, vol.4, no. 1, pp.29-49. DOI: 10.3233/DS-210031.
## About this repository
This repository contains the following:
1. An R-package called `worcs`, with convenience functions to
facilitate the WORCS workflow.
2. In the subfolder `./paper`, the source files for the paper
describing the WORCS workflow.
The repository serves two functions: To allow users to install the
`worcs` package, and to allow collaborators access to the source code
for the package and paper.
## Repository structure
| File | Description | Usage |
|:--------------|:--------------------------------|:----------------|
| \_pkgdown.yml | YAML for package website | do not edit |
| DESCRIPTION | R-package DESCRIPTION | do not edit |
| LICENSE.md | Project license | do not edit |
| NAMESPACE | R-package namespace | machine-written |
| README.md | Read this file to get started! | do not edit |
| README.Rmd | R-markdown source for readme.md | human editable |
| worcs.Rproj | RStudio project file | do not edit |
| docs/ | Package website | machine-written |
| inst/ | RStudio project template files | human editable |
| man/ | R-package documentation | do not edit |
| paper/ | WORCS paper source files | human editable |
| R/ | R-package source code | human editable |
| vignettes/ | R-package vignettes | human editable |
## Contributing and Contact Information
We are always eager to receive user feedback and contributions to help
us improve both the workflow and the software. Major contributions
warrant coauthorship to the package. Please contact the lead author at