REDCap General User Information

This page contains information about basic tasks in REDCap and actions that could cause harm to a REDCap project as well as descriptions as to why

REDCap Access

This is a list of things not to do in REDCap in order to save yourself time as a new user.

1. Do not submit a request to support to add you or someone else to a project.
   1. REDCap users are responsible for adding other users to REDCap projects. It is easier and less time consuming to reach out to someone on the project with user rights privileges and then have them add you. The only way support can add you to a project is with permission from the PI and a list of rights you should have. This is to protect data so we do not accidentally add someone to a project they should not have access to or give someone higher level user rights than needed.
2. Do not submit a request to support for a guest user or user that is not a WashU employee.
   1. Guest users need to get a guest WashU key. Guest WashU keys are managed by WashU IT. WashU REDCap has no access to this process. All you need to do is complete the Guest WashU key form and then have the person log in after they have received their guest key. REDCap support does not need to be involved at all unless you receive a confirmation email after logging in to REDCap

REDCap Admin Only Tasks

REDCap Production Project Pitfalls

This is a list of things not to do when a project is in production

1. Do not delete a field where data has already been collected.
   1. Deleting a field where data has already been collected causes data in that field to be detached from record IDs. This means you cannot view it within REDCap or export it from REDCap. Using @HIDDEN action tag family is advised instead of deleting data.
2. Do not delete an event where data has already been collected.
   1. Deleting an event from REDCap where data has been collected causes that data to become detached from the event so you are unable to view or export the data. It is better to rename events that delete events.
3. Do not change the labels of multiple choice fields where data have already been collected.
   1. Changing the label of a choice in a multiple choice field can change the meaning of data that were already collected in that field. Using the @HIDECHOICE action tag allows you to keep the data already collected safe while adding new choices.
4. Do not Move an instrument from the first position if you have created a Custom Survey Link
   1. A Public Survey URL and Custom Survey Link get attached to the first instrument in a project. The public survey link changes and the custom survey link disappears. Be sure that you are certain the first instrument in the project will stay there before creating a Custom Survey URL for the project