From 10b92568b628990f7b532b5d141634a2d11402d4 Mon Sep 17 00:00:00 2001 From: agdamsbo <43278243+agdamsbo@users.noreply.github.com> Date: Fri, 25 Oct 2024 08:36:11 +0000 Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20agdamsbo?= =?UTF-8?q?/REDCapCAST@1189da6c8658fdd766676342b70b9d297b4bb94f=20?= =?UTF-8?q?=F0=9F=9A=80?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- index.html | 12 ++++++++---- pkgdown.yml | 2 +- search.json | 2 +- 3 files changed, 10 insertions(+), 6 deletions(-) diff --git a/index.html b/index.html index e7368a7..42057fd 100644 --- a/index.html +++ b/index.html @@ -68,11 +68,15 @@

REDCap database casting and handling of castellated data when using repeated instruments and longitudinal projects.

-

This package is a fork of pegeler/REDCapRITS. The REDCapRITS represents great and extensive work to handle castellated REDCap data in different programming languages. This fork is purely minded on R usage and includes a few implementations of the main REDCap_split function.

-

I started working on this project as the castellated longitudinal data set was a little challenging. Later, I have come to learn of the redcapAPI package, which would also cover this functionality. I find the redcapAPIpackage quite advanced and a little difficult to work with. This have led to the continued work on this package, as an easy-to-use approach for data migration, data base creation and data handling. This package is very much to be seen as an attempt at a R-to-REDCap-to-R foundry for handling both the transition from dataset/variable list to database and the other way, from REDCap database to a tidy dataset. The goal was also to allow for a “minimal data” approach by allowing to filter records, instruments and variables in the export to only download data needed. I think this approach is desirable for handling sensitive, clinical data. Please refer to REDCap-Tools for other great tools for working with REDCap in R.

-

For any more advanced uses, consider using the redcapAPI package.

+

This package is a fork of pegeler/REDCapRITS. The REDCapRITS represents great and extensive work to handle castellated REDCap data in different programming languages. This fork is purely minded on R usage and includes a few implementations of the main REDCap_split function. The REDCapRITS as well as REDCapCAST would not be possible without the outstanding work in REDCapR.

-

Use and immprovements +

What problem does REDCapCAST solve? +

+

I started working on this project as the castellated longitudinal data set was a little challenging. Later, I have come to learn of the redcapAPI package, which would also cover this functionality. I find the redcapAPIpackage quite advanced and a little difficult to work with. This have led to the continued work on this package, as an easy-to-use approach for data migration, data base creation and data handling. This package is very much to be seen as an attempt at a R-to-REDCap-to-R foundry for handling both the transition from dataset/variable list to database and the other way, from REDCap database to a tidy dataset. The goal was also to allow for a “minimal data” approach by allowing to filter records, instruments and variables in the export to only download data needed. I think this approach is desirable for handling sensitive, clinical data. Please refer to REDCap-Tools for other great tools for working with REDCap in R.

+

For any more advanced uses, consider using the redcapAPI or REDCapR packages.

+
+
+

Main functionality

Here is just a short description of the main functions: