Summary
REDCap's Project Setup - Additional Customization page contains several customization options including setting custom record labels, PDF customization settings, protected email mode and more. This article will walk through each section in detail.
Project Setup - Additional Customizations
Getting to the Additional Customizations Page
- Navigate to the Project Setup Page
- Scroll down to the Enable optional modules and customizations section
- Click the Additional customizations button
Additional Customizations Settings
Set a custom record label
This feature appends other data and/or static text to any record name as the record is displayed on your data collection instruments. Simply provide the text or field variable wrapped in square brackets in the text box and after the data is collected for those variables, the record name will reflect the data and/or static text. In this example, static text "Participant ID: " and the field participant_id (wrapped in square brackets) are used to set a custom record label.
Designate a Secondary Unique Field
This feature allows for a secondary text field to serve as a unique constraint whose value cannot be duplicated or shred by any other record in the project. If a value is duplicated or shared by another record, the user will be asked to enter a different value. This feature runs in real time, even with data import process. In this example, the participant_id field is selected from the dropdown field.
Order the records by another field
This feature allows the user to change how records are sorted when displayed in the drop-down lists on your data collection instruments. The default is by record name, but the order can be sorted based on any other field within the project. In this example, the field last_name has been selected which will sort the records by last name instead of record ID.
Enable the field comment Log or Data Resolution Workflow (Data Queries)?
(Automatically enabled) Users may enable either the Field Comment Log (default option) or the Data Resolution Workflow. The Field Comment log allows users to leave comments on any given field on the data entry form by clicking the balloon icon. The Data Resolution Workflow allows users to open a workflow for documenting the process of resolving issues with data in the project.
PDF Customizations
For the downloadable PDFs of data entry forms and surveys, this feature allows customizations such as setting custom header text, displaying/hiding the REDCap logo and website URL, displaying/hiding the Secondary Unique Field (if enabled), and displaying/hiding the Record ID.
Missing Data Codes: Set up your missing data codes for this project
Fields that have a missing/blank value may be marked with a custom “Missing Data Code” to note why the value is blank. These missing codes can aid in data analysis to by specifying why the field lacks a value. There are default codes, but users can also create customized Missing Data Codes.
Enable the Data History pop-up for all data collection instruments
(Automatically enabled) This feature will display an icon next to every field on data collection instruments. When this icon is clicked, the history of all data entered in that field will appear chronologically, who changed the value, and when the value was changed.
Enable the file Version History for “File Upload” fields
(Automatically enabled) This feature keeps a file version history for File Upload fields on forms and surveys. Instead of deleting previous versions, it allows for new files to be uploaded while keeping previous versions for viewing/downloading purposes.
Display the Today/Now button for all date and time fields on the forms/surveys
(Automatically enabled) This feature displays a “Today” button next to date fields and a “Now” button next to time, datetime, and datetime_seconds fields. By clicking either of those buttons, the field will automatically fill with the current date/time. An alternative option to this button is to use the @TODAY or @NOW action tags to automatically pre-fill those fields.
Prevent branching logic from hiding fields that have values
If this setting is not enabled (default), then whenever a field is to be hidden by branching logic on a data entry form, it will always ask the user if they wish to hide the field and erase its value. For survey pages, it will automatically erase the value of the field being hidden without displaying the confirmation prompt. If this setting is enabled, the branching logic behavior will change so that fields with values will not cause the 'Erase the Value of the Field?' confirmation prompt to ask the user if they wish to keep the value or hide the field, and instead fields with values will not be hidden by branching logic and will stay visible.
Require a ‘reason’ when making changes to existing records
If this feature is enabled, users are required to enter a reason in a text box when making any data changes to an already existing record on a data collection instrument. This prompt is triggered when clicking the “Save” button on the page.
Protected Email Mode
When enabled, this feature prevents identifying data (PII/PHI) from being sent in outgoing emails for alerts, survey invitations, and survey confirmation emails. If enabled, REDCap will not send the full email text to the recipient but will instead send an email containing a link that leads them to a secure REDCap page to view the initial email. This setting can be customized for either all alerts and invitations or for those alerts and invitations that contain identifier information.
Data Entry Trigger
This advance feature provides a way for REDCap to trigger a call to a URL, in which it will send a HTTP POST request to the specified URL whenever any record or survey response has been created or modified on any data collection instrument or survey (Note: It is not triggered by data imports). Its main purpose is to alert other remote systems in real time in which other triggers or actions may need to occur by the other URL, such as making a call to the REDCap API.
