-
Notifications
You must be signed in to change notification settings - Fork 48
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
Logging (audit trail) #243
Comments
@wrlemast, I'm not seeing any API method to retrieve the logging info. If that doesn't exist, there's nothing for REDCapR to call. Two options I see:
Both are feasible. I'm willing to discuss it more if you'd like. |
@wibeasley, Thank you for a quick response. I would appreciate a discussion about pulling from MySQL. I am very new to this (my training is in biochemistry), so please excuse me if I seem a little slow at this. My supervisor said that she would all me to get MySQL to complete this. How difficult is it to pull from MySQL? Again, Thank you! |
@wibeasley, Also I do not have access to the community site. |
It's not my favorite that the community site isn't open to API developers. You'll need to talk to your REDCap admins for both requesting the feature on the site, and to access the underlying database. Politically, they'll be understandably reluctant to open up the database to you. Maybe they'll be willing to regularly export a subset of data that pertains just to your project_id. Technically, look around line 244 for the sql reading from the user table. You'd do something similar with the 'odbc' package (but pull from the table containing the audit info you want) |
@wrlemast, I hope this effort accessing the database directly went well. Here is a recent thread that might be relevant (that your site REDCap admin can access and share): https://community.projectredcap.org/questions/66080/logging-database-table-1.html |
I am trying to find a way to pull the logging data as a way of tracking employee productivity.
The text was updated successfully, but these errors were encountered: