ropensci / software-review

rOpenSci Software Peer Review.
286 stars 104 forks source link

cancerprof: API Client for extracting data from State Cancer Profiles #635

Closed realbp closed 2 months ago

realbp commented 3 months ago

Submitting Author Name: Brian Park Submitting Author Github Handle: !--author1-->@realbp<!--end-author1-- Repository: https://github.com/getwilds/cancerprof Submission type: Pre-submission Language: en


Package: cancerprof
Title: API Client for State Cancer Profiles
Version: 0.0.0.9000
Authors@R: 
    person("Brian", "Park", , "joon.brianpark@gmail.com", role = c("aut", "cre"),
           comment = c(ORCID = "YOUR-ORCID-ID"))
Description: An API Client for accessing data from State Cancer Profiles for programmable analysis.
License: MIT + file LICENSE
URL: https://github.com/getwilds/cancerprof
BugReports: https://github.com/getwilds/cancerprof/issues
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.0
Imports: 
    cdlTools,
    cli,
    dplyr,
    httr2,
    magrittr,
    rlang,
    stringr,
    utils
Suggests: 
    knitr,
    rmarkdown,
    testthat
Config/testthat/edition: 3
VignetteBuilder: knitr
Depends: 
    R (>= 2.10)

Scope

cancerprof allows users to extract data from State Cancer Profiles for programmable analysis. cancerprof makes accessing the unstructured api from state cancer profiles intuitive and easy.

The target audience for cancerprof is anyone who wants to access data from state cancer profiles to conduct programmable analysis without having to navigate the complex nature of its GUI. Specifically, cancer researchers could use cancerprof to conduct reproducable analysis of cancer crossed references with a variety of topics found within the data from state cancer profiles.

Currently there are not other softwares or packages that extracts the publicly available data from State Cancer Profiles.

Cancerprof does not breach any data privacy laws and complies with the ethics policies of ropensci.

ldecicco-USGS commented 3 months ago

Looks like a good fit for an rOpenSci submission. As for the checks, you don't need to necessarily address all the "good practices" notes. You will need to get the main checks (✔️) from the ropensci bot to pass in order to get an editor assigned (which will kick off the full process). Let me know if that doesn't make sense.

I'd recommend adding some details to the Readme. Also, I'm always a big fan of having pkgdown produce some rendered documentation. I usually recommend usethis::use_pkgdown_github_pages() to get started.

realbp commented 3 months ago

Thank you for the feedback! I pkgdown is now up and running at http://getwilds.org/cancerprof/.

I also ran pkgcheck() and got all of the checks to pass.

Screenshot 2024-04-01 at 12 14 07 PM

Should I open up a issue for submission to start the peer review process?

ldecicco-USGS commented 3 months ago

Please do, thanks!