Presubmission inquiry: bddkR

[ozancanozdemir]

Submitting Author Name: Ozancan Ozdemir
Submitting Author Github Handle: @ozancanozdemir
Repository: https://github.com/ozancanozdemir/bddkR
Submission type: Pre-submission
Language: en

---

• Paste the full DESCRIPTION file inside a code block below:

Package: bddkR
Type: Package
Title: What the Package Does (Title Case)
Version: 0.1.0
Authors@R: person(given = "Ozancan",
                  family = "Ozdemir",
                  role = c("aut", "cre"),
                  email = "ozancanozdemir@gmail.com")
Maintainer: Ozancan Ozdemir <ozancanozdemir@gmail.com>
Description: The package fetches monthly financial tables and banking sector data published on the official website of the Banking Regulation and Supervision Agency (BRSA, BDDK) of Turkey and also enables you to save it as an Excel file. It is a R implementation of the Python package of [bddkdata](https://pypi.org/project/bddkdata/).
License: MIT + file LICENSE
URL: https://github.com/ozancanozdemir/bddkR
BugReports: https://github.com/ozancanozdemir/bddkR/issues
Depends:
    R (>= 4.0)
Imports:
    httr,
    jsonlite,
    dplyr,
    writexl,
    lubridate
Encoding: UTF-8
LazyData: true
RoxygenNote: 7.2.3
Suggests:
    testthat (>= 3.0.0)
Config/testthat/edition: 3

Scope

Data Lifecycle Packages

• data retrieval
• data extraction
• data munging
• data deposition
• data validation and testing
• workflow automation
• version control
• citation management and bibliometrics
• scientific software wrappers
• field and lab reproducibility tools
• database software bindings
• geospatial data
• translation

Statistical Packages

• Bayesian and Monte Carlo Routines

• Dimensionality Reduction, Clustering, and Unsupervised Learning

• Machine Learning

• Regression and Supervised Learning

• Exploratory Data Analysis (EDA) and Summary Statistics

• Spatial Analyses

• Time Series Analyses

• Probability Distributions

• Explain how and why the package falls under these categories (briefly, 1-2 sentences). Please note any areas you are unsure of: bddkR retrieves monthly banking sector data published on the official BDDK (Banking Regulation and Supervision Agency of Turkey) website and processes it into ready-to-use tables/Excel files, so it fits the "data retrieval" category.

• If submitting a statistical package, have you already incorporated documentation of standards into your code via the srr package? Not applicable, this is not a statistical package.

• Who is the target audience and what are scientific applications of this package? Researchers, economists, and policy analysts studying the Turkish banking sector and financial stability who need programmatic access to BDDK's published data.

• Are there other R packages that accomplish the same thing? If so, how does yours differ or meet our criteria for best-in-category? To our knowledge there is no existing R package retrieving BDDK banking sector data. This package is an R implementation of an existing Python package (bddkdata).

• (If applicable) Does your package comply with our guidance around Ethics, Data Privacy and Human Subjects Research? Yes. The package only accesses publicly published, aggregate regulatory data; it does not involve personal or sensitive data.

• Any other questions or issues we should be aware of?: Our GitHub main branch DESCRIPTION file still has a placeholder Title and shows version 0.1.0, while the version released on CRAN is 0.1.1 with an updated title; happy to sync this if needed.

Use of Generative AI

• Generative AI tools were used to produce some of the material in this submission.

Generative AI tools were used to help debug some errors during development of the package.

[maurolepore]

@ropensci-review-bot check package

[ropensci-review-bot]

Thanks, about to send the query.

[ropensci-review-bot]

🚀

Error: Issue template has no 'repourl'

👋

[maurolepore]

@ropensci-review-bot similar packages

[maurolepore]

@ozancanozdemir thanks for sharing your work with rOpenSci

I see the package checks are failing with

Error: Issue template has no 'repourl'

This is likely a formatting issue. It seems like the top-comment is missing the markers that informs our system the values you passed to each field. Could you please fix it?

Compare

• Lost required tags Presubmission inquiry: bddkR #783 (comment):

Submitting Author Name: Ozancan Ozdemir
Submitting Author Github Handle: @ozancanozdemir
Repository: https://github.com/ozancanozdemir/bddkR
Submission type: Pre-submission
Language: en

• Preserves required tags: Pre-submission inquiry: brapiR2 - BrAPI v2 client for plant breeding databases #782

Submitting Author Name: Joash Joshua Ayo
Submitting Author Github Handle: <!--author1-->@josh45-source<!--end-author1-->
Repository:  <!--repourl-->https://github.com/josh45-source/brapiR2<!--end-repourl-->
Submission type: <!--submission-type-->Pre-submission<!--end-submission-type-->
Language: <!--language-->en<!--end-language-->

[ozancanozdemir]

Thanks for flagging this. I've edited the top comment to include the missing HTML comment markers around the handle, repository, submission type, and language fields. Let me know if the checks need a manual re-run.

@ozancanozdemir thanks for sharing your work with rOpenSci

I see the package checks are failing with

Error: Issue template has no 'repourl'

This is likely a formatting issue. It seems like the top-comment is missing the markers that informs our system the values you passed to each field. Could you please fix it?

Compare

• Lost required tags Presubmission inquiry: bddkR #783 (comment):

Submitting Author Name: Ozancan Ozdemir
Submitting Author Github Handle: @ozancanozdemir
Repository: https://github.com/ozancanozdemir/bddkR
Submission type: Pre-submission
Language: en

• Preserves required tags: Pre-submission inquiry: brapiR2 - BrAPI v2 client for plant breeding databases #782

Submitting Author Name: Joash Joshua Ayo
Submitting Author Github Handle: <!--author1-->@josh45-source<!--end-author1-->
Repository:  <!--repourl-->https://github.com/josh45-source/brapiR2<!--end-repourl-->
Submission type: <!--submission-type-->Pre-submission<!--end-submission-type-->
Language: <!--language-->en<!--end-language-->

[mpadge]

@ozancanozdemir You can trigger the checks yourself any time with this command:

@ropensci-review-bot check package

But it would probably be better for you first to install our pkgcheck-action GitHub workflow in your repository. That will automatically run on every push, and you'll be able to fix everything flagged there. I recommend that, as I see from local checks that quite a few aspects will need to be improved before proceeding here. Thanks!

[maurolepore]

Thanks @ozancanozdemir for your quick response. I second Mark's idea but in the interest of having a quick peek myself I'll go ahead and trigger checks now ...

[maurolepore]

@ropensci-review-bot check package

[ropensci-review-bot]

Thanks, about to send the query.

[ropensci-review-bot]

🚀

Editor check started

👋

[maurolepore]

@ropensci-review-bot similar packages

[ropensci-review-bot]

Five most similar rOpenSci packages

• stats19 'Work with Open Road Traffic Casualty Data from Great Britain' (v4.0.0, released 2026-03-18)
• rix 'Reproducible Data Science Environments with 'Nix'' (v0.18.2, released 2026-02-18)
• yfR 'Downloads and Organizes Financial Data from Yahoo Finance' (v1.1.3, released 2026-02-03)
• opentripplanner 'Setup and connect to 'OpenTripPlanner'' (v0.5.2, released 2024-05-06)
• wateRinfo 'Download Time Series Data from Waterinfo.be' (No releases to date.)

Five most similar CRAN packages

• bddkR 'Gathering Monthly Banking Sector Data from BDDK of Turkey' (v0.1.1, published 2025-09-14)
• readrba 'Download and Tidy Data from the Reserve Bank of Australia' (v0.1.12, published 2025-08-18)
• stats19 'Work with Open Road Traffic Casualty Data from Great Britain' (v4.0.0, published 2026-03-18)
• tidyquant 'Tidy Quantitative Financial Analysis' (v1.0.11, published 2026-03-16)
• usdarnass 'USDA NASS Quick Stats API' (v0.1.0, published 2019-06-21)

---

Matches are generated by the 'pkgmatch' package, based on inverse-term frequencies; see the main function documentation for details.

[ropensci-review-bot]

Checks for bddkR (v0.1.0)

git hash: 6429940c

• ✔️ Package is already on CRAN.
• ✖️ does not have a 'contributing' file.
• ✔️ uses 'roxygen2'.
• ✔️ 'DESCRIPTION' has a URL field.
• ✔️ 'DESCRIPTION' has a BugReports field.
• ✖️ Package has no HTML vignettes
• ✖️ These functions do not have examples: [fetch_data].
• ✖️ Repository has no website
• ✖️ Package has no continuous integration checks.
• ✔️ Package coverage is 79.2%.
• ✔️ R CMD check found no errors.
• ✔️ R CMD check found no warnings.
• 👀 Some goodpractice linters failed.

Important: All failing checks above must be addressed prior to proceeding

(Checks marked with 👀 may be optionally addressed.)

Package License: MIT + file LICENSE

---

1. Package Dependencies

Details of Package Dependency Usage (click to open)

The table below tallies all function calls to all packages ('ncalls'), both internal (r-base + recommended, along with the package itself), and external (imported and suggested packages). 'NA' values indicate packages to which no identified calls to R functions could be found. Note that these results are generated by an automated code-tagging system which may not be entirely accurate.

type	package	ncalls
internal	base	557
imports	httr	4
imports	jsonlite	2
imports	lubridate	2
imports	dplyr	NA
imports	writexl	NA
suggests	testthat	NA
linking_to	NA	NA

Click below for tallies of functions used in each package. Locations of each call within this package may be generated locally by running 's <- pkgstats::pkgstats(<path/to/repo>)', and examining the 'external_calls' table.

base

list (527), sprintf (7), c (3), names (3), as.character (2), as.Date (2), do.call (2), length (2), rbind (2), as.data.frame (1), for (1), lapply (1), max (1), ncol (1), sapply (1), seq_along (1)

httr

content (2), add_headers (1), POST (1)

jsonlite

fromJSON (2)

lubridate

month (1), year (1)

NOTE: Some imported packages appear to have no associated function calls; please ensure with author that these 'Imports' are listed appropriately.

---

2. Statistical Properties

This package features some noteworthy statistical properties which may need to be clarified by a handling editor prior to progressing.

Details of statistical properties (click to open)

The package has:

• code in R (100% in 1 files) and
• 1 authors
• no vignette
• no internal data file
• 5 imported packages
• 1 exported function (median 392 lines of code)
• no non-exported function in R (median lines of code)

---

Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
The following terminology is used:

• loc = "Lines of Code"
• fn = "function"
• exp/not_exp = exported / not exported

All parameters are explained as tooltips in the locally-rendered HTML version of this report generated by the checks_to_markdown() function

The final measure (fn_call_network_size) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.

measure	value	percentile	noteworthy
files_R	1	0.6	TRUE
files_vignettes	0	0.0	TRUE
files_tests	2	76.8
loc_R	514	73.1
loc_tests	18	24.6
num_vignettes	0	0.0	TRUE
n_fns_r	1	35.9
n_fns_r_exported	1	42.1
n_fns_r_not_exported	0	0.0	TRUE
n_fns_per_file_r	1	36.3
num_params_per_fn	9	94.7
loc_per_fn_r	392	98.9	TRUE
loc_per_fn_r_exp	392	99.0	TRUE
doclines_per_fn_exp	12	46.0
fn_call_network_size	0	0.0	TRUE

---

2a. Network visualisation

Click to see the interactive network visualisation of calls between objects in package

---

3. goodpractice and other checks

Details of goodpractice checks (click to open)

---

3b. goodpractice results

Test coverage with covr

Package coverage: 79.17

Cyclocomplexity with cyclocomp

The following function have cyclocomplexity >= 15:

function	cyclocomplexity
fetch_data	102

Static code analyses with lintr

lintr found the following 38 potential issues:

message	number of times
Avoid undesirable function "sapply".	1
Lines should not be more than 80 characters.	31
toString(.) is more expressive than paste(., collapse = ", ").	3
Use comparison operators (e.g.	1
Use seq_len(ncol(...)) instead of 1:ncol(...), which is likely to be wrong in the empty edge case.	2

Other goodpractice checks

✖️ All internal functions are used
✖️ URLs in Description are enclosed in angle brackets
✖️ Documented functions have @export, @nord, or @Rdname

---

Package Versions

package	version
pkgstats	0.2.3.2
pkgcheck	0.1.3.6

---

Editor-in-Chief Instructions:

Processing may not proceed until the items marked with ✖️ have been resolved.

This package has some noteworthy properties, see 'Package Statistics' details above.

[maurolepore]

@ozancanozdemir please see the pkgcheck results above:
✖️ does not have a 'contributing' file.
✖️ Package has no HTML vignettes
✖️ These functions do not have examples: [fetch_data].
✖️ Repository has no website
✖️ Package has no continuous integration checks.
👀 Some goodpractice linters failed.
Important: All failing checks above must be addressed prior to proceeding

Also I see the package has a relatively short history spanning a single day, and all files (except for README.md) have been added in a single commit

Details

https://github.com/ozancanozdemir/bddkR/commits/main/

https://github.com/ozancanozdemir/bddkR/graphs/commit-activity

https://github.com/ozancanozdemir/bddkR/graphs/code-frequency

In such cases we ought to require an additional document within the repo itself explain the design history and design decisions behind the current architecture

You can see an example of a DESIGN.md linked to at #774 (comment).

I believe we'll have a blog-post about this requirement soon (cc @mpadge).

Looking forward to it.