Skip to content

tezr: Retrieve Turkish National Thesis Center metadata #774

Description

@emraher

Submitting Author Name: Emrah Er
Submitting Author Github Handle: @emraher
Other Package Authors Github handles:
Repository: https://github.com/emraher/tezr
Version submitted: 0.1.0.9000
Submission type: Standard
Editor: @LucyMcGowan
Reviewers: TBD

Archive: TBD
Version accepted: TBD
Language: en


  • Paste the full DESCRIPTION file inside a code block below:
Package: tezr
Title: Access Thesis Metadata from Turkiye's National Thesis Center
Version: 0.1.0.9000
Authors@R:
    person("Emrah", "Er", , "eer@eremrah.com", role = c("aut", "cre"))
Description: Retrieve, parse, cache, and analyze thesis metadata from the
    Council of Higher Education's National Thesis Center (Ulusal Tez Merkezi)
    at <https://tez.yok.gov.tr>. Supports basic, advanced, and detailed
    search. Also supports thesis detail retrieval, lookup tables, adaptive
    pagination for capped search results, and aggregate statistics for
    retrieval checks.
License: MIT + file LICENSE
URL: https://eremrah.com/tezr/, https://github.com/emraher/tezr
BugReports: https://github.com/emraher/tezr/issues
Encoding: UTF-8
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.3.3
Depends:
    R (>= 4.1.0)
Imports:
    httr2,
    rvest,
    dplyr,
    tibble,
    tidyr,
    purrr,
    stringr,
    stringi,
    cli,
    rlang
Suggests:
    testthat (>= 3.0.0),
    withr,
    knitr,
    rmarkdown,
    ggplot2,
    readr
Config/testthat/edition: 3
Config/Needs/website: emraher/eerdown
VignetteBuilder: knitr
LazyData: true

Scope

  • Please indicate which category or categories from our package fit policies this package falls under:

    • 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
    • rOpenSci internal tools
  • Explain how and why the package falls under these categories:

tezr retrieves public thesis metadata from Turkiye's National Thesis Center. The portal has no documented public API or bulk export, so the package provides scripted access to search forms, thesis detail pages, lookup tables, and capped result pagination.

  • Who is the target audience and what are scientific applications of this package?

The target audience is researchers studying higher education, graduate training, scholarly production, language and subject patterns, institutional research output, and thesis access status in Turkiye. Scientific applications include reproducible thesis metadata retrieval, bibliometric preparation, field-level or institution-level trend analysis, and retrieval completeness checks for studies based on National Thesis Center records.

  • Are there other R packages that accomplish the same thing? If so, how does yours differ or meet our criteria for best-in-category?

I am not aware of another R package that retrieves and parses metadata from Turkiye's National Thesis Center. Adjacent rOpenSci packages such as rentrez and europepmc retrieve scholarly metadata from formal APIs. tezr differs because the National Thesis Center exposes records through a public web portal rather than a documented API. bibliometrix focuses on downstream bibliometric analysis after data have been obtained. tezr focuses on retrieval, parsing, caching, completeness checks, and preparation of National Thesis Center metadata for analysis.

  • Does your package comply with our guidance around Ethics, Data Privacy and Human Subjects Research?

Yes. tezr retrieves public thesis metadata exposed by the National Thesis Center. It does not download thesis full text, bypass access restrictions, collect credentials, or handle private user data. The package identifies itself with a package-specific user agent, applies request delays and retries, caches repeated requests, and documents responsible use. The documentation asks users to avoid unnecessary repeated requests, cite the National Thesis Center or Council of Higher Education, record retrieval dates, and avoid redistributing metadata in ways that conflict with the source portal's terms.

  • If you made a pre-submission inquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted.

No pre-submission inquiry was made.

  • Explain reasons for any pkgcheck items which your package is unable to pass.

None. An uncached local pkgcheck::pkgcheck(".", use_cache = FALSE) run passed. The GitHub Actions pkgcheck workflow also passes on main.

Technical checks

  • I have read the rOpenSci packaging guide.
  • I have read the author guide and I expect to maintain this package for at least 2 years or to find a replacement.

This package:

  • does not violate the Terms of Service of any service it interacts with.
  • has a CRAN and OSI accepted license.
  • contains a README with instructions for installing the development version.
  • includes documentation with examples for all functions, created with roxygen2.
  • contains a vignette with examples of its essential functions and uses.
  • has a test suite.
  • has continuous integration, including reporting of test coverage.

Use of Generative AI

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

OpenAI Codex was used to assist with package readiness review, code revisions, test planning, verification, and drafting this submission text. The package maintainer reviewed and committed the code, documentation, and submission materials. Relevant recent repository changes include emraher/tezr@c653d99 and emraher/tezr@127e8f7.

Publication options

  • Do you intend for this package to go on CRAN?

  • Do you intend for this package to go on Bioconductor?

  • Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution?

Code of conduct

  • I agree to abide by rOpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

Metadata

Metadata

Assignees

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions