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

[FEATURE] REDCapTidieR Should Support Data Access Groups #57

Closed
5 tasks done
rsh52 opened this issue Oct 25, 2022 · 0 comments · Fixed by #153
Closed
5 tasks done

[FEATURE] REDCapTidieR Should Support Data Access Groups #57

rsh52 opened this issue Oct 25, 2022 · 0 comments · Fixed by #153
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@rsh52
Copy link
Collaborator

rsh52 commented Oct 25, 2022

Feature Request Description

REDCapTidieR should support the inclusion of Data Access Groups (DAGs). This is available in REDCapR's export_data_access_groups argument.

Additional Context

Data Access Groups are used for multiple collaborators and make it possible to changes access rights. The redcap_data_access_group variable comes out in the database export as its own column, but does not come out in the metadata (similar to redcap_repeat_instrument/instance).

This could be a good use of a R/Medicine hackathon topic

Potential Problems

It will be necessary to determine what happens to a user with limited DAG access rights.

Update 2023-03-28:

  • This should be solved using a redcap_dags argument (by default set to FALSE). Likely just needs to be incorporated with the REDCapR::redcap_read_oneshot argument for export_data_access_groups

Checklist

  • The issue is atomic
  • The issue description is documented
  • The issue title describes the problem succinctly
  • Developers are assigned to the issue
  • Labels are assigned to the issue
@rsh52 rsh52 added enhancement New feature or request help wanted Extra attention is needed backlog not to be worked on now labels Oct 25, 2022
@rsh52 rsh52 self-assigned this Oct 25, 2022
@skadauke skadauke added this to the 0.3 milestone Dec 6, 2022
@rsh52 rsh52 modified the milestones: 0.3, 0.4 Feb 20, 2023
@rsh52 rsh52 removed help wanted Extra attention is needed backlog not to be worked on now labels May 23, 2023
@rsh52 rsh52 mentioned this issue May 24, 2023
16 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants