The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

repoRter.nih: R Interface to the 'NIH RePORTER Project' API

Methods to easily build requests in the non-standard JSON schema required by the National Institute of Health (NIH)'s 'RePORTER Project API' <https://api.reporter.nih.gov/#/Search/post_v2_projects_search>. Also retrieve and process result sets as either a ragged or flattened 'tibble'.

Version: 0.1.4
Depends: R (≥ 4.0.0)
Imports: assertthat (≥ 0.2.1), crayon (≥ 1.4.1), dplyr (≥ 1.0.7), httr (≥ 1.4.2), janitor (≥ 2.1.0), jsonlite (≥ 1.7.2), lubridate (≥ 1.7.10), magrittr (≥ 2.0.1), purrr (≥ 0.3.4), tibble (≥ 3.1.3)
Suggests: devtools, ggplot2, ggrepel, knitr, tinytex, rmarkdown, scales, tufte, spelling
Published: 2023-01-15
DOI: 10.32614/CRAN.package.repoRter.nih
Author: Michael Barr, ACAS, MAAA, CPCU [cre, aut]
Maintainer: "Michael Barr, ACAS, MAAA, CPCU" <mike at bikeactuary.com>
BugReports: https://github.com/bikeactuary/repoRter.nih/issues
License: MIT + file LICENSE
URL: https://github.com/bikeactuary/repoRter.nih
NeedsCompilation: no
Language: en-US
Materials: README NEWS
CRAN checks: repoRter.nih results

Documentation:

Reference manual: repoRter.nih.pdf
Vignettes: repoRter.nih: a convenient R interface to the NIH RePORTER Project API

Downloads:

Package source: repoRter.nih_0.1.4.tar.gz
Windows binaries: r-devel: repoRter.nih_0.1.4.zip, r-release: repoRter.nih_0.1.4.zip, r-oldrel: repoRter.nih_0.1.4.zip
macOS binaries: r-release (arm64): repoRter.nih_0.1.4.tgz, r-oldrel (arm64): repoRter.nih_0.1.4.tgz, r-release (x86_64): repoRter.nih_0.1.4.tgz, r-oldrel (x86_64): repoRter.nih_0.1.4.tgz
Old sources: repoRter.nih archive

Linking:

Please use the canonical form https://CRAN.R-project.org/package=repoRter.nih to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.