Skip to contents

REDCapCAST 24.4.1 - in development


  • Fix: read_redcap_tables(): field names testing allows to include “[form_name]_complete” fields.

  • Fix: ds2dd_detailed(): default record ID name is now “record_id”, the REDCap default. Default is still to use the first column name. Support was added to interpret column name prefix or suffix as instrument names. See the examples.

  • New: create_instrument_meta(): creates zip with instrument files to allow adding new instruments to project in production. Takes data dictionary as input and creates a zip for each instrument specified by the form_name column.

Documentation and more

  • Dependencies: In order to deploy shiny_cast() with shinylive, I need to remove curl as a dependency. To accomplish this, the shiny_deploy() helper functions has been moved to the package pacakge.aid. This is for a rainy day: The whole shiny part may be migrated to its own project to try to separate things and be easy on dependencies. Time will tell.

REDCapCAST 24.2.1

CRAN release: 2024-02-28


  • Fix: ds2dd(): uses correct default dd column names. Will be deprecated.

  • Fix: easy_redcap(): fixed to actually allow project naming. also specifically asks for uri. widening updated to work.

  • Fix: redcap_wider(): updated to accept more formats and allow handling of simple projects without repeating instruments and not longitudinal.

  • Fix: read_redcap_tables(): now handles non-longitudinal project without repeatable instruments.

  • NEW: ds2dd_detailed(): extension of the ds2dd(), which serves to preserve as much metadata as possible automatically. Depends on a group of helper functions also introduced. Of special note is the guess_time_only_filter(), which will try to guess which columns/variables should be formatted as time only formats. Supports hms time format. DETAILED INSTRUCTION AND VIGNETTE IS PENDING.

  • NEW: read_redcap_instrument(): convenience function to retrieve complete instrument. Goes a little against the focused approach. With REDCapR::redcap_read() you can specify a form to download. You have to also specify the record id variable though. This is done for you with read_redcap_instrument(). Nothing fancy.

  • NEW: shiny_cast(): Shiny application to ease the process of converting a spreadsheet/data set to a REDCap database. The app runs locally and data is transferred securely. You can just create and upload the data dictionary, but you can also transfer the given data in the same process. I plan to host the app with, but for now you can run it locally.


I believe renv has now been added and runs correctly. After clone, do renv::restore() to install all necessary package to modify the package. This seems to always be back and forth. renv may be on its way out again.

Added a Code of Conduct.

REDCapCAST 24.1.1

CRAN release: 2024-01-09


  • Fix: read_redcap_tables(): checking form names based on data dictionary to allow handling of non-longitudinal projects. Prints invalid form names and invalid event names. If invalid form names are supplied to REDCapR::redcap_read() (which is the backbone), all forms are exported, which is not what we want with a focused approach. Invalid event names will give an output with a rather peculiar formatting. Checking of field names validity is also added.

REDCapCAST 23.12.1

CRAN release: 2023-12-20

One new function to ease secure dataset retrieval and a few bug fixes.


  • New: easy_redcap() function to ease the retrieval of a dataset with read_redcap_tables() with keyring-package based key storage, which handles secure API set, storage and retrieval. Relies on a small helper function, get_api_key(), which wraps relevant keyring-functions. Includes option to cast the data in a wide format with flag
  • Fix: REDCap_split(): when using this function on its own, supplying a data set with check boxes would fail if metadata is supplied as a tibble. Metadata is now converted to data.frame. Fixed.
  • Fix: read_redcap_tables(): fixed bug when supplying events.

REDCapCAST 23.6.2

CRAN release: 2023-07-04

This version marks the introduction of a few helper functions to handle database creation.


REDCapCAST 23.6.1

CRAN release: 2023-06-06


  • Updated description.
  • Look! A hex icon!
  • Heading for CRAN.

REDCapCAST 23.4.1


  • Aiming for CRAN

REDCapCAST 23.3.2


  • Page added. Vignettes to follow.

  • GithubActions tests added and code coverage assessed. Badge galore..

REDCapCAST 23.3.1

New name: REDCapCAST

To reflect new functions and the limitation to only working in R, I have changed the naming of the fork, while still, of course, maintaining the status as a fork.

The versioning has moved to a monthly naming convention.

The main goal this package is to keep the option to only export a defined subset of the whole dataset from the REDCap server as is made possible through the REDCapR::redcap_read() function, and combine it with the work put into the REDCapRITS package and the handling of longitudinal projects and/or projects with repeated instruments.


  • read_redcap_tables() NEW: this function is mainly an implementation of the combined use of REDCapR::readcap_read() and REDCap_split() to maintain the focused nature of REDCapR::readcap_read(), to only download the specified data. Also implements tests of valid form names and event names. The usual fall-back solution was to get all data.

  • redcap_wider() NEW: this function pivots the long data frames from read_redcap_tables() using tidyr::pivot_wider().

  • focused_metadata() NEW: a hidden helper function to enable a focused data acquisition approach to handle only a subset of metadata corresponding to the focused dataset.


  • metadata handling IMPROVED: improved handling of different column names in matadata (DataDictionary) from REDCap dependent on whether it is acquired thorugh the api og downloaded from the server.