Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide for project level backup of redcap data #87

Open
pbchase opened this issue Nov 16, 2022 · 1 comment
Open

Provide for project level backup of redcap data #87

pbchase opened this issue Nov 16, 2022 · 1 comment

Comments

@pbchase
Copy link
Contributor

pbchase commented Nov 16, 2022

Provide for project level backup of redcap data

@pbchase
Copy link
Contributor Author

pbchase commented Nov 28, 2022

Backup method

I've gone back and forth on the type of incremental backup we should make. The choices are to read the log data via the API (see OuhscBbmc/REDCapR#320), read the log data directly, or read the updated records via redacp_read. After much vacillation, I think the best approach is redcap_read, while reading record deletion data from redcap_log_read.

Pros

  • Full backups and incremental backups of a project to be made 100% via the API if an API token is available.
  • A full restore dataset could be reconstructed by binding date-stamped rows, sorting by date, distincting, and then removing any rows that pre-date their deletion.
  • At point-in-time restore can be created by filtering the data fed full-restore process.
  • Each backup file is in the appropriate format for REDCap data input and redcap_write.
  • Each backup file is restorable without processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant