/
Quick Tips

Quick Tips

All quick tips are posted to the help_redcap Slack channel, which is available to all ASU faculty, staff, and students via the ASU Community workspace.

 

Sep 26, 2025 What's New and What's Next

Summary of What's New

  • Draft Preview Mode: preview instruments with drafted changes as if they were live and simulate live data entry without saving it to the project

  • Descriptive Pop-ups: enable the ability for a participant or data collector to hover over text to show a pop-up with descriptive text

  • Randomization module update to allow multiple, blinded randomizations, real-time trigger logic, and Smart Variables and developer/API methods

  • Integration of AI for text assistance, data summarization, and MLM translations

  • Background Bulk Record Delete

Summary of What's Next

  • Tango Gift Card Integration to send rewards to participants

  • Project Migration Tool

  • AI Project-level Chatbot

  • REDCap Share: participant-mediated EHR retrieval

Sep 19, 2025 Survey Notifications

You can set up notifications to alert any internal user (e.g. research staff, data collector, PI) using the following methods:

  1. Survey Notifications - allows you to quickly select the user that will receive the notification upon the completion of the survey

    1. Will only work for surveys (not forms)

    2. Survey must be completed (not partially completed)

  2. Alerts and Notifications - allows you to customize who will receive the notification and detailed conditions under which it will be triggered

    1. Requires additional time to set up

    2. Robust condition settings

    3. Customizable email sender, subject, and body

Note: Option 2 can be adapted to send alerts/notifications to participants (e.g. for an upcoming visit or survey invitation)

Mar 28, 2025 Survey Distribution - Immediately or at a Specified Time

I've updated the Best Practices section of ASUREDCAP to include approaches on survey distribution, particularly when trying to send invitations immediately during in-person or virtual visits and when sending invitations at specified times. Here is a summary:

  1. Sending Immediately During a Visit --> utilize the 'Survey options' menu found at the top of the instrument page (image 1). Options from this menu will be dictated by how you're visiting with the participant (in-person or virtual)

  2. Sending at a Specified Time --> utilize the 'Send on next' (image 2) or 'Send the invitation' days/hours/minutes (image 3) options. This will allow you to schedule the invitation as soon as the ASI conditions are met (and un-schedule if needed) and send it at the defined time.

Feb 14, 2025 The Power of the URL

Pay attention to the URL as you navigate REDCap web pages from the user interface (the UI, i.e. logged in as a user) as well as when testing or distributing surveys to participants. From within the system, Smart Variables can make them dynamic. For example, creating URLs using [redcap-version-url] would always navigate to the desired page even after system updates. And sharing UI links outside REDCap is secure and requires logging in and for the user to have access to the project and page. Piping adds to capabilities. And keep in mind that (if set up correctly) the generated URLs will respect the record ID, event, or instance that triggers their creation. Test thoroughly!
Here are some examples:
A project's Record Status Dashboard

A project's Record Status Dashboard listing all records (the page may take awhile to load depending on the total)

...and if I want the link to be included in an Alert from the project to my research staff:

  • [redcap-version-url]/DataEntry/record_status_dashboard.php?pid=[project-id]&num_per_page=ALL

A record's Record Home Page

...and if I want the link to be included in an Alert from the project to my research staff:

  • [redcap-version-url]/DataEntry/record_home.php?pid=[project-id]&arm=[arm-number]&id=[record-name]

Prepopulate responses (e.g. fill in [site] variable with '2' in a survey)

...and if I want to direct the participant to another survey within the project while carrying through data in [name] into [name_2], add this to the survey termination redirect:

  • [survey-url:instrument name:custom text]&name_2=name

Provide a survey link to a participant within an invitation that allows them to continuously add instances of a repeating instrument at any time:

  • [survey-url:instrument name:custom text][new-instance]

Jan 31, 2025 Conditionally Hide the Submit Button on Surveys

The Survey Settings page can be used to show or hide the buttons (e.g. Submit, Next Page, etc) at the bottom of surveys. There is no way to directly conditionally hide the Submit button, but this can be implemented with a few steps.

  1. Create a multiple choice field

    1. Indicate the field is required

    2. Create the message you want to display if the condition(s) to show the Submit button are not met

    3. Leave the 'Choices' empty

  2. In this field's branching logic, add the logic that you want to use to hide the Submit button

  3. Add section headers before and after this multiple choice field

  4. In Survey Settings, set the Pagination to 'Multiple Pages'

(optional) Use the Multi-Language Management module to customize the REDCap notification if the respondent tries to proceed without going back.

Jan 16, 2025 Automatically Add 'date imported' to imported records

Data entry dates are recorded with each field's metadata (not available for exporting) and (exportable) date fields can be created with the 'TODAY' or 'NOW' action tags. For data imports, the date can be included in the import file or a field can be formulated in your project to calculate this date automatically.

  1. Create the [date_imported] field

  2. Validate the field to be Y-M-D HMS

  3. Add the 'CALCDATE' action tag to the field

    1. include the formula if([date_imported]="" and max(1,[record_id]) > 0,"now", [date_imported]), 0, "s")

Now REDCap will add the date the data is imported without needing to include this field in import file!

Dec 6, 2024 Field Validation

When using Text Box fields to collect data (e.g. dates, numbers, email addresses, phone numbers) adding validation (see image) or an ontology service is the best practice to help ensure quality data by standardizing the format in which users or participants are entering data. The provided list is not exhaustive as other field validation types are available and we have the ability to request additional (standard or custom) validation types be added by the REDCap Field Validation Committee.
Useful examples may include:

  • specimen IDs that include site, participant ID, visit #, volume, etc., all within the specimen ID (e.g. PHX0217v04ml01)

  • other phone number or postal code formats not already listed

  • other data and/or time formats not already listed

The additional images show the currently available (enabled and disabled) field validation types. Use validation to help with data management and message if you're interested in developing or adding new types!

image-20241206-205145.png
image-20241206-205225.png

Nov 18, 2024 Survey Flow

There are numerous options for choosing how to implement a Survey Flow or a survey sequence that links surveys (i.e. instruments) together. The best way is very dependent on your data collection approach, project design, and the resulting dataset structure that is desired (it's always good to speak with a statistician to get input on how to structure a dataset so you can implement this in your design).
The most straightforward approach is to activate the Survey Auto-continue found in each survey's settings. If some skipping of fields is needed, consider branching logic, or for skipping entire instruments, implement the Form Display Logic with the Survey Auto-continue (image 1). The Survey Queue module is also an option, but note this was not its intended purpose and therefore you might encounter unexpected results (image 2). Here are some images to demonstrate these approaches! These have also been posted to our ASU FAQ.

image-20241118-212609.png

image-20241118-212637.png

Nov 14, 2024 Randomize a Survey Display Order

By default, the order surveys are displayed is dependent on the order of the instruments in the Online Designer that are activated as surveys (and designated on the event, if applicable). However, using innate REDCap functions, you can randomize the order that certain surveys are presented. The following steps will randomize the display order of 3 surveys. Adjust the steps accordingly for more surveys to be randomized.

  1. Create 3 variables ([s1], [s2], [s3]) on a separate instrument (e.g. Order) that will specify which survey is to be displayed. The data values and data labels identify the survey (i.e. use the name of the actual instrument if possible).

    1. survey1, Survey 1
      survey2, Survey 2
      survey3, Survey 3

    2. Add the READONLY action tag

  2. Create 3 variables ([s1_url], [s2_url], [s3_url]) on the same instrument that will indicate the survey URL of each survey

    1. Add the CALCTEXT action tag with the following function concat( if([s1] = 'survey1', [survey-url:Survey 1], ''), if([s1] = 'survey2', [survey-url:Survey 2], ''), if([s1] = 'survey3', [survey-url:Survey 3], ''), ))

  3. Create a variable on each survey (e.g. [next_survey_2], [next_survey_3]) to calculate the URL of the next survey (i.e. you only need two of these, since the first is displayed using step 2).

    1. Add the CALCTEXT action tag with the following function. The 'done' survey URL should can point to an exit survey page or to another survey in the project that you want the person to continue to
      concat(if[s1] = 'survey1, [s2_url], ''), if([s2] = 'survey1', [s3_url], ''), if([s3] = 'survey1', [survey-url:done], '')))

    2. Add the HIDDEN-SURVEY action tag

  4. Within each survey's settings, add the 'next survey' variable name to the 'Redirect to a URL' option (e.g. [next_survey_2] should be added to the Survey 2 redirect)

  5. Set up the ASI with logic for each survey to reference which was chosen to be displayed first (e.g. for Survey 1, add [s1] = 'survey1' to the ASI logic; for Survey 2, add [s2] = 'survey2' to the ASI logic, and so on)

Oct 18, 2024 Sending Automated Surveys on the 1st of each month

The various methods of survey distribution allow users to specify an exact date to send a survey to participant(s) and the ASI allows for the automation of this to apply it to all participants. Since a month is not a standard unit of time, there is no innate option to send on the 1st of the month. This can be designed and implemented in your project using the CALCTEXT action tag and some functions.

  1. Create a date fields for each month the survey will need to be sent (for organizational purposes I recommend keeping these in a separate instrument)

    1. The first field should be the starting date - i.e. the date the person is enrolled

    2. Subsequent fields will be date-validated fields that will display the 'next first of the month' dates

  2. For each 'first of the month' field, add the CALCTEXT action tag with a series of IF functions that contain 'month',  'year', and 'concat_ws' functions to build the date that's inserted into the field. Each field should reference the previous 'first of the month' field

  • 1st 'first of the month' field [date_month_1]

    • determine if starting date has a value if([starting_date]<> ""

    • determine if the starting date is in December if(month([starting_date])+1 > 12

    • if it is, then the month will be "1", the day will be "1", and the year will be incremented by 1 concat_ws("-","1","1",year([starting_date])+1)

    • if it's not, then increment the month by 1, the day will be "1", and the year will be the same concat_ws("-",(month([starting_date]) + 1, -12,"1", year([starting_date])))

    • Build the function @CALCTEXT(if([starting_date]<> "", if(month([starting_date])+1 > 12, concat_ws("-","1","1",year([starting_date])+1), concat_ws("-",(month([starting_date]) + 1, -12,"1", year([starting_date]))),""),)

  • 2nd 'first of the month' field [date_month_2]

    • Same function, just referencing [date_month_1] instead of [starting_date]

    • @CALCTEXT(if([date_month_1]<> "", if(month([date_month_1])+1 > 12, concat_ws("-","1","1",year([date_month_1])+1), concat_ws("-",(month([date_month_1]) + 1, -12,"1", year([date_month_1]))),""),)

  • 3rd 'first of the month' field [date_month_3]

    • Same function, just referencing [date_month_2]

4th 'first of the month' field [date_month_4]

  • Same function, just refencing [date_month_3]

...and so on.

Oct 4, 2024 Sending Surveys at random times within a defined time window

Step 3/4 of defining conditions for ASIs allow you to send it using four criteria. To define different conditions, some creativity with existing functions can be implemented. To send a survey invitation at a random time within a defined time window, follow these steps:

  1. Create a date field (e.g. [date_send]) that will indicate the date to send the ASI.

  2. Create a calculated field to choose a random number (e.g. [random_1])

    1. In the logic, add this JSON command if([random_1]=' ', Math.random(), [random_1])

  3. Create a calculated field to determine your time window (e.g. [random_hour]).

    1. Add this REDCap command rounddown([random_1] * (::max value:: - ::min value:: + 1) + ::min value::, 0)

    2. You can pipe in max and min values from other fields to provide different records with custom time windows or simply replace ::max:: and ::min:: with integers representing the hour of the day.

  4. Create a text field to create the send time (e.g [send_datetime])

    1. Add this REDCap action tag command to the field annotation @CALCDATE([date_send],[random_hour],"h")

  5. In the ASI for that instrument, choose to send the invitation 0 days, 0 hours, and 0 minutes after [send_datetime]

Sep 20, 2024 Active Tasks Using MyCap

The MyCap app offers the ability to implement Active Tasks, such as Range of Motion, Gait and Balance, Stroop, Sustained Phonation, and Tone Audiometry; that collect data using the participant's phone and sync to the integrated REDCap project. ResearchKit and Mobile Toolbox are currently offered. Please reach out if other Active Task programs are available that you'd like to see integrated into MyCap!

Sep 10, 2024 Citing REDCap

When publishing manuscripts and/or data that utilized REDCap to collect or manage data, it's appropriate to cite its use. Tips on how to cite REDCap are provided when exporting data via the user interface (see image). REDCap is being used in ~7,500 institutions across 159 countries and currently has over 41,000 citations, which fuels its continued development and improvement. We will share some of these citations describing REDCap use cases going forward.
Please cite so :

image-20241113-194230.png

Aug 23, 2024 Survey Start, Stop, Duration Times and Date

REDCap innately documents the survey timestamp as a date-time field, but this is only available in the export file. Knowing the start time, completion time, and completion date is useful within a REDCap report and can be used to detect fraudulent responses (e.g. bots, persons clicking through questions without reading). Smart Variables (see picture) that can be added as fields to an instrument that automatically collect information when the instrument is completed as a survey. Here is a list:

  • [survey-time-started:instrument] --> The date and time the survey was started (i.e. opened)

  • [survey-date-started:instrument] --> The date (only) the survey was started (i.e. opened)

  • [survey-time-completed:instrument] --> The date and time the survey was completed

  • [survey-date-completed:instrument] --> The date (only) the survey was completed

  • [survey-duration:instrument:units] --> The amount of time elapsed since survey was started to current or completion time

  • [survey-duration-completed:instrument:units] --> The total time it took to complete the survey (if the survey isn't 'complete' then the value will be blank)

Please note that Smart Variables use hyphens to fill an NBSP and reference information other than data fields. Data fields are refenced using piping, which use underscores (if needed) to fill the NBSP

Aug 9, 2024 New Features, Improvements, and Changes

VUMC has put together a publicly facing change log that can be used to view and search for the features, improvements, and changes that come with each update released. Please note the live filter at the top to filter the system (Enterprise REDCap = Standard; HIPAA REDCap = LTS). The version each system is operating on can be found at the bottom of nearly all web pages or in the web browser URL within a project page.

Jul 12, 2024 Troubleshooting

We've put together a good step-by-step of how to diagnose an issue or obstacle in your REDCap project Support

  1. Check the REDCap Help & FAQ section, found at the top of the My Projects page.

  1. Search the help_redcap channel for previous posts on similar topics

  2. Check the Confluence site for possible solutions, such as our own FAQ

  3. If there are no previous posts discussing similar topics that are helpful, create a new post with the system name (Enterprise or HIPAA), project ID and the following:

  4. What is your end-goal with the function or action?

  5. What are you currently doing (what module, function, action tag, etc. are you using) to accomplish the goal?

  6. What is the outcome of what you’re doing and how is it different from the end-goal?

May 17, 2024 Scoring Surveys/Forms

When developing scoring equations for instruments, either surveys or forms, or transferring a scoring algorithm from its original source into REDCap, here are some tips to consider:

  1. Check to see if the instrument is available in the REDCap Shared Library. Many of these instruments have scoring algorithms included

    1. If you have a validated instrument you'd like to share, either for ease of use or to gain visibility, consider submitting it here.

  2. Break it down into pieces, starting at the smallest level of aggregation then build up, for example:

    1. The PSQI items/fields/variables assess sleep and are aggregated into 7 domains, which then contribute to a Total Score. Score the 'Duration' domain first by creating a calculated field based on the response to 'How many hours of actual sleep did you get at night?'. Then score the 'Disturbance' domain by creating a calculated field based on the responses to the 'How often have you had trouble sleeping' questions. After all domains have been scored, create a calculated field for the Total Score. Finally, create a field that returns the interpretation, if needed. Please follow up if you would like more details.

    2. The PHQ-9, for screening, diagnosing, monitoring, and measuring depression severity, contains several steps that include multiple item responses. Some items are considered precursors to others and might be used differently depending on the purpose of the assessment (i.e. are you using it for diagnosis or to monitor severity). Start with a calculation field that scores the first two questions. Then develop a score for items 1-9. Finally, develop the total score based on the results of the previous steps.

  3. Utilize Action Tags when appropriate. For example:

    1. The PSQI results interpretation includes the option for the respondent to have 'good sleep quality' or 'poor sleep quality'. A text field that includes the CALCTEXT action tag which evaluates logic (e.g. if([psqi_total] <= 5)) and returns text (e.g. 'GOOD SLEEP') will provide a clear scoring result

    2. It's usually not desirable to display scored survey results to participants. Consider the HIDDEN-SURVEY action tag so the scoring fields remain on the instrument, but are not shown if the instrument is displayed as a survey.

    3. If a checkbox field is utilized, utilize the NONEOFTHEABOVE action tag to ensure data quality in responses

  4. Be aware of how your item/field/variable responses are coded. This includes considering items that might need reverse coded. For example:

    1. Checkbox fields are dummy coded. If [q1] is a checkbox field with 4 options to select, a selection of option 1 will result in a variable named [q1___1], option 2 will result in a variable named [q1___2], and so on. Therefore, a calculated field [total] with the equation sum([q1],[q2],[q3]) will not return accurate results. A calculated field for each option response will likely need to be created (e.g. for a calculated field [q1_score], the equation sum([q1___1],[q1___2],{q1___3]) will return a sum of the selected choices.

    2. Minimize your calculation complexity with how your data values are assigned. If you plan to sum multiple variables that result in a total score, assigning data values, such as 0, Never | 1, Rarely | 2, Sometimes | 3, Often | 4, Always instead of 1, Never | 2, Rarely | 3, Sometimes | 4, Often | 5, Always will reduce the complexity of the fields you need to develop to score the instrument.

Apr 19, 2024 User Accounts vs User Rights

User accounts

  • Unique profiles comprised of a username, password, contact information (emails, phone numbers), preferences for how dates and times appear in REDCap, and notification preferences for within-system messages. You can view your profile at the top-right corner of the My Projects page (e.g. Enterprise system Profile page)

  • Enterprise system accounts: this system is single-sign on, meaning you can log into the system through this page https://redcap.rc.asu.edu/redcap/ using your ASURite and password. User account status (e.g. active, suspended) is dependent on the status of the ASURite in the ASU profile system

  • HIPAA system accounts: this system requires users be added manually. If you need access, please view this page to request an account and view the access requirements https://rto.asu.edu/research-data-management/redcap/ . User account status is dependent on the expiration date (refer to next bullet)

  • User account policies, such as expiration dates, for each system can be found here Policies and Guidelines

  • Note: beginning in mid-May, all account management will be routed to Research Technology Support. More details to come soon!

User rights

  • define the level of access users have within the system, to particular projects and capabilities within those projects

  • the User Rights module allows for granting users accounts access to the project and for managing the privileges of those users

  • functions the same across both REDCap systems

  • if a user account is not able to be added to the project via the User Rights module, then they have yet to log in to the system

Mar 22, 2024 What happened?? Investigating Project and Data Changes

Have you ever encountered a situation where you're unsure "what's happened" in the project after noticing something isn't working anymore or functionality seems to have changed? There are a few options available to investigate any changes to your project or data.

  1. Logging Module: this module is available in the left-hand Applications menu (if allowed in the user's User Rights) and lists all activity in the project. Event activity includes survey responses, page views, data exports, and more. Helpfully, there are robust filtering options since this list can get very, very, long (i.e. hundreds of thousands of rows or more, depending on the number of participants and the change history). Be advised when choosing long periods of time that the page may take awhile to load.

  2. Project Revision History: this provides a history of changes made primarily to the data fields (e.g. data dictionary items) as well as project status changes. It's a good practice to take a snapshot of your data dictionary prior to and after making changes.

  3. Field Data History: next to the data entry field is a small 'H' bubble icon. Click, and you'll see the entry history for the field, including the username that entered the data. This is only accessible from the 'form' view of the instrument, but still captures any changes made by survey respondents.

image-20240809-175006.png

image-20240809-175049.png
image-20240809-175104.png
image-20240809-175113.png

Jan 30, 2024 e-Consenting

The Code of Federal Regulations set forth criteria under which electronic records, electronic signatures, and handwritten signatures executed to electronic records to be trustworthy, reliable, and generally equivalent to paper records and handwritten signatures executed on paper. The following information can be used as a template, while still requiring the research team to implement the procedure to fully comply.

  1. Create a 'Consent' instrument

  2. Consent document field

    1. Descriptive Text field, attach the file, and display it as an Inline image

    2. Use a variable indicative of the approved version (e.g. consent_2024_01_30 for a Consent approved on January 30th, 2024)

  3. First Name field - indicate required

  4. Last Name field  - indicate required

  5. The meaning associated with the ‘signature’ field (e.g. a Yes/No question asking the participant if they consent to the procedures stated in the approved document) - indicate required

  6. Date field

    1. Employ the READONLY and TODAY action tags

  7. Enable the instrument as a survey

  8. Under ‘Survey Customizations’, choose ‘Yes’ to allow participants to download a PDF of their responses at end of survey

  9. Enable the e-Consent Framework in the Survey Settings

    1. Uncheck the ‘Allow e-Consent responses to be edited by users?’ checkbox

    2. Choose ‘first_name’ for Signature field #1

    3. Choose ‘last_name’ for Signature field #2

If additional information is required to complete the process, such as including a witness signature, please search the channel or create a new post for support.

Dec 15, 2023 Survey Termination Options

Actions on how to proceed once a single survey has been completed include

  1. Auto-continuing to the next survey listed in the Online Designer (forms will be skipped)

  2. Redirecting to a URL - this can include non-REDCap webpages or survey links within any REDCap project, including a Smart Variable link accessible within the project

  3. Viewing a Survey Completion Text page - this page is completely customizable and can include piping or Smart Variables

image-20240809-175621.png

Dec 1, 2023 Bots and fraudulent responses in screening surveys

Humans:

  • eligible individuals with no malicious intent (e.g. curious, interested in research)

  • eligible individuals seeking additional compensation

  • ineligible individuals trying to gain eligibility to profit from compensation

Solutions to prevent 2nd and 3rd bullet point activity while not limiting those falling into 1st bullet point:

  1. disclose consequences of submitting fraudulent data, such as denial of compensation

  2. highlight that all responses are screened by study staff and include disclaimers that investigators can contact directly to confirm eligibility

  3. be deliberate with recruitment and distribution

  4. use smart incentives

Bots: scripts or programs that are written to fill in the fields of a survey with fake values and submit the survey repeatedly with the goal of receiving compensation
Solutions to prevent non-human responses:

  1. use ReCAPTCHA to determine if the respondent is human

  2. include honeypot questions (e.g. open text entry field to capture a response to a basic math equation) and potentially include the response in subsequent item branching logic

  3. add survey start and stop times, calculate time to completion, and use this to identify human responses

  4. add a dummy field with '@HIDDEN-SURVEY' action tag - a human won't be able to respond, but a bot will find the field and respond to it

image-20240809-175701.png

Nov 3, 2023 Public Survey URL

The public survey link is the simplest and fasted way to collect responses for your survey. You can email the link to participants and responses will be collected anonymously. Since this method uses a single survey link for all participants, it allows for the possibility of participants taking the survey multiple times, but does not restrict who can open the survey.
To create/access the public survey URL:

  1. Surveys must be enabled in the project (image 1)

  2. The first survey in the Online Designer must be enabled as a survey (image 2)

  3. Navigate to the Survey Distribution Tools from the left-hand Data Collection menu (image 3)

Upon clicking the public survey URL link, REDCap will generate unique record IDs for your project corresponding to each participant's responses.
This feature is useful for:

  1. Recruiting, as a link to a 'Screening' or 'Eligibility' form

  2. E-consenting, if screening or eligibility are conducted in a different arm or different project

  3. Cross-sectional survey data collection when results should be anonymous

  4. ...respond to this thread to add your own use cases!

Bonus tips

  1. each arm within a single project can have its own public survey URL as long as the first instrument is assigned to the first event of each arm

  2. renaming the URL : this can be done within the Survey Distribution Tools, but it's preferred to use ASU Short Links for consistency with materials and customizability should you need to change to where the short link is directed

  3. make sure to use the reCAPTCHA to avoid bots from completing your survey(s)

image-20240809-175756.png
image-20240809-175807.png
image-20240809-175814.png

Oct 20, 2023 External Tools

External Modules are individual packages of software that can be downloaded and installed by a REDCap administrator. Modules can extend REDCap's current functionality and can also provide customizations and enhancements for REDCap's existing behavior and appearance. A list of available modules can be found here https://redcap.vanderbilt.edu/consortium/modules/index.php. If you are interested in adding a module to your project, please post to this channel. If you are interested in developing a module to submit to the repository for easy download, please message me privately.
Application Programming Interface (API) - The REDCap API is an interface that allows external applications to connect to REDCap remotely, and is used for programmatically retrieving or modifying data or settings within REDCap, such as performing automated data imports/exports from a specified REDCap project. API's are specific to each project and access is unique to each project user. Project's API are accessible in the left-hand Applications menu (image 1).
Mobile App - The REDCap Mobile App is an app that can be installed on an Android or iOS tablet or mobile device so that data may then be collected in an offline fashion on that device. At some point later on, it may then be synced back to this project on the REDCap server. The app is most useful when data collection will be performed where there is no Internet service (e.g., no WiFi or cellular service) or where there is unreliable Internet service. The project's Mobile App management is accessible in the left-hand Applications menu (image 2).
MyCap App - MyCap is a participant-facing mobile application (on iOS and Android) used for data collection and the automated administration of active tasks (activities performed by participants using mobile device sensors under semi-controlled conditions). All data collected in the MyCap app are automatically sent back to the REDCap server as soon as internet connection is available (i.e., it can also be used for offline participant data collection). MyCap is a no-code solution for research teams conducting longitudinally-designed projects or projects with frequent participant contact. MyCap also facilitates participant engagement and retention by providing quick access to project staff and two-way communications (e.g., messaging and announcements) within the app. To access your project's MyCap, enable it on the Project Setup page.

image-20240809-175854.png image-20240809-175903.png image-20240809-175907.png

Oct 6, 2023 Survey Themes (including ASU color scheme)

In the Online Designer, ensure the instrument is enabled as a survey. If it is, the Survey Settings will be accessible. If it is not, click the Enable button and you will be navigated to the Survey Settings module for that instrument (image 2). Under the Survey Design Options section, there is an option to change the theme (or colors) of your survey (image 3). The dropdown contains some default styles (image 4). Clicking customize will allow you to pick and choose the color scheme of your surveys by clicking on the color palette or by enter the color's HTML hex code (image 5). The ASU color palette can be found here https://brandguide.asu.edu/brand-elements/design/color . Once complete, save the custom theme (image 6).
ASU Maroon = #8c1d40

  • ASU Gold = #ffc627

  • Rich Black = #000000

  • White = #ffffff

  • ASU Gray = #747474 - associated ASU grayscale steps can be found in the brandguide by scrolling down.

image-20240809-180058.png image-20240809-180113.png image-20240809-180117.png image-20240809-180121.png image-20240809-180126.png image-20240809-180132.png

Mar 14, 2023 User Rights Expiration Dates

You could find this utility in Applications > User Rights > Click on the Username you want to modify > Edit user privileges > Basic Privileges > Expiration Date (it is located on the top left section).You can set up the time so that after the time you enter the specific user would no longer have access to the project. This is the tip for managing the users to your projects.

image-20240809-181032.png

Feb 8, 2023 Field Embedding

This week we are going to talk about “Field Embedding” which is a very easy and convenience way to change the look of your survey or form by repositioning field elements. Here are the steps for how to embed a field: