REDCap

REDCap Language File Creator/Updater
This page can be used for creating new language files for the text used within REDCap or for cleaning up and updating existing language files used in previous versions of REDCap. These REDCap language files are text files saved with an INI file extension and have strings of text (paragraphs, phrases, or words) mapped to specific variables in the language file. To translate REDCap's English text into a new language, follow Option #1 below. To update the text of an existing language file with any new text from the current version of REDCap, use Option #2 to streamline the process. Before utilizing either option, you may want to check if someone has already performed a translation you might want by navigating to the REDCap Community website REDCap Community Language Library.
1.) Obtain the English language file to begin a new translation

If you wish to begin creating a new language file for REDCap, you will need to take the English text and translate it all into the desired language. To do so, follow these steps:
1.) Click the button immediately below, copy the text from the text box, and paste it into a text editor (e.g., WordPad, Notepad++)
2.) Translate all the English text
3.) On your computer, save the file as an INI file with the name of the language (e.g., Chinese.ini)
4.) Place the file in your web server folder named "/var/www/html/redcap/languages"
5.) Share your translation with the REDCap Consortium by uploading it as an attachment on the REDCap Community website REDCap Community Language Library
(currently contains 13836 language variables)
; Translate all English in this file, save the file (e.g., Chinese.ini), then place the file in "/var/www/html/redcap/languages"
	
period = "."
colon = ":"
questionmark = "?"
exclamationpoint = "!"
comma = ","
leftparen = "("
rightparen = ")"
global_01 = "ERROR"
global_02 = "NOTE"
global_03 = "NOTICE"
global_04 = "Double Data Entry module"
global_05 = "ACCESS DENIED!"
global_06 = "(optional)"
global_07 = "Control Center"
global_08 = "Arm"
global_09 = "Data Dictionary"
global_10 = "Event Name"
global_11 = "Username"
global_12 = "Form Name"
global_13 = "Time"
global_14 = "page"
global_15 = "at"
global_16 = "Define My Events"
global_17 = "User"
global_18 = "Date"
global_19 = "Delete"
global_20 = "Description"
global_21 = "[This message was automatically generated by REDCap]"
global_22 = "Data Access Groups"
global_23 = "Disabled"
global_24 = "Instructions"
global_25 = "Scheduling"
global_27 = "Edit"
global_28 = "Designate Instruments for My Events"
global_29 = "Development"
global_30 = "Production"
global_32 = "Password"
global_33 = "Email"
global_34 = "E-signature"
global_35 = "Data Collection Instrument"
global_36 = "Data Collection Instruments"
global_37 = "From:"
global_38 = "To:"
global_39 = "Saved"
global_40 = "Field Label"
global_41 = "First Name"
global_42 = "Last Name"
global_43 = "and"
global_44 = "Variable Name"
global_45 = "Events"
global_46 = "OR"
global_47 = "or"
global_48 = "WARNING"
global_49 = "Record"
global_51 = "on"
global_53 = "Cancel"
global_54 = "Form"
global_55 = "Datetime"
global_58 = "Tell me more"
global_59 = "survey"
global_60 = "Single Survey"
global_61 = "Data Entry Forms"
global_63 = "Project types"
global_64 = "Woops! An error occurred. Please try again."
global_65 = "Project"
global_66 = "email failed to send"
global_67 = "Controls"
global_68 = "user has been notified via email"
global_69 = "email notification FAILED"
global_71 = "Export"
global_72 = "Import"
global_73 = "Rights"
global_74 = "Both"
global_75 = "None"
global_76 = "Last Used"
global_77 = "Return to previous page"
global_78 = "Data Access Group"
global_79 = "SUCCESS!"
global_80 = "VIDEO:"
global_83 = "Thank you!"
global_84 = "View"
global_85 = "PDF"
global_86 = "Multiple Surveys and/or Data Entry Forms"
global_87 = "AND"
global_88 = "Access REDCap"
global_89 = "Instrument"
global_90 = "Survey Link"
global_91 = "Record Status Dashboard"
global_92 = "Incomplete"
global_93 = "Unverified"
global_94 = "Completed Survey Response"
global_95 = "Partial Survey Response"
global_96 = "Day"
global_97 = "Weekday"
global_98 = "Weekend Day"
global_99 = "Sunday"
global_100 = "Monday"
global_101 = "Tuesday"
global_102 = "Wednesday"
global_103 = "Thursday"
global_104 = "Friday"
global_105 = "Saturday"
global_106 = "Deleted"
global_107 = "in"
global_108 = "for event"
global_109 = "Errors:"
global_110 = "Instruments"
global_111 = "surveys"
global_112 = "form"
global_113 = "forms"
global_114 = "DAGs"
global_115 = "Role"
global_116 = "Data Dictionary Codebook"
global_117 = "STEP"
global_118 = "REDCap Mobile App"
global_121 = "[Your browser does not support the HTML5 Audio element.]"
global_122 = "Audio file (play in embedded player on page)"
global_123 = "OTHERWISE"
global_124 = "Administrators:"
global_125 = "Update"
global_127 = "Section Header: "
global_128 = "Cancel request"
global_130 = "EVENTS"
global_131 = "FIELDS"
global_132 = "Action Tags"
global_133 = "Repeat Instance"
global_134 = "More"
global_135 = "Show data collection instruments"
global_136 = "Hide data collection instruments"
global_137 = "Copy to clipboard"
global_138 = "Repeat Instrument"
global_139 = "Repeat Instance"
global_141 = "Event"
global_142 = "External Modules"
global_143 = "Checked"
global_144 = "Unchecked"
global_146 = "Smart Variables"
global_147 = "REDCap Auto Logout Warning"
global_148 = "Log In"
global_149 = "Continue on this page"
global_150 = "You will be automatically logged out of REDCap in <b>2 MINUTES</b> due to inactivity. Click the button below to prevent auto logout."
global_151 = "You will be automatically logged out of REDCap in <b>30 SECONDS</b> due to inactivity. Click the button below to prevent auto logout."
global_152 = "<b>Due to inactivity, your REDCap session has expired.</b> Click the button below to log in again."
global_153 = "Record Status Dashboards"
global_154 = "Alerts & Notifications"
global_155 = "Clinical Data Mart"
global_156 = "Miscellaneous"
global_159 = "Analysis/Cleanup"
global_161 = "Remember previous search"
global_162 = "Comma (,)"
global_163 = "Tab"
global_164 = "Semicolon (;)"
global_167 = "Regular View Mode"
global_168 = "Fullscreen Mode"
global_169 = "Update & Close Editor"
global_170 = "Logic Editor"
global_171 = "Error in syntax"
global_172 = "(The determination of validity may not be 100% accurate in all contexts.)"
global_173 = "Enter new logic here"
global_174 = "NOTICE: Please be advised that it is not possible to pipe the choice label of a multiple choice field into any of the special functions listed below. In other words, you cannot use the ':label' option, such as [my_field:label], to output the text label into a function. <b>The special functions only utilize the value of a field, never its label.</b>"
global_176 = "It is possible to embed a Descriptive field inside another field, even though descriptive fields do not have an actual input element for saving data. Embedding a descriptive field would merely relocate the field's label to the new location where it is embedded. This is typically only useful if the descriptive field has branching logic, in which you could use branching logic to make the descriptive field's text appear conditionally in a specific place on the page."
global_177 = "Data can be piped into the locations listed above *FROM* any type of field in REDCap. If you are piping the answer *FROM* a multiple choice field (e.g., radio, drop-down), by default it will display the option label (not the coded data value) into the location where the field is piped, but for all other field types, it will pipe the literal data value. See below how to append ':value' to the variable name inside brackets to pipe the value (instead of the label) for multiple choice fields. Also see below how to pipe data from checkbox fields, which is slightly different than with other field types."
global_179 = "<b><u>File Upload fields:</u></b> File Upload fields have unique piping options. If you are piping *FROM* a File Upload field or Signature field, the field's numerical value will be piped by default, but you can pipe the original filename of the uploaded file by appending the '<b>:label</b>' option, such as <code>[my_field:label]</code>. Additionally, if you use the '<b>:inline</b>' option for a File Upload field, such as <code>[my_field:inline]</code>, in which the uploaded file is a PDF file or image file (JPG, JPEG, GIF, PNG, TIF, BMP), the file will be displayed in an inline manner so that it is viewable on the page. (The @INLINE action tag does not need to be used on a field in order to utilize the :inline piping option. So while the @INLINE action tag can be used to display the PDF/image on the field's instrument, the :inline piping option allows you to display the PDF/image in places outside the field's instrument.) Note: Inline images are not able to be displayed inside a downloaded PDF of a survey/instrument that contains data. Additionally, <b>the :inline option also operates inside emails, so you can pipe a field via :inline inside the email body, thus allowing you to display inline images inside survey invitations or Alerts & Notifications</b>. If the file being piped via :inline inside an email is not an image file type, it will still attach the file to the email but will display the file's filename in the email text as an alternative to displaying it as an inline image. File Upload fields can also utilize the '<b>:link</b>' piping option, such as <code>[my_field:link]</code>, where <b>the file's filename will be displayed as a clickable hyperlink for downloading the file</b>, which works on webpages and also inside the body of email text (i.e., survey invitations or Alerts & Notifications)."
global_180 = "The mean/average value of a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_181 = "Aggregate Functions, Charts, and Tables"
global_182 = "Project Dashboards"
global_183 = "The minimum value of a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_184 = "The maximum value of a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_185 = "The median value of a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_186 = "The sum of all values for a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_187 = "The count of all values for a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_188 = "The standard deviation of a field across all records in the project (including all events and/or repeating instances in all records) Multiple fields may be used and must be comma-separated.."
global_189 = "The count of unique values (i.e., a count that does not consider duplicate values) of a field across all records in the project (including all events and/or repeating instances in all records). Multiple fields may be used and must be comma-separated."
global_190 = "[A chart displayed on the page]"
global_191 = "[A table displayed on the page]"
global_192 = "Displays a pie chart for a single multiple choice field."
global_193 = "Displays a donut chart for a single multiple choice field.Note: A donut chart is essentially the same as a pie chart but with the center removed."
global_194 = "Displays a bar chart for a single multiple choice field. It can optionally perform color grouping if a second field (multiple choice only) is provided. The fields must be comma-separated."
global_195 = "Displays a scatter plot of one number/date/datetime field for the x-axis and a second field (number field only) for the y-axis. (If a second field is not provided, a random value will be assigned for the y-axis.) It can optionally perform color grouping if a third field (multiple choice only) is provided. All fields must be comma-separated."
global_196 = "Displays a line chart of one number/date/datetime field for the x-axis and a second field (number field only) for the y-axis. It can optionally perform color grouping if a third field (multiple choice only) is provided. All fields must be comma-separated. Note: A line chart is essentially the same as a scatter plot except with dots connected with a line."
global_197 = "Displays a table of descriptive statistics for one or more fields (comma-separated) in which each field is represented as a row in the table. There is no limit to the number of fields that can be used. By default, all columns will be displayed and are as follows: Count, Missing, Unique, Min, Max, Mean, Median, StDev, Sum. To display only a subset of the columns, you may provide any of the following designations (comma-separated) that represent a specific column in the table: count, missing, unique, min, max, mean, median, stdev, sum."
global_198 = "Optional Parameters for Aggregate Functions, Charts, and Tables"
global_199 = "<u>Unique Report Name</u> - For Aggregate Functions, Charts, and Tables, filter the data being used by appending a Unique Report Name. Next to each report on the 'My Reports & Exports' page is its unique report name, which has 'R-' following by alphanumeric characters. By default, all Aggregate Functions, Charts, and Tables will use the values of all records in the project, but if a unique report name is appended to any of them, only data from that specific report will be used. Using a report as a surrogate to filter data is a very useful technique of performing complex filtering logic for Aggregate Functions, Charts, and Tables."
global_200 = "\"<u>record-name</u>\" - For Aggregate Functions, Charts, and Tables, filter the data being used to the *current record* by using the literal value 'record-name'. Note: This parameter will only work in a context where a single record is being viewed/accessed, such as on a survey page, data entry form, etc. This parameter can be used with any of the other parameters except unique report names."
global_201 = "\"<u>event-name</u>\" - For Aggregate Functions, Charts, and Tables, filter the data being used to the *current event* (longitudinal projects only) by using the literal value 'event-name'. Note: This parameter will only work in a context where a single record/event is being viewed/accessed, such as on a survey page, data entry form, etc. This parameter can be used with any of the other parameters except unique report names."
global_202 = "<u>Unique Event Names</u> - For Aggregate Functions, Charts, and Tables, filter the data being used to specific events (longitudinal projects only) by providing an event's unique event name (found on the Define My Events page). You may use one or more unique event names (comma-separated). Note: This parameter can be used with any of the other parameters except unique report names."
global_203 = "\"<u>user-dag-name</u>\" - For Aggregate Functions, Charts, and Tables, filter the data being used to the records assigned to the *current user's Data Access Group* by using the literal value 'user-dag-name'. Note: This parameter will only work in a context where an authenticated user belongs to a project and has been assigned to a DAG in the project (this excludes survey pages and public project dashboards). This parameter can be used with any of the other parameters except unique report names."
global_204 = "<u>Unique DAG Names</u> - For Aggregate Functions, Charts, and Tables, filter the data being used to the records assigned to specific Data Access Groups by providing a DAG's unique group name (found on the Data Access Groups page). You may use one or more unique DAG names (comma-separated). Note: This parameter can be used with any of the other parameters except unique report names."
global_205 = "\"<u>bar-vertical</u>\" - Display a bar chart with the bars going vertically instead of horizontally (the default) by using the literal value 'bar-vertical'. Note: This parameter can be used with any of the other parameters."
global_206 = "\"<u>bar-stacked</u>\" - Only for bar charts using two fields, display the bar chart with the bars stacked on top of one another for each choice. Whereas the default view is that the bars of each field are displayed side by side to show the color grouping. To enable this, use the literal value 'bar-stacked'. Note: This parameter can be used with any of the other parameters."
global_207 = "ERROR: Public dashboards are not enabled on this installation of REDCap."
global_208 = "Use the text box below to compose your logic, calculation, action tags, etc. If you need more space, click the Fullscreen Mode button to enlarge the text box. When you are finished, click the 'Update' button to minimize the Editor window."
global_209 = "\"<u>no-export-link</u>\" - Only used for [stats-table], hides the \"Export table (CSV)\" link that by default is displayed immediately below the Smart Table."
global_210 = "CALCULATION ERRORS EXIST!"
global_211 = "There is a syntactical error in the calculation for the field"
global_212 = "on this page. None of the calculations on this data entry form will function correctly until this error has been corrected."
global_213 = "If you are not sure what this means, please contact your project administrator."
global_214 = "There is a syntactical error in one or more of the calculations on this page. It cannot be determined which fields contain the error, so please check the equation for every calculated field on this page. None of the calculations on this data entry form will function correctly until this error has been corrected."
global_215 = "SURVEY ERRORS EXIST: CANNOT CONTINUE!"
global_216 = "BRANCHING LOGIC ERRORS EXIST!"
global_217 = "This survey will not function correctly until these errors have been fixed. Sorry for any inconvenience."
global_218 = "ERASE THE VALUE OF THE FIELD"
global_219 = "None of the Branching Logic on this data entry form will function correctly until this error has been corrected."
global_220 = "Please contact your survey administrator and let them know that Branching Logic errors exist on this survey for the field"
global_221 = "There is a syntactical error in the Branching Logic for the field"
global_222 = "on this page."
global_223 = "The current field for which you just entered data requires that the field named"
global_224 = "be hidden from view. However, that field already has a value, so its value might need to be reset back to a blank value."
global_225 = "Click OK to HIDE this field and ERASE its current value. Click CANCEL if you DO NOT wish to hide this field or erase its current value."
global_226 = "Please contact your survey administrator and let them know that Branching Logic errors exist on this survey."
global_227 = "There is a syntactical error in the Branching Logic of one or more fields on this page. It cannot be determined which fields contain the error, so please check the Branching Logic for every field on this page."
global_228 = "Alternate Twilio phone number for Voice Call verification option only (optional)"
global_229 = "(If provided, Voice Call verification will be made from this number, whereas SMS verification will come from the first phone number above. If left blank, the first phone number above will be used for both SMS and Voice Call verification.)"
global_230 = "(also known as Smart Functions, Smart Charts, and Smart Tables)"
global_232 = "<b><u>AM/PM time formats:</u></b> When piping a time or datetime field, you may convert their time component from military time to 12-hour AM/PM time format by appending the '<b>:ampm</b>' option, such as <code>[visit_time:ampm]</code>, in which it will display the 12-hour time appended with lowercase 'am' or 'pm'. Note: The seconds component of datetime fields (if applicable) will be removed. Also, any leading zeros will be removed. For example, the value '23:59' would be converted to '11:59pm', and '07:13' will display as '7:13am'."
global_233 = "ERROR: This is not a valid URL."
global_234 = "REDCap secure message verification"
global_235 = "Protected Email Mode"
global_236 = "<b>ERROR:</b> The 'openssl' PHP extension is not loaded but is required by REDCap on this page. Please notify the REDCap administrator to have the 'openssl' PHP extension installed on the REDCap web server, after which they must reboot the server."
global_237 = "Confidential"
global_238 = "Data Collection Instruments:"
global_239 = "Username:"
global_240 = "Password:"
global_241 = "Passcode:"
global_242 = "Event Label"
global_243 = "Event ID"
global_244 = "(auto-generated, unchangeable)"
global_245 = "Search by variable name or by keyword in field label"
global_246 = "Field finder:"
global_247 = "Scroll to top of page"
global_248 = "Try searching instead:"
global_249 = "The full list of choices cannot be displayed because there are too many."
global_250 = "Try typing a value to search all options"
global_251 = "View record"
global_252 = "Password or PIN:"
global_253 = "Click one of the buttons below to choose how you wish to log in to REDCap."
global_254 = "OpenID Connect"
global_256 = "OpenID Connect & Table-based"
global_257 = "Log in using"
global_258 = "Local REDCap Login"
global_259 = "Number of records in project:"
global_260 = "MyCap Mobile App"
global_264 = "(optional) OpenID Connect button text on REDCap login page"
global_265 = "Provide the button text for the OpenID Connect button on the REDCap login page when users choose between 'Local REDCap Login' and 'OpenID Connect'.  If left empty, the button text will default to 'OpenID Connect'. Note: This setting is only used for OpenID Connect & Table-based authentication."
global_266 = "TIP: Your logic and calculations may contain <b>comments</b>, which are not evaluated but only serve as annotations to help document or explain what the calc/logic is doing. Comments must be on their own lines and start with // (double forward slash) or # (hash sign), optionally preceded by whitespace characters (spaces, tabs). You may not append a comment to a line that is part of the logic or calc expression."
global_267 = "View example"
global_268 = "Text can be put here to explain what the logic/calculation does and why."
global_269 = "This comment can explain what the next line does."
global_270 = "Return '0' if the condition is False."
global_271 = "The code block below illustrates how one might use # and // as comments in your logic and calculations."
global_272 = "Upload a file"
global_273 = "Drop a file or click here<br>to upload an attachment"
global_274 = "NOTE: Any files uploaded here using the rich text editor will be given a <b>publicly accessible download link</b> that will be placed into the text, in which anyone in possession of that link (including people not logged into REDCap) will be able to download the file at any time. Files containing <b>confidential or sensitive information (e.g., PHI or PII) should *not* be uploaded here</b>. Additionally, all files uploaded here can be later accessed and/or deleted in the File Repository's \"Miscellaneous File Attachments\" folder, whose contents does not count against the total amount of file storage used in the project. "
global_275 = "Auto-fill form"
global_276 = "Auto-fill survey"
global_277 = "instrument"
global_278 = "Custom Text"
global_279 = "fields"
global_280 = "parameters"
global_281 = "units"
global_282 = "field"
global_283 = "columns"
global_284 = "x-axis-field"
global_285 = "y-axis-field"
global_286 = "grouping-field"
global_287 = "Invalid value!"
global_288 = "IMPORTANT: When referencing a unique report name in Smart Charts, Smart Tables, or Smart Functions, no other filtering parameters can be used (e.g., DAGs, events) with the report filter. If you wish to additionally filter by DAGs and/or events, it is recommended that you added such filtering to the report itself by editing the report."
global_289 = "Note: When using multiple fields, data will be naturally grouped from the same event and/or repeating instance."
global_290 = "View media"
global_291 = "Enter a record name"
global_292 = "(optional) Microsoft Entra ID button text on REDCap login page"
global_293 = "Microsoft Entra ID"
global_294 = "Provide the button text for the Microsoft Entra ID button on the REDCap login page when users choose between 'Local REDCap Login' and 'Microsoft Entra ID'.    If left empty, the button text will default to 'Microsoft Entra ID'. Note: This setting is only used for Microsoft Entra ID & Table-based authentication."
global_295 = "Field is an Identifier"
global_296 = "Take a {0:Icon} {1:LinkStart}tour{2:LinkEnd} of this page."
global_297 = "This will start a guided tour of this page."
global_298 = "Enabled by default for new projects"
global_299 = "Disabled by default for new projects"
global_300 = "Project-level setting:"
global_301 = "PDF (all instruments)"
global_302 = "<b><u>Blank values:</u></b> If a field value or Smart Variable value is blank/null (i.e., does not exist), then by default the blank value will be piped  as six underscore characters (literally ______) as a placeholder to visually indicate that no value exists.  However, if this behavior is not desired, you may append <code>:hideunderscore</code> to the variable name inside the square brackets,  and this will cause value to be piped as-is, that is, as a blank/null/invisible value.  Note: The <code>:hideunderscore</code> notation may be appended to both field variables and Smart Variables."
global_303 = "<b><u>Piping a field label:</u></b> If you wish to pipe the field label of a given field (instead of its data value), you may append <code>:field-label</code> to the variable name inside the square brackets."
global_304 = "Cookie policy"
global_305 = "<h4>REDCap Cookie Usage Policy</h4><br>    <b>1. What Are Cookies?</b><br><br>Cookies are small text files that are placed on your device (computer, tablet, or mobile) when you visit a website. They are widely used to make websites work more efficiently, as well as to provide information to the owners of the site.<br><br>    <b>2. Types of Cookies Used</b><br><br>REDCap uses two primary types of cookies: Necessary Cookies and Functional Cookies. Details about each type and their purposes are provided below.<br><br>    <b>3. Necessary Cookies</b><br><br>Necessary cookies are essential for the proper functioning of this web application (REDCap). These cookies ensure basic functionalities and security features of the website.    Without these cookies, certain features and services may not be available. Example of necessary cookies: Session cookies that keep you logged in while you navigate through different pages.<br><br>    <b>4. Functional Cookies</b><br><br>Functional cookies enable the web application to provide enhanced functionality and personalization. If you do not allow these cookies,    some or all of these services may not function properly. Examples of functional cookies: 1) Cookies that remember your preferences, such as language, and 2) Cookies that provide enhanced features,    such as remembering your desired custom size of text on survey pages.<br><br>    <b>5. Managing Cookies</b><br><br>You have the right to accept or reject cookies. Most web browsers automatically accept cookies, but you can usually modify your browser settings to delete or decline cookies if you prefer.    Please note that if you choose to decline cookies, you will not be able to experience all features of this web application (REDCap)."
upgrade_001 = "PREPARATION"
upgrade_002 = "REDCap has determined that this will be a quick upgrade, so taking the system offline  is not necessary. REDCap has special safeguards to ensure that no data is lost during this upgrade process  for users that are already logged in or for respondents currently taking a survey. Please continue to Step 2."
upgrade_003 = "The upgrade to REDCap"
upgrade_004 = "has completed successfully.  You will now be redirected to the Configuration Check page."
upgrade_005 = "Upgrade Complete!"
upgrade_006 = "Upgrade Module"
upgrade_007 = "Go to Configuration Check"
upgrade_008 = "Unable to upgrade!"
upgrade_009 = "You are currently on version"
upgrade_010 = "You must be on REDCap version 3.0.0 or higher in order to upgrade to"
upgrade_011 = "Upgrade to 3.0.0 first, then you may upgrade to"
upgrade_012 = "Already upgraded!"
upgrade_013 = "It appears that you have already upgraded to version"
upgrade_014 = "There is nothing to do here."
upgrade_015 = "Return to REDCap"
upgrade_016 = "It has been determined that <b>REDCap does *NOT* need to be taken offline</b> when performing this upgrade."
upgrade_017 = "It appears that your upgrade to REDCap"
upgrade_018 = "was successful! As the final step of the upgrade process, please navigate to the Configuration Check page to make sure there is nothing else that needs to be done."
upgrade_019 = "Approximately"
upgrade_020 = "minutes before upgrading, go into the Control Center's"
upgrade_021 = "General Configuration page"
upgrade_022 = "and set the System Status as \"System Offline\", which will take all REDCap projects offline and allow users  to save any data before exiting. (When you are done upgrading, REDCap will remind you to bring the system back online."
upgrade_024 = "It is recommended that you first take your REDCap system offline."
upgrade_025 = "Language check:"
upgrade_026 = "It appears that you are using one or more non-English languages in your installation of REDCap.  The translation of REDCap's English text into other languages is now supported solely through the REDCap Consortium  community. For more information on this, please see the"
upgrade_027 = "REDCap Community Language Library"
upgrade_028 = "REDCap stores the language files in  the following location on your server:"
upgrade_029 = "A diagnostic of your language files is given below, showing if the file  can be located, and if it needs to be updated because of any new language variables added in REDCap version"
upgrade_030 = "If any files are out of date, you can update them using the"
upgrade_031 = "page"
upgrade_032 = "OR you may check the REDCap Community website's Language Center for any updated versions of these languages.  <b>NOTE:</b> It will not harm REDCap if a language file is out of date; it will merely show English text in place of  the missing translated text. If you wish, you may translate any new language variables in your language files  before performing this upgrade by following the instructions on the Language File Creator/Updater page and then returning  to this page afterward."
upgrade_033 = "ERROR!"
upgrade_034 = "Could not find the \"languages\" folder at the expected path:"
upgrade_035 = "is up to date."
upgrade_036 = "is out of date."
upgrade_037 = "Recommendation:"
upgrade_038 = "new language variables need to be added to this file and then translated."
upgrade_039 = "Could not find the following language file:"
upgrade_040 = "Without this file, any projects set with"
upgrade_041 = "as the language will instead render in English."
upgrade_042 = "PERFORMING THE UPGRADE:"
upgrade_043 = "Now you must"
upgrade_044 = "follow"
upgrade_045 = "Option A, B, or C"
upgrade_046 = "Option A or B"
upgrade_047 = "below"
upgrade_048 = "in which you will execute the SQL upgrade script on your MySQL database server"
upgrade_049 = "Once you have executed the upgrade script, move on to Step 3 below. Please note that depending on your server's processing speed and also what REDCap version you are upgrading to and from, the upgrade script could take several seconds, several minutes, or several hours to fully execute. Most small upgrades often take just a few seconds. NOTE: If you anticipate that the upgrade script will take a long time to run, such as if you are skipping over many versions at once, then it is best to use Option B because it can avoid timeouts that sometimes occur when executing lots of queries in certain MySQL clients, especially web-based clients (e.g., phpMyAdmin)."
upgrade_050 = "Generating the SQL upgrade script..."
upgrade_051 = "OPTION A: Automatic upgrade (recommended)"
upgrade_052 = "You have the convenient option of upgrading simply by clicking the button below, which will automatically begin to execute the SQL upgrade script to complete the upgrade process."
upgrade_053 = "Upgrade"
upgrade_054 = "OPTION"
upgrade_055 = "Copy the text from the box below and execute it in MySQL"
upgrade_056 = "Download the SQL upgrade script as a file"
upgrade_057 = "Download upgrade script"
upgrade_058 = "Download the SQL upgrade script file by clicking the button above, and place the file somewhere on your MySQL database server (via FTP or however you access the database server's file system). Make sure the filename remains as"
upgrade_059 = "Open a terminal window (command line interface) to your MySQL database server, and on that server navigate to the directory where you placed the upgrade script file (using \"cd\" or other similar command)."
upgrade_060 = "Via command line, execute the line below (replacing USERNAME with the username of the MySQL user you are connecting with)."
upgrade_061 = "AFTER THE UPGRADE - TEST YOUR CONFIGURATION:"
upgrade_062 = "Once you have successfully executed the SQL upgrade script above, you must now navigate to the Configuration Check page to ensure that all necessary REDCap components are correctly in place."
upgrade_063 = "Configuration Check page"
upgrade_064 = "Go to Configuration Check page"
upgrade_065 = "Your REDCap system is currently offline. It is recommended that the system be offline for {0} minutes before continuing to Step 2."
check_001 = "SUCCESSFUL!"
check_002 = "FAILED!"
check_003 = "Communicated successfully with the REDCap Consortium server. You WILL be able to use the \"automatic reporting\" method to report your site stats, as well as use the REDCap Shared Library."
check_004 = "Could NOT communicate with the REDCap Consortium server. You will NOT be able to report your institutional REDCap statistics using the \"automatic reporting\" method, but you may try the \"manual reporting\" method instead (see the General Configuration page in the Control Center for this setting)."
check_005 = "Communicated successfully with the REDCap survey end-point"
check_007 = "Communicated successfully with the Twilio API server (https://api.twilio.com)."
check_008 = "Could NOT communicate with the Twilio API server (https://api.twilio.com)."
check_009 = "Communicated successfully with the Mosio SMS API server"
check_010 = "Could NOT communicate with the Mosio SMS server"
check_011 = "Communicated successfully with the SendGrid API server (https://api.sendgrid.com/v3)."
check_012 = "Could NOT communicate with the SendGrid API server (https://api.sendgrid.com/v3)."
check_013 = "Communicated successfully with the PROMIS API server"
check_014 = "Could NOT communicate with the PROMIS API server"
check_015 = "Communicated successfully with the BioPortal API server"
check_016 = "Could NOT communicate with the BioPortal API server"
check_017 = "Communicated successfully with the Bit.ly API server (http://api.bit.ly)."
check_018 = "Could NOT communicate with the Bit.ly API server (http://api.bit.ly)."
check_019 = "Communicated successfully with the IS.GD API server (https://is.gd)."
check_020 = "Could NOT communicate with the IS.GD API server (https://is.gd)."
check_021 = "Communicated successfully with the REDCAP.LINK API server (https://redcap.link)."
check_022 = "Could NOT communicate with the REDCAP.LINK API server (https://redcap.link)."
check_023 = "Communicated successfully with the Google reCAPTCHA server (https://www.google.com/recaptcha/api/siteverify)."
check_024 = "Could NOT communicate with the Google reCAPTCHA server (https://www.google.com/recaptcha/api/siteverify)."
check_025 = "Communicated successfully with the Field Bank NLM server (https://cde.nlm.nih.gov)."
check_026 = "Could NOT communicate with the Field Bank NLM server (https://cde.nlm.nih.gov)."
check_027 = "Because some components are added to REDCap at a specific version and are never modified thereafter, they are not included in every version of REDCap in the upgrade zip file. Since such components are only added once, it does not make sense to include them in every upgrade file, so instead they are thus only included in the version that first utilizes them. This triggers the error you see here, which prompts you to go download them now. This is not ideal, but it is the best approach for now. Sorry for any inconvenience."
check_028 = "This page will test your current REDCap configuration to determine if any errors exist that might prevent it from functioning properly."
check_029 = "Basic tests"
check_030 = "TEST 1: Establish basic REDCap file structure"
check_031 = "Search for necessary files and folders that should be located in the main REDCap folder (i.e."
check_032 = "MISSING!"
check_033 = "ERROR!"
check_034 = "This file (ControlCenter/check.php) should be located in a folder named with the following format: /redcap/redcap_v?.?.?/. Find this folder and place the ControlCenter/check.php file in it, and run this test again."
check_035 = "The sub-folder named \"webdav\" is missing from the \"webtools2\" folder."
check_036 = "Find this folder and place it in the \"webtools2\" folder. Then run this test again."
check_037 = "This folder needs to be in the folder named"
check_038 = "Must be obtained from install/upgrade zip file from version"
check_039 = "REDCap download page"
check_040 = "One or more of the files/folders listed above could not be found in the folder named"
check_041 = "Please locate those files/folders in the Install/Upgrade zip file that you downloaded from the REDCap Community website, then add them to the correct location on your server and run this test again."
check_042 = "All necessary files and folders were found."
check_043 = "Why is this missing?"
check_044 = "The table \"redcap_config\" in the MySQL database named"
check_045 = "The database table named \"redcap_config\" could NOT be accessed."
check_046 = "This error may have resulted if there was an error during the install/upgrade process. Please make sure that the \"redcap_config\" table is located in the MySQL project"
check_047 = "If it is not, you will need to re-install/re-upgrade REDCap, and then run this test again."
check_048 = "TEST 3: Check REDCap database table structure"
check_049 = "Your REDCap database structure is correct!"
check_050 = "TEST 4: Check if PHP cURL extension is installed"
check_051 = "The cURL extension is installed."
check_052 = "Your web server does NOT have the PHP library cURL installed."
check_053 = "cURL is required to utilize many major features in REDCap. To add cURL to REDCap, you will need to download cURL/libcurl, and then install and configure it with PHP on your web server. You will find"
check_054 = "http://us.php.net/manual/en/book.curl.php"
check_055 = "instructions for cURL/libcurl installation here"
check_056 = "TEST 5: Checking communication with REDCap Consortium server"
check_057 = "(used to report weekly site stats and connect to Shared Library)"
check_058 = "Communicating with server... please wait"
check_059 = "TEST 6: Check if REDCap Cron Job is running"
check_060 = "REDCap Cron Job is running properly."
check_061 = "Secondary tests"
check_062 = "Using SSL"
check_063 = "<b>NOT using SSL - CRITICAL:</b> It is HIGHLY recommended that you use SSL (i.e. https) on your web server when hosting REDCap. Otherwise, data security could be compromised. If your server does not already have an SSL certificate, you will need to obtain one."
check_064 = "NOT using PHP"
check_065 = "or higher - CRITICAL:"
check_066 = "It is required that you upgrade your web server to a more recent supported version of PHP, you are currently running PHP"
check_067 = "Using PHP"
check_068 = "or higher"
check_069 = "NOT using MySQL/MariaDB"
check_070 = "It is required that you upgrade your database server to a more recent supported version of MySQL or MariaDB (you are currently running"
check_071 = "Some important features of REDCap will not function correctly unless you are on the minimum version or higher."
check_072 = "<b>DOM extension in PHP is not installed - CRITICAL:</b> It is recommended that you <a target='_blank' href='http://php.net/manual/en/book.dom.php'>install the DOM extension</a> in PHP on your web server. Some important features in REDCap will not be available without it being installed."
check_073 = "<b>XMLReader extension in PHP is not installed - CRITICAL:</b> It is recommended that you <a target='_blank' href='http://php.net/manual/en/book.xmlreader.php'>install the XMLReader extension</a> in PHP on your web server. Some important features in REDCap will not be available without it being installed."
check_074 = "GD library (version 2 or higher) is installed"
check_075 = "<b>GD Library (version 2 or higher) is not installed - CRITICAL:</b> It is recommended that you <a target='_blank' href='http://php.net/manual/en/image.installation.php'>install the GD2 Library</a> in PHP on your web server. Some features in REDCap will not be available without GD2 installed, such as the ability for users to generate QR codes for survey links."
check_076 = "<b>Imagick extension cannot render PDFs</b>. While the Imagick PHP extension is installed and enabled, rendering of inline PDFs is not possible, because <b>Ghostscript</b> is not available. See <a target='_blank' href='https://www.ghostscript.com/'>https://www.ghostscript.com</a>. The detailed error returned was:"
check_077 = "<b>PHP Imagick extension is installed</b>"
check_078 = "<b>Imagick extension in PHP is not installed - RECOMMENDED:</b> It is recommended that you <a target='_blank' href='https://www.php.net/manual/en/book.imagick.php'>install the Imagick extension</a> in PHP on your web server. Some features in REDCap will not be available without it being installed. For example, any inline PDF attachments on Descriptive Text fields will *not* be able to be displayed inside a PDF export of a given form or survey unless the Imagick extension in PHP has been installed."
check_079 = "<b>Imagick's security policy is too restrictive:</b> While the Imagick extension is enabled in PHP, its security policy is too restrictive. In order to render PDF files as images, it must be allowed to read PDF files. Add or change the respective security policy:"
check_080 = "See <a target='_blank' href='https://stackoverflow.com/questions/52998331/imagemagick-security-policy-pdf-blocking-conversion'>this StackOverflow page</a> for more information. A webserver restart will be necessary to apply the changes."
check_081 = "<b>Imagick extension not working:</b> The Imagick PHP extension, while enabled, gives an error that REDCap doesn't know how to handle. Until this is fixed, rendering of inline PDFs in descriptive fields will not work. The error message returned was:"
check_082 = "<b>PHP Fileinfo extension is installed</b>"
check_083 = "<b>Your web server does NOT have the PHP Fileinfo extension installed.</b>Fileinfo extension for PHP is NOT necessary to run REDCap normally, but it is highly recommended. Fileinfo is used for some optional functionality in REDCap, such as for file import operations when importing whole REDCap projects as XML files (i.e., CDISC ODM file imports). It is recommended that you download the Fileinfo extension, and then install and configure it with PHP on your web server. You will find <a href='http://php.net/manual/en/book.fileinfo.php' target='_blank' style='text-decoration:underline;'>instructions for Fileinfo installation here</a>."
check_084 = "<b>OpenSSL extension not installed - CRITICAL:</b> It is recommended that you install the <a target='_blank' href='http://php.net/manual/en/book.openssl.php'>PHP OpenSSL extension</a> on your web server since certain application functions depend upon it. After installing the extension, reboot your web server, and then reload this page."
check_085 = "<b>ZipArchive is not installed - CRITICAL:</b> It is recommended that you install the <a target='_blank' href='http://php.net/manual/en/book.zip.php'>PHP Zip extension</a>. Some features in REDCap will not be available without this extension installed, such as the feature in the Data Export Tool that allows users to download a ZIP file of all their uploaded files for records in a project."
check_086 = "<b>PHP extension \"mbstring\" not installed - CRITICAL:</b> This extension is required because it is used by many different processes and features in REDCap. To enable it, you must install the <a href='http://php.net/manual/en/mbstring.setup.php' target='_blank'>PHP extension \"mbstring\"</a> on your web server. Once installed, reboot your web server."
check_087 = "This email was sent when the user"
check_088 = "opened the Configuration Check page for"
check_089 = "REDCap version"
check_090 = "REDCap Email Test"
check_091 = "REDCap Configuration Check:"
check_092 = "REDCap is able to send emails"
check_093 = "REDCap is not able to send emails - CRITICAL:</b>It appears that your SMTP configuration (email-sending functionality) is either not set up or not configured correctly on the web server. It is HIGHLY recommended that you configure your email/SMTP server correctly in your web server's PHP.INI configuration file or else emails will not be able to be sent out from REDCap. REDCap requires email-sending capabilities for many vital application functions. For more details on configuring email-sending capabilities on your web server, visit <a href='http://php.net/manual/en/mail.configuration.php' target='_blank'>PHP's mail configuration page.</a>"
check_094 = "<b>Missing administrator email address:</b> It appears that the system-level email address for the REDCap administrator has not been set on the General Configuration page in the Control Center. Some features might not work correctly if a valid email address is not added."
check_095 = "<b>Error inside a REDCap configuration file:</b> It appears that in one or more of REDCap's configuration files (e.g., database.php, webtools2/ldap/ldap_config.php, webtools2/webdav/webdav_connection.php) there is some extra \"whitespace\", such as trailing spaces or empty lines that occur either before the opening PHP '<?php' tag or after the closing PHP '?>' tag. Please make sure all preceding spaces, trailing spaces, and empty lines are removed from before or after the PHP tags in those files. Certain things in REDCap will not work correctly until this is fixed."
check_096 = "<b>InnoDB engine is NOT enabled in MySQL - CRITICAL:</b> It appears that your MySQL database server does not have the InnoDB table engine enabled, which is required for REDCap to run properly. To enable it, open your my.cnf (or my.ini) configuration file for MySQL and remove all instances of \"--innodb=OFF\" and \"--skip-innodb\". Then restart MySQL, and then reload this page. If that does not work, then see the official MySQL documentation for how to enable InnoDB for your specific version of MySQL."
check_097 = "<b>\"max_allowed_packet\" setting in MySQL should be increased - RECOMMENDED:</b> It appears that your MySQL database server's \"max_allowed_packet\" setting is lower than recommended for optimal REDCap usage. It is suggested that you increase that setting to <code>128M</code> (i.e., 128 MB) or higher, <b>preferably to the maximum value of <code>1G</code> (i.e., 1 GB)</b>. Setting it to the max value of 1G will not have any negative side effects. To change this setting, open your my.cnf (or my.ini) configuration file for MySQL and modify the line for max_allowed_packet to set it as the following: <code>max_allowed_packet=1G</code>. Then restart MySQL, and then reload this page."
check_098 = "<b>'max_input_vars' could be larger - RECOMMENDED:</b> It is highly recommended that you change your value for 'max_input_vars' in your PHP.INI configuration file to a value of"
check_099 = "or higher. If not increased, then REDCap might not be able to successfully save data when entered on a very long survey or data entry form. You can modify this setting in your server's PHP.INI configuration file. If 'max_input_vars' is not found in your PHP.INI file, you should add it as <i style='color:#800000;'>max_input_vars ="
check_100 = "</i>. Once done, restart your web server for the changes to take effect."
check_101 = "<b>'upload_max_filesize' and 'post_max_size' are too small:</b> It is HIGHLY recommended that you change your value for both 'upload_max_filesize' and 'post_max_size' in PHP to a higher value, preferably greater than 10MB (e.g., 32M). You can modify this in your server's PHP.INI configuration file, then restart your web server. At such small values, your users will likely have issues uploading files if you do not increase these."
check_102 = "<b>'upload_max_filesize' and 'post_max_size' could be larger - RECOMMENDED:</b> It is recommended that you change your value for both 'upload_max_filesize' and 'post_max_size' in PHP to a higher value, preferably greater than 10MB (e.g., 32M). You can modify this in your server's PHP.INI configuration file, then restart your web server. At such small values, your users could potentially have issues uploading files if you do not increase these."
check_104 = "<b>SUGGESTION: Missing some hook functions in your Hook Functions file</b><br>It appears that your hook functions file"
check_105 = "does not contain one or more REDCap hook functions that can be utilized in your current version of REDCap.<b>NOTE:</b> These hook functions are only necessary if you are using custom REDCap Hooks on this REDCap installation (this does NOT include hooks used in External Modules, which are not affected by this). It is recommended that these hook functions be added to that file on your web server. The following hooks are missing from the hook functions file:"
check_106 = "To obtain the default code for these hook functions, it is recommended that you download the latest Install Zip file of REDCap (Standard Release) from the REDCap Community website and open the file in the zip file named \"redcap/hook_functions.php\" in a text editor. Find the functions in that PHP file, and copy and paste the entire function(s) into your Hook Functions file (located at"
check_107 = "on your web server). Then save the file. Once they have been added, this warning message should no longer display."
check_108 = "<b>'innodb_buffer_pool_size' could be larger - RECOMMENDED:</b> It is recommended that you change your value for 'innodb_buffer_pool_size' in MySQL to a higher value. It is generally recommended that it be set to 10% larger than the size of your database, which is currently"
check_109 = "MB in size. So ideally <b>'innodb_buffer_pool_size' should be set to at least"
check_110 = "MB</b> if possible (it is currently"
check_111 = "MB). Also, it is recommended that the size of 'innodb_buffer_pool_size' <b>not exceed 80% of your total RAM (memory) that is allocated to MySQL</b> on your database server. You can modify this in your MY.CNF configuration file (or MY.INI for Windows), then restart MySQL. If you do not increase this value, you may begin to see performance issues in MySQL."
check_112 = "<b>Database configuration issue:</b> There is a configuration issue with the MySQL setting named \"optimizer_switch\" that needs to be fixed. If not fixed, if may cause some things not to function correctly in REDCap or might cause the database server to crash unexpectedly. To fix this, add the line<br><code><b>optimizer_switch=rowid_filter=OFF</b></code><br> under the [mysqld] section in your MY.CNF (or MY.INI) configuration file for MySQL/MariaDB. If there is already a line in the file that begins with \"optimizer_switch\", then add this new line directly below it. After that new line has been added, save that configuration file, and then restart the MySQL/MariaDB service. Then reload this page to ensure the fix has successfully taken effect."
check_113 = "<b>Database configuration change - RECOMMENDED:</b> It is recommended that the MySQL setting named \"innodb_file_format\" be modified. To prevent issues with REDCap upgrades in the future, it is recommended that the database server have innodb_file_format=Barracuda. To fix this, add the line<br><code><b>innodb_file_format=Barracuda</b></code><br> under the [mysqld] section in your MY.CNF (or MY.INI) configuration file for MySQL/MariaDB. If there is already a line in the file that begins with \"innodb_file_format\", then modify that setting so that its value is now <b>Barracuda</b>. Additionally, make sure that the MySQL setting \"innodb_file_per_table\" is set to ON. If not, add/update the line as follows:<br><code><b>innodb_file_per_table=ON</b></code><br> Then save that configuration file, and restart the MySQL/MariaDB service. Reload this page to ensure the fix has successfully taken effect."
check_114 = "<b>Some database tables need to be modified - RECOMMENDED:</b> It is recommended that "
check_115 = "REDCap database tables be modified in order to conform to newer standards for InnoDB database tables. To prevent issues with REDCap upgrades in the future, it is recommended that all REDCap database tables have ROW_FORMAT=DYNAMIC. Some of your tables do not have Dynamic row format and thus should be fixed using the queries provided below. NOTE: If you have a fairly large or old REDCap installation, <b>each query may take minutes or hours to run</b>. You may do these individually if you wish and/or do them slowly in batches over a period of weeks until all have been fixed. Each time you refresh this page, it will build a new dynamic list below of the tables that have not yet been fixed. <u>This is not a requirement but is highly recommended.</u><b>IMPORTANT NOTE: Make sure you perform a full database backup</b> prior to running any of the queries below. Run the SQL queries below to fix the database tables:"
check_116 = "configuration settings appear sufficient for optimal performance and stability"
check_117 = "<b>Possible issue with Windows Scheduled Task for the REDCap Cron Job - SUGGESTION:</b></span> It appears that <u>REDCap's cron job has not been running every minute</u> according to the cron job's log over the past"
check_118 = "days. This might imply that the scheduled task on your Windows server might not be configured correctly. Check the Windows Task Scheduler on your REDCap web server and make sure the scheduled task for the REDCap Cron job is set to \"<u>Run a new instance in parallel</u>\" under the Settings tab for that task. If not, then change it to that setting.<br><br> If you are certain that this is not the case, then you may ignore this suggestion; however, there might be other problems that exist if for some reason the REDCap Cron Job has not been running every minute as expected."
check_119 = "The REDCap web server's temp directory is writable<br>Location:"
check_120 = "<b>The REDCap web server's temp directory is NOT writable - CRITICAL:</b> It is HIGHLY recommended that you modify your web server's temp directory (located at"
check_121 = "so that it is writable for all server users. Some functionality within REDCap will not be functional until this directory is writable."
check_122 = "\"temp\" directory is writable<br>Location:"
check_123 = "<b>\"temp\" directory is NOT writable - CRITICAL:</b> It is HIGHLY recommended that you modify the REDCap \"temp\" folder (located at"
check_124 = "so that it is writable for all server users. Some functionality within REDCap will not be functional until this folder is writable."
check_125 = "File upload directory is writable<br>Location:"
check_126 = "<b>File upload directory is NOT writable - CRITICAL:</b> It is HIGHLY recommended that you modify the REDCap \"edocs\" folder (located at"
check_127 = "so that it is writable for all server users. Some functionality within REDCap will not be functional until this folder is writable."
check_128 = "<b>Directory that stores user-uploaded documents is exposed to the web:</b><br> It is HIGHLY recommended that you change your location where user-uploaded files are stored. Currently, they are being stored in REDCap's \"edocs\" directory, which is the default location and is completely accessible to the web. Although it is extremely unlikely that anyone could successfully retrieve a file from that location on the server via the web, it is still a potential security risk, especially if the documents contain sensitive information.<br><br> It is recommend that you go to the File Upload Settings page in the Control Center and set a new path for your user-uploaded documents (i.e. \"Enable alternate internal storage of uploaded files rather than default 'edocs' folder\"), and set it to a path on your web server that is NOT accessible from the web. Once you have changed that value, go to the 'edocs' directory and copy all existing files in that folder to the new location you just set."
check_129 = "File upload directory is writable on Amazon S3 server in bucket"
check_130 = "<b>File upload directory is NOT writable on Amazon S3 server - CRITICAL:</b> It is HIGHLY recommended that you investigate your Amazon S3 connection info on the File Upload Settings page in the Control Center. REDCap is not able to successfully store files in the Amazon S3 bucket named \"$amazon_s3_bucket\". Please make sure all the connection values are correct and also that the directory is writable. Some functionality within REDCap will not be functional until files can be written to that bucket."
check_131 = "<b>File upload directory is NOT writable on Microsoft Azure Blob Storage server - CRITICAL:</b> It is HIGHLY recommended that you investigate your Microsoft Azure Blob Storage connection info on the File Upload Settings page in the Control Center. REDCap is not able to successfully store files in the Blob Container named"
check_132 = "Please make sure all the connection values are correct and also that the directory is writable. Some functionality within REDCap will not be functional until files can be written to that bucket."
check_133 = "<b>File upload directory is NOT writable on Google Cloud Storage server - CRITICAL:</b> It is HIGHLY recommended that you investigate your Google Cloud Storage connection info on the File Upload Settings page in the Control Center. REDCap is not able to successfully store files in the Storage bucket named"
check_134 = "Please make sure all the connection values are correct and also that the directory is writable. Some functionality within REDCap will not be functional until files can be written to that bucket."
check_135 = "ERROR: Could not read the file"
check_143 = "<b>\"modules\" directory - MISSING!</b> - The REDCap \"modules\" folder (located at"
check_144 = "is missing, and must be obtained from install zip file from the latest version (or someone can just create an empty directory named \"modules\" at the location"
check_145 = "\"modules\" directory is writable<br>Location:"
check_146 = "<b>\"modules\" directory is NOT writable - CRITICAL:</b> It is HIGHLY recommended that you modify the REDCap \"modules\" folder (located at"
check_147 = "so that it is writable for all server users. The External Modules functionality in REDCap will not be functional until this folder is writable."
check_148 = "This user has CREATE table privileges, but does NOT have ALTER or DROP table privileges."
check_149 = "This user has CREATE and ALTER table privileges, but does NOT have DROP table privileges."
check_150 = "This user has CREATE and DROP table privileges, but might NOT have ALTER or REFERENCE table privileges."
check_151 = "This user has CREATE and DROP table privileges, but does NOT have ALTER table privileges."
check_152 = "<b>MySQL database user privileges should be modified - RECOMMENDED:</b> It is recommended that you modify the database privileges of your MySQL user"
check_153 = "This user must have all four privileges (CREATE, ALTER, DROP, REFERENCES) or else none of those four. If this is not fixed, REDCap may mistakenly create many database tables with names beginning with \"redcap_ztemp_\", which are created as temporary tables when testing your MySQL user's privileges. Also, if you wish to use the Easy Upgrade module, the MySQL user must have all four privileges (CREATE, ALTER, DROP, REFERENCES)."
check_154 = "<b>Remove insecure REDCap versions from web server - RECOMMENDED:</b> It is recommended that you remove all the REDCap version directories from your web server that are listed below. These versions are known to have security vulnerabilities that could possibly be exploited by malicious attackers if left on your REDCap web server."
check_155 = "<b>RECOMMENDED: Update your REDCap Database Tables to support full Unicode</b><br>REDCap installations that were initially installed using a version prior to REDCap 8.5.0 will have an older, legacy type of database encoding/charset (character set) configuration. This affects your REDCap installation, in which it is *highly* recommended that you follow the steps on the page linked below to update your database. Please note that this is NOT an urgent issue, but it is something we recommend you address sooner rather than later since your current database collation and charset (UTF8 or UTFMB3) have been deprecated in the latest versions of MySQL/MariaDB and thus will eventually be removed altogether in future versions of MySQL/MariaDB."
check_156 = "Learn about how to update the REDCap Database Tables to support full Unicode"
check_157 = "<b>Your web server does NOT have the PHP library Zlib installed.</b> Zlib is required to utilize many major features in REDCap. To add Zlib to REDCap, you will need to download Zlib, and then install and configure it with PHP on your web server. You will find <a href='https://www.php.net/manual/en/zlib.setup.php' target='_blank' style='text-decoration:underline;'>instructions for Zlib installation here</a>."
check_158 = "Internal Service Check: Checking communication with the REDCap survey end-point"
check_159 = "External Service Check: Checking communication with Twilio telephony API services"
check_160 = "External Service Check: Checking communication with Mosio SMS API services"
check_161 = "External Service Check: Checking communication with SendGrid email API services"
check_162 = "External Service Check: Checking communication with PROMIS assessment API services"
check_163 = "External Service Check: Checking communication with BioPortal biomedical ontology API services"
check_164 = "External Service Check: Checking communication with REDCAP.LINK URL shortening API services"
check_165 = "External Service Check: Checking communication with Bit.ly URL shortening API services"
check_166 = "External Service Check: Checking communication with IS.GD URL shortening API services"
check_167 = "External Service Check: Checking communication with Google reCAPTCHA API services"
check_168 = "External Service Check: Checking communication with Field Bank NLM services"
check_169 = "<b>Security improvement - SUGGESTION:</b></span>It appears that you are running REDCap over SSL/HTTPS (which you *should* if this is a production server). For better security, it is recommended that you enable the <i>session.cookie_secure</i> option in your web server's PHP.INI file. To enable \"session.cookie_secure option\", simply open your web server's PHP.INI file for editing and change the value of \"session.cookie_secure\" option to \"On\", or if it does not exist yet, add the following line in the <code>[Session]</code> section of PHP.INI:<br><code>session.cookie_secure = On</code><br>Then reboot your web server. Doing this is not required, but it is recommended since it improves the overall security of the REDCap system."
check_170 = "CONGRATULATIONS!"
check_171 = "<b>It appears that the REDCap software has been correctly installed/upgraded and configured on your system. It is ready for use.</b> You may begin using REDCap by first visiting the REDCap home page at the link below. (It may be helpful to bookmark this link.)"
check_172 = "REDCap home page:"
check_173 = "<b>Currently, REDCap is using the authentication method \"None (Public)\"</b>, which is utilized solely by a generic user named \"<b>site_admin</b>\". This authentication method is best to use if you are using a development server or if you have not yet worked out all issues with user authentication on your system. Once you have your site's authentication working properly, you may go into the Control Center to the Security & Authentication page to change the authentication method to the one you will be implementing on your system (i.e. LDAP, Table-based, RSA SecurID, LDAP/Table combination, Shibboleth).<b>If you decide to switch from \"None\" authentication to \"Table-based\"</b>, please be sure to add yourself as a new Table-based user (on the User Control tab in the Control Center) before you switch over the authentication method, otherwise you won't be able to log in."
check_174 = "<b>NOTICE: The Read Replica Database might be offline!</b> At the moment, REDCap cannot connect to the secondary read-only database. It may be offline. REDCap will still function normally, but please  be aware that the read replica might not be utilized currently on any REDCap pages to improve performance."
check_175 = "<b>NOTICE:</b> The Read Replica Database is currently lagging behind the Primary Database by"
check_176 = "seconds. This may be a temporary lag. If the Replica lags more than"
check_178 = "The Read Replica Database is currently lagging"
check_179 = "seconds behind the Primary Database, which is good enough for the Replica to be utilized for many REDCap pages that perform large read operations."
check_180 = "The Read Replica Database is performing well"
check_181 = "<b>NOTICE: The Read Replica Database lag time cannot be determined!</b> For unknown reasons, it is not possible for REDCap to detect by how much time the Read Replica Database is lagging behind the Primary Database. Please check the MySQL/MariaDB user permissions on the Read Replica to ensure it has the ability to run the SQL query <code>SHOW SLAVE STATUS</code> successfully in order to properly determine if the Read Replica can be utilized by REDCap."
check_182 = "Replica Lag (seconds):"
check_183 = "<b>The cron job's timezone setting is incorrect - CRITICAL:</b> It is HIGHLY recommended that you modify the PHP.INI file that is used by the REDCap cron job.  It appears that you have two PHP.INI files in use (one for the main web interface located at <code>{0}</code> and one for the cron job located at <code>{1}</code>).  The web interface PHP.INI has a timezone setting of <b>{2}</b> while the cron job has a timezone setting of <b>{3}</b>. If they are not the same, issues may occur when running the REDCap cron job correctly.  Please modify one of them so that they are the same."
check_184 = "<b>Database configuration issue - CRITICAL:</b> It is required that the MySQL setting named \"sql_generate_invisible_primary_key\" be disabled since it can cause false positives to appear for the  'Database structure issues exist' check in REDCap. To fix this, add the line<br><code><b>sql_generate_invisible_primary_key=OFF</b></code><br> to your MY.CNF (or MY.INI) configuration file for MySQL.  If there is already a line in the file that begins with \"sql_generate_invisible_primary_key\", then modify that setting so that its value is now <b>OFF</b>.  Then save that configuration file, and restart the MySQL service. Reload this page to ensure the fix has successfully taken effect."
check_185 = "<b>Cannot connect to the WebDAV file server - CRITICAL:</b><br>It is HIGHLY recommended that you modify your WebDAV server configuration or your WebDAV connection info in <b>{0}</b>. The current connection info is attempting to communicate with WebDAV server \"{1}\" at path \"{2}\" and it is failing. Please make sure all the connection values are correct and also that the directory is writable. Some functionality within REDCap will not be functional until this is fixed."
check_186 = "The WebDaV client reported this error ({0}):<br><code>{1}</code>"
check_187 = "<b>File upload directory is NOT writable on WebDAV server - CRITICAL:</b><br>It is HIGHLY recommended that you modify your WebDAV server configuration or your WebDAV connection info in <b>{0}</b>. The current connection info is attempting to communicate with WebDAV server \"{1}\" at path \"{2}\" and it is failing. Please make sure all the connection values are correct and also that the directory is writable. Some functionality within REDCap will not be functional until that WebDAV directory is writable."
check_188 = "<b>File upload directory is writable on WebDAV server \"{0}\" at path \"{1}\"</b>"
check_189 = "<b>Rapid Retrieval directory not writable - CRITICAL:</b> It is HIGHLY recommended that you modify the Rapid Retrieval alternate cached file storage directory (located at <b>{0}</b>) so that the directory  is writable for all server users. The Rapid Retrieval caching functionality will not be functional until this folder is writable."
check_190 = "seconds behind Primary, the Replica will likely not be used in many cases. Such a lag is often a temporary thing that should resolve later on its own when the database is not so busy."
check_191 = "'Generated Invisible Primary Keys' setting should be disabled - CRITICAL:"
check_192 = "It appears that the MySQL feature 'Generated Invisible Primary Keys' is enabled on your database server. That feature is NOT compatible with REDCap, and thus it should be disabled.  You should be able to set <code>sql_generate_invisible_primary_key</code> to <code>OFF</code> in your <b>my.cnf</b> (or <b>my.ini</b>) configuration file, or else execute the query <code>SET GLOBAL sql_generate_invisible_primary_key = OFF;</code>  directly on the MySQL database to disable this setting."
check_193 = "Could NOT communicate with the internal REDCap survey end-point ({0}). This means that REDCap somehow cannot make server-side requests to itself. This issue sometimes occurs when using a proxy or load balancer,  or else it could be caused by a specific network configuration in which an outgoing HTTP call from the REDCap web server somehow does not get fully routed back to itself when making an HTTP call to itself.  Regardless, this cannot be fixed through any configuration within REDCap, but you should contact your IT/network team to resolve this on the server/network side."
check_194 = "(Optional) If clustering or replication is implemented on your database server, in which it might be required that every database table has an auto-incremented Primary Key, you may execute the SQL in the box below to add Primary Keys to all REDCap database tables. Please keep in mind that these queries might take minutes or possibly hours to execute depending on the size of your database. Note: We do not recommend running the SQL below unless you think you truly need it."
api_docs_001 = "Introduction to the REDCap API"
api_docs_002 = "Provided here is all documentation for utilizing the REDCap API. For general information about the REDCap API or the methods supported by the REDCap API, see the list on the left-hand menu. Each API method provides a specific action that can be performed by REDCap."
api_docs_003 = "The acronym 'API' stands for 'Application Programming Interface'. An API is just a defined way for a program to accomplish a task. 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 for a specified REDCap project. Programmers can use the REDCap API to make applications, websites, apps, widgets, and other projects that interact with REDCap. Programs talk to the REDCap API over HTTP, the same protocol that your browser uses to visit and interact with web pages."
api_docs_004 = "To get started using the REDCap API, begin with the General API Info section on the left-hand menu. There is also an API Playground page in each of your REDCap projects, in which the playground will allow you to experiment with the REDCap API and see the range of its functionality without even having to write any code."
api_docs_005 = "In order to use the REDCap API for a given REDCap project, you must first be given a token that is specific to your username for that particular project. Rather than using username/passwords, the REDCap API uses tokens as a means of secure authentication, in which a token must be included in every API request. Please note that each user will have a different token for each REDCap project to which they have access. Thus, multiple tokens will be required for making API requests to multiple projects."
api_docs_006 = "To obtain an API token for a project, navigate to that project, then click the API link in the Applications sidebar. On that page you will be able to request an API token for the project from your REDCap administrator, and that page will also display your API token if one has already been assigned. If you do not see a link for the API page on your project's left-hand menu, then someone must first give you API privileges within the project (via the project's User Rights page)."
api_docs_007 = "HTTP Status Codes:"
api_docs_008 = "The REDCap API attempts to return appropriate HTTP status codes for every request. Below is a comprehensive list of all possible HTTP codes that could be returned from the API and what each code signifies."
api_docs_009 = "200 OK: "
api_docs_010 = "Success!"
api_docs_011 = "400 Bad Request: "
api_docs_012 = "The request was invalid. An accompanying message will explain why."
api_docs_013 = "401 Unauthorized: "
api_docs_014 = "API token was missing or incorrect."
api_docs_015 = "403 Forbidden: "
api_docs_016 = "You do not have permissions to use the API."
api_docs_017 = "404 Not Found: "
api_docs_018 = "The URI you requested is invalid or the resource does not exist."
api_docs_019 = "406 Not Acceptable: "
api_docs_020 = "The data being imported was formatted incorrectly."
api_docs_021 = "500 Internal Server Error: "
api_docs_022 = "The server encountered an error processing your request."
api_docs_023 = "501 Not Implemented: "
api_docs_024 = "The requested method is not implemented."
api_docs_025 = "Error Messages:"
api_docs_026 = "When the API returns error messages, it does so in the return format that you specified in your API request (and if not specified, it returns in default format). You can specify the format you want using the <b>returnFormat</b> parameter. For example, an error from an XML method might look like this:"
api_docs_027 = "detailed error message"
api_docs_028 = "Although API requests to REDCap are done using SSL (HTTPS), which means that the traffic to and from the REDCap server is encrypted, there is still more that can be done to ensure the highest level of security when using the API. This is especially important if you are moving sensitive data into or out of REDCap. One thing that is *highly* recommended is for your API script/program (i.e. the thing making the request to the REDCap API) to <b>validate the SSL certificate of the REDCap web server</b> when it makes the API request."
api_docs_029 = "Background on SSL certificates:"
api_docs_030 = "Man in the Middle Attack"
api_docs_031 = "Java verify ssl certificate"
api_docs_032 = "Thus by adding the SSL certificate check, you have completely prevented the possibility of MiM attacks and are using the most secure form of communication with the REDCap API."
api_docs_033 = "Web servers have SSL certificates so that their identity can be validated and thus trusted, after which secure, encrypted communication can take place with the server. The reason it is important to validate the server's SSL certificate is because it is possible (although extremely rare) to be the victim of a "
api_docs_034 = " even when your web traffic is secure over SSL/HTTPS. A Man in the Middle (MiM) attack can be performed by a hacker who impersonates the REDCap web server using a fake/invalid SSL certificate. In this way, it is possible for your API script to think that the hacker is really the REDCap server and thus unwittingly send your request not to REDCap but to the hacker, in which he/she can actually see the contents of your request, including your API token, and then use your token to impersontate you to make API requests to REDCap in the future as if they were you."
api_docs_035 = "How to prevent Man in the Middle attacks:"
api_docs_036 = "Preventing MiM attacks is pretty simple. Essentially all you need to do is to force your API script to validate the SSL certificate of the REDCap server. REDCap's SSL certificate will always be valid, but the hacker's fake certificate can never be determined to be valid if you attempt to validate it. In many programs or programming languages that can make API requests, validating an SSL certificate is often as easy as setting a flag. For example, "
api_docs_037 = " is popularly used by many API scripts in programming languages such as PHP, R, SAS, and many more in order to make the web request to REDCap. <b>So if your API script is utilizing cURL, all you need to do is modify your script so that it sets the cURL option named CURLOPT_SSL_VERIFYPEER to have a value of TRUE.</b> Once done, your API script will attempt to make the API request to REDCap *only* if it can validate REDCap's SSL certificate. "
api_docs_038 = " If you are not using cURL, there are plenty of other examples on the web for how to validate an SSL certificate in different programming languages. Such examples can be found simply by Googling the name of your programming language + 'verify ssl certificate' (e.g., '"
api_docs_039 = "'), which should provide you with many helpful results."
api_docs_040 = "REMINDER:"
api_docs_041 = "Please remember that while REDCap itself has many security layers to help protect you and to ensure the highest level of security and data integrity, it is *your* responsibility to ensure that you are using the most secure methods and best practices when using the REDCap API."
api_docs_042 = "The REDCap API can be called from a variety of clients using any popular client-side or web development language that you are able to implement (e.g .NET, Python, PHP, Java). Below you may download a ZIP file containing several examples of how to call the API using various software languages. The files contained therein may be modified however you wish."
api_docs_045 = "Download API examples (.zip)"
api_docs_046 = "Note about export rights: "
api_docs_047 = "Method Name"
api_docs_048 = "Export Records"
api_docs_049 = "Description"
api_docs_050 = "URL"
api_docs_051 = "Supported Request Method"
api_docs_052 = "This method allows you to export a set of records for a project."
api_docs_053 = "Please be aware that Data Export user rights will be applied to this API request. For example, if you have 'No Access' data export rights in the project, then the API data export will fail and return an error. And if you have 'De-Identified' or 'Remove All Identifier Fields' data export rights, then some data fields *might* be removed and filtered out of the data set returned from the API. To make sure that no data is unnecessarily filtered out of your API request, you should have 'Full Data Set' export rights in the project."
api_docs_054 = "Parameters (case sensitive)"
api_docs_055 = "The API token specific to your REDCap project and username (each token is unique to each user for each project). See the section on the left-hand menu for obtaining a token for a given project."
api_docs_056 = "record"
api_docs_057 = "csv, json, xml [default]"
api_docs_058 = "* 'record' refers to the record ID for the project"
api_docs_059 = "flat - output as one record per row [default]"
api_docs_060 = "eav - output as one data point per row"
api_docs_061 = "Non-longitudinal: Will have the fields - record*, field_name, value"
api_docs_062 = "Longitudinal: Will have the fields - record*, field_name, value, redcap_event_name"
api_docs_063 = "Required"
api_docs_064 = "Optional"
api_docs_065 = "an array of record names specifying specific records you wish to pull (by default, all records are pulled)"
api_docs_066 = "an array of field names specifying specific fields you wish to pull (by default, all fields are pulled)"
api_docs_067 = "an array of form names you wish to pull records for. If the form name has a space in it, replace the space with an underscore (by default, all records are pulled)"
api_docs_068 = "an array of unique event names that you wish to pull records for - only for longitudinal projects"
api_docs_069 = "raw [default], label - export the raw coded values or labels for the options of multiple choice fields"
api_docs_070 = "raw [default], label - (for 'csv' format 'flat' type only) for the CSV headers, export the variable/field names (raw) or the field labels (label)"
api_docs_071 = "true, false [default] - specifies the format of checkbox field values specifically when exporting the data as labels (i.e., when rawOrLabel=label) in flat format (i.e., when type=flat). When exporting labels, by default (without providing the exportCheckboxLabel flag or if exportCheckboxLabel=false), all checkboxes will either have a value 'Checked' if they are checked or 'Unchecked' if not checked. But if exportCheckboxLabel is set to true, it will instead export the checkbox value as the checkbox option's label (e.g., 'Choice 1') if checked or it will be blank/empty (no value) if not checked. If rawOrLabel=false or if type=eav, then the exportCheckboxLabel flag is ignored. (The exportCheckboxLabel parameter is ignored for type=eav because 'eav' type always exports checkboxes differently anyway, in which checkboxes are exported with their true variable name (whereas the 'flat' type exports them as variable___code format), and another difference is that 'eav' type *always* exports checkbox values as the choice label for labels export, or as 0 or 1 (if unchecked or checked, respectively) for raw export.)"
api_docs_072 = "csv, json, xml - specifies the format of error messages. If you do not pass in this flag, it will select the default format for you passed based on the 'format' flag you passed in or if no format flag was passed in, it will default to 'xml'."
api_docs_073 = "true, false [default] - specifies whether or not to export the survey identifier field (e.g., 'redcap_survey_identifier') or survey timestamp fields (e.g., instrument+'_timestamp') when surveys are utilized in the project. If you do not pass in this flag, it will default to 'false'. If set to 'true', it will return the redcap_survey_identifier field and also the survey timestamp field for a particular survey when at least one field from that survey is being exported. NOTE: If the survey identifier field or survey timestamp fields are imported via API data import, they will simply be ignored since they are not real fields in the project but rather are pseudo-fields."
api_docs_074 = "true, false [default] - specifies whether or not to export the 'redcap_data_access_group' field when data access groups are utilized in the project. If you do not pass in this flag, it will default to 'false'. NOTE: This flag is only viable if the user whose token is being used to make the API request is *not* in a data access group. If the user is in a group, then this flag will revert to its default value."
api_docs_075 = "Returns"
api_docs_076 = "Data from the project in the format and type specified ordered by the record (primary key of project) and then by event id"
api_docs_077 = "EAV XML:"
api_docs_078 = "Flat XML:"
api_docs_079 = "each data point as an element"
api_docs_080 = "the report ID number provided next to the report name on the report list page"
api_docs_081 = "csv, json, xml - specifies the format of error messages. If you do not pass in this flag, it will select the default format for you passed based on the 'format' flag you passed in or if no format flag was passed in, it will default to 'xml'."
api_docs_082 = "raw [default], label - (for 'csv' format 'flat' type only) for the CSV headers, export the variable/field names (raw) or the field labels (label)"
api_docs_083 = "true, false [default] - specifies the format of checkbox field values specifically when exporting the data as labels (i.e., when rawOrLabel=label). When exporting labels, by default (without providing the exportCheckboxLabel flag or if exportCheckboxLabel=false), all checkboxes will either have a value 'Checked' if they are checked or 'Unchecked' if not checked. But if exportCheckboxLabel is set to true, it will instead export the checkbox value as the checkbox option's label (e.g., 'Choice 1') if checked or it will be blank/empty (no value) if not checked. If rawOrLabel=false, then the exportCheckboxLabel flag is ignored."
api_docs_084 = "Export Reports"
api_docs_085 = "This method allows you to export the data set of a report created on a project's 'Data Exports, Reports, and Stats' page."
api_docs_086 = "Please be aware that Data Export user rights will be applied to this API request. For example, if you have 'No Access' data export rights in the project, then the API report export will fail and return an error. And if you have 'De-Identified' or 'Remove All Identifier Fields' data export rights, then some data fields *might* be removed and filtered out of the data set returned from the API. To make sure that no data is unnecessarily filtered out of your API request, you should have 'Full Data Set' export rights in the project."
api_docs_087 = "Also, please note the the 'Export Reports' method does *not* make use of the 'type' (flat/eav) parameter, which can be used in the 'Export Records' method. All data for the 'Export Reports' method is thus exported in flat format. If the 'type' parameter is supplied in the API request, it will be ignored."
api_docs_088 = "Data from the project in the format and type specified ordered by the record (primary key of project) and then by event id"
api_docs_089 = "eav - input as one data point per row"
api_docs_090 = "normal - blank/empty values will be ignored [default]"
api_docs_091 = "overwrite - blank/empty values are valid and will overwrite data"
api_docs_092 = "** Event name is the unique name for an event, not the event label"
api_docs_093 = "The formatted data to be imported."
api_docs_094 = "NOTE: "
api_docs_095 = "When importing data in EAV type format, please be aware that checkbox fields must have their field_name listed as variable+'___'+optionCode and its value as either '0' or '1' (unchecked or checked, respectively). For example, for a checkbox field with variable name 'icecream', it would be imported as EAV with the field_name as 'icecream___4' having a value of '1' in order to set the option coded with '4' (which might be 'Chocolate') as 'checked'."
api_docs_096 = "MDY, DMY, YMD [default] - the format of values being imported for dates or datetime fields (understood with M representing 'month', D as 'day', and Y as 'year') - NOTE: The default format is Y-M-D (with "
api_docs_097 = "dashes"
api_docs_098 = "), while MDY and DMY values should always be formatted as M/D/Y or D/M/Y (with "
api_docs_099 = "slashes"
api_docs_100 = "), respectively."
api_docs_102 = "Import Records"
api_docs_103 = "This method allows you to import a set of records for a project"
api_docs_104 = "the content specified by "
api_docs_105 = "an array of field names specifying specific fields you wish to pull (by default, all metadata is pulled)"
api_docs_106 = "an array of form names specifying specific data collection instruments for which you wish to pull metadata (by default, all metadata is pulled). NOTE: These 'forms' are not the form label values that are seen on the webpages, but instead they are the unique form names seen in Column B of the data dictionary."
api_docs_107 = "Export Metadata (Data Dictionary)"
api_docs_108 = "This method allows you to export the metadata for a project"
api_docs_109 = "Metadata from the project (i.e. Data Dictionary values) in the format specified ordered by the field order"
api_docs_110 = "A field's variable name. By default, all fields are returned, but if field is provided, then it will only the export field name(s) for that field. If the field name provided is invalid, it will return an error."
api_docs_111 = "csv, json, xml - specifies the format of error messages. If you do not pass in this flag, it will select the default format for you passed based on the 'format' flag you passed in or if no format flag was passed in, it will default to 'xml'. The list that is returned will contain the original field name (variable) of the field and also the export field name(s) of that field."
api_docs_112 = "Export List of Export Field Names (i.e. variables used during exports and imports)"
api_docs_113 = "This method returns a list of the export/import-specific version of field names for all fields (or for one field, if desired) in a project. This is mostly used for checkbox fields because during data exports and data imports, checkbox fields have a different variable name used than the exact one defined for them in the Online Designer and Data Dictionary, in which *each checkbox option* gets represented as its own export field name in the following format: field_name + triple underscore + converted coded value for the choice. For non-checkbox fields, the export field name will be exactly the same as the original field name. Note: The following field types will be automatically removed from the list returned by this method since they cannot be utilized during the data import process: 'calc', 'file', and 'descriptive'."
api_docs_114 = "The list that is returned will contain the three following attributes for each field/choice: 'original_field_name', 'choice_value', and 'export_field_name'. The choice_value attribute represents the raw coded value for a checkbox choice. For non-checkbox fields, the choice_value attribute will always be blank/empty. The export_field_name attribute represents the export/import-specific version of that field name."
api_docs_115 = "Returns a list of the export/import-specific version of field names for all fields (or for one field, if desired) in a project in the format specified and ordered by their field order . The list that is returned will contain the three following attributes for each field/choice: 'original_field_name', 'choice_value', and 'export_field_name'. The choice_value attribute represents the raw coded value for a checkbox choice. For non-checkbox fields, the choice_value attribute will always be blank/empty. The export_field_name attribute represents the export/import-specific version of that field name."
api_docs_116 = "the record ID"
api_docs_117 = "the name of the field that contains the file"
api_docs_118 = "the unique event name - only for longitudinal projects"
api_docs_119 = "Export a File"
api_docs_120 = "This method allows you to download a document that has been attached to an individual record for a File Upload field. Please note that this method may also be used for Signature fields (i.e. File Upload fields with 'signature' validation type)."
api_docs_121 = "Note about export rights: "
api_docs_122 = "Please be aware that Data Export user rights will be applied to this API request. For example, if you have 'No Access' data export rights in the project, then the API file export will fail and return an error. And if you have 'De-Identified' or 'Remove All Identifier Fields' data export rights, then the API file export will fail and return an error *only if* the File Upload field has been tagged as an Identifier field. To make sure that your API request does not return an error, you should have 'Full Data Set' export rights in the project."
api_docs_123 = "the contents of the file"
api_docs_124 = "How to obtain the filename of the file: "
api_docs_125 = "The MIME type of the file, along with the name of the file and its extension, can be found in the header of the returned response. Thus in order to determine these attributes of the file being exported, you will need to parse the response header. Example: content-type = application/vnd.openxmlformats-officedocument.wordprocessingml.document; name='FILE_NAME.docx'"
api_docs_126 = "the name of the field that contains the file"
api_docs_127 = "the unique event name - only for longitudinal projects"
api_docs_128 = "the contents of the file"
api_docs_129 = "Import a File"
api_docs_130 = "This method allows you to upload a document that will be attached to an individual record for a File Upload field. Please note that this method may NOT be used for Signature fields (i.e. File Upload fields with 'signature' validation type) because a signature can only be captured and stored using the web interface."
api_docs_131 = "This method allows you to remove a document that has been attached to an individual record for a File Upload field. Please note that this method may also be used for Signature fields (i.e. File Upload fields with 'signature' validation type)."
api_docs_132 = "Delete a File"
api_docs_133 = "Export Instruments (Data Entry Forms)"
api_docs_134 = "This method allows you to export a list of the data collection instruments for a project. This includes their unique instrument name as seen in the second column of the Data Dictionary, as well as each instrument's corresponding instrument label, which is seen on a project's left-hand menu when entering data. The instruments will be ordered according to their order in the project."
api_docs_135 = "Instruments for the project in the format specified and will be ordered according to their order in the project."
api_docs_136 = "the record ID. The value is blank by default. If record is blank, it will return the PDF as blank (i.e. with no data). If record is provided, it will return a single instrument or all instruments containing data from that record only."
api_docs_137 = "the unique event name - only for longitudinal projects. For a longitudinal project, if record is not blank and event is blank, it will return data for all events from that record. If record is not blank and event is not blank, it will return data only for the specified event from that record."
api_docs_138 = "the unique instrument name as seen in the second column of the Data Dictionary. The value is blank by default, which returns all instruments. If record is not blank and instrument is blank, it will return all instruments for that record."
api_docs_139 = "[The value of this parameter does not matter and is ignored.] If this parameter is passed with any value, it will export all instruments (and all events, if longitudinal) with data from all records. Note: If this parameter is passed, the parameters record, event, and instrument will be ignored."
api_docs_140 = "csv, json, xml [default] - The returnFormat is only used with regard to the format of any error messages that might be returned."
api_docs_141 = "Export PDF file of Data Collection Instruments (either as blank or with data)"
api_docs_142 = "This method allows you to export a PDF file for any of the following: 1) a single data collection instrument (blank), 2) all instruments (blank), 3) a single instrument (with data from a single record), 4) all instruments (with data from a single record), or 5) all instruments (with data from ALL records). This is the exact same PDF file that is downloadable from a project's data entry form in the web interface, and additionally, the user's privileges with regard to data exports will be applied here just like they are when downloading the PDF in the web interface (e.g., if they have de-identified data export rights, then it will remove data from certain fields in the PDF). If the user has 'No Access' data export rights, they will not be able to use this method, and an error will be returned."
api_docs_143 = "A PDF file containing one or all data collection instruments from the project, in which the instruments will be blank (no data), contain data from a single record, or contain data from all records in the project, depending on the parameters passed in the API request."
api_docs_144 = "the record ID. The name of the record in the project."
api_docs_145 = "the unique instrument name as seen in the second column of the Data Dictionary. This instrument must be enabled as a survey in the project."
api_docs_146 = "the unique event name (for longitudinal projects only)."
api_docs_147 = "Export a Survey Link for a Participant"
api_docs_148 = "This method returns a unique survey link (i.e., a URL) in plain text format for a specified record and data collection instrument (and event, if longitudinal) in a project. If the user does not have 'Survey Distribution Tools' privileges, they will not be able to use this method, and an error will be returned. If the specified data collection instrument has not been enabled as a survey in the project, an error will be returned."
api_docs_149 = "Returns a unique survey link (i.e., a URL) in plain text format for the specified record and instrument (and event, if longitudinal)."
api_docs_150 = "Export a Survey Queue Link for a Participant"
api_docs_151 = "This method returns a unique Survey Queue link (i.e., a URL) in plain text format for the specified record in a project that is utilizing the Survey Queue feature. If the user does not have 'Survey Distribution Tools' privileges, they will not be able to use this method, and an error will be returned. If the Survey Queue feature has not been enabled in the project, an error will be returned."
api_docs_152 = "Returns a unique Survey Queue link (i.e., a URL) in plain text format for the specified record in the project."
api_docs_153 = "the unique instrument name as seen in the second column of the Data Dictionary. This instrument must be enabled as a survey in the project."
api_docs_154 = "Export a Survey Return Code for a Participant"
api_docs_155 = "This method returns a unique Return Code in plain text format for a specified record and data collection instrument (and event, if longitudinal) in a project. If the user does not have 'Survey Distribution Tools' privileges, they will not be able to use this method, and an error will be returned. If the specified data collection instrument has not been enabled as a survey in the project or does not have the 'Save & Return Later' feature enabled, an error will be returned."
api_docs_156 = "Returns a unique Return Code in plain text format for the specified record and instrument (and event, if longitudinal)."
api_docs_157 = "the unique instrument name as seen in the second column of the Data Dictionary. This instrument must be enabled as a survey in the project."
api_docs_158 = "the unique event name (for longitudinal projects only)."
api_docs_159 = "Export a Survey Participant List"
api_docs_160 = "This method returns the list of all participants for a specific survey instrument (and for a specific event, if a longitudinal project). If the user does not have 'Survey Distribution Tools' privileges, they will not be able to use this method, and an error will be returned. If the specified data collection instrument has not been enabled as a survey in the project, an error will be returned."
api_docs_161 = "Returns the list of all participants for the specified survey instrument [and event] in the desired format. The following fields are returned: email, email_occurrence, identifier, invitation_sent_status, invitation_send_time, response_status, survey_access_code, survey_link. The attribute 'email_occurrence' represents the current count that the email address has appeared in the list (because emails can be used more than once), thus email + email_occurrence represent a unique value pair. 'invitation_sent_status' is '0' if an invitation has not yet been sent to the participant, and is '1' if it has. 'invitation_send_time' is the date/time in which the next invitation will be sent, and is blank if there is no invitation that is scheduled to be sent. 'response_status' represents whether the participant has responded to the survey, in which its value is 0, 1, or 2 for 'No response', 'Partial', or 'Completed', respectively. Note: If an incorrect event_id or instrument name is used or if the instrument has not been enabled as a survey, then an error will be returned."
api_docs_162 = "an array of arm numbers that you wish to pull events for (by default, all events are pulled)"
api_docs_163 = "Export Events"
api_docs_164 = "This method allows you to export the events for a project"
api_docs_165 = "This only works for longitudinal projects."
api_docs_166 = "Events for the project in the format specified"
api_docs_167 = "Export Arms"
api_docs_168 = "This method allows you to export the Arms for a project"
api_docs_170 = "Arms for the project in the format specified"
api_docs_171 = "Export Instrument-Event Mappings"
api_docs_172 = "This method allows you to export the instrument-event mappings for a project (i.e., how the data collection instruments are designated for certain events in a longitudinal project)."
api_docs_173 = "Instrument-event mappings for the project in the format specified"
api_docs_174 = "Export Users"
api_docs_175 = "This method allows you to export the list of users for a project, including their user privileges and also email address, first name, and last name. Note: If the user has been assigned to a user role, it will return the user with the role's defined privileges."
api_docs_178 = "Form Rights: 0=No Access, 2=Read Only, 1=View records/responses and edit records (survey responses are read-only), 3=Edit survey responses"
api_docs_180 = "Export Project Information"
api_docs_181 = "This method allows you to export some of the basic attributes of a given REDCap project, such as the project's title, if it is longitudinal, if surveys are enabled, the time the project was created and moved to production, etc."
api_docs_182 = "Attributes for the project in the format specified. For any values that are boolean, they will be represented as either a '0' (no/false) or '1' (yes/true). Also, all date/time values will be returned in Y-M-D H:M:S format. The following attributes will be returned:"
api_docs_183 = "Export REDCap Version"
api_docs_184 = "This method returns the current REDCap version number as plain text (e.g., 4.13.18, 5.12.2, 6.0.0)."
api_docs_185 = "the current REDCap version number (three numbers delimited with two periods) as plain text - e.g., 4.13.18, 5.12.2, 6.0.0"
api_docs_186 = "Note about export rights: "
api_docs_187 = "This method allows you to delete Arms from a project. Notice: Because of this method's destructive nature, it is only available for use for projects in Development status. Additionally, please be aware that deleting an arm also automatically deletes all events that belong to that arm, and will also automatically delete any records/data that have been collected under that arm (this is non-reversible data loss)."
api_docs_188 = "Delete Arms"
api_docs_189 = "Number of Arms deleted"
api_docs_190 = "an array of arm numbers that you wish to delete"
api_docs_191 = "Import Arms"
api_docs_192 = "This method allows you to import Arms into a project or to rename existing Arms in a project. You may use the parameter override=1 as a 'delete all + import' action in order to erase all existing Arms in the project while importing new Arms."
api_docs_193 = "Number of Arms imported"
api_docs_194 = "Delete Events"
api_docs_195 = "This method allows you to delete Events from a project. Notice: Because of this method's destructive nature, it is only available for use for projects in Development status. Additionally, please be aware that deleting an event will automatically delete any records/data that have been collected under that event (this is non-reversible data loss)."
api_docs_197 = "Number of Events deleted"
api_docs_198 = "Import Events"
api_docs_199 = "This method allows you to import Events into a project or to update existing Events' attributes, such as the event name, days offset, etc. The unique event name of an Event cannot be changed because it is auto-generated by REDCap. Please note that the only way to update an existing Event is to provide the unique_event_name attribute, and if the unique_event_name attribute is missing for an Event being imported (when override=0), it will assume it to be a new Event that should be created."
api_docs_200 = "Number of Events imported"
api_docs_201 = "Import Instrument-Event Mappings"
api_docs_202 = "This method allows you to import Instrument-Event Mappings into a project (this corresponds to the 'Designate Instruments for My Events' page in the project)."
api_docs_203 = "Number of Instrument-Event Mappings imported"
api_docs_204 = "Import Metadata (Data Dictionary)"
api_docs_205 = "This method allows you to import metadata (i.e., Data Dictionary) into a project. Notice: Because of this method's destructive nature, it is only available for use for projects in Development status."
api_docs_206 = "Number of fields imported"
api_docs_207 = "Create A New Project"
api_docs_208 = "This method allows you to create a new REDCap project. A 64-character Super API Token is required for this method (as opposed to project-level API methods that require a regular 32-character token associated with the project-user). In the API request, you must minimally provide the project attributes 'project_title' and 'purpose' (with numerical value 0=Practice/Just for fun, 1=Other, 2=Research, 3=Quality Improvement, 4=Operational Support) when creating a project."
api_docs_210 = "Import Users"
api_docs_211 = "This method allows you to import new users into a project while setting their user privileges, or update the privileges of existing users in the project."
api_docs_212 = "Number of users added or updated"
api_docs_213 = "Introduction"
api_docs_214 = "Obtaining API Tokens"
api_docs_215 = "API Error Codes & Responses"
api_docs_216 = "API Security & Best Practices"
api_docs_217 = "API Examples"
api_docs_218 = "REDCap API Documentation"
api_docs_219 = "General API Info"
api_docs_220 = "Supported Methods"
api_docs_221 = "When a project is created, a 32-character project-level API Token is returned (associated with both the project and user creating the project). This token could then ostensibly be used to make subsequent API calls to this project, such as for adding new events, fields, records, etc."
api_docs_222 = "The Super API Token specific to a user"
api_docs_223 = "0 - false [default], 1 - true"
api_docs_224 = "This method is only available for use for projects in Development status."
api_docs_225 = "Notice: Because of the 'override' parameter's destructive nature, this method may only use override=1 for projects in Development status."
api_docs_226 = "The method will return all the attributes below with regard to user privileges in the format specified. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), in which each form will have its own Form Rights value (see the key below to learn what each numerical value represents). Most user privilege attributes are boolean (0=No Access, 1=Access). Attributes returned:"
api_docs_227 = "KEY:"
api_docs_228 = "Users & User Privileges"
api_docs_229 = "Other attribute values: 0=No Access, 1=Access."
api_docs_230 = "When a project is created with this method, the project will automatically be given all the project-level defaults just as if you created a new empty project via the web user interface, such as a automatically creating a single data collection instrument seeded with a single Record ID field and Form Status field, as well as (for longitudinal projects) one arm with one event. And if you intend to create your own arms or events immediately after creating the project, it is recommended that you utilize the override=1 parameter in the 'Import Arms' or 'Import Events' method, respectively, so that the default arm and event are removed when you add your own. Also, the user creating the project will automatically be added to the project as a user with full user privileges and a project-level API token, which could then be used for subsequent project-level API requests."
api_docs_231 = "NOTE: Only users with Super API Tokens can utilize this method. Users can only be granted a super token by a REDCap administrator (using the API Tokens page in the REDCap Control Center). Please be advised that users with a Super API Token can create new REDCap projects via the API without any approval needed by a REDCap administrator. If you are interested in obtaining a super token, please contact your local REDCap administrator."
api_docs_232 = "JSON Example:"
api_docs_233 = "CSV Example:"
api_docs_234 = "XML Example:"
api_docs_235 = "Contains the attributes of the project to be created, in which they are provided in the specified format. While the only required attributes are 'project_title' and 'purpose', the fields listed below are all the possible attributes that can be provided in the 'data' parameter. The 'purpose' attribute must have a numerical value (0=Practice/Just for fun, 1=Other, 2=Research, 3=Quality Improvement, 4=Operational Support), in which 'purpose_other' is only required to have a value (as a text string) if purpose=1. The attributes is_longitudinal (0=False, 1=True; Default=0), surveys_enabled (0=False, 1=True; Default=0), and record_autonumbering_enabled (0=False, 1=True; Default=1) are all boolean. Please note that either is_longitudinal=1 or surveys_enabled=1 does not add arms/events or surveys to the project, respectively, but it merely enables those settings which are seen at the top of the project's Project Setup page."
api_docs_236 = "All available attributes:"
api_docs_237 = "Contains the attributes 'arm_num' (referring to the arm number) and 'name' (referring to the arm's name) of each arm to be created/modified, in which they are provided in the specified format."
api_docs_238 = "Contains the required attributes 'event_name' (referring to the name/label of the event) and 'arm_num' (referring to the arm number to which the event belongs - assumes '1' if project only contains one arm). In order to modify an existing event, you must provide the attribute 'unique_event_name' (referring to the auto-generated unique event name of the given event). If the project utilizes the Scheduling module, the you may optionally provide the following attributes, which must be numerical: day_offset, offset_min, offset_max. If the day_offset is not provided, then the events will be auto-numbered in the order in which they are provided in the API request."
api_docs_239 = "Contains the attributes 'arm_num' (referring to the arm number), 'unique_event_name' (referring to the auto-generated unique event name of the given event), and 'form' (referring to the unique form name of the given data collection instrument), in which they are provided in the specified format."
api_docs_240 = "Contains the attributes of the user to be added to the project or whose privileges in the project are being updated, in which they are provided in the specified format. All values should be numerical with the exception of username, expiration, data_access_group, and forms. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), in which each form will have its own Form Rights value (see the key below to learn what each numerical value represents). Most user privilege attributes are boolean (0=No Access, 1=Access). Please notice the distinction between data_access_group (contains the unique DAG name for a user) and data_access_groups (denotes whether the user has access to the Data Access Groups page)."
api_docs_242 = "Super Tokens: If you wish to utilize the 'Create Project' API method, then a Super API Token is required. Super tokens are 64-characters in length (as opposed to 32-character-long regular tokens), in which a REDCap user can only have one super token at most. If you are interested in obtaining a super token, please contact your local REDCap administrator."
api_docs_243 = "Permissions Required"
api_docs_244 = "To use this method, you must have API Export privileges in the project."
api_docs_245 = "To use this method, you must have API Import/Update privileges in the project."
api_docs_246 = "To use this method, you must have API Import/Update privileges *and* User Rights privileges in the project."
api_docs_247 = "To use this method, you must have API Import/Update privileges *and* Project Design/Setup privileges in the project."
api_docs_248 = "To use this method, you must have a Super API Token."
api_docs_249 = "String of logic text (e.g., [age] > 30) for filtering the data to be returned by this API method, in which the API will only return the records (or record-events, if a longitudinal project) where the logic evaluates as TRUE. This parameter is blank/null by default unless a value is supplied. Please note that if the filter logic contains any incorrect syntax, the API will respond with an error message."
api_docs_250 = "csv, json, xml [default], odm ('odm' refers to CDISC ODM XML format, specifically ODM version 1.3.1)"
api_docs_251 = "default: NULL - The 'odm' parameter must be an XML string in CDISC ODM XML format that contains project metadata (fields, forms, events, arms) and might optionally contain data to be imported as well. The XML contained in this parameter can come from a REDCap Project XML export file from REDCap itself, or may come from another system that is capable of exporting projects and data in CDISC ODM format. If the 'odm' parameter is included in the API request, it will use the XML to import its contents into the newly created project. This will allow you not only to create the project with the API request, but also to import all fields, forms, and project attributes (and events and arms, if longitudinal) as well as record data all at the same time."
api_docs_252 = "Export Project XML"
api_docs_253 = "Export Entire Project as REDCap XML File (containing metadata & data)"
api_docs_254 = "The entire REDCap project's metadata (and data, if specified) will be returned in CDISC ODM format as a single XML string."
api_docs_255 = "NOTE: All the option paramters listed below ONLY apply to data returned if the 'returnMetadataOnly' parameter is set to FALSE (default). For this API method, ALL metadata (all fields, forms, events, and arms) will always be exported. Only the data returned can be filtered using the optional parameters."
api_docs_256 = "true, false [default] - TRUE returns only metadata (all fields, forms, events, and arms), whereas FALSE returns all metadata and also data (and optionally filters the data according to any of the optional parameters provided in the request)"
api_docs_257 = "If the 'returnMetadataOnly' parameter is set to FALSE, then please be aware that Data Export user rights will be applied to any data returned from this API request. For example, if you have 'De-Identified' or 'Remove All Identifier Fields' data export rights, then some data fields *might* be removed and filtered out of the data set returned from the API. To make sure that no data is unnecessarily filtered out of your API request, you should have 'Full Data Set' export rights in the project."
api_docs_258 = "Delete Records"
api_docs_260 = "To use this method, you must have 'Delete Record' user privileges in the project."
api_docs_261 = "delete"
api_docs_262 = "an array of record names specifying specific records you wish to delete"
api_docs_264 = "the arm number of the arm in which the record(s) should be deleted. (This can only be used if the project is longitudinal with more than one arm.) NOTE: If the arm parameter is not provided, the specified records will be deleted from all arms in which they exist. Whereas, if arm is provided, they will only be deleted from the specified arm."
api_docs_265 = "Import Project Information"
api_docs_266 = "This method allows you to update some of the basic attributes of a given REDCap project, such as the project's title, if it is longitudinal, if surveys are enabled, etc. Its data format corresponds to the format in the API method Export Project Information."
api_docs_267 = "Contains some or all of the attributes from Export Project Information in the same data format as in the export. These attributes will change the project information."
api_docs_268 = "csv, json, xml"
api_docs_269 = "Returns the number of values accepted to be updated in the project settings (including values which remained the same before and after the import)."
api_docs_270 = "Attributes for the project in the format specified. For any values that are boolean, they should be represented as either a '0' (no/false) or '1' (yes/true). The following project attributes can be udpated:"
api_docs_272 = "Generate Next Record Name"
api_docs_273 = "To be used by projects with record auto-numbering enabled, this method exports the next potential record ID for a project. It generates the next record name by determining the current maximum numerical record ID and then incrementing it by one."
api_docs_274 = "Note: This method does not create a new record, but merely determines what the next record name would be."
api_docs_275 = "If using Data Access Groups (DAGs) in the project, this method accounts for the special formatting of the record name for users in DAGs (e.g., DAG-ID); in this case, it only assigns the next value for ID for all numbers inside a DAG. For example, if a DAG has a corresponding DAG number of 223 wherein records 223-1 and 223-2 already exist, then the next record will be 223-3 if the API user belongs to the DAG that has DAG number 223. (The DAG number is auto-assigned by REDCap for each DAG when the DAG is first created.) When generating a new record name in a DAG, the method considers all records in the entire project when determining the maximum record ID, including those that might have been originally created in that DAG but then later reassigned to another DAG."
api_docs_276 = "Note: This method functions the same even for projects that do not have record auto-numbering enabled."
api_docs_277 = "The maximum integer record ID + 1."
api_docs_278 = "(only for projects with repeating instruments/events) The repeat instance number of the repeating event (if longitudinal) or the repeating instrument (if classic or longitudinal). Default value is '1'."
api_docs_279 = "true, false [default] - TRUE will cause the XML returned to include all files uploaded for File Upload and Signature fields for all records in the project, whereas FALSE will cause all such fields not to be included. NOTE: Setting this option to TRUE can make the export very large and may prevent it from completing if the project contains many files or very large files."
api_docs_280 = "false (or 'false') - The record names provided in the request will be used. [default]"
api_docs_281 = "true (or 'true') - New record names will be automatically determined."
api_docs_282 = "If record auto-numbering has been enabled in the project, it may be desirable to import records where each record's record name is automatically determined by REDCap (just as it does in the user interface). If this parameter is set to 'true', the record names provided in the request will not be used (although they are still required in order to associate multiple rows of data to an individual record in the request), but instead those records in the request will receive new record names during the import process. NOTE: To see how the provided record names get translated into new auto record names, the returnContent parameter should be set to 'auto_ids', which will return a record list similar to 'ids' value, but it will have the new record name followed by the provided record name in the request, in which the two are comma-delimited. For example, if "
api_docs_283 = "count [default] - the number of records imported, ids - a list of all record IDs that were imported, auto_ids = (used only when forceAutoNumber=true) a list of pairs of all record IDs that were imported, includes the new ID created and the ID value that was sent in the API request (e.g., 323,10)."
api_docs_284 = "Set to TRUE to return a compact-formatted PDF that excludes fields that have no data saved and excludes unselected multiple choice options, thus producing a smaller PDF file. If set to FALSE, all fields will be displayed normally."
api_docs_285 = "To return only records that have been <u>created or modified</u> *after* a given date/time, provide a timestamp in the format YYYY-MM-DD HH:MM:SS (e.g., '2017-01-01 00:00:00' for January 1, 2017 at midnight server time). If not specified, it will assume no begin time."
api_docs_286 = "To return only records that have been <u>created or modified</u> *before* a given date/time, provide a timestamp in the format YYYY-MM-DD HH:MM:SS (e.g., '2017-01-01 00:00:00' for January 1, 2017 at midnight server time). If not specified, it will use the current server time."
api_docs_287 = "Set the delimiter used to separate values in the CSV data file (for CSV format only). Options include: comma ',' (default), 'tab', semi-colon ';', pipe '|', or caret '^'. Simply provide the value in quotes for this parameter."
api_docs_288 = "If specified, force all numbers into same decimal format. You may choose to force all data values containing a decimal to have the same decimal character, which will be applied to all calc fields and number-validated text fields. Options include comma ',' or dot/full stop '.', but if left blank/null, then it will export numbers using the fields' native decimal format. Simply provide the value of either ',' or '.' for this parameter."
api_docs_289 = "Note: Super API Tokens can also be utilized for this method instead of a project-level API token. Users can only be granted a super token by a REDCap administrator (using the API Tokens page in the REDCap Control Center)."
api_docs_290 = "Export DAGs"
api_docs_291 = "This method allows you to export the Data Access Groups for a project"
api_docs_292 = "DAGs for the project in the format specified"
api_docs_293 = "Import DAGs"
api_docs_294 = "This method allows you to import new DAGs (Data Access Groups) into a project or update the group name of any existing DAGs."
api_docs_295 = "DAGs can be renamed by simply changing the group name (data_access_group_name). DAG can be created by providing group name value while unique group name should be set to blank."
api_docs_296 = "Contains the attributes 'data_access_group_name' (referring to the group name) and 'unique_group_name' (referring to the auto-generated unique group name) of each DAG to be created/modified, in which they are provided in the specified format."
api_docs_297 = "Number of DAGs added or updated"
api_docs_298 = "Delete DAGs"
api_docs_299 = "This method allows you to delete DAGs from a project."
api_docs_300 = "an array of unique group names that you wish to delete"
api_docs_301 = "Number of DAGs deleted"
api_docs_302 = "Export User-DAG Assignments"
api_docs_303 = "This method allows you to export existing User-DAG assignments for a project"
api_docs_304 = "User-DAG assignments for the project in the format specified"
api_docs_305 = "Import User-DAG Assignments"
api_docs_306 = "This method allows you to assign users to any data access group."
api_docs_307 = "If you wish to modify an existing mapping, you *must* provide its unique username and group name. If the 'redcap_data_access_group' column is not provided, user will not assigned to any group. There should be only one record per username."
api_docs_308 = "Contains the attributes 'username' (referring to the existing unique username) and 'redcap_data_access_group' (referring to existing unique group name) of each User-DAG assignments to be modified, in which they are provided in the specified format."
api_docs_309 = "Number of User-DAG assignments added or updated"
api_docs_310 = "This method allows you to export the logging (audit trail) of all changes made to this project, including data exports, data changes, project metadata changes, modification of user rights, etc."
api_docs_311 = "You may choose event type to fetch result for specific event type"
api_docs_312 = "To return only the events belong to specific user (referring to existing username), provide a user. If not specified, it will assume all users."
api_docs_313 = "To return only the events belong to specific record (referring to existing record name), provide a record. If not specified, it will assume all records. This parameter is available only when event is related to record."
api_docs_314 = "To return only the events belong to specific DAG (referring to group_id), provide a dag. If not specified, it will assume all dags."
api_docs_315 = "To return only the events that have been <u>logged</u> *after* a given date/time, provide a timestamp in the format YYYY-MM-DD HH:MM (e.g., '2017-01-01 17:00' for January 1, 2017 at 5:00 PM server time). If not specified, it will assume no begin time."
api_docs_316 = "To return only records that have been <u>logged</u> *before* a given date/time, provide a timestamp in the format YYYY-MM-DD HH:MM (e.g., '2017-01-01 17:00' for January 1, 2017 at 5:00 PM server time). If not specified, it will use the current server time."
api_docs_317 = "List of all changes made to this project, including data exports, data changes, and the creation or deletion of users."
api_docs_318 = "Filter by event (logtype): <br>export = Data export, <br>manage = Manage/Design, <br>user = User or role created-updated-deleted, <br>record = Record created-updated-deleted, <br>record_add = Record created (only), <br>record_edit = Record updated (only), <br>record_delete = Record deleted (only), <br>lock_record = Record locking & e-signatures, <br>page_view = Page Views"
api_docs_319 = "This method allows you to delete Users from a project."
api_docs_320 = "an array of unique usernames that you wish to delete"
api_docs_321 = "Number of Users deleted"
api_docs_322 = "Export User Roles"
api_docs_323 = "This method allows you to export the list of user roles for a project, including their user privileges."
api_docs_324 = "The method will return all the attributes below with regard to user roles privileges in the format specified. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), in which each form will have its own Form Rights value (see the key below to learn what each numerical value represents). Most user role privilege attributes are boolean (0=No Access, 1=Access). Attributes returned:"
api_docs_325 = "Import User Roles"
api_docs_326 = "This method allows you to import new user roles into a project while setting their privileges, or update the privileges of existing user roles in the project."
api_docs_327 = "Contains the attributes of the user role to be added to the project or whose privileges in the project are being updated, in which they are provided in the specified format. All values should be numerical with the exception of unique_role_name, role_label and forms. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), in which each form will have its own Form Rights value (see the key below to learn what each numerical value represents). Most user privilege attributes are boolean (0=No Access, 1=Access)."
api_docs_328 = "Number of user roles added or updated"
api_docs_329 = "Delete User Roles"
api_docs_330 = "This method allows you to delete User Roles from a project."
api_docs_331 = "an array of unique rolenames that you wish to delete"
api_docs_332 = "Number of User Roles deleted"
api_docs_333 = "Export User-Role Assignments"
api_docs_334 = "This method allows you to export existing User-Role assignments for a project"
api_docs_335 = "User-Role assignments for the project in the format specified"
api_docs_336 = "Import User-Role Assignments"
api_docs_337 = "This method allows you to assign users to any user role."
api_docs_338 = "If you wish to modify an existing mapping, you *must* provide its unique username and role name. If the 'unique_role_name' column is not provided, user will not assigned to any user role. There should be only one record per username."
api_docs_340 = "Number of User-Role assignments added or updated"
api_docs_341 = "Missing attributes: If a user role is being added to a project in the API request, then any attributes not provided for a user role in the request (including form-level rights) will automatically be given the minimum privileges (typically 0=No Access) for the attribute/privilege. However, if an existing user role's privileges are being modified in the API request, then any attributes not provided will not be modified from their current value but only the attributes provided in the request will be modified."
api_docs_342 = "the unique instrument name (column B in the Data Dictionary) of an instrument (as a string) if you wish to delete the data for all fields on the specified instrument for the records specified."
api_docs_343 = "the repeating instance number for a repeating instrument or repeating event. NOTE: If project has repeating instruments/events, it will remove only the data for that repeating instance."
api_docs_344 = "an array of unique event names that you wish to delete"
api_docs_345 = "NOTE: If instrument is provided for a longitudinal project, the event parameter is mandatory."
api_docs_346 = "This method allows you to delete one or more records from a project in a single API request, and also optionally allows you to delete parts of a record, such as a single instrument's data for one or more records or a single event's data for one or more records."
api_docs_347 = "the number of records deleted or (if instrument, event, and/or instance are provided) the number of items deleted over the total records specified."
api_docs_348 = "This method allows the current API user to switch (assign/reassign/unassign) their current Data Access Group assignment if they have been assigned to multiple DAGs via the DAG Switcher page in the project."
api_docs_349 = "The unique group name of the Data Access Group to which you wish to switch."
api_docs_350 = "Returns \"1\" when the current API user is switched to the specified Data Access Group, otherwise it returns an error message."
api_docs_351 = "This method allows you to rename a record from a project in a single API request."
api_docs_352 = "To use this method, you must have 'Rename Record' user privileges in the project."
api_docs_353 = "record name of the current record which you want to rename to new name."
api_docs_354 = "new record name to which you want to rename current record."
api_docs_355 = "specific arm number in which current record exists. If null, then all records with same name across all arms on which it exists (if longitudinal with multiple arms) will be renamed to new record name, otherwise it will rename the record only in the specified arm."
api_docs_356 = "Returns \"1\" if record is renamed or error message if any."
api_docs_357 = "true, false [default] - specifies whether or not to export blank values for instrument complete status fields that have a gray status icon. All instrument complete status fields having a gray icon can be exported either as a blank value or as \"0\" (Incomplete). Blank values are recommended in a data export if the data will be re-imported into a REDCap project."
api_docs_358 = "Data Export: 0=No Access, 2=De-Identified, 3=Remove Identifier Fields, 1=Full Data Set"
api_docs_359 = "To use this method, you must have API Export privileges *and* Logging privileges in the project."
api_docs_360 = "Contains the attributes 'username' (referring to the existing unique username) and 'unique_role_name' (referring to existing unique role name) of each User-Role assignments to be modified, in which they are provided in the specified format. Note: If the project contains Data Access Groups, you may pass a third attribute 'data_access_group' with a valid unique DAG name of the DAG to which you wish to assign the user during the process of assigning them to a user role."
api_docs_361 = "or alternatively as a string (comma-separated list)."
api_docs_362 = "Missing attributes: If a user is being added or re-imported to a project in the API request, then any attributes not provided for a user in the request (including form-level rights) will automatically be given the minimum privileges (typically 0=No Access) for the attribute/privilege. However, if an existing user's privileges are being modified in the API request, then any attributes not provided will not be modified from their current value but only the attributes provided in the request will be modified."
api_docs_363 = "provide a value of '0' (\"keep logging\") or '1' (\"delete logging\"). This option can only be utilized for projects with the \"Delete a record's logging activity when deleting the record?\" setting enabled  by an administrator on the Edit Project Settings page.  If that setting is enabled in the project, then the default value will be '1', and if the project-level setting is not enabled, the default value will be '0'. If the project-level setting has been enabled,  this option must be provided with a value of '0' in order to prevent the record's logging activity from being deleted when the record is deleted."
api_docs_364 = "To use this method, you must have API Export privileges *and* User Rights privileges (Full Access or Read Only) in the project."
api_docs_365 = "Specifies whether to do the import as background process."
api_docs_366 = "1 or 'true' for yes."
api_docs_367 = "0 or 'false' for no. [default]"
api_docs_368 = "NOTE: Does not apply when importing as a background process (i.e., backgroundProcess=true). When using a background process, success:true (upon success) or success:false (upon failure) will be returned in the appropriate format (csv, json, xml)."
api_docs_369 = "false [default], true - return the value for the alternative target field, i.e. the randomization number for open allocations. Note: with concealed allocations only the value '*' will be returned, not the real allocation group (which would break the blinding)."
api_docs_370 = "Performs the specified randomization for the record and returns the value for the target randomization field (plus optionally the alternative target value), or an error message on failure (such as if the record does not exist or if stratification information is missing)."
api_docs_371 = "This method allows the current API user to randomize a record."
api_docs_372 = "To use this method you must have the Randomize privilege in the project."
api_docs_373 = "The record name (id) of the record to randomize. The record must already exist and contain all necessary stratification information."
api_docs_374 = "The unique id of the randomization (viewable on the Randomization page for users with Design permissions, or on the API Playground page). Corresponds to a specific target field and event."
api_01 = "The REDCap API is not enabled."
api_03 = "Request API token"
api_05 = "Your API token for project"
api_06 = "Please contact your REDCap administrator to discuss activation of the API."
api_07 = "As a REDCap administrator, you may enable the REDCap API on the Control Center's"
api_08 = "Create API token now"
api_09 = "API Security: Best Practices"
api_10 = "It is important to remember that when making requests to the REDCap API, you should always validate the REDCap server's SSL certificate to ensure the highest level of security during communication with the API. For details on what this means and how to do it, see the 'API Security: Best Practices' section in the"
api_11 = "The REDCap project no longer exists because it was deleted."
api_12 = "API Method: "
api_13 = "Format: "
api_14 = "Raw Request Parameters"
api_16 = "Response"
api_17 = "PHP"
api_18 = "Perl"
api_19 = "Python"
api_20 = "Ruby"
api_21 = "Java"
api_22 = "Arms: "
api_23 = "Errors: "
api_24 = "Instrument: "
api_25 = "Event: "
api_26 = "Record: "
api_27 = "Field: "
api_28 = "Fields: "
api_29 = "Forms: "
api_30 = "Type: "
api_31 = "Records: "
api_32 = "Events: "
api_33 = "Raw Labels: "
api_34 = "Raw Headers: "
api_35 = "Checkbox Labels: "
api_36 = "Survey Fields: "
api_37 = "Data Access Groups: "
api_38 = "Report ID: "
api_39 = "Overwrite: "
api_40 = "Data: "
api_41 = "Update"
api_42 = "Date Format: "
api_43 = "Return Content: "
api_44 = "HTTP Status: "
api_45 = "File: "
api_46 = "Download"
api_47 = "All Records: "
api_48 = "Export Records"
api_49 = "Export Reports"
api_50 = "Import Records"
api_51 = "Export Metadata (Data Dictionary)"
api_52 = "Export List of Export Field Names"
api_53 = "Export a File"
api_54 = "Import a File"
api_55 = "Delete a File"
api_56 = "Export Instruments (Data Entry Forms)"
api_57 = "Export PDF file of Instruments"
api_58 = "Export a Survey Link"
api_59 = "Export a Survey Queue Link"
api_60 = "Export a Survey Return Code"
api_61 = "Export Survey Participants"
api_62 = "Export Events"
api_63 = "Export Arms"
api_64 = "Export Instrument-Event Mappings"
api_65 = "Export Users"
api_66 = "Export Project Info"
api_67 = "Export REDCap Version"
api_68 = "Download "
api_70 = "R"
api_71 = "cURL"
api_72 = "Production - Some APIs have been disabled for the playground because they affect data"
api_73 = "Execute Request"
api_74 = "Displayed in the box below is the code you would use to execute this API request in the selected programming language."
api_75 = "Displayed in the box below are all the POST parameters that would be sent in the API request based on the selections above."
api_76 = "Click the Execute Request button to execute a real API request, and it will display the API response in a text box below."
api_77 = "Select an API method from the drop-down list below, after which it will load any other options that are specific to that method."
api_78 = "Create Project"
api_79 = "Import Metadata (Data Dictionary)"
api_80 = "Import Users"
api_81 = "Import Instrument-Event Mappings"
api_82 = "Import Arms"
api_83 = "Delete Arms"
api_84 = "Import Events"
api_85 = "Delete Events"
api_86 = "Select your CSV file of Arms to be added or renamed:"
api_87 = "Select your CSV file of Events to be added or modified:"
api_88 = "Select your CSV File of Instrument-Event Designations:"
api_91 = "You can add new arms to the project or update the arm name of any existing arms by uploading a CSV file with a new arms configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing arms. <b>NOTE:</b> Arms can be renamed by simply changing the arm name in the CSV file. Arms cannot be deleted using the CSV file. If you wish to delete an arm or change an arm's number, please do so using the specified links for each arm on this page."
api_92 = "You can add new events to the project or update the event name or event order of any existing events by uploading a CSV file with a new events configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing events. <b>NOTE:</b> If you wish to modify an existing event, you *must* provide its unique event name. If the 'unique_event_name' column is not provided, it will simply create the event as a new event. You cannot delete events using the CSV file but can only do that by clicking the delete icon next to a given event."
api_94 = "instrument-event mappings were added or updated."
api_95 = "arms were added or updated. Note: If you just created a new arm, you will now need to add events to the arm."
api_96 = "events were added or updated. Note: If you just created a new event, you will now need to designate instruments for that event."
api_97 = "Arms"
api_98 = "Field Names"
api_99 = "Files"
api_100 = "Metadata"
api_101 = "REDCap"
api_102 = "This method cannot be used while the project is in Production status."
api_103 = "Insufficient user privileges: You must have 'API Import/Update' privileges and 'User Rights' privileges in the project in order to import/update users via the API Import Users method."
api_104 = "The 'arms' parameter is either missing or is not an array. It must be provided as an array even if it only contains one value."
api_105 = "One or more of the arm numbers provided are either not numeric or do not exist in this project. Note: No arms were deleted. Arm numbers that do not exist:"
api_106 = "You can import all the instrument-event designations for *all* arms by uploading a CSV file with a new instrument-event mappings configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing instrument-event mappings. <b>NOTE:</b> The mappings that you upload here will *completely* replace your existing mappings, so if multiple arms exist in this project, make sure you include designations for all arms."
api_107 = "This 'override' parameter cannot be used while the project is in Production status."
api_108 = "You may use override=1 as a 'delete all + import' action in order to erase all existing Arms in the project while importing new Arms. If override=0, then you can only add new Arms or rename existing ones."
api_109 = "You may use override=1 as a 'delete all + import' action in order to erase all existing Events in the project while importing new Events. If override=0, then you can only add new Events or modify existing ones."
api_111 = "is not a valid unique Data Access Group name for this project."
api_112 = "cannot have their user privileges modified because the user belongs to a user role. Users in roles cannot have their privileges modified via the 'Import User' API method."
api_113 = "The form named"
api_114 = "is incorrect for the user"
api_115 = "The form does not exist in this project."
api_116 = "with value"
api_117 = "is not a valid form-level rights value. It must be 0, 1, 2 or 3."
api_118 = "The username is missing for user #"
api_119 = "in the list of users provided."
api_120 = "You do not have permissions to use the API 'Create Project' method. You must have been granted a 64-character Super API Token from a REDCap administrator in order to utilize this method."
api_121 = "Also, 'purpose' must have a value of 0, 1, 2, 3, or 4."
api_122 = "You must provide some text for 'purpose_other' since you specified 'purpose' as '1' (Other)."
api_123 = "Only one project can be created at a time using the API 'Create Project' method. It appears that you have provided attributes for more than one project in the API request."
api_124 = "Insufficient user privileges: You must have 'API Import/Update' privileges and 'Project Design and Setup' privileges in the project in order to utilize this API method."
api_125 = "Displayed below is a preview of all the changes you are about to commit. Please look over the changes, and then approve them by clicking the Upload button. A value with a gray background denotes that the value will not change. If it has a green background, it is being added. If yellow, it is being modified."
api_126 = "And if red, it is being deleted."
api_127 = "Filter Logic: "
api_128 = "NOTICE: This user cannot be granted a Super API Token because the user does not have 'Create/Copy Project' privileges in their user account. You may give them these privileges on the Browser Users page (click the Edit User Info button)."
api_129 = "Return Metadata Only? "
api_130 = "Delete Records"
api_131 = "One or more of the records provided cannot be deleted because they do not exist in the project. The following records do not exist:"
api_132 = "The arm provided is not correct for the project."
api_133 = "Import Project Info"
api_134 = "Generate Next Record Name"
api_135 = "Insufficient user privileges: You must have 'API Import/Update' privileges and 'Delete Records' privileges in the project in order to utilize this API method."
api_136 = "Incorrect format for 'records' parameter. It must be passed as an array, even if it only contains a single record name."
api_137 = "The 'records' parameter is an empty array. The parameter must be an array containing one or more record names to delete."
api_138 = "Generate API token"
api_139 = "Obtain API token for"
api_140 = "Allow user to auto-generate API tokens?"
api_141 = "Allow normal users to auto-generate API tokens for their projects?"
api_142 = "If the option is set to allow only selected users to generate API tokens, then any given user can be given this privilege on the Browse Users page when modifying their user account settings."
api_143 = "No, an administrator must approve each token request"
api_144 = "Yes, allow ALL users to generate API tokens on their own"
api_145 = "Yes, allow SELECTED users to generate API tokens on their own"
api_146 = "Force Record Auto-number: "
api_147 = "Records Created or Modified in Timespan (begin)<br>(YYYY-MM-DD HH:MM:SS format): "
api_148 = "Records Created or Modified in Timespan (end)<br>(YYYY-MM-DD HH:MM:SS format): "
api_149 = "Export files for File<br>Upload/Signature fields? "
api_150 = "The REDCap project is no longer accessible because it was marked as Completed."
api_151 = "is not in a valid username format."
api_152 = "Export DAGs"
api_153 = "Import DAGs"
api_154 = "Delete DAGs"
api_155 = "Export User-DAG Assignment"
api_156 = "Import User-DAG Assignment"
api_157 = "One or more of the dags provided are not valid unique group names that do not exist in this project. Note: No dags were deleted. DAGs that do not exist:"
api_158 = "Export Logging"
api_159 = "Delete Users"
api_160 = "One or more of the users provided are not valid usernames that do not exist in this project. Note: No users were deleted. Users that do not exist:"
api_161 = "The 'users' parameter is either missing or is not an array. It must be provided as an array even if it only contains one value."
api_162 = "User Roles"
api_163 = "Export User Roles"
api_164 = "Import User Roles"
api_165 = "Delete User Roles"
api_166 = "Roles:"
api_167 = "The 'roles' parameter is either missing or is not an array. It must be provided as an array even if it only contains one value."
api_170 = "One or more of the roles provided are not valid rolenames that do not exist in this project. Note: No roles were deleted. Roles that do not exist:"
api_171 = "Insufficient user privileges: You must have 'API Import/Update' privileges and 'User Rights' privileges in the project in order to import/update user roles via the API Import User Roles method."
api_172 = "Export User-Role Assignment"
api_173 = "Import User-Role Assignment"
api_174 = "The username for unique role name"
api_175 = "is incorrect for the user role"
api_176 = "One or more of the records provided are either do not exist in this project or not valid with selected params. Note: No records were deleted. Records that do not exist:"
api_177 = "Record must be provided."
api_178 = "Record does not exists."
api_179 = "Invalid Unique Event Name."
api_180 = "Invalid instrument."
api_181 = "Event is mandatory for longitudinal project."
api_182 = "Repeating instance should be numeric."
api_183 = "You do not have permission to export/import/delete Data Access Groups because you have been assigned to a Data Access Group."
api_184 = "You do not have permission to import User-DAG Assignment because you have been assigned to a Data Access Group."
api_185 = "The 'dags' parameter is either missing or is not an array. It must be provided as an array even if it only contains one value."
api_186 = "Switch DAG"
api_187 = "Current record name must be provided."
api_188 = "Current Record does not exists."
api_189 = "New record name must be provided."
api_190 = "Rename Record"
api_191 = "Rename To: "
api_192 = "code examples"
api_193 = "Export a File from the File Repository"
api_194 = "Import a File into the File Repository"
api_195 = "Delete a File from the File Repository"
api_196 = "File doc_id:"
api_197 = "the doc_id of the file in the File Repository"
api_198 = "This method allows you to download a single file stored in the File Repository by providing the file's doc_id number."
api_199 = "To use this method, you must have API Export privileges and File Repository privileges in the project."
api_200 = "To use this method, you must have API Import/Update privileges and File Repository privileges in the project."
api_201 = "This method allows you to import a single file into a project's File Repository. The file may be stored in a specific folder in the File Repository if a folder_id is provided."
api_202 = "This method allows you to delete a single file in a project's File Repository. Once deleted, the file will remain in the Recycle Bin folder for up to 30 days."
api_203 = "the folder_id of a specific folder in the File Repository where you wish to store the file. If none is provided, the file will be stored in the top-level directory of the File Repository."
api_204 = "Export a List of Files/Folders from the File Repository"
api_205 = "Folder folder_id:"
api_206 = "This method allows you to export a list of all files and subfolders from a specific folder in a project's File Repository. Each sub-folder will have an associated folder_id number, and each file will have an associated doc_id number."
api_207 = "the folder_id of a specific folder in the File Repository for which you wish to export a list of its files and subfolders. If none is provided, the top-level directory of the File Repository will be used."
api_208 = "The list of all files and folders within a given sub-folder in the File Repository in the format specified."
api_209 = "Create a New Folder in the File Repository"
api_210 = "Folder folder_id where to create sub-folder:"
api_211 = "Name of new folder:"
api_212 = "This method allows you to create a new folder in the File Repository. You may optionally provide the folder_id of the parent folder under which you wish this folder to be created. Providing a dag_id and/or role_id will allow you to restrict access to only users within a specific DAG (Data Access Group) or User Role, respectively."
api_213 = "the folder_id of a specific folder in the File Repository for which you wish to create this sub-folder. If none is provided, the folder will be created in the top-level directory of the File Repository."
api_214 = "The desired name of the folder to be created (max length = 150 characters)"
api_215 = "the dag_id of the DAG (Data Access Group) to which you wish to restrict access for this folder. If none is provided, the folder will accessible to users in all DAGs and users in no DAGs."
api_216 = "the role_id of the User Role to which you wish to restrict access for this folder. If none is provided, the folder will accessible to users in all User Roles and users in no User Roles."
api_217 = "The folder_id of the new folder created in the specified format. For example, if using format=json, the output would look similar to this: <code>[{folder_id:45}]</code>."
api_218 = "External Module-provided API actions for {0}"
api_219 = "Use these methods with <code>content</code> set to \"<b>externalModule</b>\" and <code>prefix</code> and <code>action</code> set to the module <b>prefix</b> and <b>action</b> as shown in the table below, respectively. Please refer to the respective module's documentation for more information on the individual action and any further parameters that may be required."
api_220 = "Randomize Record"
api_221 = "Insufficient user privileges: You must have 'API Export' privileges and 'Data Access Groups' privileges in the project."
api_222 = "Insufficient user privileges: You must have 'API Import/Update' privileges and 'Data Access Groups' privileges in the project."
api_223 = "To use this method, you must have API Import/Update privileges *and* Data Access Groups privileges in the project."
api_224 = "To use this method, you must have API Export privileges *and* Data Access Groups privileges in the project."
api_225 = "To use this method, you must have API Export privileges *and* Project Setup/Design privileges in the project."
api_226 = "To use this method, you must have API Import/Update privileges *and* Project Setup/Design privileges in the project."
api_227 = "Insufficient user privileges: You must have 'API Export' privileges and 'Project Setup/Design' privileges in the project."
api_228 = "Insufficient user privileges: You must have 'API Import/Update' privileges and 'Project Setup/Design' privileges in the project."
api_229 = "Insufficient user privileges: You must have 'API Export' privileges and 'User Rights' privileges (Full Access or Read Only) in the project."
api_230 = "C#"
app_01 = "Data Import Tool"
app_02 = "Data Comparison Tool"
app_04 = "File Repository"
app_05 = "User Rights"
app_06 = "Reports"
app_07 = "Logging"
app_08 = "Calendar"
app_11 = "Record Locking Customization"
app_17 = "Project Setup"
app_18 = "Project Revision History"
app_19 = "Project Bookmarks"
app_20 = "Data Quality"
app_21 = "Randomization"
app_23 = "Data Exports, Reports, and Stats"
app_24 = "Survey Distribution Tools"
bottom_01 = "Logged in as"
bottom_02 = "Log out"
bottom_03 = "My Projects"
bottom_19 = "Generate schedules for the calendar<br/>using your defined events"
bottom_20 = "Data Entry"
bottom_23 = "Event:"
bottom_25 = "Applications"
bottom_27 = "Help & FAQ"
bottom_28 = "Video Tutorials"
bottom_33 = "The Calendar"
bottom_36 = "Project Field Types"
bottom_39 = "REDCap administrator"
bottom_42 = "Help & Information"
bottom_44 = "Project Home"
bottom_47 = "Data Collection"
bottom_48 = "Navigate to this form for"
bottom_51 = "Creating and managing surveys"
bottom_52 = "Suggest a New Feature"
bottom_54 = "REDCap Warning:"
bottom_55 = "The project header and footer can only be displayed properly for project-level pages (i.e. when the project_id 'pid' exists in the URL). If you append '?pid=X' to the current web address, in which X is the project_id of a project you have access to, then the project header and footer should then display properly."
bottom_56 = "Data Entry Overview"
bottom_57 = "Detailed Overview"
bottom_58 = "Brief Overview"
bottom_59 = "Locked on"
bottom_60 = "View data collection status of all records"
bottom_61 = "(all records)"
bottom_62 = "Add / Edit Records"
bottom_63 = "Select other record"
bottom_64 = "Create new records or edit/view existing ones"
bottom_67 = "Project was deleted"
bottom_68 = "As an Administrator, you may restore/undelete the project by clicking the Undelete button below."
bottom_69 = "Return to My Projects page"
bottom_72 = "View / Edit Records"
bottom_73 = "View or edit existing records"
bottom_74 = "Mobile App Overview"
bottom_75 = "Installing the Mobile App"
bottom_76 = "Contact REDCap administrator"
bottom_77 = "[REDCap question]"
bottom_78 = "Dear REDCap administrator,"
bottom_79 = "[Your REDCap question here]"
bottom_80 = "Sincerely,"
bottom_81 = "Project link:"
bottom_82 = "Mobile App Project Setup"
bottom_83 = "Launch Clinical Data Mart for pulling EHR data"
bottom_89 = "Do not ask again"
bottom_90 = "Close"
bottom_91 = "Log in to"
bottom_93 = "Please note that this project has been marked as 'Completed' and is no longer accessible. If the project was marked Completed by mistake or needs to be restored for some other reason, it may be returned back to its previous state by a REDCap administrator."
bottom_95 = "Restore Project"
bottom_96 = "Project was marked as Completed"
bottom_97 = "The project has now been restored. The page will now reload to reflect the changes."
bottom_98 = "PROJECT RESTORED!"
bottom_99 = "This project is currently in <b>Analysis/Cleanup status</b>, so it is assumed that formal data collection has ended, except for cleaning and analyzing the data already collected. While in this status, many features are disabled, such as surveys, Alerts & Notifications, Automated Survey Invitations, and other features typically used during data collection. Also, no new records can be created while in this status."
bottom_100 = "The data in this project is currently:"
bottom_101 = "Editable (existing records only)"
bottom_102 = "Read-only / Locked"
bottom_103 = "The project was marked as Completed at"
bottom_104 = "View users & privileges"
bottom_105 = "Once you have finished cleaning and analyzing the data, it is recommended that you navigate to the Other Functionality tab where you can mark the project as Completed, after which the project will become inaccessible. If the project is marked as Completed, it is assumed that you are completely done with the project but wish to preserve it and its data for a certain amount of time (or indefinitely). If you need to move back to Production status for whatever reason, you may do so using the Other Functionality page."
bottom_106 = "Are you done cleaning and analyzing your data?"
bottom_107 = "Modify data locking mode?"
bottom_108 = "While the project is in Analysis/Cleanup status, you may set the data in the project to be either 1) Editable (existing records only), or 2) Read-only/Locked. If set to Read-only/Locked mode, then no data in the project will be able to be modified in any way."
bottom_109 = "Set to Editable (existing records only)"
bottom_110 = "Lock entire record"
bottom_111 = "Unlock entire record"
bottom_112 = "Set all project data as Read-only / Locked"
bottom_113 = "Please note that this project has been deleted and is no longer accessible. If the project was deleted by mistake or needs to be restored for some other reason, it may be undeleted/restored by a REDCap administrator before <b>{0}</b>, after which time the project will be PERMANENTLY DELETED and will no longer be restorable."
bottom_114 = "As an Administrator, you may return the project back to its previous project status (e.g., Production, Analysis/Cleanup status) by clicking the Restore Project button below."
bottom_115 = "Full Project Build"
bottom_116 = "Learn Advanced Design Features"
ehr_launch_modal_01 = "You must establish connection to the EHR"
ehr_launch_modal_02 = "Before you may pull clinical data from the EHR, you must first establish connection to the clinical system by logging in to the EHR. By clicking the 'Log in' button below, you will be directed to a webpage to log in with your EHR credentials, after which you will be redirected back to this page to begin importing clinical data from the EHR."
ehr_launch_modal_03 = "Please be informed that the login page needs to be accessible from your current network and could require you to use a VPN connection."
calc_disclaimer_01 = "For various reasons, it is recommended that 'calc' field types not be excessively utilized on REDCap data collection instruments, but rather only be used when it is necessary to know the calculated value while on that page or following pages, such as when the result of the calculation affects data entry workflow. Otherwise, it is much more preferred to perform the calculation in a statistical analysis package after exporting the data out of REDCap, rather than using a 'calc' field in REDCap."
calc_disclaimer_02 = "When possible, performing the calculation outside of REDCap is more preferred for several reasons. Statistical analysis packages can provide much more robust and precise calculation methods, and can handle a wider variety of calculation functions than can REDCap. Also, the method by which REDCap performs calculations (using JavaScript, a common technology found in all web browsers) is known in rare cases to have calculation precision issues (e.g., the result of a complex calculation should be 0.06 but instead results as 0.06000000000000000005). However, such precision errors are very uncommon and are very seldom ever experienced. This can often be remedied by strategically using the REDCap round() function within your calculation, although such is not 100% preventative for all cases."
calc_disclaimer_03 = "Summarily, 'calc' field types should not be used excessively in REDCap and should only be used when the calculation result is necessary and affects data entry workflow. Instead, when possible, perform the calculation in a statistical analysis package after it has been exported out of REDCap."
calendar_02 = "The Calendar application can be used as a project calendar within this project to help organize your schedule and keep track of any upcoming events. It will allow you to add or modify calendar events and then view them either in a daily, weekly, or monthly format below. To add a new note or calendar event to any day, click <b>+New</b> at the top of that day's box to begin entering the information. "
calendar_03 = "Since you have already defined multiple events for this project, you may additionally "
calendar_04 = "generate a schedule"
calendar_05 = "using your pre-defined Events, which will then be added to the calendar."
calendar_06 = "Since you have been assigned to a Data Access Group, you are only able to view calendar events from your group."
calendar_07 = "Day"
calendar_08 = "Week"
calendar_09 = "Month"
calendar_10 = "Agenda"
calendar_11 = "VIDEO: How to use the calendar"
calendar_12 = "min"
calendar_13 = "upcoming calendar events"
calendar_14 = "No upcoming calendar events"
calendar_15 = "Save Notes"
calendar_16 = "The table below displays this record's upcoming calendar events for the next"
calendar_17 = "upcoming calendar event"
calendar_18 = "Generate Schedule"
calendar_19 = "Sync Calendar to External Application"
calendar_20 = "Allow the Calendar Feed feature to be used in a project (displayed on the project's Calendar page), including its associated Smart Variables (e.g., [calendar-url], [calendar-link])."
calendar_21 = "The web address (URL) of the calendar feed or downloadable ICS calendar file belonging to the current record."
calendar_22 = "The HTML web link that, when clicked, will navigate to the calendar feed or downloadable ICS calendar file belonging to the current record. 'Custom Text' is an optional parameter whereby you can specify the visible link text, and if it is not provided, it defaults to simply displaying the URL as the link text."
calendar_popup_01 = "Close"
calendar_popup_02 = "Event deleted"
calendar_popup_04 = "View/Edit Calendar Event"
calendar_popup_05 = "View Schedule"
calendar_popup_06 = "Ad Hoc"
calendar_popup_08 = "Status"
calendar_popup_11 = "Notes"
calendar_popup_12 = "Changes not saved"
calendar_popup_13 = "Saving"
calendar_popup_15 = "Delete from Calendar"
calendar_popup_16 = "Are you sure you wish to delete this calendar event?"
calendar_popup_18 = "Close this window"
calendar_popup_19 = "Date is not a valid date."
calendar_popup_20 = "Add New Calendar Event"
calendar_popup_22 = "24-hr format"
calendar_popup_25 = "Add Calendar Event"
calendar_popup_26 = "You must provide some detail for this new calendar event in the Notes box."
calendar_popup_27 = "Your new calendar event was created and added to the calendar!"
calendar_popup_28 = "The new calendar event was not created."
calendar_popup_29 = "Your calendar event was successfully deleted!"
calendar_popup_30 = "Additional notes (read-only):"
calendar_popup_31 = "Data Access<br>Group:"
calendar_popup_32 = "You may sync your REDCap calendar or perform a one-time import of your calendar events to external calendar applications such as Google Calendar, Outlook, Office 365, Zoho, Apple Calendar, or any application that supports iCal or ICS files."
calendar_popup_33 = "One-time import:"
calendar_popup_34 = "Choose one of the two options below to sync or import your project calendar events to an external calendar application."
calendar_popup_35 = "The web address below represents a real-time live feed of your REDCap project calendar. <b>Copy the URL to paste it as the calendar URL in your calendar application</b> using the option \"Add calendar from URL/Internet\". This will subscribe your external application to the REDCap project calendar. Notice: Different calendar applications have different refresh rates. So if new events are added to the calendar in REDCap, they may not immediately appear in the external application but will appear after the next refresh interval, which might be some time later that day or the next day (depending on the calendar application). Additionally, this calendar feed represents a <u>one-way feed</u>. This means that while changes made to the calendar in REDCap will automatically show up in the external calendar application, you will not be able to modify them in the external calendar application because they will be read-only."
calendar_popup_36 = "Select a record if the calendar event is associated with an existing record."
calendar_popup_37 = "Live calendar feed: Add calendar from URL/Internet"
calendar_popup_38 = "Copy URL to clipboard"
calendar_popup_39 = "Download and open the calendar ICS file below to import your REDCap calendar events manually into your calendar application on your computer, or upload the file to a web-based calendar service. Notice: This is <u>not a live feed but a one-time import</u>. Thus, any new events added to your REDCap calendar in the future will not be automatically added to your external calendar application. Additionally, please note that if you download and import the ICS file more than one time, it may create duplicate events in your calendar application."
calendar_popup_40 = "Download ICS file"
calendar_popup_41 = "NOTE: Since you have been assigned to a Data Access Group, you are only able to view calendar events from your group in the live calendar feed and also in the downloadable ICS file."
calendar_popup_ajax_03 = "change date"
calendar_popup_ajax_04 = "Save Date"
calendar_popup_ajax_06 = "Save Time"
calendar_popup_ajax_07 = "change time"
calendar_popup_ajax_08 = "Due Date"
calendar_popup_ajax_09 = "Scheduled"
calendar_popup_ajax_10 = "Confirmed"
calendar_popup_ajax_11 = "Cancelled"
calendar_popup_ajax_12 = "No Show"
calendar_popup_ajax_13 = "change status"
calendar_popup_ajax_14 = "Save Status"
calendar_table_01 = "Previous Month"
calendar_table_02 = "Next Month"
calendar_table_03 = "Print Calendar"
calendar_table_04 = "Day"
calendar_table_07 = "No calendar events to display"
calendar_table_08 = "Sunday"
calendar_table_09 = "Monday"
calendar_table_10 = "Tuesday"
calendar_table_11 = "Wednesday"
calendar_table_12 = "Thursday"
calendar_table_13 = "Friday"
calendar_table_14 = "Saturday"
config_02 = "You have no access rights to this page. Please see"
config_03 = "for additional details."
config_04 = "Your access to this particular REDCap project has expired. In order to gain access again, you will need someone to remove or change the expiration date of your user account for this project on the User Rights page."
config_05 = "You have no access rights to this page."
config_06 = "the project owner for more information."
config_07 = "You have no access rights to this page. Please see <a href=mailto:{0}>{1}</a> for additional details."
config_functions_01 = "REDCap crashed due to an unexpected PHP fatal error!"
config_functions_02 = "Error message:"
config_functions_03 = "File:"
config_functions_04 = "Line:"
config_functions_05 = "FILE TOO BIG!"
config_functions_06 = "Unfortunately, the file you uploaded contains too much data for REDCap to process all at once. Please break up the file into smaller pieces, and then upload each file one at a time into REDCap so that all your data gets fully imported into the project."
config_functions_07 = "REDCap crashed due to an unexpected fatal error!"
config_functions_08 = "Please try again what you were doing. If this error persists, please contact a REDCap administrator. We apologize for any inconvenience."
config_functions_20 = "A method of authentication has not been selected for this project.<p>Please select a valid authentication method for this project in the"
config_functions_22 = "The PEAR Auth module is not installed!"
config_functions_30 = "Modify Project Settings"
config_functions_36 = "REDCap is currently offline. Please return at another time. We apologize for any inconvenience."
config_functions_37 = "If you require assistance or have any questions about REDCap, please contact"
config_functions_40 = "RETURN TO PREVIOUS PAGE"
config_functions_41 = "The following query failed:"
config_functions_42 = "Your web server does NOT have the PHP library cURL installed, which is necessary for running this module. You will need to download cURL/libcurl and then install and configure it with PHP on your web server. You will find"
config_functions_43 = "instructions for cURL/libcurl installation here"
config_functions_45 = "Log In"
config_functions_52 = "This value you provided is not a number. Please try again."
config_functions_53 = "This value you provided is not an integer. Please try again."
config_functions_54 = "The value entered is not a valid Vanderbilt Medical Record Number (i.e. 4- to 9-digit number, excluding leading zeros). Please try again."
config_functions_55 = "The value entered in this field must be a date. You may use one of several formats (ex. YYYY-MM-DD or MM/DD/YYYY), but the final result must constitute a real date. Please try again."
config_functions_56 = "The value you provided must be within the suggested range"
config_functions_57 = "The value you provided is outside the suggested range"
config_functions_58 = "This value is admissible, but you may wish to double check it."
config_functions_59 = "The value entered must be a time value in the following format HH:MM within the range 00:00-23:59 (e.g., 04:32 or 23:19)."
config_functions_60 = "This field must be a 5 or 9 digit U.S. ZIP Code (like 94043). Please re-enter it now."
config_functions_61 = "This field must be a 10 digit U.S. phone number (like 415 555 1212). Please re-enter it now."
config_functions_62 = "This field must be a valid email address (like joe@user.com). Please re-enter it now."
config_functions_63 = "ERROR! Could not find the language file at the following expected location:"
config_functions_64 = "ERROR: Multiple tabs/windows open! Your changes were <u>not saved</u>."
config_functions_65 = "<b>For security reasons, REDCap only permits one tab/window at a time</b> in your web browser when submitting a form. This restriction is for security measures. If you were in the process of saving any changes on the previous page, please note that such changes were not saved, so you will need to go back and perform them again. Our apologies for any inconvenience."
config_functions_69 = "For security purposes, your REDCap user account has been temporarily disabled because it has exceeded the maximum amount of failed login attempts that are allowed within a set period of time"
config_functions_70 = "After that time, your account will become active again, after which you may return and log in."
config_functions_71 = "If you believe someone other than you is attempting to log in to REDCap using your username without your permission, immediately contact your REDCap administrator:"
config_functions_72 = "minutes"
config_functions_75 = "The following REDCap user account has been suspended:"
config_functions_76 = "Access to REDCap is prohibited. For more information, you may contact"
config_functions_77 = "The value you provided could not be validated because it does not follow the expected format. Please try again."
config_functions_78 = "The following user account has not yet been granted access to REDCap:"
config_functions_79 = "To request access to REDCap, you may contact"
config_functions_80 = "PDF file too big!"
config_functions_81 = "The PDF file that REDCap is trying to generate is just too large or contains too many pages for REDCap to handle. REDCap will not be able to export this PDF file. If you are trying to export a PDF with the data for all your project records, then you may need to instead try downloading each record one at a time as a PDF from the data entry form. Sorry for any inconvenience."
config_functions_82 = "REDCap could not determine your username for unknown reasons. There appears to be some kind of technical problem. Please try logging in again by clicking the button below or contact the following person to notify them of this issue:"
config_functions_83 = "If you are having trouble logging in, please contact"
config_functions_84 = "You will log in to REDCap using the login provider"
config_functions_85 = "Log in using"
config_functions_86 = "After clicking the button below, you will log in with the provider and then return back to REDCap."
config_functions_87 = "There is an error in the REDCap plugin that you are currently using. Please contact this plugin's developer and send them the error info listed below so that they may fix this issue. If you do not know who the developer is for this plugin, then notify your REDCap administrator about this issue."
config_functions_88 = "Must be less than or equal to"
config_functions_89 = "Must be greater than or equal to"
config_functions_90 = "and less than or equal to"
config_functions_91 = "no limit"
config_functions_92 = "(Your PIN + 6-digit Tokencode)"
config_functions_93 = "NOTE: Cross-site Request Forgery (CSRF) was detected and blocked! If you were attempting a CSRF attack, it has been successfully blocked. If this was not the case, then please ignore this part of the message."
config_functions_94 = "Required format:"
config_functions_116 = "Access denied due to username conflict!"
config_functions_117 = "There appears to be another person that already has the REDCap username"
config_functions_118 = "Thus you will not be able to use that username in REDCap because the other person already owns it. Please contact your REDCap administrator"
config_functions_119 = "to inform them that a Table-based user account already exists with your username, and therefore you will not be able to log in to REDCap using your LDAP username. This means that your administrator may have to create a Table-based user account for you to work around this username conflict."
config_functions_120 = "To disable the Rate Limiter, set the value to '0' or leave it blank."
config_functions_121 = "This REDCap project is currently offline. Please return to this project at another time. We apologize for any inconvenience. You may click the REDCap logo above to return to the My Projects page."
config_functions_122 = "Profile"
config_functions_123 = "<b>NOTE:</b> The data you just submitted will be saved once you log in again above."
config_functions_124 = "<b>ERROR:</b><br>Your web server does NOT have the PHP library cURL installed, which is necessary for running this module. You will need to download cURL/libcurl and then install and configure it with PHP on your web server. You will find {0:Link - see config_functions_43}."
config_functions_125 = "Please log in with your user name and password. If you are having trouble logging in, please contact {0:EmailLink}."
config_functions_126 = "Backtrace"
config_functions_127 = "REDCap Admins Only: Details of the error may be obtained by running the database query below."
config_functions_128 = "ERROR: You entered an invalid user name or password!"
config_functions_129 = "Please log in with your user name and password. If you are having trouble logging in, try clicking the \"Forgot your password\" link below."
control_center_19 = "Your system configuration values have now been changed!"
control_center_22 = "select a user"
control_center_28 = "Subject:"
control_center_29 = "The user could not be added!"
control_center_30 = "A user already exists named"
control_center_33 = "View User List By Criteria"
control_center_34 = "Provides sortable list of all REDCap users based on criteria and their basic info."
control_center_41 = "Loading"
control_center_43 = "To create a new user (Table-based authentication ONLY), provide the new user name along with the user's name and email address. Once created, the user will receive an email with log in information."
control_center_46 = "Allow this user to create or copy projects?"
control_center_48 = "Your changes have been saved!"
control_center_49 = "Your changes could not be saved!"
control_center_50 = "You may modify the governing settings for any REDCap project on this page. Some settings were created as defaults when the project was initially created, but others serve as extra settings used for customization and other functions. You may modify the values below and click the button at the bottom to commit these changes to the selected project."
control_center_51 = "Choose an existing project to edit its settings:"
control_center_52 = "Select a project"
control_center_53 = "Navigate to project"
control_center_56 = "Email Address"
control_center_57 = "Administrator?"
control_center_60 = "Search the user list for:"
control_center_61 = "Ready to upgrade to"
control_center_62 = "Click here"
control_center_64 = "An email has been sent to"
control_center_66 = "The email could not be sent to"
control_center_68 = "The password could not be reset."
control_center_72 = "Time of first login"
control_center_73 = "Time of first activity"
control_center_74 = "Time of last activity"
control_center_76 = "Projects user can access"
control_center_79 = "Allow this user to create or copy projects?"
control_center_80 = "Currently normal users CANNOT create or copy projects. See the User Settings page in the Control Center to change this setting."
control_center_81 = "RESET PASSWORD FOR USER"
control_center_83 = "DELETE USER"
control_center_84 = "Are you sure you wish to delete the user from REDCap?"
control_center_85 = "This will also remove this user from the"
control_center_86 = "REDCap projects to which they currently have access."
control_center_87 = "The user"
control_center_88 = "has now been removed and deleted from all REDCap projects."
control_center_89 = "The user could not be deleted!"
control_center_92 = "Your old primary email address in"
control_center_93 = "has now been changed to"
control_center_94 = "This only affects how your email address is stored in REDCap, and does not affect anything outside of REDCap. If this is incorrect, please reply to this email to notify the REDCap administrator who made this change."
control_center_98 = "If you have any questions, please contact"
control_center_100 = "email address changed to"
control_center_101 = "access granted"
control_center_102 = "password reset"
control_center_104 = "drafted changes are in review"
control_center_105 = "Delete the project"
control_center_107 = "Project title:"
control_center_108 = "(Click icon to open project in new window)"
control_center_109 = "Browse Users"
control_center_110 = "Browse Projects"
control_center_112 = "Security & Authentication Configuration"
control_center_113 = "Security & Authentication"
control_center_116 = "Notifications"
control_center_117 = "Notifications & Reporting"
control_center_118 = "If there are any important notifications to show to REDCap administrators, they will appear here on this page."
control_center_119 = "Reporting Your Stats"
control_center_121 = "Use alternative reporting method (if above does not work)"
control_center_122 = "The alternative method may be used if you are not able to connect with the consortium server, such as if you are behind a firewall. It will send an automated email, and your stats will be reported within 24 hours."
control_center_125 = "General Configuration"
control_center_129 = "Control Center Home"
control_center_131 = "System Configuration"
control_center_132 = "Users"
control_center_134 = "Projects"
control_center_136 = "Default Project Settings"
control_center_138 = "Time of suspension"
control_center_139 = "Delete user from system"
control_center_140 = "Reset password"
control_center_142 = "Suspend user account"
control_center_143 = "Do you wish to suspend this user's REDCap account? If suspended, they will no longer be able to log in to REDCap or access any projects, although their username and logged activity will remain in the system."
control_center_144 = "Success! The user has now been suspended from REDCap."
control_center_145 = "unsuspend user"
control_center_146 = "Success! The user has now been unsuspended and will now be able to access REDCap again."
control_center_147 = "Do you wish to unsuspend this user's REDCap account, thus allowing them to access REDCap again?"
control_center_148 = "Last Activity"
control_center_149 = "N/A"
control_center_150 = "Field Validation Types"
control_center_151 = "REDCap has a variety of different types of field validation that users may utilize within their projects to ensure good data quality. The table below will allow you to enable or disable any of the field validation types that come pre-packaged in your current version of REDCap. Once a validation type has been enabled, it will then be displayed in the Validation drop-down list in the Online Designer (inside the Add/Edit Field pop-up window). If not enabled, then it will stay hidden as an option. Listed below are all the available field validation types. The label for each is seen in bold, while the unique validation name that is used in the Data Dictionary can be found immediately below it in parentheses. "
control_center_152 = "Validation Types Currently Available for Use in All Projects"
control_center_153 = "Disable"
control_center_154 = "If any validation types are used for fields in a project and then are later disabled here by a REDCap administrator, they will still function properly in all projects utilizing them. NOTE: While only the ones enabled below will be displayed as an option in the Online Designer, <u>every</u> validation type listed below is accessible and able to be utilized in a Data Dictionary that is uploaded (i.e. all disabled validation types will function as an 'Easter Egg' option)."
control_center_155 = "No users are currently allowlisted"
control_center_156 = "Add new users to Allowlist"
control_center_157 = "You may add a single user or multiple users at once to the allowlist by simply copy and pasting their username(s) in the text box below, separating them with <b>one username per line</b>."
control_center_158 = "Users have been added to allowlist!"
control_center_159 = "If you are utilizing an external method of authentication (e.g., LDAP, Shibboleth) then you have the option of enabling the user allowlist. By default (i.e. allowlist disabled) when using external authentication methods, REDCap would normally authenticate the user and then allow them access to the application automatically, thus allowing everyone with a valid username for that external authentication to gain access to REDCap without any approval process."
control_center_160 = "Alternatively, when the allowlist is enabled, externally authenticated users will <u>not</u> be able to access REDCap until they have been added to the allowlist. So anyone not on the allowlist that authenticates via an external method will be given a message saying that they cannot access REDCap until an administrator adds them to the allowlist. When the allowlist is enabled, you will be given the option of automatically adding to the allowlist all users who have already accessed REDCap. All Administrators will always automatically be added the allowlist when it is enabled."
control_center_161 = "Enable the User Allowlist?"
control_center_162 = "User Allowlist"
control_center_163 = "When enabling the user allowlist, you have two different options. You have the option of 1) adding to the allowlist all existing REDCap users (using external authentication only), or 2) leaving the allowlist as is without adding any existing users (although all Administrators will still be added automatically). "
control_center_164 = "User Allowlist for External Authentication Methods"
control_center_165 = "If you already have users utilizing REDCap but now you simply want to limit the introduction of new users to REDCap via the allowlist, then you should choose option 1. If you choose option 2, then no one using external authentication (except Administrators) will be able to access REDCap, not even if they could previously access REDCap, until they are added to the allowlist (unless they already exist in the allowlist if it was enabled at a previous time)."
control_center_166 = "Add Users to Allowlist"
control_center_167 = "User Allowlist has been enabled!"
control_center_168 = "User Allowlist has been disabled!"
control_center_169 = "The following usernames were added:"
control_center_170 = "The following usernames could NOT be added:"
control_center_171 = "No users were added. They may have already existed in the allowlist."
control_center_172 = "Delete all"
control_center_173 = "All users have been removed from the User Allowlist (excluding Administrators)."
control_center_174 = "NOTICE: Authentication is not enabled!"
control_center_175 = "Please note that authentication has not yet been enabled for this installation of REDCap. This means that no login screen will appear when accessing REDCap, and all users will be given the default username 'site_admin'. You can set the authentication method on the Security & Authentication page. However, first you may want to read an overview on the REDCap Community website of all the steps required when changing your authentication method for REDCap (see link below)."
control_center_176 = "How to change your authentication method"
control_center_178 = "user should not be an Administrator!"
control_center_179 = "It appears that the user"
control_center_180 = "is an Administrator. However, this user account should ONLY ever be an Administrator when the system-level authentication method is set to None (Public), otherwise this user should NOT be an Administrator. You should go to the 'Administrators & Acct Managers' page and remove them as an Administrator immediately, otherwise users accessing public REDCap projects may gain access to things that only REDCap Administrators should be accessing."
control_center_182 = "All users"
control_center_183 = "Suspended users"
control_center_184 = "Active in past month"
control_center_186 = "Active in past 3 months"
control_center_187 = "Active in past 6 months"
control_center_188 = "Active in past 12 months"
control_center_191 = "No users to display"
control_center_192 = "users"
control_center_193 = "(Active = performed a logged activity)"
control_center_194 = "Not active in past month"
control_center_195 = "Not active in past 3 months"
control_center_196 = "Not active in past 6 months"
control_center_197 = "Not active in past 12 months"
control_center_198 = "Was logged in within past month"
control_center_199 = "Was logged in within past 3 months"
control_center_200 = "Was logged in within past 6 months"
control_center_201 = "Was logged in within past 12 months"
control_center_202 = "Was not logged in within past month"
control_center_203 = "Was not logged in within past 3 months"
control_center_204 = "Was not logged in within 6 months"
control_center_205 = "Was not logged in within 12 months"
control_center_207 = "Start Date:"
control_center_208 = "End Date:"
control_center_221 = "Customizable Settings"
control_center_236 = "Institution ID"
control_center_237 = "OPTIONAL identifier specific to your institution."
control_center_239 = "Edit user info"
control_center_240 = "The user could not be saved!"
control_center_241 = "User has been successfully saved."
control_center_242 = "An email with login information was sent to:"
control_center_243 = "Email could NOT be sent, so it is displayed below, if you wish to copy it and send it manually:"
control_center_244 = "You may edit the user's name, email address, and institution ID. If the user's email address changes, they will be notified via email."
control_center_245 = "API Tokens"
control_center_247 = "Revoke user's API access for this project"
control_center_248 = "Are you sure you wish to remove user's API access for this project?"
control_center_249 = "Regenerate user's API token for this project"
control_center_250 = "Are you sure you wish to regenerate the user's API token for this project?"
control_center_251 = "Create API token"
control_center_253 = "Create token"
control_center_255 = "Unable to create token"
control_center_256 = "missing username."
control_center_257 = "missing project."
control_center_258 = "token already exists."
control_center_259 = "could not save to database."
control_center_260 = "API token has been created"
control_center_261 = "Unable to delete token"
control_center_262 = "API token has been deleted"
control_center_263 = "An API token has been created for you for project"
control_center_265 = "Click here to retrieve your API token"
control_center_266 = "Manage API tokens by"
control_center_268 = "All existing tokens (by user)"
control_center_269 = "All existing tokens (by project)"
control_center_270 = "token does not exist."
control_center_271 = "All API tokens successfully deleted."
control_center_272 = "Unable to delete all tokens."
control_center_273 = "Create new API token"
control_center_274 = "Review API rights for user"
control_center_275 = "Before you create a new API token, please review the API rights (below) that this user has on the project named"
control_center_277 = "user has no API rights."
control_center_278 = "- select a user - "
control_center_279 = "- select a project - "
control_center_280 = "This page is used to manage the API tokens utilized by your REDCap users. The two drop-downs below will allow you to view either individual users or entire projects as a means of determining which users have API tokens, as well as be able to create a new API token for a user. Users that already have an API token for a specific project can have their token deleted or regenerated."
control_center_281 = "<b>NOTE:</b> Remember that tokens are specific to a single user for a single project. Thus a single project could have multiple tokens, and additionally an individual user could have several tokens, each pertaining to a different project."
control_center_282 = "Your API token has been deleted for the project named"
control_center_283 = "Create new API token for user"
control_center_285 = "Setting up the REDCap Cron Job"
control_center_286 = "REDCap requires that a cron job be set up on your REDCap web server, in which the cron job will be run by the web server at a periodic frequency throughout the day. The cron will perform any necessary tasks that need to be performed and will run those tasks as asynchronous background processes. The steps below will guide you through setting up this cron job and troubleshooting any possible errors."
control_center_287 = "Cron Jobs"
control_center_288 = "ERROR: Cron job not running!"
control_center_289 = "It appears that your REDCap cron job has either not been set up or is not running at the proper interval. Please see the Cron Jobs page in the Control Center for details on setting it up. This cron job is very important and must be running on a regular basis at the prescribed interval in order for certain background tasks to be performed correctly."
control_center_290 = "Go to Cron Jobs page"
control_center_291 = "The path of the PHP executable file on your web server could not be determined, so you will need to determine its path and replace"
control_center_292 = "in the text box with the real path."
control_center_293 = "A file is missing that is required, but you can"
control_center_295 = "Once downloaded, place the cron.php file in the directory"
control_center_297 = "How to schedule the REDCap cron job on a Windows server"
control_center_298 = "Open the command line prompt (cmd.exe) in Windows and run the command below. This will create a Windows scheduled task that will be run once per minute. If you wish to have this scheduled task be run under a specific user account, you will additionally need to set the following parameters:"
control_center_299 = "If you need help, here are more details on"
control_center_300 = "scheduling a Windows task via command line"
control_center_301 = "Paste this command in a Windows command prompt and hit Enter:"
control_center_302 = "How to schedule the REDCap cron job for a Linux/Unix server using CronTab"
control_center_303 = "Start a telnet/SSH session on your Linux/Unix server and add the text in the box to your CronTab file (use 'crontab -e' to open your cron list for editing). This will create a scheduled job that will be run once per minute. If you receive a permission denied error after starting 'crontab -e', you may need to use sudo (i.e. 'sudo crontab -e'). To list your current existing crons in CronTab, use 'crontab -l'. If you do not have CronTab installed on your server, you will need to download and install it."
control_center_304 = "Add the following two lines to your CronTab file:"
control_center_305 = "Trigger REDCap cron job in a web browser"
control_center_306 = "Diagnostic check"
control_center_307 = "Last cron job ran at:"
control_center_308 = "Current server type (Windows or Linux/Unix):"
control_center_309 = "Windows"
control_center_310 = "Linux/Unix"
control_center_311 = "Cron job status:"
control_center_312 = "Good"
control_center_313 = "Not running properly"
control_center_314 = "(Cron has not run in the past hour. Please check it.)"
control_center_315 = "User Settings"
control_center_316 = "on your web server, and then reload this page. (Note: Please do not confuse this cron.php file with the one that already exists in the REDCap version directory.)"
control_center_317 = "Need help troubleshooting your LDAP configuration?"
control_center_318 = "The value above does NOT match the URL at which you are currently accessing REDCap:"
control_center_319 = "If the value above is incorrect, you should change it immediately."
control_center_320 = "Allow this user to request that projects be created for them by a REDCap administrator?"
control_center_321 = "(If not checked, they will neither be able to create new projects nor request that new ones be created for them.)"
control_center_322 = "View user's API token for this project"
control_center_323 = "You may view the API token for this user for this project by clicking the View Token button below."
control_center_324 = "Are you sure you wish to view the user's token?"
control_center_325 = "Displayed below is the API token for user"
control_center_326 = "for the project"
control_center_327 = "Please be aware that your action of viewing this token has now been logged, and the user"
control_center_328 = "has been notified via email that you have just viewed their API token."
control_center_329 = "Another user viewed your API token"
control_center_330 = "This email is simply to notify you that the REDCap administrator named"
control_center_331 = "has just viewed the API token for your REDCap username"
control_center_332 = "If you are viewing the token of another user, then please be advised that your action of viewing their token will be logged on the project's Logging page, and the user will be notified via email that you have just viewed their API token."
control_center_333 = "API Token"
control_center_334 = "If you wish to change or delete your existing API token for this project, you may do so on the project's"
control_center_335 = "API page"
control_center_336 = "If you have any concerns regarding this, please contact this REDCap administrator immediately."
control_center_337 = "Notify user via email that token was created?"
control_center_339 = "Manage tokens of all project users"
control_center_340 = "My Token"
control_center_341 = "Manage All Project Tokens"
control_center_342 = "As a REDCap Administrator, you may manage the tokens of all users in this project. You may create, regenerate, delete, or view tokens for any user by clicking the icons in the Controls column."
control_center_343 = "Was logged in within past 24 hours"
control_center_344 = "Was not logged in within past 24 hours"
control_center_345 = "Was logged in within past 12 hours"
control_center_346 = "Was not logged in within past 12 hours"
control_center_347 = "Was logged in within past hour"
control_center_348 = "Was not logged in within past hour"
control_center_349 = "Active in past 24 hours"
control_center_350 = "Not active in past 24 hours"
control_center_351 = "Active in past 12 hours"
control_center_352 = "Not active in past 12 hours"
control_center_353 = "Active in past hour"
control_center_354 = "Not active in past hour"
control_center_355 = "Currently logged in"
control_center_356 = "Not currently logged in"
control_center_357 = "Active/not active in given time period"
control_center_358 = "Was logged in/not logged in within given time period"
control_center_359 = "Currently logged in or not"
control_center_360 = "General"
control_center_361 = "The value of 'REDCap base URL' ("
control_center_362 = ") does NOT match the URL at which you are currently accessing REDCap, which is"
control_center_363 = "is used to dynamically construct the survey links included in emails for survey invitations. If this value is not set properly, the survey links inside the invitation emails will not work. Read about the options below to resolve this issue."
control_center_364 = "to modify this value. It is suggested that you change its value to the following:"
control_center_365 = "Keep the current value of 'REDCap base URL', which is"
control_center_366 = "Do not show this warning message again"
control_center_367 = "Option 1:"
control_center_368 = "Option 2:"
control_center_369 = "How to fix:"
control_center_370 = "If you keep the current value, then nothing needs to be done, although you may wish to click the button below to prevent this warning message from displaying again in the future."
control_center_371 = "This may be a serious issue that you should fix immediately."
control_center_372 = "Are you sure you wish to hide this warning message?"
control_center_373 = "The user's primary email was changed, and the user was notified about this change."
control_center_375 = "Undelete project"
control_center_376 = "Are you sure you wish to restore/undelete this project?"
control_center_377 = "If restored, the project will become immediately accessible again to all users with access to it."
control_center_378 = "Restore/undelete project?"
control_center_379 = "Restoring project named"
control_center_380 = "Will be permanently deleted on"
control_center_381 = "Delete it now"
control_center_382 = "Deleting the project below will PERMANENTLY DELETE the project immediately, after which the project and all its data CANNOT BE RECOVERED. Are you sure you really want to do this?"
control_center_383 = "Password has never been reset"
control_center_384 = "Password was last reset on"
control_center_385 = "Help support REDCap by reporting your REDCap stats to the consortium, preferably on a weekly basis. You can set your stats to be sent automatically once per week by setting it on the Control Center's General Configuration page. Your participation helps promote the longevity of REDCap and the consortium."
control_center_386 = "Map of Users"
control_center_387 = "This page allows you to view on a map the locations of all your users that have accessed REDCap in a given period of time. (The map excludes survey participants since REDCap does not track the IP address of survey participants.) You may modify the window of time that the map represents by selecting another option in the drop-down list right above the map."
control_center_388 = "Please be advised that the GPS locations displayed on the map may not be 100% precise but might possibly contain some inaccuracies."
control_center_389 = "Setup and configuration"
control_center_390 = "It seems that you may not have used this page before. To make sure this page will work successfully with your server configuration, it is recommended that an initial test be performed. (NOTE: If your web server is behind a firewall and cannot contact outside websites on the World Wide Web, then this page will not work since it requires the use of third-party web services.)"
control_center_391 = "Test web service"
control_center_392 = "Failed!"
control_center_393 = "Success! The web service was successfully contacted. The page will now refresh to allow you to utilize the services."
control_center_394 = "Failed! Unfortunately, your server was not able to contact the web service, so you will not be able to utilize the services on this page. The reason for this might be because the server is behind a firewall and cannot make outbound calls to the web."
control_center_395 = "Locations of users accessing REDCap"
control_center_396 = "in the past"
control_center_397 = "Uses IP address of users to determine location, excluding survey participants"
control_center_398 = "(representing"
control_center_399 = "unique IP addresses)"
control_center_400 = "IP addresses have not been processed and are not displayed yet."
control_center_401 = "Update map"
control_center_402 = "view projects"
control_center_403 = "month"
control_center_404 = "months"
control_center_405 = "year"
control_center_406 = "hours"
control_center_407 = "week"
control_center_409 = "Create single user"
control_center_410 = "Create users (bulk upload)"
control_center_411 = "New REDCap user accounts (Table-based authentication ONLY) may be created on this page. They may be created one at a time, or they may be created in bulk by uploading an Excel/CSV file containing the usernames and user information. See instructions under each tab below."
control_center_412 = "The user could not be added!"
control_center_413 = "The following user is missing an email address:"
control_center_414 = "The following user has an invalid email address:"
control_center_415 = "has invalid email"
control_center_416 = "Allow ALL users in file to request that projects be created for them by a REDCap admin?"
control_center_417 = "Allow ALL users in file to create or copy projects?"
control_center_418 = "Upload CSV file of new users:"
control_center_419 = "File format:"
control_center_421 = "Download template file"
control_center_422 = "Start Over"
control_center_423 = "The uploaded file did not contain any users. Please try again."
control_center_424 = "The user could not be added!"
control_center_425 = "User was successfully added, and an email with login info was sent to user"
control_center_426 = "A user already exists named"
control_center_427 = "Invalid username:"
control_center_428 = "Please complete all fields"
control_center_429 = "Last Login"
control_center_430 = "Time of last login"
control_center_431 = "User currently logged in?"
control_center_433 = "File Attachments (General)"
control_center_434 = "Upload max file size for general file attachments."
control_center_435 = "(Includes the following: attachments for Descriptive fields, attachments uploaded for Data Resolution Workflow)"
control_center_437 = "Viewing projects accessible by user:"
control_center_439 = "Search"
control_center_440 = "Filter projects by title"
control_center_441 = "User does not exist!"
control_center_443 = "Configuration Check"
control_center_445 = "API Documentation"
control_center_446 = "To-Do List"
control_center_4370 = "Publication Matching"
control_center_4371 = "Institution Keywords: Set the institution name(s) to be explicitly used when searching for publications in online publication databases"
control_center_4372 = "If multiple institutions are used, then separate each institution name with a line break so that each is on its own line."
control_center_4373 = "This module can be used to match REDCap projects to publications listed in online publication databases (currently only PubMed is searched). If enabled, the module will automatically use the Principal Investigators (and their affiliated institutions) listed for your REDCap projects to search online publication databases. Use the Setup tab for general settings and the To-Do List to back-fill information needed for individual PIs (in case some info for them is missing). The PIs you specify will be used in REDCap's nightly search of online publication databases. Please note that PIs will *not* be emailed by this module until the 'P.I. Emailing' setting has been enabled."
control_center_4374 = "If you are not able to set up the REDCap cron job on your web server just yet, you can easily trigger the scheduled jobs via your web browser. To trigger the jobs using a web browser, navigate to"
control_center_4380 = "View all projects"
control_center_4381 = "Time that the user's account will be automatically suspended. User will be notified via email"
control_center_4382 = "Time of account expiration"
control_center_4383 = "Time of account creation"
control_center_4384 = "Non-suspended users"
control_center_4385 = "Suspended or not suspended"
control_center_4386 = "User expiration time set or not"
control_center_4387 = "Expiration time set"
control_center_4388 = "No expiration time"
control_center_4389 = "Enable auto-suspension for Table-based users only (excludes LDAP users)"
control_center_4390 = "Enable auto-suspension for all users"
control_center_4391 = "Auto-suspend users after period of inactivity"
control_center_4393 = "Period of inactivity:"
control_center_4394 = "If using 'LDAP & Table-based' authentication, there will appear an additional choice above to enable auto-suspension only for Table-based users."
control_center_4397 = "Home Page Settings"
control_center_4398 = "Footer Settings (All Projects)"
control_center_4399 = "Miscellaneous Modules"
control_center_4400 = "prior to their suspension, and if the user has a sponsor listed above, the sponsor will be CC'd on that email so that they are aware."
control_center_4401 = "Since you are not using a type of authentication where Table-based users can be utilized, you cannot use this page."
control_center_4402 = "Also, please note that your REDCap user account has been given an expiration date ("
control_center_4403 = "), which means that after that time you will no longer be able to access REDCap. You will, however, be given a warning prior to your account expiration in case you need to inquire about changing the expiration date (if applicable)."
control_center_4404 = "The following user has an invalid sponsor username:"
control_center_4405 = "The following sponsor username is not a valid REDCap username:"
control_center_4406 = "In order to perform a bulk upload to create new users, you need to upload an Excel/CSV file containing the following items: desired REDCap username (column A), the user's first name (column B), the user's last name (column C), the user's email address (column D), an optional institution ID (column E), an optional sponsor username, which is the REDCap username of a secondary contact person (column F), optional user expiration time, which must be in YYYY-MM-DD HH:MM or MM/DD/YYYY HH:MM format (column G) - will assume 00:00 if time is not provided, and miscellaneous comments about the user (column H). See the header example text below for the expected file format. The uploaded file is assumed to contain a header row, so the first row is always ignored. The file should contain only one user per line. Once created, each user will receive an email with login information. If any errors exist in the uploaded file, those errors will be displayed."
control_center_4408 = "User information for"
control_center_4409 = "Editable user attributes"
control_center_4410 = "Statistics & Other Information"
control_center_4411 = "Reset user's password?"
control_center_4412 = "Delete user from the REDCap system?"
control_center_4413 = "Verified"
control_center_4414 = "Not yet verified"
control_center_4415 = "Resend verification email"
control_center_4416 = "Auto-verify email address"
control_center_4417 = "An email was sent to the user for them to verify their email address"
control_center_4418 = "Resend the email to the user for them to verify their email address?"
control_center_4419 = "Resend email"
control_center_4420 = "The user's email address was auto-verified, which means that they no longer need to verify their email account using the verification email sent to their account. They can now freely log in to REDCap. You may wish to notify them about this."
control_center_4421 = "Would you like to auto-verify the user's email address? If so, it means that they will not need to verify their email account using the verification email sent to their account. You should really only do this if they cannot access their email or if for some reason are not receiving the verification emails."
control_center_4422 = "Notify user via email when suspended?"
control_center_4423 = "If enabled, users that have not logged into REDCap or used the API in the past X number of days (specified above) will automatically have their account suspended and (if set to Yes above) will be notified via email of their suspension. If the user has a sponsor (i.e., secondary contact) listed on their account, the sponsor will be CC'd on the email so that they are aware."
control_center_4424 = "Additionally, please be aware that REDCap has a user access policy in place, in which it will auto-suspend a user's account if the user has not logged into REDCap after an extended period of time. For details regarding this, please contact your REDCap administrator."
control_center_4425 = "Please note that if a user has been UNsuspended by an administrator within the period of inactivity, then the user will NOT get auto-suspended."
control_center_4427 = "User Management for Table-based Authentication"
control_center_4428 = "Search by username, first name, last name, or primary email"
control_center_4429 = "Search for user by username, first name, last name, or primary email"
control_center_4431 = "YOUR REDCAP DATABASE STRUCTURE IS INCORRECT!"
control_center_4434 = "TIP: Use only 1-3 words per line, and do not use words such as 'the', 'of', 'a', etc. For example, instead of 'The University of Texas Southwestern University', just use 'University of Texas Southwestern' for best results."
control_center_4436 = "NOTICE: REDCap Base URL does not begin with 'https'"
control_center_4437 = "It appears that you are using a secure HTTPS connection (i.e. SSL). However, your REDCap Base URL does not reflect this. If you will continue using an SSL connection for this server, it is advised that you navigate to the General Configuration page to modify the REDCap Base URL so that it begins with 'https'. Otherwise, many of the REDCap links, such as those sent out via email, will be incorrect."
control_center_4438 = "days from now"
control_center_4439 = "The value you entered for REDCap base URL may not be correct since it does not match the URL above for this webpage. Are you sure it is correct? If so, leave it as is, otherwise please change it."
control_center_4440 = "Recommended value:"
control_center_4441 = "Table-based users only"
control_center_4442 = "LDAP users only"
control_center_4443 = "Transfer user's API token to another user"
control_center_4444 = "You may transfer a user's API token to another user."
control_center_4445 = "This may be done if the current user with the token will have their access revoked from the project or from REDCap, after which their token needs to be maintained by another user (often because it is being used by a program or script). So if the user's current token needs to maintained, the best option is to transfer the token to another user. To do this, select another user from the project using the drop-down list below. NOTE: If you transfer the token to a user that already has an API token, then the new token will overwrite their old one."
control_center_4446 = "Transfer token to selected user"
control_center_4447 = "The API token has been successfully transferred to the user"
control_center_4448 = "Transfer API token from"
control_center_4449 = "and removed from the user"
control_center_4450 = "API token transferred to another user"
control_center_4451 = "This email is simply to notify you that a REDCap administrator has transferred your API token for your REDCap user"
control_center_4452 = "to another REDCap user"
control_center_4453 = "This email is to notify you that a REDCap administrator has transferred an API token to your REDCap user"
control_center_4454 = "from another REDCap user"
control_center_4455 = "for the project named"
control_center_4456 = "Please note that both users have been notified via email regarding this API token transfer."
control_center_4458 = "No Activity"
control_center_4459 = "The table below is an enhanced version of MySQL's process list that displays a comprehensive view of real-time server activity for REDCap. This page can be helpful to troubleshoot any issues with regard to server performance."
control_center_4460 = "Kill"
control_center_4461 = "NOTE: If you wish to allow REDCap administrators to be able to 'kill' any MySQL queries that appear on this page, then someone with back-end access must execute the following query in the MySQL database where the REDCap tables are stored:"
control_center_4462 = "Show full queries"
control_center_4463 = "Don't show full queries"
control_center_4464 = "Kill a MySQL Process?"
control_center_4465 = "Are you absolutely sure you wish to kill MySQL Process ID"
control_center_4466 = "Doing so will prevent the query from completing, as well as other queries to be executed in the same script. Are you sure?"
control_center_4467 = "Success: Killed MySQL process"
control_center_4468 = "ERROR: Could NOT kill MySQL process"
control_center_4469 = "seconds"
control_center_4470 = "page refresh frequency"
control_center_4471 = "Refresh"
control_center_4472 = "Server:"
control_center_4473 = "Database:"
control_center_4474 = "Time:"
control_center_4475 = "REDCap Project ID, User, and URL"
control_center_4476 = "Script Time"
control_center_4477 = "Query Time"
control_center_4478 = "Query State"
control_center_4479 = "Query"
control_center_4480 = "Process ID"
control_center_4481 = "Project ID"
control_center_4482 = "(seconds)"
control_center_4483 = "Stop refresh"
control_center_4484 = "Total Processes:"
control_center_4487 = "Set your new REDCap password"
control_center_4488 = "A REDCap account has been created for you in which your REDCap username is"
control_center_4489 = "Do you wish to reset their password for logging in to REDCap? They will be sent an email with a link that will allow them to set their new password."
control_center_4490 = "with a link to allow them to set a new password."
control_center_4491 = "You will need to manually provide the user with the following link for resetting their password:"
control_center_4492 = "Display user on 'Email Users' page?"
control_center_4493 = "The domain of the email for this user is invalid. (The domain name is the part of the email address after the @ sign.) The only acceptable domain names for email addresses are the following:"
control_center_4494 = "The following user's email address is not acceptable:"
control_center_4495 = "Expiration time for 2-step login code"
control_center_4496 = "All user attributes"
control_center_4497 = "Search Users"
control_center_4498 = "Manage <u>Super</u> API Tokens by User:"
control_center_4499 = "Your Super API Token has been deleted from your REDCap account"
control_center_4500 = "A Super API Token has been created for your REDCap account"
control_center_4501 = "Are you sure you wish to regenerate the user's Super API Token?"
control_center_4502 = "Are you sure you wish to remove the user's Super API Token?"
control_center_4503 = "View user's Super API Token"
control_center_4504 = "You may view the Super API Token for this user by clicking the View Super Token button below."
control_center_4505 = "Super API Token has been deleted"
control_center_4506 = "Create Super Token"
control_center_4507 = "Create new Super API Token for user"
control_center_4508 = "Creating a Super API Token for this user will allow them to create new REDCap projects via the API without any approval needed by a REDCap administrator. Additionally, after creating a new project with a Super API Token, it will provide them with their new project-level API token for the project, which is also given to them without any approval needed by an administrator. It is generally recommended that Super API Tokens only be granted to the most trusted users. Are you sure you wish to create a Super API Token for this user?"
control_center_4509 = "Create new Super API Token"
control_center_4510 = "Super API Token has been created"
control_center_4511 = "Transfer user's Super API Token to another user"
control_center_4512 = "You may transfer a user's Super API Token to another user."
control_center_4513 = "Transfer Super API Token from"
control_center_4515 = "Super API Token"
control_center_4516 = "Organize"
control_center_4517 = "This may be done if the current user with the Super API Token will have their access revoked from REDCap, after which their token needs to be maintained by another user (often because it is being used by a program or script). So if the user's current Super API Token needs to maintained, the best option is to transfer the token to another user. To do this, select another user from the drop-down list below. NOTE: If you transfer the token to a user that already has a Super API Token, then the new token will overwrite their old one."
control_center_4518 = "Super API Token has been transferred"
control_center_4519 = "This email is simply to notify you that a REDCap administrator has transferred your Super API Token for your REDCap user"
control_center_4520 = "You may obtain your Super API Token on your REDCap"
control_center_4521 = "This email is to notify you that a REDCap administrator has transferred a Super API Token to your REDCap user"
control_center_4522 = "You may grant users a Super API Token, which will allow them to create new REDCap projects via the API without any approval needed by a REDCap administrator. Super API Tokens are 64 characters in length (to differentiate them from regular 32-character-long project-level tokens). A user can only have one super token. When a user creates a new project with a Super API Token, it will provide them with their new project-level API token for the project, which is also given to them without any approval needed by an administrator. It is generally recommended that Super API Tokens only be granted to the most trusted users."
control_center_4523 = "Super API Tokens"
control_center_4524 = "Revoke user's Super API Token"
control_center_4525 = "Regenerate user's Super API Token"
control_center_4526 = "If you are viewing the Super API Token of another user, then please be advised that your action of viewing their token will be logged, and the user will be notified via email that you have just viewed their Super API Token."
control_center_4528 = "Another user viewed your Super API Token"
control_center_4529 = "You have been granted a Super API Token, which can be used for creating new REDCap projects via the API's Create Project method. To obtain your super token, click the 'Show token' link below to reveal it on this page."
control_center_4530 = "Show token"
control_center_4531 = "REDCap Home Page"
control_center_4532 = "Request delete project"
control_center_4533 = "Enable email notifications for administrators"
control_center_4534 = "Pending Requests"
control_center_4535 = "Low Priority Pending Requests"
control_center_4536 = "Completed & Archived Requests"
control_center_4537 = "Req #"
control_center_4538 = "Request time"
control_center_4539 = "Request type"
control_center_4540 = "Actions"
control_center_4541 = "When enabled, an email will be sent to the REDCap administrator for each of the actions listed in the tables on this page, in which the requests can be processed by clicking the link in the email or by using the table interface on this page. If this option is left unchecked, no emails will be sent, and all processing of requests must be performed on this page."
control_center_4542 = "Move to low priority section"
control_center_4543 = "Move to pending section"
control_center_4544 = "Not yet processed"
control_center_4545 = "No requests to view"
control_center_4546 = "Listed below are all user-submitted requests that need to be processed by a REDCap administrator."
control_center_4547 = "To approve any request, click the green checkmark button, which will open up a popup window to allow you to process the request on this page. Any pending request can be moved to the low-priority list and then moved back at any time. All processed requests get moved to the 'Completed & Archived' table at the bottom. If you do not need to process a request, you can click the Archive icon, which moves it to the bottom. NOTE: This page will always reflect the current status of all requests, whether or not they were processed using the tables below or using the link inside the email to the administrator (if email notifications are enabled)."
control_center_4548 = "Copy project"
control_center_4549 = "Approve draft changes"
control_center_4550 = "Create project"
control_center_4551 = "Delete project"
control_center_4552 = "Move to prod"
control_center_4553 = "Send email to"
control_center_4554 = "Request Completion Time:"
control_center_4556 = "Request Completed By:"
control_center_4557 = "If the user cannot Export (read) or Import (write), then their API token will be useless unless they have Mobile App rights and are accessing via the Mobile App. NOTE: These rights correspond to the same options seen on the User Rights page for this user on this project."
control_center_4558 = "obtain the <b>cron.php</b> file from the install zip file of the latest REDCap version. (This will be the cron.php file that sits alongside database.php in the zip file.)"
control_center_4559 = "Comment:"
control_center_4560 = "Link Customizations"
control_center_4561 = "Link Actions"
control_center_4562 = "Get Embed Code"
control_center_4563 = "Create Custom Survey Link"
control_center_4564 = "Get Short Survey Link"
control_center_4565 = "You may create a short and easy to remember custom URL that redirects to your public survey. <b>Enter the your desired custom URL</b> that you wish to redirect to your public survey. When submitted, it will check if the URL has already been taken. If not, it will save the custom URL here in your project so that you may continue to use it."
control_center_4566 = "Custom Public Survey URL:"
control_center_4567 = "Are you sure you want to delete the custom survey link?"
control_center_4568 = "Your Custom Public Survey Link was successfully created:"
control_center_4569 = "This new custom survey link will be stored on this page and can be obtained at any time in the future. It can also be deleted, if desired."
control_center_4570 = "Add Users (Table-based Only)"
control_center_4604 = "Modules/Services Configuration"
control_center_4605 = "Plugin, Hook, & External Module Documentation"
control_center_4608 = "Set account expiration"
control_center_4609 = "Unsuspend user"
control_center_4610 = "Suspend user"
control_center_4611 = "Reset selections"
control_center_4612 = "Extend account expiration"
control_center_4613 = "SUCCESS! The user's request has been saved successfully, and they have been notified via email."
control_center_4614 = "Sponsor request -"
control_center_4615 = "is a User Sponsor making a request for one or more of their sponsored users. As an administrator, you must click the link below to review and approve the user's request."
control_center_4616 = "Review and approve sponsor request -"
control_center_4617 = "Your request has been successfully sent to a REDCap administrator. You will be notified once your request has been approved."
control_center_4618 = "NOTE: You will not be able to make another request of the same type until this request has first been approved."
control_center_4619 = "Submit request to administrator?"
control_center_4620 = "It appears that the users listed below are not applicable for the following action:"
control_center_4621 = "Uncheck non-applicable users"
control_center_4622 = "Fixes required before submitting!"
control_center_4623 = "Before this request can be submitted, the users below must be unchecked since this action cannot be applied to them. If you click the 'Uncheck...' button below, it will automatically uncheck all those users, and allow you to re-submit this request."
control_center_4624 = "Users to uncheck"
control_center_4625 = "users (listed below) have been selected for the following action:"
control_center_4626 = "Clicking the submit button below will submit this request to an administrator for the selected users."
control_center_4627 = "As a user sponsor in REDCap, your sponsor request"
control_center_4628 = "has been successfully applied to"
control_center_4629 = "Your sponsor request has been approved:"
control_center_4630 = "Return to your Sponsor Dashboard"
control_center_4631 = "users. If you wish to make more requests, you may visit the Sponsor Dashboard page again at any time."
control_center_4632 = "Time of latest password reset"
control_center_4633 = "Not yet fetched"
control_center_4634 = "Fetch for selected"
control_center_4635 = "View user's projects"
control_center_4636 = "has access to the projects listed below. You may click the project link to navigate to the project, but if you have not been granted access to the project, you will not able to open it."
control_center_4637 = "NOTE: User does not have access to any projects"
control_center_4638 = "Displaying projects for user"
control_center_4639 = " - select users by the projects they can access - "
control_center_4640 = "User Search"
control_center_4641 = "Display only:"
control_center_4642 = "Display User List"
control_center_4643 = "to the following date/time"
control_center_4644 = "(you may modify the value or set it to blank to remove the expiration):"
control_center_4645 = "Dashboard pages:"
control_center_4646 = "Search project title"
control_center_4647 = "Search project title by keyword(s):"
control_center_4648 = "AND / OR"
control_center_4649 = "To find a project in the whole system, you may search by project title and/or by username. Since you are an Administrator, you may access and view any aspect of these projects."
control_center_4650 = "Request applied to the following users:"
control_center_4651 = "(Note: The selected user's Project Folders will not be displayed when searching by project title.)"
control_center_4652 = "Has never logged in"
control_center_4653 = "Request will be applied to the following users:"
control_center_4654 = "Selected users:"
control_center_4656 = "Want an easier REDCap upgrade process?"
control_center_4657 = "Learn how to enable Easy Upgrade"
control_center_4658 = "It appears that your REDCap web server is not able to make outbound HTTP requests to https://redcap.vumc.org, which is the server that generates the list of new REDCap versions available. You should speak to your IT/server staff to ensure it can do so."
control_center_4659 = "The 'redcap' webroot directory ("
control_center_4660 = ") on the REDCap web server is not writable by the REDCap application. REDCap needs to be able to create new directories in that webroot directory. Please adjust the permissions of that directory to allow the application (e.g., Apache, IIS) to be able to write to that directory."
control_center_4661 = "The Easy Upgrade feature cannot be utilized until some small changes are made to the REDCap system to allow it the feature to function. Please review and address the issues below. Once accomplished, return to this page (or reload it) for further instruction."
control_center_4662 = "The MySQL user that REDCap utilizes for database connections does not have sufficient user privileges. It requires higher-level privileges (CREATE, DROP, ALTER, REFERENCES) in order to utilize Easy Upgrade. There are two solutions for this."
control_center_4663 = "<b>Option 1:</b> Increase the privileges of your existing MySQL user. You can do this by simply executing the SQL immediately below."
control_center_4665 = "LTS versions"
control_center_4666 = "Standard Release versions"
control_center_4668 = "Upgrades are available for the versions listed below in which it will display the REDCap version number, a brief description, and release date. This process will download the upgrade zip file from the REDCap Community website and then (if possible) automatically execute the Upgrade SQL script to fully complete the upgrade. Click the button to upgrade to a specific version."
control_center_4669 = "New REDCap versions are available for upgrade"
control_center_4670 = "Easy Upgrade"
control_center_4671 = "Using valid REDCap Community credentials,"
control_center_4672 = "will be downloaded automatically, and the upgrade process will begin immediately thereafter. If for some reason the upgrade process is not able to be completed automatically, it will notify you about how to finish the upgrade manually."
control_center_4673 = "REDCap Community username:"
control_center_4674 = "REDCap Community password:"
control_center_4675 = "You must provide a valid username/password that you (or someone on your REDCap team) uses to login to the"
control_center_4676 = "REDCap Community website"
control_center_4677 = "(If credentials were used previously, they will be pre-filled below.)"
control_center_4678 = "No new REDCap versions are available for upgrade."
control_center_4679 = "Check again"
control_center_4680 = "Auto-Fix"
control_center_4681 = "Click this button to fix the issue automatically."
control_center_4682 = "Your current database table structure does not match REDCap's expected table structure, which means that database tables and/or parts of tables are missing. This can happen if an issue occurs during an upgrade and is not corrected afterward."
control_center_4683 = "Copy the SQL in the box below and execute it on the MySQL database server where the REDCap database tables are stored, then reload this page to run this check again."
control_center_4684 = "Multiple REDCap versions have been detected on this REDCap server that are possible upgrade paths. Some versions might require taking REDCap offline in order to complete the upgrade, while others may not. Listed below are the possible versions to which you may upgrade. Click the link for a given version to navigate to that version's upgrade page."
control_center_4685 = "(fast upgrade - does <u>not</u> require taking REDCap offline)"
control_center_4686 = "(requires taking REDCap offline temporarily)"
control_center_4687 = "Upgrade to"
control_center_4688 = "NOTICE: The Easy Upgrade feature cannot be used if the REDCap web server is using load balancing (multiple application servers). This is because the source code would only get downloaded to a single server (rather than to all of them) during the upgrade process."
control_center_4689 = "Administrator Resources"
control_center_4690 = "REDCap Community"
control_center_4691 = "Project REDCap website"
control_center_4692 = "REDCap Training Materials"
control_center_4693 = "NOTE: While the examples above list the database hostname as"
control_center_4694 = ", that may not be correct for your MySQL user account. For example, the hostname might instead be listed for your MySQL user as"
control_center_4695 = "So you may need to make those adjustments in the example queries above if your configuration is different."
control_center_4696 = "View changelog"
control_center_4697 = "<b>Option 2 (Recommended):</b> Create a new MySQL user with higher privileges that is only used for REDCap upgrades. Below is an example that you may use and execute as-is in MySQL, or you may replace the username and/or password seen in bold in the queries below with the username/password of your choosing. <b>NOTICE:</b> This new MySQL user *MUST* use all the exact same parameters as the current MySQL user (i.e., the connection values listed in the REDCap file database.php) with the exception of username and password."
control_center_4698 = "Select another project"
control_center_4699 = "Re-send account creation email"
control_center_4700 = "This error most likely means that the selected users have successfully logged into REDCap before, so you should <u>try resetting their password</u> instead."
control_center_4701 = "Can create projects?"
control_center_4702 = "Survey Link Lookup"
control_center_4703 = "Enter a REDCap survey link or hash value to find the corresponding project, survey, record and data entry form."
control_center_4704 = "Survey link or hash:"
control_center_4705 = "Can create project and pull medical records using Clinical Data Mart?"
control_center_4707 = "Enter PID to go to project"
control_center_4708 = "URL Shortener"
control_center_4709 = "All-Purpose REDCap URL Shortener (https://redcap.link)"
control_center_4710 = "This URL Shortener can create a random or custom link beginning with <b>https://redcap.link/</b> to be used as a redirect to any URL you wish. Note: This service is provided by Vanderbilt and is hosted on AWS. It is recommended that you utilize this service for REDCap-related matters only."
control_center_4711 = "Create a random short URL"
control_center_4712 = "Enter any web address to shorten, e.g. https://..."
control_center_4713 = "Create a custom short URL"
control_center_4714 = "OPTION 1:"
control_center_4715 = "OPTION 2: Define a custom alias"
control_center_4716 = "Please provide a URL to shorten."
control_center_4717 = "Please provide a custom alias to use."
control_center_4718 = "The value provided is not a valid URL. Please enter a valid web address."
control_center_4719 = "The URL"
control_center_4720 = "has been shortened to the following:"
control_center_4721 = "Request Copy"
control_center_4722 = "Server info:"
control_center_4723 = "NOTICE: The current recommended versions of PHP for REDCap are PHP"
control_center_4724 = "While your current PHP version is compatible with REDCap, we suggest that you consider upgrading to one of the recommended versions in the near future."
control_center_4726 = "PID of project with a public survey"
control_center_4728 = "<b>'Move to Production status' survey:</b><br>Force users to complete this public survey before moving a project to Production status."
control_center_4729 = "<b>'Move to Analysis/Cleanup status' survey:</b> Force users to complete this public survey before moving a project to Analysis/Cleanup status."
control_center_4730 = "<b>'Mark project as Completed' survey:</b><br>Force users to complete this public survey before marking a project as Completed."
control_center_4732 = "Sorry, but the PID for the custom public survey you just entered matches another PID/survey in this section. The custom survey PIDs cannot be reused here but must instead be unique across all of the project status transition surveys. Please change the value."
control_center_4733 = "REDCap Administrator Videos"
control_center_4734 = "Administrator Privileges"
control_center_4735 = "Set REDCap Administrator Privileges"
control_center_4736 = "Access to all projects and data with maximum user privileges"
control_center_4737 = "Manage user accounts"
control_center_4738 = "Modify system configuration pages"
control_center_4739 = "Perform REDCap upgrades"
control_center_4740 = "Install, upgrade, and configure External Modules"
control_center_4741 = "Set administrator privileges"
control_center_4742 = "Access to Control Center dashboards"
control_center_4743 = "This page may be used to grant administrator-level privileges to users in this REDCap installation. Granting admin privileges to users allows them to access certain pages or functionality used for administering REDCap, which may include managing user accounts, accessing users' projects, modifying system configurations, performing upgrades, etc. The different categories of admin privileges can be seen in the table below and are described in detail if you click the link below. If a user has at least one admin privilege, they are considered a REDCap administrator and thus will be able to access the Control Center; however, they will only be able to access the things to which they have been granted access. You may"
control_center_4744 = "Administrators"
control_center_4745 = "Search users to add as admin"
control_center_4746 = "It appears that the user"
control_center_4747 = "does not exist as a valid username in REDCap. Please enter a valid username."
control_center_4748 = "Please check one or more of the permissions checkboxes for the user to which you want to grant administrator privileges."
control_center_4749 = "has now been granted one or more administrator privileges."
control_center_4750 = "has already been granted administrator privileges and exists in the table above. Closing this dialog will take you to this user in the table."
control_center_4751 = "read-only"
control_center_4752 = "Please be aware that you have unchecked ALL the administrator privileges for this user"
control_center_4753 = ", thus they are no longer considered an administrator and will not be displayed on this page anymore. However, this user can always be re-added anytime in the future by granting them an admin privilege again, if you wish."
control_center_4754 = "Because you have restricted admin privileges, this page is read-only, and no settings can be modified."
control_center_4755 = "View descriptions of all admin privileges"
control_center_4756 = "User can access the 'Administrator Privileges' page (i.e., this page), and can set admin rights for any user."
control_center_4757 = "User has full access to all REDCap projects in the system and has maximum privileges within those projects. Within the Control Center interface, the user can access and use the following pages that pertain to project administration: To-Do List, Edit Project Settings, Survey Link Lookup, and API Tokens."
control_center_4758 = "User can access, modify, and (if using Table-based authentication) create REDCap user accounts. The following pages can be accessed and utilized: Browse Users, Add Users, User Allowlist, and Email Users."
control_center_4759 = "User can modify settings on all system configuration pages in the Control Center, which includes all pages listed under the 'Miscellaneous Modules' and 'System Configuration' sections on the left-hand menu. Note: If the user does not have this specific privilege but does have at least one other administrator privilege, they may still access and view the system configuration pages but only in read-only mode."
control_center_4760 = "User can access tools used for upgrading the REDCap software, including notifications about new versions available and also accessing the Easy Upgrade feature (if enabled). Note: This admin privilege does not apply when upgrading REDCap using traditional methods (i.e., when not using the Easy Upgrade) because the traditional upgrade process occurs mostly outside of the REDCap user interface in a database client and via direct server access."
control_center_4761 = "User has the ability to install External Modules from the REDCap Repo, and can enable and configure them at the system level. This does not apply to enabling and configuring an External Module in a project, which is governed by other user privileges. Note: If the user does not have this specific privilege but does have at least one other administrator privilege, they may still access and view the External Modules page in the Control Center but only in read-only mode."
control_center_4762 = "User can access and utilize all pages listed under the 'Dashboard' section of the Control Center's left-hand menu."
control_center_4763 = "add a new admin"
control_center_4764 = "at the bottom of the page."
control_center_4765 = "This user is already listed as a REDCap user in the system. If you need to add this user, you must first delete the user from the whole system via the Browse Users page, and then return here to add them again."
control_center_4766 = "Please note that the date/time entered for the user expiration is either today's date or a date in the past. If this is in error, you should consider changing this value. If this is correct, then simply click the Save button again to create this user."
control_center_4767 = "TIP: As users are completing the public surveys identified below, you may track which survey response corresponds to the user's project. This is done by adding the field variable <code>project_id</code> to any of the projects identified below (if longitudinal, the field must exist in the first event of the first arm in the project). If the 'project_id' field exists, then when the user completes a project transition survey below, the PID of the project for which they are completing the survey will then be saved in the 'project_id' field of those identified below. This allows you to know which survey response applies to which project of the user that is completing the survey."
control_center_4768 = "Custom Surveys for Project Status Transitions (optional):"
control_center_4769 = "The fields below allow you to utilize public surveys to capture custom information from users when projects transition to a new status (i.e., project creation, copy project, move to Production status, move to Analysis/Cleanup status, mark as Completed). This allows administrators to create custom surveys to capture all the info they desire from users during these project transitions. The survey will be presented inside an iframe on the page, in which the user must complete the survey before completing the process on the page. You may use any or none of these fields. NOTE: Administrators will not be forced to complete any of the public surveys set below but will be exempt from this process."
control_center_4770 = "<b>'Create/Copy Project' survey:</b><br>Force users to complete this public survey before creating a new project."
control_center_4771 = "Until"
control_center_4772 = "Set an expiration date"
control_center_4773 = "Your current PHP version has not yet been verified as being compatible with this version of REDCap."
control_center_4774 = "REDCap Language Library"
control_center_4775 = "<b>IMPORTANT:</b> When adding the cron job as a new scheduled task to the Windows server, be sure to set the task to \"<u>Run a new instance in parallel</u>\" under the Settings tab in the Windows Task Scheduler."
control_center_4776 = "View Project"
control_center_4777 = "Banned IP Addresses"
control_center_4778 = "Below is the list of all IP addresses that have been banned/blocked for this REDCap installation. Anyone that attempts to load any REDCap page (including surveys) from a banned IP address will be immediately presented with a message stating that they will not be able to use REDCap in any way because their IP address has been banned. The IP addresses listed here are IPv4 or IPv6 addresses that have been blocked manually using this page or have been banned automatically via the Rate Limiter feature (enabled on the General Configuration page in the Control Center)."
control_center_4779 = "No IP addresses are currently blocked."
control_center_4780 = "Please add some IP addresses"
control_center_4781 = "All IP addresses have been removed from the IP Address blocklist."
control_center_4782 = "Add IP addresses to blocklist"
control_center_4783 = "You may add a single IP address or multiple IP addresses at once to the blocklist by simply copy and pasting their IP address(es) in the text box below, separating them with <b>one IP address per line</b>."
control_center_4784 = "IP Addresses have been added to blocklist."
control_center_4785 = "The following IP addresses were blocked:"
control_center_4786 = "The following IP addresses could NOT be added to blocklist:"
control_center_4787 = "No IP addresses were blocked. They may have already existed in the blocklist."
control_center_4788 = "IP Address Blocklist"
control_center_4789 = "Are you sure you wish to remove the IP address"
control_center_4790 = "from the blocklist?"
control_center_4791 = "Are you sure you wish to remove ALL IP addresses from the blocklist?"
control_center_4792 = "Time Of Ban"
control_center_4793 = "IP Address(es)"
control_center_4794 = "Please enter the Time of Ban."
control_center_4795 = "You have entered an invalid IP address:"
control_center_4796 = "Set or change user's sponsor"
control_center_4797 = "to the following username:"
control_center_4798 = "already exists in selected users list. You can not assign same user sponsor for user. Please enter a another username."
control_center_4799 = "is suspended. You can not assign suspended user sponsor for user. Please enter a another username."
control_center_4800 = "The Sponsor username is blank. Please enter a valid username."
control_center_4801 = "<b>Note:</b> You can not assign user sponsor with username listed in selected users OR suspended users."
control_center_4803 = "Database Query Tool"
control_center_4804 = "This page allows administrators to directly query REDCap's MySQL/MariaDB database. You may enter an SQL query into the text box below to execute it. Since only read-only queries are supported (i.e., show, select, explain), this tool is not able to modify database tables in any way. You may also save custom queries on the left via a popup dialog. Saving a custom query allows you to easily run the query at any time by simply clicking a link on this page's left-hand menu."
control_center_4805 = "NOTICE: This tool is currently DISABLED and cannot be used until someone with special privileges enables it. Because the page allows you to view data directly from the back-end MySQL/MariaDB database, this tool can only be enabled by someone with direct database access, in which they must execute the query below in the MySQL/MariaDB database where the REDCap tables are stored. Once the query has been run, reload this page."
control_center_4806 = "NOTICE: Only administrators with the admin right 'Access to all projects and data with maximum user privileges' can access this page."
control_center_4807 = "Database Activity Monitor"
control_center_4808 = "Dashboards & Activity"
control_center_4809 = "User Activity Log"
control_center_4810 = "User Activity Graphs"
control_center_4811 = "Custom Queries:"
control_center_4812 = "Add or edit custom queries"
control_center_4813 = "REDCap database tables:"
control_center_4814 = "SQL Query:"
control_center_4815 = "Execute"
control_center_4816 = "Can only accept the following query types:"
control_center_4817 = "You may add as many custom SQL queries as you wish so that you may run them on this page at any time. Provide a title and the SQL for each custom query, then click the Save button to store them, after which they will appear as clickable links on the left side of this page. Once saved, you may click a custom query at any time to run it in real time."
control_center_4818 = "Save custom queries"
control_center_4819 = "The queries have been successfully saved. The page will now reload to reflect the changes."
control_center_4820 = "ERROR: All fields must have a value. Please enter a value for each text box or else remove any empty ones."
control_center_4821 = "Query Title:"
control_center_4822 = "SQL:"
control_center_4823 = "Delete query"
control_center_4824 = "Add another query"
control_center_4825 = "ERROR: All queries must begin with either 'select', 'show', or 'explain'."
control_center_4826 = "Export results (CSV)"
control_center_4828 = "This email was sent because you requested that your REDCap password be reset for the user"
control_center_4829 = "Click the link below to set your new password and log in."
control_center_4830 = "Set custom text that is included in the email to the user after entering an INVALID username when attempting to recover their password."
control_center_4831 = "NOTE: Password recovery custom text can be be used when utilizing one of the 'X & Table-based' authentication methods in which external users might mistakenly attempt to reset their password, which is not possible using REDCap. For example, you may provide a link to direct them to the correct place to reset their password for their external account."
control_center_4832 = "Date of last REDCap upgrade:"
control_center_4833 = "Copy version numbers to clipboard"
control_center_4834 = "to navigate to the REDCap upgrade page."
control_center_4835 = "<b>Unable to determine if your server supports TLS 1.2 or not - RECOMMENDED</b>"
control_center_4836 = "TEST 2: Check TLS 1.2 Support."
control_center_4837 = "<b>SUCCESSFUL!</b> - Your server supports TLS 1.2"
control_center_4838 = "<b>Your server does not seem to support TLS 1.2 - CRITICAL:</b><br><br>See the"
control_center_4839 = "REDCap Community Post"
control_center_4840 = "for detail."
control_center_4841 = "Unable to determine if this module can communicate with MyCap Central. - RECOMMENDED"
control_center_4842 = "TEST 3: Check communication with MyCap Central."
control_center_4843 = "<b>SUCCESSFUL!</b> - Your module can communicate with MyCap Central."
control_center_4844 = "<b>Your server does not seem to communicate with MyCap Central. - CRITICAL."
control_center_4845 = "Choose project and participant"
control_center_4846 = "In order to run the secondary tests, a MyCap-enabled project must exist in the system, and that project must have at least one record in it. In order to execute the API tests, please select a MyCap-enabled project from the list and participant from the selected project."
control_center_4847 = "Select MyCap-enabled project:"
control_center_4848 = "Select participant:"
control_center_4849 = "Execute API Tests"
control_center_4850 = "Secondary Tests (MyCap API Tests)"
control_center_4851 = "This executes a total of"
control_center_4852 = "API requests. It may take a few minutes. <br>Please wait..."
control_center_4853 = "This page will test your current MyCap configuration to determine if any errors exist  that might prevent it from functioning properly."
control_center_4854 = "Basic tests"
control_center_4855 = "<b>TEST 1: Check internal API calls.</b><br>Enter this link on your mobile device to ensure the endpoint is accessible from external devices."
control_center_4856 = "<b>SUCCESSFUL!</b> - MyCap can make internal API calls."
control_center_4857 = "<b>NOT making API Call  - CRITICAL:</b> MyCap cannot make internal API calls. We expected a status code of 200 and content to be returned from the request.      <br>Note: Secondary Tests cannot be executed unless this test is passed."
control_center_4858 = "Path to web server's PHP.INI configuration file:"
control_center_4859 = "Other useful info:"
control_center_4860 = "Path to web server's PHP error log file:"
control_center_4862 = "Unsuspend user from REDCap"
control_center_4863 = "ERROR: An unknown error occurred!"
control_center_4864 = "Enable allowlist"
control_center_4865 = "Disable allowlist"
control_center_4866 = "Remove all users from the allowlist (excludes super users)?"
control_center_4867 = "2) Enable and Do Not Add All Existing Users"
control_center_4868 = "1) Enable and Add All Existing Users"
control_center_4869 = "Sorry, but you cannot delete yourself from the User Allowlist."
control_center_4870 = "Remove user"
control_center_4871 = "from the allowlist?"
control_center_4872 = "Remove user from allowlist"
control_center_4873 = "Add users to allowlist"
control_center_4874 = "GB"
control_center_4875 = "MB"
control_center_4876 = "Save Changes"
control_center_4877 = "Display"
control_center_4878 = "Save"
control_center_4879 = "Saved!"
control_center_4880 = "Time of Ban:"
control_center_4881 = "e.g., Epic, Cerner, EMR, EDW"
control_center_4882 = "e.g., urn:oid:1.2.840.114350.1.13.478.3.7.5.737384.14<br>e.g., urn:oid:1.1.1.1.1.1"
control_center_4883 = "Note for Epic customers: This is the HL7 Root item in the Epic ID Type Record (IIT) specified in the Patient ID Type field of the Integration Configuration Record (FDI)."
control_center_4884 = "Please enter a value for the base URL endpoint first"
control_center_4885 = "ERROR"
control_center_4886 = "Cron History"
control_center_4887 = "Start"
control_center_4888 = "End"
control_center_4889 = "Job Name (External Module)"
control_center_4890 = "Description"
control_center_4891 = "Duration (sec)"
control_center_4892 = "Max Run Time (min)"
control_center_4893 = "Standalone Launch"
control_center_4894 = "Mapping Helper"
control_center_4895 = "EHR access"
control_center_4897 = "auto-login"
control_center_4898 = "No auto-login"
control_center_4899 = "<b>Notice:</b> The web server and the cron job are using different PHP.INI configuration files. The cron job uses the file located at: <code>{0}</code>. This may lead to undesired side effects if the configurations differ (e.g., different time zone settings). It is often recommended that the cron job use the same configuration file as the web server."
control_center_4900 = "Navigate to page"
control_center_4901 = "Enter a <b>project id</b> (or <b>cc</b> for Control Center), optionally followed by one of the following target codes:"
control_center_4902 = "Tip: Use shortcuts without project id or cc to navigate inside a project or within the Control Center, respectively. Holding <code>CTRL</code> while pressing <code>ENTER</code> or clicking on a destination link will open that destination in a new tab. Use <code>CTRL</code><code>ALT</code><code>N</code> to move focus to the navigation input or to toggle this popup when focus is already set on the navigation input."
control_center_4903 = "(read replica)"
control_center_4904 = "(primary)"
control_center_4905 = "NOTICE: The cron job URL above is a publicly accessible URL, so anyone calling that web address can trigger the cron job. This is not really a concern unless the current server  is a test/staging server that is a copy of the production server, in which triggering the cron might send out unwanted emails that should come from the production server rather than this one."
control_center_4906 = "2-Step Login Expiration (minutes)"
control_center_4907 = "Project's data table in the database:"
control_center_4908 = "Project's logging table in the database:"
control_center_4909 = "Want to move the project's data to another redcap_dataX table? If this project contains a lot of data and has pages that often appear to load slower than expected, consider visiting the {0} to move the project's data from redcap_data to another redcap_dataX table in the database. This *may* improve the performance of the project."
control_center_4910 = "Move Project Data page"
control_center_4911 = "REDCap server's current time: {0} ({1} timezone)"
control_center_4912 = "Your browser's current time: {0}"
control_center_4913 = "Please do NOT post about this on REDCap Community unless the Repair SQL fails to resolve this issue."
control_center_4914 = "My Custom Query Folders"
control_center_4915 = "STEP 2: Assign Your Custom Query To Folders"
control_center_4916 = "Hide queries already assigned"
control_center_4917 = "Custom Query Folders are a way to organize your queries by putting them into groups. You may create new folders below and then assign queries to them on the right. A custom query can be assigned to multiple folders at the same time. To reorder your folders, you can drag and drop them in the left-hand table."
control_center_4918 = "Custom Query Folders"
control_center_4919 = "Select queries below to add to this folder"
control_center_4920 = "Import custom queries (CSV)"
control_center_4921 = "You can add new custom queries or update the custom query title or SQL query of any existing query by uploading a CSV file with a new Custom Queries configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing Custom Queries. <b>NOTE:</b> Custom Queries can be renamed by simply changing the Custom Query title or SQL query in the CSV file. Custom Queries cannot be deleted using the CSV file. If you wish to delete a Custom Query, please do so using the specified \"Add or edit custom queries\" popup provided on this page."
control_center_4922 = "Select your CSV file of Custom Queries to be added or modified:"
control_center_4923 = "Upload Custom Queries (CSV)"
control_center_4924 = "Export custom queries (CSV)"
control_center_4925 = "custom queries were updated."
control_center_4926 = "One or more records are missing title. Please enter a value or else remove any empty ones."
control_center_4927 = "One or more records are missing SQL query. Please enter a value or else remove any empty ones."
control_center_4928 = "Custom query options"
control_center_4929 = "Organize queries"
control_center_4930 = "Use query context:"
control_center_4931 = "Smart Variables Context:"
control_center_4932 = "Toggle to view the query as executed (indicated by a red button/frame). Click again to toggle back to the original query."
control_center_4933 = "Note: When a project id is not set, smart variable piping will be limited considerably."
control_center_4934 = "Note: Not all smart variables can be used on this page."
control_center_4935 = "Providing Query Context"
control_center_4936 = "<p>When <i>Use query context</i> is checked, context (project id, record name, event id, etc.) can be set. This context is used to resolve <b>[<i class='fa-solid fa-bolt fa-xs' style='margin:0 1px;'></i>] Smart Variables</b> in SQL queries. Which of these can be resolved depends on the extent to which the context is defined. For example, a project id is required for most smart variables (except the ones that are explicitly set on this page).</p><p>A few additional smart variables are available on this page only: <code>[survey-id]</code>, <code>[user-id]</code>.</p><p>Furthermore, when query context is enabled, clicking on a table in the list of REDCap database tables will automatically add <code>WHERE</code> clauses for a number of fields when corresponding values can be derived from the available context.</p><p><b>Tip:</b> While context can be set manually, there are shortcuts on various pages that will automatically set context values. Such shortcuts are available, e.g., on data entry and survey pages, as well as on various other project pages such as <i>Project Home</i> and <i>Record Home Page</i> (in the actions dropdown). Using the <i>Navigate to page</i> widget with the <code>cc dqt</code> command, in most cases, will also set the context of the page it is used on.</p><p>To clear the context, simply uncheck <i>Use query context</i> and re-select a database table.</p>"
control_center_4937 = "(has at least one<br>Admin privilege)"
control_center_4938 = "Recent Errors"
control_center_4939 = "retained for {0} days"
copy_project_02 = "To make an exact duplicate of the current project"
copy_project_05 = "Since only REDCap administrators can copy a project, clicking the button below will send a request to a REDCap admin, who will make the copy for you. An email will be sent to your address"
copy_project_06 = "when this has been done."
copy_project_07 = "Also copy the following:"
copy_project_11 = "Please change the title of the new project so that it is different from the original."
copy_project_15 = "records total)"
copy_project_16 = "set the details below for the new project you are creating, and click the button at the bottom. This will copy over all project forms and their fields, and optionally, you may also copy the current users and any reports that have been created."
copy_project_18 = "The titles of your surveys are listed below:"
copy_project_24 = "Note: Automated Invitations will all be set to 'Not Active' status in the new project."
copy_project_30 = "(including data access groups and assignments)"
copy_project_31 = "Note: Alerts & Notifications will all be set to 'Deactivated' status in the new project."
copy_project_34 = "All records ("
copy_project_35 = "Users and their user rights"
copy_project_36 = "User roles"
copy_project_37 = "Report folders"
copy_project_38 = "Project dashboards"
copy_project_39 = "Data quality rules"
copy_project_40 = "Project folders to which this project is assigned"
copy_project_41 = "Project bookmarks"
copy_project_42 = "Custom record status dashboards"
copy_project_43 = "Form Display Logic settings"
copy_project_44 = "Multi-Language Management translations"
copy_project_45 = "Survey Queue and Automated Survey Invitation settings"
copy_project_46 = "External Module configuration settings (modules will be disabled by default)"
copy_project_47 = "Note: All settings for the MyCap Mobile App will be copied to the new project (including App Design settings and Task settings; excluding messages and sync issues). A new configuration will automatically be published in the new project as version 0."
copy_project_48 = "Since you are not a REDCap administrator, the MyCap Mobile App will initially be disabled in the new project, so you will need to go through the normal admin approval process in order to enable it."
copy_project_49 = "Notice: Please be advised that this project contains {0} Dynamic SQL field(s). Thus, after copying this project, you may want to consider if the SQL query for the field(s)  needs to be modified in order to work correctly in the new project."
copy_project_50 = "Please be aware that if you select to copy all records below, the survey completion time for any survey responses will not be copied with the normal project data. This is because the survey completion times are considered a form of logging, and because a project's logging is never copied when copying a project, the survey completion times are also not copied."
copy_project_51 = "Additionally, since your project contains one or more surveys, please note that although you may change the project title above for your new project, all survey settings (including the survey title) for each survey will be copied and remain as-is in the copied project. If want to change your survey titles, survey instructions, or other settings after copying this project, you are welcome to do so on the Online Designer page using the Survey Settings button for each data collection instrument."
create_project_01 = "Project title:"
create_project_12 = "Project's purpose:"
create_project_13 = "How will it be used?"
create_project_14 = "Select One"
create_project_15 = "Practice / Just for fun"
create_project_16 = "Operational Support"
create_project_17 = "Research"
create_project_18 = "Quality Improvement"
create_project_19 = "Other"
create_project_20 = "Please specify:"
create_project_21 = "Basic or bench research"
create_project_22 = "Clinical research study or trial"
create_project_23 = "Translational research 1 (applying discoveries to the development of trials and studies in humans)"
create_project_24 = "Translational research 2 (enhancing adoption of research findings and best practices into the community)"
create_project_25 = "Behavioral or psychosocial research study"
create_project_26 = "Epidemiology"
create_project_27 = "Repository (developing a data or specimen repository for future use by investigators)"
create_project_28 = "Approved: Project Copied"
create_project_30 = "Your REDCap request has now been approved and the project has been copied as the following new project:"
create_project_31 = "Access your new project in REDCap"
create_project_32 = "Approved: New Project Created"
create_project_33 = "The REDCap project that you requested has now been approved and created:"
create_project_34 = "Name of P.I. (if applicable):"
create_project_35 = "IRB number (if applicable):"
create_project_36 = "VUnetID of P.I. (if applicable):"
create_project_37 = "Grant number (if applicable):"
create_project_41 = "The settings below cannot be modified once the project is in production status."
create_project_42 = "Design your project:"
create_project_43 = "STEP 1: Choose the type of project you want to build"
create_project_44 = "Each option below represents a different type of project that can be built. If you merely want to build a survey and collect results with it from participants, then the 'Single Survey' might be best for you. If you are interested in traditional project data collection where everyone entering data has been authorized as a REDCap user, then Data Entry Forms is likely the most appropriate project type. The 'Single Survey + Data Entry Forms' project type is useful if you wish to seed new records in your project using survey responses from participants, thus the survey response initiates the data collection (e.g., a pre-screening survey), and afterward, authorized REDCap users may append more data to each survey response/record using the data collection instruments that you have defined."
create_project_45 = "(e.g., traditional database)"
create_project_47 = "STEP 2: Choose collection format for data entry forms"
create_project_48 = "The 'classic' data collection format is the best option if all data collection instruments will only need to be used once for each subject/record in the project. If some instruments need to be utilized repeatedly to collect data numerous times (e.g., using an instrument named 'Visit Data' over ten visits for the same subject), the 'longitudinal / repeating forms' option will likely be best. Additionally, the longitudinal format also allows the use of the scheduling module, if needed (see more info below)."
create_project_49 = "Classic"
create_project_50 = "(each form available for use <u>once</u> for each subject/record)"
create_project_51 = "Longitudinal / repeating forms"
create_project_52 = "(each form available for use <u>one or more times</u> for each subject/record)"
create_project_53 = "Enable the scheduling module?"
create_project_54 = "The scheduling module can generate schedules for your project calendar that are auto-generated from project-defined events (e.g., visits, time-points). Scheduling is only available for projects using longitudinal data collection."
create_project_55 = "First name"
create_project_56 = "MI"
create_project_57 = "Last name"
create_project_58 = "Name of P.I. as cited in publications (if applicable):"
create_project_59 = "Email of P.I. (if applicable)"
create_project_60 = "Additional options:"
create_project_61 = "Enable the randomization module?"
create_project_63 = "User privileges can be set to allow only certain users to be able to set up the randomization, perform the randomization, or view the allocation dashboard to view progress. If someone is given 'Randomize' privileges, they will be able to view and modify any existing data already collected for the randomization strata fields (if stratification is used) when they are performing the randomization, even if they do not specifically have form-level rights to view the form on which a strata field exists. Thus Randomize rights trumps form-level rights in this way, but only for the randomization strata fields."
create_project_64 = "(e.g., data capture + follow-up surveys; pre-screening survey + follow-up data capture)"
create_project_66 = "Choose a project template"
create_project_67 = "Empty project (blank slate)"
create_project_68 = "Use a template (choose one below)"
create_project_69 = "Template description"
create_project_71 = "After creating data collection instruments in the steps below, you and other users in this project may enter data for those instruments. Additionally, you may enable any instrument as a survey and then collect data for that instrument from survey respondents. The only difference is who will be entering the data: project users, survey participants, or both. For surveys, you may utilize a Participant List for emailing your recipients and also to track who has taken your survey(s). And if your first data collection is enabled as a survey, then you may use a public survey link, which is a single link that can be emailed to all participants or even posted on a website."
create_project_72 = "I Agree"
create_project_73 = "Template title"
create_project_74 = "select template"
create_project_77 = "No templates are available"
create_project_78 = "Add templates (Admins only)"
create_project_79 = "Project Templates"
create_project_80 = "Any given project in REDCap may be designated by an Administrator as a project template. Once designated as a template, that project will become available as an option when creating a new project, in which a user may choose that project as a template from which to start when creating their new project. When creating a new project using a template, all of the template's data collection instruments, fields, surveys, and general project settings will be added to the new project at the point of creation. Below are some options for managing all the templates available, including adding, editing, or removing a project as a template."
create_project_81 = "List of project templates"
create_project_82 = "[Project title missing]"
create_project_83 = "Add new template"
create_project_84 = "Edit template"
create_project_85 = "choose another project"
create_project_86 = "Added!"
create_project_87 = "Project:"
create_project_88 = "Below you may add or edit the template's title and description for this project as they will be seen by users when creating a new project. Designating a project as a template allows it to be used as a quick starting point when users create a new project, as well as a way to illustrating various project designs in REDCap."
create_project_90 = "Edit template"
create_project_91 = "Project is used as a template"
create_project_92 = "Project is not used as a template"
create_project_93 = "Remove as template"
create_project_94 = "Show more"
create_project_95 = "Are you sure you wish to remove the project below as a template project? If so, the project will remain fully accessible to its users, but it will merely not be listed any longer in the list of project templates."
create_project_96 = "The project has now been successfully removed as a template project."
create_project_97 = "The page will now reload to reflect the changes."
create_project_98 = "The title and/or description of the project template has now been successfully modified."
create_project_99 = "The project has now been successfully added as a template project, and it will thus now be visible as a choice in the list of project templates from which users may choose when creating a new project."
create_project_100 = "In order to designate an existing REDCap project as a template, first choose the project below."
create_project_101 = "Edited!"
create_project_102 = "Deleted!"
create_project_103 = "(sorted by title)"
create_project_104 = "Enabled?"
create_project_105 = "Enable as template?"
create_project_106 = "(will not appear in Project Template list)"
create_project_107 = "Project notes (optional):"
create_project_109 = "Upload a REDCap project XML file (CDISC ODM format)"
create_project_110 = "Select XML file:"
create_project_112 = "File already uploaded by user."
create_project_113 = "By default, new projects will use the 'classic' data collection format, which is the best option if all data collection instruments will only need to be used once for each record in the project. If some instruments need to be utilized repeatedly a specific *finite* number of times (e.g., using an instrument named 'Visit Data' over ten visits for the same subject), then 'longitudinal' data collection will likely be best. Additionally, the longitudinal format also allows one to utilize the scheduling module, if needed."
create_project_114 = "NOTE: If you are looking to repeat instruments *without limit* (i.e., ad hoc repetition)"
create_project_115 = ", then you should instead use the 'repeating instruments and events' option seen on the Enable Optional Modules step on the Project Setup page. With longitudinal data collection, you must up front create all the events you wish to utilize for reusing an instrument more than once. However, with 'repeating instruments and events',"
create_project_116 = "you can repeat them a different number of times *without limit for each record*."
create_project_129 = "ERROR: An error occurred while creating the project. The process could not be completed. Details are provided below."
create_project_130 = "Clinical Data Mart: Create a project and pull multiple medical records from"
create_project_132 = "Project creation option:"
create_project_133 = "Description of the project's use or purpose (displayed on the My Projects page)"
create_project_134 = "Copy all the records/data from the template?"
create_project_135 = "Please use the search field below to find the existing REDCap project that you would like to designate as new template."
create_project_136 = "Search by project title"
create_project_137 = "Source REDCap version:"
create_project_138 = "File creation date:"
create_project_139 = "This file does not appear to be a valid REDCap project XML file!"
create_project_140 = "[unknown]"
custom_reports_02 = "Number of results returned:"
custom_reports_03 = "Total number of records queried:"
custom_reports_06 = "The query returned no results!"
custom_reports_13 = "Print Page"
custom_reports_14 = "Edit Report"
custom_reports_15 = "Live filters:"
custom_reports_16 = "Apply live filters?"
custom_reports_17 = "One or more live filters have been selected on this report. Do you wish to apply the live filters to the data export, thus producing the same data set that you currently see displayed on the report?"
custom_reports_18 = "Apply live filters selected on this report"
custom_reports_19 = "Report execution time:"
custom_reports_20 = "(\"records\" = total available data across all events and/or instances)"
dashboard_01 = "Loading statistics"
dashboard_02 = "No activity for this period"
dashboard_03 = "All User Activity for"
dashboard_04 = "events"
dashboard_06 = "View graphs for:"
dashboard_07 = "Past Week"
dashboard_08 = "Past Month"
dashboard_09 = "Past 3 Months"
dashboard_10 = "Past 6 Months"
dashboard_11 = "Past Year"
dashboard_12 = "All"
dashboard_13 = "Page Hits"
dashboard_14 = "Loading chart"
dashboard_15 = "Projects Created"
dashboard_16 = "Logged Events"
dashboard_17 = "Active Users"
dashboard_18 = "First-Time Visitors"
dashboard_21 = "Event"
dashboard_23 = "Count"
dashboard_24 = "Total projects"
dashboard_30 = "Total logged events"
dashboard_31 = "Past 30 minutes"
dashboard_32 = "Today"
dashboard_33 = "Past 7 days"
dashboard_34 = "Past 30 days"
dashboard_35 = "Total files sent using Send-It"
dashboard_36 = "Data collection instruments"
dashboard_37 = "Fields on all data collection instruments"
dashboard_38 = "Records"
dashboard_39 = "Loading"
dashboard_41 = "Calendar events"
dashboard_42 = "Schedules generated"
dashboard_43 = "Longitudinal (using multiple events)"
dashboard_44 = "Double Data Entry"
dashboard_45 = "MySQL database server"
dashboard_46 = "Web server"
dashboard_47 = "External space usage for"
dashboard_48 = "System Statistics"
dashboard_50 = "Active users"
dashboard_51 = "User Statistics"
dashboard_52 = "Your stats were last reported on"
dashboard_53 = "Report my stats to the REDCap Consortium"
dashboard_54 = "NEVER"
dashboard_55 = "Automatic"
dashboard_56 = "Manual"
dashboard_57 = "Your current method for sending REDCap stats is"
dashboard_58 = "The button above is for manual stats submission only."
dashboard_59 = "Is the automatic method not working? If not, try the Manual method."
dashboard_60 = "(excludes 'practice' projects)"
dashboard_61 = "Project attributes (all projects)"
dashboard_62 = "Space usage"
dashboard_65 = "Data Transfer Service (DTS)"
dashboard_66 = "Users (table-based authentication)"
dashboard_67 = "This refers to users that have performed some kind of action that was logged in REDCap (e.g., created project, entered data) as opposed to someone merely logging in and browsing the webpages."
dashboard_68 = "Non-active users"
dashboard_69 = "Surveys"
dashboard_70 = "Project purpose"
dashboard_71 = "Users currently logged in"
dashboard_72 = "Project users"
dashboard_73 = "Survey participants"
dashboard_75 = "Avg/mdn # projects a user can access"
dashboard_77 = "(What stats are sent?)"
dashboard_79 = "Survey responses"
dashboard_80 = "Survey participants (in participants list)"
dashboard_81 = "view types"
dashboard_82 = "view subcategories"
dashboard_83 = "[Subcategory not selected]"
dashboard_84 = "Survey invitations sent"
dashboard_85 = "Responded"
dashboard_86 = "Not responded"
dashboard_88 = "Projects Moved to Production"
dashboard_89 = "Past Day"
dashboard_90 = "If sending stats manually, you will need to click the button at the bottom of the Control Center's Notifications & Reporting page."
dashboard_91 = "Aggregate Counts for Activity for "
dashboard_92 = "Suspended users"
dashboard_94 = "Statistics from your REDCap server will be sent to the REDCap Consortium website to track the progress of REDCap across the entire consortium. Project data will NOT be sent. The following represents what stats will be sent:"
dashboard_96 = "Projects created from a project template"
dashboard_97 = "Modules utilized"
dashboard_98 = "Total user accounts"
dashboard_99 = "Daily User Logins"
dashboard_100 = "(excluding suspended users)"
dashboard_102 = "Alternative Method: Report site stats"
dashboard_103 = "Sorry, but you may only submit your stats once a day. Thanks!"
dashboard_104 = "Users utilizing the mobile app"
dashboard_105 = "Projects initialized on the mobile app"
dashboard_106 = "Projects with data imported from the mobile app"
dashboard_108 = "Surveys using Text-to-Speech functionality"
dashboard_109 = "Database Usage (MB)"
dashboard_110 = "Usage by Uploaded Files (MB)"
dashboard_111 = "To-Do List"
dashboard_113 = "Repeating instruments or events (either)"
dashboard_114 = "Repeating instruments"
dashboard_115 = "Repeating events"
dashboard_116 = "Repeating instruments and events (both)"
dashboard_117 = "Repeating instruments/events"
dashboard_118 = "Try auto-sending stats (recommended)"
dashboard_119 = "e-Consent"
dashboard_120 = "Projects with surveys utilizing e-Consent"
dashboard_121 = "PDF consent files stored via e-Consent"
dashboard_122 = "Alerts (for all projects - excluding deactivated alerts)"
dashboard_123 = "Projects with one or more alerts"
dashboard_124 = "Median # users per project (prod/analysis-cleanup)"
dashboard_125 = "counts of total users, active users, and users who have logged in, type of authentication used, the REDCap version number, a count of the project purposes, a listing and count of all Shared Library instruments being utilized, a listing of all publication ID numbers for publications that have been matched to REDCap projects (via Publication Matching module), a count of projects utilizing certain modules (e.g., randomization, Clinical Data Pull), and a count of production, development, and analysis/cleanup projects."
dashboard_126 = "FHIR Statistics"
dashboard_127 = "Concurrent Users/Respondents"
dashboard_128 = "SendGrid email service for Alerts & Notifications"
dashboard_129 = "Twilio telephony services"
dashboard_130 = "Mosio SMS services"
dashboard_131 = "Mosio Two-Way Text Messaging (SMS) Services"
data_access_groups_01 = "Access to certain project records may be limited by using Data Access Groups (DAGs), in which only users within a given Data Access Group can access records created by users within that group. This may be useful in the case of a multi-site or multi-group project that requires that groups not be able to access another group's data."
data_access_groups_02 = "Below you can create Data Access Groups for this project and afterward assign any current user to that group. You may delete the group at any time, if you wish. To rename an existing Data Access Group, simply click the group name in the table below and type the new name."
data_access_groups_03 = "RESTRICTED:"
data_access_groups_04 = "You do not have permission to view this page because you have been assigned to a Data Access Group."
data_access_groups_06 = "Click to rename group"
data_access_groups_07 = "VIDEO: How to use Data Access Groups"
data_access_groups_08 = "DAG Switcher:"
data_access_groups_09 = "Users assigned to Data Access Groups (DAGs) can optionally be assigned to multiple *potential* DAGs, in which they may be given the privilege of switching in and out of specific DAGs on their own whenever they wish. To assign a user to multiple DAGs, check the checkboxes below for that user. At least two DAGs must be checked for a user in order for them to use the DAG Switcher. NOTE: This does not override a user's <u>current</u> DAG assignment, as set above or on the User Rights page."
data_access_groups_10 = "Rows are DAGs"
data_access_groups_11 = "Rows are Users"
data_access_groups_12 = "Administrators see all!"
data_access_groups_13 = "Current Data Access Group:"
data_access_groups_14 = "Select the Data Access Group to which you would like to switch:"
data_access_groups_15 = "Switch"
data_access_groups_16 = "Switch Data Access Group"
data_access_groups_17 = "Successfully switched to"
data_access_groups_18 = "The DAG Switcher feature is disabled while viewing a record on a data entry form or Record Home Page. If you wish to utilize the DAG Switcher, you may navigate outside the current record to do so."
data_access_groups_19 = "Display options:"
data_access_groups_20 = "Enable multiple Data Access Groups for users"
data_access_groups_21 = "Once you have created DAGs, if you would like your users to be in multiple DAGs, you may use the optional DAG Switcher feature to allow users to move themselves in and out of specific DAGs on their own."
data_access_groups_22 = "If you wish to assign users to multiple Data Access Groups, this can be done using the DAG Switcher feature at the bottom of this page. With it, you can place a user into several *potential* DAGs, after which the users can move themselves in and out of those specific DAGs on their own at any time. When assigned to multiple DAGs, the user will see a blue banner at the top of every project page, which will present them with the option to switch to another DAG. NOTE: Users may not move themselves into another DAG unless someone with rights to this page has explicitly granted them privileges to be in multiple DAGs."
data_access_groups_23 = "To assign users to <u>multiple groups</u>, use the DAG Switcher at the bottom."
data_access_groups_24 = "We're sorry, but the DAG Switcher feature cannot be used when there are a large number of users and/or DAGs in the project (if Users X DAGs > 10,000), so the DAG Switcher has been disabled in this project. Our apologies for the inconvenience."
data_access_groups_25 = "Incorrect setup for DAG Switcher! It appears that you have been given the ability to use the DAG Switcher; however, your current Data Access Group has not been enabled for you in the DAG Switcher. Please have someone in your project with appropriate rights enable your current Data Access Group in the DAG Switcher for you. You will not be able to switch yourself in and out of DAGs until this is fixed."
data_access_groups_26 = "Upload or download DAGs/User-DAG assignments"
data_access_groups_27 = "Import data access groups (CSV)"
data_access_groups_28 = "Export data access groups (CSV)"
data_access_groups_29 = "Upload User-DAG assignments (CSV)"
data_access_groups_30 = "Download User-DAG assignments (CSV)"
data_access_groups_31 = "Due to the large amount of users and/or DAGs in this project, the DAG Switcher table is not loaded by default. Click the button to display the DAG Switcher."
data_access_groups_32 = "Display the DAG Switcher"
data_access_groups_ajax_08 = "Users in group"
data_access_groups_ajax_09 = "Delete<br>group?"
data_access_groups_ajax_12 = "Assign user"
data_access_groups_ajax_13 = "Select User"
data_access_groups_ajax_14 = "to"
data_access_groups_ajax_16 = "No Assignment"
data_access_groups_ajax_17 = "You must first select a user!"
data_access_groups_ajax_18 = "Unique group name"
data_access_groups_ajax_19 = "The unique group name is auto-generated from the Data Access Group name that has been defined for each group. The unique group names can be used for importing data on the Data Import Tool page and via the REDCap API."
data_access_groups_ajax_20 = "Data Access Group names for"
data_access_groups_ajax_21 = "Data Access Group label"
data_access_groups_ajax_22 = "select a group"
data_access_groups_ajax_23 = "[No Assignment]"
data_access_groups_ajax_24 = "[Not assigned to a group]"
data_access_groups_ajax_25 = "Number of records in group"
data_access_groups_ajax_26 = "* Can view ALL records"
data_access_groups_ajax_28 = "has been deleted!"
data_access_groups_ajax_29 = "has been created!"
data_access_groups_ajax_30 = "has been assigned to Data Access Group"
data_access_groups_ajax_31 = "is no longer assigned to a Data Access Group!"
data_access_groups_ajax_32 = "Assign user to a group:"
data_access_groups_ajax_33 = "Select Role"
data_access_groups_ajax_35 = "The group could not be deleted because users or roles are still assigned to it. Unassign all users and roles first, and then you can then delete the group."
data_access_groups_ajax_36 = "Users may be assigned to any data access group."
data_access_groups_ajax_38 = "Press ENTER to save"
data_access_groups_ajax_40 = "You may assign a user to a Data Access Group by selecting the username and group name below and then clicking the 'Assign' button. Once assigned to a Data Access Group, the user will be able to see ONLY the project records created by themselves and others in that group. This includes being able to view records on data entry forms, in reports, and in exported data sets. Users can be un-assigned from a group by selecting the user name and selecting 'No Assignment'."
data_access_groups_ajax_41 = "Group ID number"
data_access_groups_ajax_42 = "The Group ID number is automatically generated by REDCap, and is used when the record auto-numbering feature in a project has been enabled, in which any records created by someone assigned to a Data Access Group (DAG) will automatically have its record name prepended with the Group ID number and a dash/hyphen. For example, the first three records for a DAG might get automatically named 98-1, 98-2, and 98-3 if the Group ID number is 98, whereas without utilizing DAGs in a project, the record auto-numbering mechanism would instead name the records 1, 2, and 3, respectively. The prepended Group ID number provides an inherent grouping that allows the records to be sorted and grouped together naturally when viewing the list of records in a project. The Group ID number is displayed in the table on this page so that users are aware of what each DAG's Group ID number is."
data_access_groups_ajax_43 = "The group could not be deleted because one or more records are still assigned to it. Unassign all records first, and then you can then delete the group."
data_access_groups_ajax_44 = "You can add new DAGs to the project or update the DAG name of any existing DAGs by uploading a CSV file with a new DAGs configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing DAGs. <b>NOTE:</b> DAGs can be renamed by simply changing the DAG name in the CSV file. DAGs cannot be deleted using the CSV file. If you wish to delete a DAG, please do so using the specified links for each DAG on this page."
data_access_groups_ajax_45 = "Select your CSV file of DAGs to be added or renamed:"
data_access_groups_ajax_46 = "You can assign users to any data access group by uploading a CSV file. The format for the CSV upload file can be acquired by exporting the CSV file of your existing User-DAG assignments. <b>NOTE:</b> If you wish to modify an existing mapping, you *must* provide its unique username and group name. If the 'redcap_data_access_group' column is not provided, user will not assigned to any group."
data_access_groups_ajax_47 = "Select your CSV file of User-DAG Assignment to be added or modified:"
data_access_groups_ajax_48 = "The data access group name for unique group name"
data_access_groups_ajax_49 = "The data access group name"
data_access_groups_ajax_50 = "groups were added or updated. Note: If you just created a new group, you will now need to assign user(s) to a group."
data_access_groups_ajax_51 = "The username for unique group name"
data_access_groups_ajax_52 = "User-DAG assignments were updated."
data_access_groups_ajax_53 = "occurs in more than one record."
data_access_groups_ajax_54 = "<b>Note: </b>You can assign a user to only one Data Access Group. If you wish to assign users to multiple Data Access Groups, this can be done using the DAG Switcher feature at the bottom of this page."
data_access_groups_ajax_55 = "The group could not be deleted because one or more folders in the File Repository are restricted to this Data Access Group. Please delete all DAG-restricted folders first that are associated with this DAG, and then you can then delete the group."
data_comp_tool_01 = "for Double Data Entry"
data_comp_tool_02 = "Compare"
data_comp_tool_03 = "This page may be used for comparing project records that have been entered by designated data entry persons. Select a record from the list below and hit the 'Compare' button. A comparison table will then be displayed showing the differences between the records. Only records that have been entered by both data entry persons will be displayed in the selection box below."
data_comp_tool_04 = "This page may be used for comparing two records currently in the project. Select a record from each of the lists below and hit the 'Compare' button. A comparison table will then be displayed showing the differences between the two records."
data_comp_tool_05 = "Since you have been assigned to a Data Access Group, you are only able to view records from your group."
data_comp_tool_06 = "You did not select a record."
data_comp_tool_07 = "The new record may not have been saved."
data_comp_tool_08 = "has now been created by merging the values you selected from records"
data_comp_tool_09 = "RECORD CREATED!"
data_comp_tool_10 = "The two records you selected"
data_comp_tool_11 = "are the same record."
data_comp_tool_16 = "The table below compares the two records named"
data_comp_tool_17 = "Only the fields that have differing values are listed below. If you need to correct or change the value of one of the records below, simply click on the data displayed in red, and it will take you to that form for that particular record."
data_comp_tool_18 = "These two records have already been merged into the record named"
data_comp_tool_19 = ", which is displayed below."
data_comp_tool_20 = "MERGE THEM?"
data_comp_tool_21 = "If you wish to merge selected values from the two records below into a NEW third record, you may "
data_comp_tool_22 = "click here to merge them"
data_comp_tool_23 = "Instructions for merging records:"
data_comp_tool_24 = "In the table below, only the fields that have differing values for the existing two records are displayed. Since you are merging these two records, you will need to decide which of those two values you wish to include in the new record you are creating. You may also choose to enter a new value rather than selecting one from the existing records."
data_comp_tool_25 = "Simply click on the dot in each cell to select that field's value as the value to be included for the NEW third record you will be creating. When you are done making your selections, click the Merge Records button at the bottom to create the new record."
data_comp_tool_26 = "Label"
data_comp_tool_27 = "(field name)"
data_comp_tool_29 = "Choose one of the existing values<br/>or enter a new value"
data_comp_tool_31 = "(merged)"
data_comp_tool_32 = "New Value"
data_comp_tool_33 = "Merge Records"
data_comp_tool_34 = "The two records named"
data_comp_tool_35 = "are identical. No differences were found."
data_comp_tool_37 = "If you wish to merge these records into a new record named"
data_comp_tool_38 = "Create Record"
data_comp_tool_39 = ", then click the 'Create Record' button below."
data_comp_tool_41 = "A merged file named"
data_comp_tool_42 = "also exists."
data_comp_tool_43 = "Choose a record"
data_comp_tool_44 = "Compare selected record"
data_comp_tool_45 = "Compare all records"
data_comp_tool_46 = "Differences were found between the two records named"
data_comp_tool_47 = "MERGED"
data_comp_tool_48 = "<b>NOTICE: The Data Comparison Tool does not *fully* support the Repeating Instruments and Events feature</b>, which appears to be enabled in this project. Data can be compared (and even merged if using Double Data Entry), but it will only allow comparison and merging of Instance #1 of a repeating instrument or repeating event. Thus all other repeating data will be ignored on this page. Also, all non-repeating data can still be compared and merged."
data_entry_03 = "OR type a new "
data_entry_04 = "and hit the TAB key"
data_entry_08 = "successfully edited"
data_entry_16 = "Incomplete Records"
data_entry_17 = "Complete Records"
data_entry_23 = "Unverified Records"
data_entry_24 = "Choose an existing"
data_entry_25 = "Show Unverified Records above"
data_entry_26 = "Hide Unverified Records drop-down"
data_entry_31 = "Enter a new or existing"
data_entry_39 = "must provide value"
data_entry_46 = "Add new record"
data_entry_49 = "DELETE RECORD"
data_entry_55 = "Return to the Record Home Page for"
data_entry_56 = "This project is using Auto-Numbering for records and is also using Double Data Entry. Using both at the same time will produce errors in your data. Please ask your project administrator to turn off one of these two features."
data_entry_62 = "Select a file then click the 'Upload File' button"
data_entry_63 = "Max file size:"
data_entry_64 = "Loading..."
data_entry_65 = "Upload in progress..."
data_entry_66 = "Listed below is the history of all data entered for the variable"
data_entry_67 = "for"
data_entry_68 = "You must now supply the reason for the data changes being made on this page in the text box below."
data_entry_69 = "Reason for changes:"
data_entry_70 = "You must enter a reason for the data changes."
data_entry_72 = "Your data was successfully saved, but you did not provide a value for some fields that require a value. Please enter a value for the fields on this page that are listed below."
data_entry_73 = "Provide a value for..."
data_entry_74 = "Ignore and go to next form"
data_entry_76 = "Ignore and leave record"
data_entry_84 = "Check again"
data_entry_85 = "This conflict is in error"
data_entry_88 = "Partial Responses"
data_entry_89 = "Complete Responses"
data_entry_91 = "-- select record --"
data_entry_92 = "-- select response --"
data_entry_95 = "You may view an existing record/response by selecting it from one of the drop-down lists below. The records are separated into each drop-down list according to their status for this particular data collection instrument."
data_entry_96 = "To create a new record/response, click the button below."
data_entry_97 = "To create a new record/response, type a new value in the text box below and hit Tab or Enter. To quickly find a record without using the drop-downs, the text box will auto-populate with existing record names as you begin to type in it, allowing you to select it."
data_entry_98 = "Unverified Responses"
data_entry_101 = "Response is only partial and is not complete."
data_entry_102 = "Total survey responses:"
data_entry_105 = "DUPLICATE VALUE!"
data_entry_112 = "Select another record"
data_entry_117 = "Return Code for participant to continue survey:"
data_entry_119 = "survey not yet taken"
data_entry_120 = "Last survey response:"
data_entry_121 = "Search for existing"
data_entry_124 = "Choose an existing response"
data_entry_125 = "Secondary unique field"
data_entry_129 = "Once you are finished making changes to your instruments in Draft Mode, you will be able to share your instruments to the REDCap Shared Library."
data_entry_137 = "(blank)"
data_entry_138 = "Data Search"
data_entry_139 = "Choose a field to search"
data_entry_141 = "(excludes multiple choice fields)"
data_entry_142 = "Search query"
data_entry_143 = "Begin typing to search the project data, then click an item in the list to navigate to that record."
data_entry_145 = "Searching..."
data_entry_146 = "Survey response is read-only"
data_entry_147 = "You have not been given permission to edit survey responses. However, your permissions may be changed on the User Rights page in order to allow editing of survey responses."
data_entry_148 = "Survey response is editable"
data_entry_149 = "You have permission to edit this survey response from its original values."
data_entry_150 = "(now editing)"
data_entry_151 = "In order to begin editing the response, you must click the Edit Response button above."
data_entry_163 = ")"
data_entry_166 = "No one"
data_entry_167 = "Survey responses are not able to be edited once a participant has completed a survey. They are read-only."
data_entry_172 = "The drop-down list for choosing a record cannot be displayed because this project has exceeded"
data_entry_173 = "records"
data_entry_174 = "Edit response"
data_entry_175 = "Continue on to Next Form"
data_entry_176 = "Displayed below is a table listing all existing records/responses and their status for every data collection instrument (and if longitudinal, for every event). You may click any of the colored buttons in the table to open a new tab/window in your browser to view that record on that particular data collection instrument. Please note that if your form-level user privileges are restricted for certain data collection instruments, you will only be able to view those instruments, and if you belong to a Data Access Group, you will only be able to view records that belong to your group."
data_entry_177 = "Displaying record"
data_entry_178 = "Legend for status icons:"
data_entry_179 = "No records exist yet"
data_entry_181 = "View data history"
data_entry_182 = "Unlock form"
data_entry_183 = "This data collection instrument has been locked, so if fields on this instrument caused the Data Quality rules listed below to be violated, those fields cannot be modified unless this instrument is unlocked. So if you have Locking/Unlocking privileges, you may consider unlocking this instrument so that you may change any field values that caused the violations. Or if you do not wish to modify any field values, you may simply close this pop-up."
data_entry_184 = "Since you have Locking/Unlocking privileges, you may click the 'Unlock form' button to unlock this instrument."
data_entry_185 = "FORM IS LOCKED!"
data_entry_186 = "The value entered must be 100 characters or less in length"
data_entry_188 = "Are you sure you wish to PERMANENTLY delete this record and its data?"
data_entry_189 = "This will delete ALL DATA for ALL INSTRUMENTS for this record."
data_entry_190 = "This process is permanent and CANNOT BE REVERSED."
data_entry_191 = "Leave without saving changes"
data_entry_192 = "Stay on page"
data_entry_193 = "Save your changes?"
data_entry_194 = "Are you sure you wish to leave this page?"
data_entry_195 = "If you have made any data changes on this page, they will be lost if you leave without saving them."
data_entry_196 = "Below you may choose to 1) save your changes and leave the page, 2) abandon your changes and leave the page, or 3) stay on the current page."
data_entry_197 = "Save changes and leave"
data_entry_198 = "Are you sure you wish to close the page? If you have made any data changes on this page, then they will be lost if you close the page now. IF YOU DO NOT WISH TO ABANDON YOUR DATA CHANGES, click the 'Stay on page' button below and then save your changes."
data_entry_199 = "SAVE YOUR CHANGES?"
data_entry_202 = "Modify instrument"
data_entry_203 = "Value removed!"
data_entry_204 = "(One selection allowed per column)"
data_entry_205 = "(no data saved)"
data_entry_206 = "Save Record"
data_entry_207 = "-- Cancel --"
data_entry_210 = "Save & Go To Next Form"
data_entry_211 = "Upload Instrument"
data_entry_212 = "Save & Mark Survey as Complete"
data_entry_215 = "Save & Return Later"
data_entry_216 = "through"
data_entry_217 = "Adaptive Instrument"
data_entry_218 = "This instrument is a computer adaptive test (CAT), so its questions are generated dynamically based on answers given. Because it is dynamic, it can only be taken in survey form, and all fields below are thus permanently locked and uneditabled."
data_entry_219 = "This survey response cannot be edited because this instrument is a computer adaptive test (CAT). It is thus read-only."
data_entry_220 = "This survey is a computer adaptive test (CAT). Please note that some settings below have been disabled because they cannot be utilized for a CAT. CATs are taken one question at a time, and their questions are generated dynamically based on answers given. It is highly recommended that CATs require the participant to answer each question and not to skip any, but if absolutely necessary, you may allow participants to skip any given question on the survey by setting the option below to 'Yes'."
data_entry_221 = "To begin the adaptive instrument, click the Open Survey button below."
data_entry_224 = "E-signed on"
data_entry_225 = "Displaying:"
data_entry_226 = "Instrument status only"
data_entry_227 = "Lock status only"
data_entry_228 = "E-signature status only"
data_entry_229 = "All status types"
data_entry_230 = "Lock and E-signature status"
data_entry_231 = "Return Code for participant to edit the completed response:"
data_entry_232 = "The gray circle icon denotes a Form Status of 'Incomplete' (0), in which no data has been entered on that instrument. This is different from the red status icon, which denotes an 'Incomplete' status but has had data entered on it. SPECIAL NOTE: The gray icon status excludes calculated field values, which can be automatically calculated when a user is on another instrument and saved in the background by REDCap. So if the instrument does contain some calculated fields that get values automatically calculated and saved for them, the status icon will not change to red until you navigate into that instrument and click the Save button or until you perform a data import of values into that instrument."
data_entry_233 = "ERROR: You are not allowed to download PDFs containing data because currently you have 'No Access' data export rights."
data_entry_234 = "Delete data for THIS FORM only"
data_entry_235 = "Delete data for THIS EVENT only"
data_entry_237 = "DELETE ALL DATA ON THIS FORM FOR RECORD"
data_entry_238 = "DELETE ALL DATA ON THIS EVENT FOR RECORD"
data_entry_239 = "Are you sure you wish to PERMANENTLY delete this record's data on THIS INSTRUMENT ONLY?"
data_entry_240 = "Are you sure you wish to PERMANENTLY delete this record's data for ALL INSTRUMENTS on THIS EVENT ONLY?"
data_entry_241 = "Also, this survey response will be reverted back to Incomplete survey status as if the survey had never been taken."
data_entry_243 = "Are you sure you wish to PERMANENTLY delete this record's data on THIS INSTRUMENT ONLY for THIS EVENT ONLY?"
data_entry_246 = "Instance"
data_entry_247 = "Add new"
data_entry_248 = "[signature]"
data_entry_249 = "Auto-scoring Instrument"
data_entry_250 = "This instrument is an auto-scoring instrument. It can only be taken in survey form, and all fields below are thus permanently locked and uneditabled."
data_entry_253 = "To begin the auto-scoring instrument, click the Open Survey button below."
data_entry_254 = "This survey response cannot be edited because this instrument is an auto-scoring instrument. It is thus read-only."
data_entry_255 = "(Auto-scoring)"
data_entry_256 = "Cannot modify auto-scoring instrument!"
data_entry_257 = "This instrument cannot be modified in any way because it is an auto-scoring instrument, which means that its questions and final scores are utilized using a service outside of REDCap. You may, however, rename or delete the instrument."
data_entry_258 = "Auto-scoring Instrument Settings"
data_entry_259 = "This survey is an auto-scoring instrument. Please note that some settings below have been disabled because they cannot be utilized for an auto-scoring instrument. Auto-scoring instruments are taken one question at a time. It is highly recommended that auto-scoring instruments require the participant to answer each question and not to skip any (otherwise a score cannot be calculated), but if absolutely necessary, you may allow participants to skip any given question on the survey by setting the option below to 'Yes'."
data_entry_260 = "Type to begin searching"
data_entry_261 = "Displaying Data Access Group"
data_entry_262 = "Please note that although the value entered here is obfuscated and not readable, the value will be visible outside of this page to the individuals that are administering this survey."
data_entry_263 = "Please note that although the value entered here is obfuscated and not readable on this page, the value will be visible outside of this page (e.g., in a report or data export) to the individuals that are administering this project."
data_entry_264 = "Share instrument in the Library"
data_entry_265 = "Are you sure you wish to close the survey? Any responses you have added on this page will be lost if you close the survey now. IF YOU DO NOT WISH TO ABANDON YOUR CHANGES, click the 'Stay on page' button below and then click the button at the bottom of the page to save your changes."
data_entry_266 = "Sorry, but this data entry form contains one or more fields used in randomization, and since the current record has already been randomized, you will NOT be allowed to delete all data for this form."
data_entry_267 = "Sorry, but this event contains one or more fields used in randomization, and since the current record has already been randomized, you will NOT be allowed to delete all data for this event."
data_entry_268 = "Sorry, but this event contains one or more data entry forms that have been locked. Thus you will NOT be allowed to delete all data for this event until a user with locking/unlocking privileges first unlocks all locked forms on this event for this record."
data_entry_271 = "The fields listed below had values entered that are not considered valid. Please note that <b>the invalid values were *NOT SAVED*.</b> If you wish to save a correct value for them, please re-enter a value for these fields and re-submit the page."
data_entry_272 = "Fields with invalid values:"
data_entry_273 = "ERROR: The form is locked. Your submitted changes were not saved. Data on the form cannot be modified unless the form is unlocked first."
data_entry_274 = "ERROR: You do not have record locking/unlocking privileges!"
data_entry_275 = "Save & Add New Instance"
data_entry_276 = "Save & Go To Next Instance"
data_entry_279 = "Simultaneous users - Data editing capabilities are disabled (read-only mode)"
data_entry_280 = "To prevent data entry conflicts, you will not be allowed to edit this record on this form until the other user has left the page. Until then, you may click the button below at any time to check if they have left, or you may edit other forms for this record and check back later."
data_entry_281 = "Many statuses (mixed)"
data_entry_282 = "Many statuses (all same)"
data_entry_283 = "Multiple repeating instruments are locked"
data_entry_284 = "Multiple repeating instruments are e-signed"
data_entry_287 = "More save options"
data_entry_288 = "Save & Exit Form"
data_entry_289 = "Save & ..."
data_entry_290 = "The option chosen for this button will become its default for you next time in this project."
data_entry_291 = "Click the down arrow button to view more save options."
data_entry_292 = "Save & Stay"
data_entry_293 = "Watch in-depth video"
data_entry_296 = "In-depth overview of how to set up and utilize the Repeating Instruments and Repeating Events functionality in both classic and longitudinal projects."
data_entry_297 = "Delete this event"
data_entry_298 = "Delete this instance of this event"
data_entry_299 = "Are you sure you wish to PERMANENTLY delete this record's data for ALL INSTRUMENTS on THIS INSTANCE of THIS EVENT ONLY?"
data_entry_300 = "DELETE ALL DATA ON THIS EVENT INSTANCE FOR RECORD"
data_entry_303 = "REDCap has the ability to repeat a data collection instrument or an entire event of instruments an unlimited number of times without having to specify the amount needed. This is sometimes called one-to-many data collection, in which a project can have one or more repeating parts. For example, if each record in a hypothetical project represents a person, then one might have a repeating instrument for medications, one for family members, one or adverse events, and one for collecting data over multiple visits (or weekly surveys), so that each repeating element is connected to the overall record but can repeat independently of the other instruments. So if using repeating instruments or repeating events, each record in the project can have a different number of repeated instances of any given instrument or event. One record may have five medications, but another may have two or none, for example. Such flexibility makes this feature very powerful, and setting up repeating instruments and/or repeating events in a project is very quick and easy. The repeating instruments/events feature can be enabled and set up by clicking the Enable button in the Optional Modules section on the Project Setup page."
data_entry_304 = "Repeating Instruments (for classic and longitudinal projects)"
data_entry_305 = "Classic projects (i.e., in which the longitudinal module is not enabled) can utilize repeating instruments as a very simple way of doing longitudinal data collection. When traditionally using the longitudinal module in a project, one downside is that one must specify all the events (i.e., the repetitions of instruments) ahead of time, making sure to build out the maximum number of events that one might need, even though all of them likely won't be used by all records. However, with the repeating instruments functionality, one does not need to specify how many repetitions will needed ahead of time; one can simply repeat an instrument an unlimited amount of times. It is important to note that multiple instruments in a project can be enabled as repeating instruments (even all of them, if one wishes). Projects utilizing the longitudinal module can have repeating instruments as well, in which one or more instruments on any defined event can be set to repeat within that event. The repeating instruments functionality behaves very much the same way in both classic and longitudinal projects."
data_entry_306 = "Repeating Events (for longitudinal projects only)"
data_entry_307 = "If a project has the longitudinal module enabled, it can utilize the repeating events feature, which works somewhat differently than the repeating instruments feature. While the repeating instruments feature allows one to repeat a given instrument as a single unit, the repeating events feature allows one to repeat an entire event of instruments together in unison. This might be useful if one has several instruments whose data correlates together, such as completing multiple surveys back to back for a specific time-point or visit, for example. Previously, one may have had to create X number of identical events to capture repeating data for the instruments on those events (e.g., Week 1, Week 2, ...), but the repeating events feature makes this much simpler by allowing one to create only one single event that can be repeated in unlimited fashion."
data_entry_308 = "Enabling Surveys for Repeating Instruments"
data_entry_310 = "Reports and Data Exports with Repeating Instruments and Events"
data_entry_311 = "If one creates a report that contains data from a repeating instrument or repeating event, a field named 'redcap_repeat_instance' will be included that represents the instance number, which is an auto-numbered value (starting with '1') that gets incremented each time the instrument/event is repeated. And if the report contains data specifically from a repeating instrument (as opposed to a repeating event), then a field named 'redcap_repeat_instrument' will additionally be included that represents the instrument name that denotes to which instrument the row of data belongs. These two fields will only be included automatically in the report or data export if data originates from a repeating instrument or event. Note: Each repeated instance of an instrument or event will be displayed as a new row in the report or export file. This means that if a medications survey is repeated three times for one record, for example, it will be displayed as three rows in the report."
data_entry_312 = "Record deleted!"
data_entry_313 = "Download PDF of record data for all instruments"
data_entry_314 = "Download PDF of record data for all instruments/events"
data_entry_315 = "Download ZIP file of all uploaded documents"
data_entry_316 = "Rename record"
data_entry_317 = "to the following record name:"
data_entry_318 = "could not be changed to"
data_entry_319 = "because that record already exists! Please try again."
data_entry_321 = "NOTE: This will rename the record for the current arm ONLY."
data_entry_323 = "Assign to Data Access Group"
data_entry_324 = "(or unassign/reassign)"
data_entry_325 = "Assign record"
data_entry_326 = "to one of the following Data Access Groups:"
data_entry_329 = "ERROR: You did not change the Data Access Group assignment from the record's current assignment. Please try again."
data_entry_330 = "How to assign to a Data Access Group"
data_entry_331 = "When a record is first being created, it can be assigned to a Data Access Group here on the data entry form. But once a record exists, you <b>must use the record action drop-down at top of the Record Home Page</b> to assign/reassign/unassign the record to a Data Access Group."
data_entry_332 = "records per page"
data_entry_333 = "[Default dashboard]"
data_entry_334 = "Dashboard displayed:"
data_entry_335 = "Create custom dashboard"
data_entry_336 = "Custom Record Dashboard"
data_entry_337 = "You may create your own custom version of the Record Status Dashboard by setting up the configuration options below. Only users with Project Setup/Design privileges will be able to create custom dashboards. Once a custom dashboard has been created, it will be viewable to all users in the project."
data_entry_338 = "Dashboard title:"
data_entry_339 = "Description / instructions:"
data_entry_340 = "Group columns by instrument or event:"
data_entry_341 = "Sort by:"
data_entry_342 = "Filter by arm:"
data_entry_343 = "Select instruments:"
data_entry_344 = "Select instruments/events:"
data_entry_345 = "Header orientation:"
data_entry_346 = "Filter logic:"
data_entry_347 = "Save dashboard"
data_entry_348 = "Delete dashboard"
data_entry_349 = "Refresh dashboard"
data_entry_350 = "View dashboard"
data_entry_351 = "Your custom record status dashboard has been successfully saved. Click the button below to refresh the page to view your dashboard."
data_entry_352 = "Display all arms"
data_entry_353 = "Show legend"
data_entry_354 = "Your custom record status dashboard has been successfully deleted. The page will now be reloaded to display the default dashboard."
data_entry_355 = "Are you sure you wish to delete this custom record status dashboard?"
data_entry_358 = "(Optional) Displayed near top of page"
data_entry_359 = "Use 'Vertical' to transpose headers for a more compact display."
data_entry_360 = "Horizontal (default)"
data_entry_361 = "Vertical"
data_entry_362 = "Grouping by Event will display event name at top spanning over its instruments, whereas grouping by Instrument will do vice versa."
data_entry_363 = "(Optional) Include/exclude specific instruments (to display less columns)"
data_entry_364 = "(Optional) Filter the records displayed based on conditional logic"
data_entry_365 = "Display all arms in a tabbed display or display only a single arm"
data_entry_366 = "Sort the records by the value of a specific field in either ascending or descending order"
data_entry_367 = "Sort the records by the value of a specific event's field in either ascending or descending order"
data_entry_368 = "ERROR: This custom dashboard's filter logic is not syntactically correct and contains an error. It must first be fixed in order for this dashboard to display properly."
data_entry_369 = "Remove"
data_entry_370 = "Recommended: Leave this page while survey is in session"
data_entry_371 = "Since you just opened the survey for this instrument, <b>it is recommended that you leave this page</b> without saving any changes so that you <u>do not overwrite any existing survey responses</u> that were collected for the survey in another browser tab."
data_entry_372 = "No records were returned"
data_entry_373 = "select one of your existing REDCap projects to add below"
data_entry_376 = "Add patient to project"
data_entry_377 = "View patient in project"
data_entry_378 = "new items to adjudicate"
data_entry_379 = "No new items to adjudicate"
data_entry_380 = "Not a viable project"
data_entry_381 = "Enter new record name:"
data_entry_382 = "You may add this patient to this REDCap project by clicking the 'Create record' button below, which will create a new record in the project and will add the patient's ID number (i.e., medical record number) to that record."
data_entry_383 = "Since this project does not have record auto-numbering enabled, you will additionally need to provide a record name for the record you are created."
data_entry_384 = "The record was successfully created. If you wish, you may now navigate to the project to view or add data to the new record."
data_entry_385 = "INSTRUCTIONS: This REDCap module allows you to import the currently selected patient record into one or more REDCap projects and then afterward view the record in the project(s)."
data_entry_386 = "NOTE: You do not yet have any REDCap projects registered to utilize here. Please select a project from the drop-down list above to add the project to this page."
data_entry_388 = "WARNING: It appears that no 'MRN' field validation types have been enabled in REDCap. Please ask your REDCap administrator about enabling an 'MRN' field validation type in the REDCap Control Center."
data_entry_389 = "REDCap Clinical Data Pull"
data_entry_390 = "For full REDCap functionality, log in to REDCap in your web browser."
data_entry_394 = "NOTICE: You do not have 'Create Record' privileges in the project, so you will not be allowed to add the patient to this project."
data_entry_395 = "Viable projects"
data_entry_396 = "Non-viable projects (cannot be utilized here)"
data_entry_398 = "An active FHIR access token was not found and could not be refreshed. You will need to launch REDCap for this patient from inside your EHR system first in order to restore communication with the EHR."
data_entry_400 = "The request to the EHR system for the API method named"
data_entry_401 = "seems to have failed. Please check to ensure that this particular API has been enabled for your FHIR client in your EHR system and also that you (i.e., your EHR user account) have access to the EHR data provided by this API/endpoint."
data_entry_402 = "Confirm:"
data_entry_403 = "words remaining"
data_entry_404 = "characters remaining"
data_entry_405 = "Sets the maximum number of words that can be entered into a Text field or Notes field, and also displays the number of words remaining. The format must follow the pattern @WORDLIMIT=??, in which ?? is the desired max word count (alternatively, the number value can be inside single or double quotes). NOTE: This action tag cannot be used at the same time as @CHARLIMIT for the same field. NOTE: This action tag does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms."
data_entry_406 = "Sets the maximum number of characters that can be entered into a Text field or Notes field, and also displays the number of characters remaining. The format must follow the pattern @CHARLIMIT=??, in which ?? is the desired max character count (alternatively, the number value can be inside single or double quotes). NOTE: This action tag cannot be used at the same time as @WORDLIMIT for the same field. NOTE: This action tag does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms."
data_entry_407 = "Randomizes the order of multiple choice field options as displayed on survey pages and data entry forms, in which their order will always be different each time the page is loaded by any given user. NOTE: This action tag can only be utilized for the following field types: Checkbox, Radio, Drop-down, Yes-No, and True-False. This tag also works for enhanced radios and checkboxes on surveys. However, this tag does *not* work for a matrix of fields."
data_entry_409 = "Save & Exit Record"
data_entry_410 = "Save & Go To Next Record"
data_entry_411 = "(Although you clicked 'Go To Next Record', there is no record listed that follows the one you just saved.)"
data_entry_412 = "Incompatible checkbox selection"
data_entry_414 = "Allows for the designation of a checkbox choice to be a 'none of the above' option, thus ensuring that no other choices are checked if that one choice is selected. This means that if that particular option is selected, it will alert the user that all other checked-off choices will be unchecked. And if the 'none of the above' option is already checked when the user checks off another choice, it will automatically uncheck the 'none of the above' option. This action tag makes it possible to have a 'none of the above' option without the risk of users mistakenly having other choices selected at the same time. The format must follow the pattern @NONEOFTHEABOVE=??, in which ?? is the coded value of the 'none of the above' checkbox choice - e.g., @NONEOFTHEABOVE=98. Alternatively, it is possible to set multiple options as a 'none of the above' option at the same time, in which the coded values must be comma delimited inside single or double quotes - e.g., @NONEOFTHEABOVE='45,99'. This is useful for certain situations, such as if you have a 'none of the above' option and also have a 'refuse to answer' option, thus allowing either of those to be the only option that can be selected at a time. NOTE: This action tag can only be utilized by Checkbox fields."
data_entry_417 = "Yes, clear other selections"
data_entry_418 = "[no choices available]"
data_entry_419 = "Causes one or more specified choices to be disabled (i.e., displayed but not usable) for a checkbox, radio button, or drop-down field after a specified amount of records have been saved with that choice. For example, @MAXCHOICE(0=50,1=75,2=50) would imply that once 50 records have selected the '0' coded choice, that choice will become disabled for any record viewed afterward that does not have that choice saved, such as when the form/survey is opened for a new record, and thus 75 records for choice '1', 50 for choice '2', etc. The format must be the action tag name followed by the choice designations inside parentheses, in which each will follow the format of ChoiceCode=MaxCount with each choice separated by commas. Note: For longitudinal projects, when counting the number of choices saved for records, it will treat all events as separate, meaning that in the example above, choice '0' can have a max number of 50 selections in EACH event in the project."
data_entry_420 = "Allows a checkbox field to have a maximum number of checkboxes that can be checked. If other checkbox options are clicked after the maximum has been reached, those choices will not be able to be checked. The format must be @MAXCHECKED=#, in which # is a positive integer. For example, @MAXCHECKED=3 will allow a maximum of 3 checkbox choices to be checked. NOTE: This action tag can only be utilized by Checkbox fields, and it does not get enforced during data imports."
data_entry_421 = "Cannot select choice! The maximum number of choices has been selected."
data_entry_423 = "The fields listed below had values entered, but unfortunately the maximum number of responses that can be entered for the choice(s) you selected for those fields has already been reached. Please note that <b>your selections for the fields below were *NOT SAVED*.</b> If you wish to select a different choice for those fields, please do so and then re-submit the page."
data_entry_424 = "Fields in which the maximum response limit was reached:"
data_entry_425 = "(compact)"
data_entry_426 = "Also, you may optionally click the Compact option to download a PDF that excludes fields that have no data saved and excludes unselected multiple choice options. (Note: Section headers and descriptive fields will still be included.)"
data_entry_427 = "NOTE: Modifying this value will also change the value any corresponding instances of this field in other Events or Repeating Instances where this form is used."
data_entry_428 = "Version:"
data_entry_429 = "Type:"
data_entry_430 = "The only projects that may be utilized on this page are those projects that have the Clinical Data Pull (CDP) module enabled. When CDP mapping has been performed, REDCap knows how to link specific patient records from the EHR system to that REDCap project, which allows this module to easily add patient records to a CDP project."
data_entry_431 = "[Project cannot be utilized since the Clinical Data Pull module has not been enabled for it]"
data_entry_433 = "This field's value contains extra spaces at the beginning or end. Would you like to remove them?"
data_entry_434 = "Because this project has exceeded"
data_entry_435 = "records, the drop-down list(s) for choosing a record will only display the last"
data_entry_436 = "Also remove all the logged data values for the record (not common)?"
data_entry_437 = "If checked, all the logged activity for the record, including entered data values that were logged, will also be deleted. (Note: The logged events will remain, but the data in the logged events will be removed.)"
data_entry_438 = "To confirm you wish to remove all the logged data values for this record, you must type the word DELETE below."
data_entry_439 = "Confirmation: Type 'DELETE'"
data_entry_440 = "Survey response is read-only because it was completed via the e-Consent Framework."
data_entry_441 = "However, because you have 'Lock/Unlock Records' privileges, you will still be able to lock this form at the bottom."
data_entry_442 = "for this arm"
data_entry_443 = "Enter new record name"
data_entry_444 = "Click to view choices"
data_entry_445 = "'File Upload' field enhancement: Password verification & automatic external file storage"
data_entry_446 = "This feature allows any given project to utilize extra functionality regarding the use of File Upload fields in the project. When enabled below and also in a project, any user that is uploading a file for a File Upload field on a data entry form or survey will be asked to confirm that the file is the correct file. And when on data entry forms specifically, it will additionally ask the user to enter their REDCap password as part of the verification process. Once confirmed/verified, the file will successfully upload, and in addition to saving the file normally in REDCap, it will also store a duplicate copy of the file on a secure, external server using the configuration settings defined below. This feature may be utilized for projects wishing to adhere to certain regulatory compliance, such as 21 CFR Part 11 for FDA trials. Note: This feature is disabled by default for all projects, but users with 'Project Setup & Design' rights can enable it for a project in the Additional Customizations popup on a project's Project Setup page."
data_entry_448 = "Note: By enabling this, it will NOT be auto-enabled in any projects. It is disabled by default for all projects. Users with 'Project Setup & Design' rights will need to enable this feature in the Additional Customizations popup on a project's Project Setup page."
data_entry_450 = "Enabled using"
data_entry_451 = "Enable 'File Upload' field enhancement: Password verification & automatic external file storage?"
data_entry_452 = "If enabled, users will receive a prompt when uploading a file for any File Upload field, in which they must confirm that they are uploading the correct file and will ask them to successfully re-enter their REDCap password as a verification step (survey participants will not be asked to enter a password if on a survey). This feature has been specifically created for projects wishing to be compliant for specific regulations, such as 21 CFR Part 11 compliance for FDA trials. Note: When this feature is enabled, all files uploaded via a File Upload field will have a duplicate copy of the file automatically stored on a secure file server outside of REDCap (please contact your REDCap administrator regarding any questions or details of this external server)."
data_entry_453 = "File Upload: Confirmation & username/password verification"
data_entry_454 = "By clicking the Confirm button below, you are confirming that the following file is the correct file that you wish to upload here:"
data_entry_455 = "Confirm file"
data_entry_456 = "Enable the File Version History for 'File Upload' fields?"
data_entry_458 = "File Version"
data_entry_459 = "Upload new version"
data_entry_460 = "By providing your REDCap password and clicking the Confirm button below, you are confirming that the following file is the correct file that you wish to upload here:"
data_entry_461 = "Your file will be uploaded once you successfully initiate this confirmation process."
data_entry_462 = "This setting can be enabled/disabled in the Additional Customizations popup on the Project Setup page for any given project."
data_entry_463 = "If disabled here, then users will not be able to utilize this feature in their projects. If enabled, then users may enable it for a project via the Additional Customizations popup on the Project Setup page."
data_entry_464 = "The File Version History allows users to maintain previous versions of a file for a File Upload field on a form or survey. If a new version of a file needs to be uploaded for the field, instead of deleting the current file before uploading the new one, a user may simply upload a new file, in which all older versions will be kept and will be accessible for viewing/download in the Data History popup for the field."
data_entry_465 = "Deleted on"
data_entry_466 = "File Uploaded"
data_entry_467 = "Information / Action"
data_entry_468 = "(replace and keep current file)"
data_entry_469 = "Are you sure you wish to CANCEL and lose all changes made on this page?"
data_entry_470 = "It appears that you are using both the Randomization module AND the Double Data Entry module in this project. Please be aware that these two modules are not compatible with each other, so it is recommended that you only use one or the other and not both. Using both together could result in data not being saved correctly."
data_entry_472 = "Disable 'missing data codes' for a field - If custom codes for specifying missing data have been set up in this project (in the Additional Customizations popup on the Project Setup page), this action tag will disable the missing data code functionality for a given field, thus hiding the 'M' icon next to the field."
data_entry_473 = "Since you just set the survey invitation to be sent 'Immediately', <b>it is recommended that you leave this page</b> so that you <u>do not overwrite any survey responses</u> that might be entered soon by the respondent receiving the survey invitation."
data_entry_474 = "Leave page"
data_entry_475 = "Also, this feature does not work for Signature field types but only for File Upload fields."
data_entry_476 = "Review record data before locking record"
data_entry_477 = "Displayed below is a read-only copy of the entire record. Please review it and the options at the bottom."
data_entry_478 = "is now LOCKED"
data_entry_479 = "is now UNLOCKED"
data_entry_480 = "Do you wish to LOCK record"
data_entry_481 = "Do you wish to UNLOCK record"
data_entry_482 = "Lock entire record"
data_entry_483 = "Unlock entire record"
data_entry_484 = "This will lock the ENTIRE record, not just a single instrument. After doing this, no one will be able to edit this record until it is unlocked by someone with Lock/Unlock privileges."
data_entry_485 = "Record-level Locking Enhancement: PDF confirmation & automatic external file storage"
data_entry_486 = "This feature allows any given project to utilize extra functionality regarding the use of the Record-Level Locking feature in a project. When enabled below and also in a project, any user that is locking an ENTIRE record (as opposed to instrument-level locking) will be asked to review a PDF copy of the entire record to confirm it is the correct record and/or file. Once the PDF has been reviewed and confirmed, the record will be locked, after which the PDF file will be stored in the project's File Repository and a duplicate copy will be stored on a secure, external server using the configuration settings defined below. This feature may be utilized for projects wishing to adhere to certain regulatory compliance, such as 21 CFR Part 11 for FDA trials. Note: This feature is disabled by default for all projects, but users with 'Project Setup & Design' rights can enable it for a project in the Additional Customizations popup on a project's Project Setup page."
data_entry_487 = "Enable the Record-level Locking Enhancement: PDF confirmation & automatic external file storage?"
data_entry_488 = "If enabled, users will receive a prompt when locking an entire record (i.e., when performing record-level locking but not instrument-level locking), in which they will be asked to review a PDF copy of the entire record to confirm it is the correct record and/or file. Once the PDF has been reviewed and confirmed, the record will be locked, after which a copy of the record's PDF file will be stored in the project's File Repository. This feature has been specifically created for projects wishing to be compliant for specific regulations, such as 21 CFR Part 11 compliance for FDA trials. Note: When this feature is enabled, all records that are locked using record-level locking will have a duplicate copy of the PDF file automatically stored on a secure file server outside of REDCap (please contact your REDCap administrator regarding any questions or details of this external server)."
data_entry_489 = "PDF Archive of Locked Records"
data_entry_490 = "I approve the data that is contained in this record."
data_entry_491 = "Time record was locked"
data_entry_492 = "Displayed below are PDF files that have been automatically captured and stored when records have been locked (i.e., via record-level locking). Only users with 'Full data set' data export privileges will be able to download the archived PDF files. Note: The PDFs below were archived when the record was locked, which means they might be different from other downloadable PDFs in the project that are generated on demand using the current data."
data_entry_493 = "Lock this instrument?"
data_entry_494 = "If locked, no user will be able to modify this instrument for this record until someone with Instrument Level Lock/Unlock privileges unlocks it."
data_entry_495 = "total:"
data_entry_496 = "max:"
data_entry_497 = "Allows a PDF file or image file (JPG, JPEG, GIF, PNG, TIF, BMP) that is uploaded to a File Upload field to be displayed in an inline manner on the survey page or data entry form so that the PDF/image can be viewed by the user or survey participant without having to download it. The PDF/image will be displayed inline on the page immediately above the download link for the field and will be displayed with 100% width by default (i.e., 100% width of the area in which it is contained). Images will be displayed with their native width:height ratio, although PDFs will be displayed with a 300 pixel height by default. If you wish to manually set the width and/or height of the image/PDF, you may put the width/height values inside parentheses after the action tag in the following manner: @INLINE(width) or @INLINE(width,height). The width/height can be a percentage value (e.g., 50%) or a number representing size in pixels (e.g., 400). Thus @INLINE(50%) will display an image at 50% size for the area in which it is contained on the page, and @INLINE(400,100) would display the image always at 400px tall and 100px wide. To make an inline PDF appear taller on the page, you might use @INLINE(100%,600) since 300px is the default height for inline PDFs. Note: The @INLINE action tag also works if the File Upload field is embedded inside another field on the page."
data_entry_499 = "Causes one or more specified choices to be disabled (i.e., displayed but not usable) for a checkbox, radio button, or drop-down field after a specified amount of records have been saved with that choice <u>for completed survey responses only</u>. This means that partial survey responses or data entered only via a data entry form (as opposed to on a survey page) would not be counted. For example, @MAXCHOICE-SURVEY-COMPLETE(0=50,1=75,2=50) would imply that once 50 records have selected the '0' coded choice on completed survey responses, that choice will become disabled for any record viewed afterward that does not have that choice saved, such as when the form/survey is opened for a new record, and thus 75 records for choice '1', 50 for choice '2', etc. The format must be the action tag name followed by the choice designations inside parentheses, in which each will follow the format of ChoiceCode=MaxCount with each choice separated by commas. Note: For longitudinal projects, when counting the number of choices saved for records, it will treat all events as separate, meaning that in the example above, choice '0' can have a max number of 50 selections in EACH event in the project."
data_entry_500 = "Allows various action tags to be set based on conditional logic provided inside an @IF() function - e.g., <code>@IF(CONDITION, ACTION TAGS if condition is TRUE, ACTION TAGS if condition is FALSE)</code>. Simply provide a condition using normal logic syntax (similar to branching logic), and it will implement one set of action tags or another based on whether that condition is true or false. For example, you can have <code>@IF([yes_no] = '1', @HIDDEN, @HIDECHOICE='3' @READONLY)</code>, in which it will implement @HIDDEN if the 'yes_no' field's value is '1', otherwise, it will implement the two action tags @HIDECHOICE='3' and @READONLY. If you wish not to output any action tags for a certain condition, set it with a pair of apostrophes/quotes as a placeholder - e.g., <code>@IF([my_radio]='1', @READONLY, '')</code>. You may have multiple instances of @IF for a single field. You may also have multiple nested instances of @IF() inside each other. Both field variables and Smart Variables may be used inside the @IF condition. The @IF action tag is also evaluated for a given field when downloading the PDF of an instrument/survey, in case there are any PDF-specific action tags used inside of @IF(). Note: The conditional logic will be evaluated only when the survey page or data entry form initially loads; thus the action tag conditions will not be evaluated in real time as data is entered on the page."
data_entry_501 = "Enable this system-level setting for password verification for File Upload fields AND enable the external storage device? Choose storage method (SFTP, WebDAV, Azure, S3):"
data_entry_503 = "To rename the record, see the record action drop-down at top of the {0}."
data_entry_504 = "Note: You may not search over 'All fields' since this project has more than {0} records"
data_entry_505 = "In group: {0}"
data_entry_506 = "Total: {0}"
data_entry_507 = "Editing existing {0:RecordID-Label} <b>{1:RecordID}</b>."
data_entry_508 = "Adding new {0:RecordID-Label} <b>{1:RecordID}</b>."
data_entry_509 = "{0:RecordID-Label} <b>{1:RecordID}</b> successfully edited."
data_entry_510 = "{0:RecordID-Label} <b>{1:RecordID}</b> successfully added."
data_entry_511 = "{0:RecordID-Label} <b>{1:RecordID}</b> successfully deleted."
data_entry_512 = "{0:RecordID-Label} <b>{1:RecordID}</b> data entry cancelled - not saved."
data_entry_513 = "{0:RecordID-Label} <b>{1:RecordID}</b> was successfully renamed!"
data_entry_514 = "{0:RecordID-Label} <b>{1:RecordID}</b> was successfully assigned to a Data Access Group!"
data_entry_515 = "{0:RecordID-Label} <b>{1:RecordID}</b> was successfully unassigned from its Data Access Group!"
data_entry_516 = "{0:RecordID-Label} <b>{1:RecordID}</b> successfully deleted entire event of data."
data_entry_517 = "{0:RecordID-Label} <b>{1:RecordID}</b> {2:Instance} successfully edited<br/><b>but {3:RecordID-Label} could not be changed because it already exists</b>."
data_entry_518 = "The option {0} can only be selected by itself. Selecting this option will clear your previous selections for this checkbox field. Are you sure?"
data_entry_519 = "(Instance #{0})"
data_entry_520 = "Since this record has not been created yet, you will need to visit the {0} page to begin this auto-scoring instrument in survey mode."
data_entry_521 = "Since this record has not been created yet, you will need to visit the {0} page to begin this adaptive instrument in survey mode."
data_entry_522 = "Response was completed on {0}."
data_entry_523 = "Response was completed on {0} by {1}."
data_entry_524 = "Response was added on {0}."
data_entry_525 = "Response was added on {0} by {1}."
data_entry_526 = "Max file size: {0} MB"
data_entry_527 = "Another user ({0}) is currently on this data collection instrument editing the same record ({1})."
data_entry_528 = "If this conflict is in error, and you have confirmed that the user listed above is no longer on this page for this record, then you will either have to wait for the logout time to expire ({0} minutes from the time of the other user's last activity on this page), or you can have that other user log back in to REDCap, which will immediately release this page and allow you to access it."
data_entry_529 = "NOTE: Some fields are required!"
data_entry_530 = "WARNING: Invalid values entered!"
data_entry_531 = "NOTICE: SOME DATA NOT SAVED - Max response limit reached for some fields"
data_entry_532 = "<b>NOTICE:</b> This project is currently in Development status. <b>Real data should NOT be entered</b> until the project has been moved to Production status."
data_entry_533 = "Add new record for the arm selected above"
data_entry_534 = "<b>WARNING:</b> Your first field *must* be a 'Text Box (Short Text)' field, but it currently is not. Errors may result if this is not changed. You must add a new field as a 'Text Box (Short Text)' field and place it immediately before the following field: {0:FieldNameAndLabel}."
data_entry_535 = "Response was added on {0:Timestamp}."
data_entry_536 = "Next Page >>"
data_entry_537 = "<< Previous Page"
data_entry_538 = "Cannot yet randomize {0}"
data_entry_539 = "Randomizing {0}"
data_entry_540 = "[*DATA REMOVED*]"
data_entry_541 = "(Instance #{0})"
data_entry_542 = "This data entry form (blank)"
data_entry_543 = "This survey (blank)"
data_entry_544 = "This data entry form with saved data"
data_entry_545 = "This survey with saved data"
data_entry_546 = "This data entry form with saved data (via browser's <i>Save as PDF</i>)"
data_entry_547 = "This survey with saved data (via browser's <i>Save as PDF</i>)"
data_entry_548 = "This data entry form with saved data (compact)"
data_entry_549 = "This survey with saved data (compact)"
data_entry_550 = "All data entry forms (blank)"
data_entry_551 = "All forms/surveys (blank)"
data_entry_552 = "All data entry forms with saved data"
data_entry_553 = "All forms/surveys with saved data"
data_entry_554 = "All data entry forms with saved data (compact)"
data_entry_555 = "All forms/surveys with saved data (compact)"
data_entry_556 = "This survey with saved data (for survey participant)"
data_entry_557 = "Video: Basic data entry"
data_entry_558 = "Overview of Basic Data Entry"
data_entry_559 = "NOTE: This only applies to the current repeating instance of this form, which is Instance <b>{0}</b>."
data_entry_560 = "NOTE: To delete the entire record (all forms/events), see the record action drop-down at top of the {0:LinkToRecordHomePage}."
data_entry_561 = "Also, to delete all the data from THIS EVENT only, see the bottom row of the status table on the {0:LinkToRecordHomePage}."
data_entry_562 = "This will delete ALL DATA for ALL EVENTS."
data_entry_563 = "This will delete ALL DATA for ALL EVENTS for ONLY THE CURRENT ARM."
data_entry_564 = "Assign to Data Access Group (or unassign/reassign)"
data_entry_565 = "Delete record (all forms)"
data_entry_566 = "Delete record (all forms/events)"
data_entry_567 = "Now displaying the next record: <u>{0:RecordIDLabel} {1:RecordID}</u>"
data_entry_569 = "This browser does not support inline PDFs. Please open the PDF <b>in a new tab</b> to view it:"
data_entry_571 = "For Textbox fields with a min or max validation range, users/participants will not be able to enter a value unless it is within the field's specified validation range. This is different from the default behavior in which out-of-range values are permissible. Note: @FORCE-MINMAX is also enforced for data imports to ensure the value is always within the specified range."
data_entry_572 = "Response was initially started on {0}."
data_entry_573 = "(It is unknown when the response was initially started.)"
data_entry_574 = "The total completion time of the response is {0}."
data_entry_575 = "The current question requires that its value never duplicate the value from a prior survey response. The value you entered (\"{0}\") has already been taken, so please enter another value. You must change this value before you can proceed."
data_entry_576 = "The current field is the secondary unique field ({0}), so its value must be unique for all records and cannot be duplicated. Another record or another event within the current record already has this same value (\"{1}\"). You must change this value before you can proceed."
data_entry_577 = "You may alternatively enter your Two-Factor Authentication 6-digit PIN in place of your password above."
data_entry_578 = "If you need your PIN sent to you, click one of the following options:"
data_entry_579 = "Send PIN via email"
data_entry_580 = "Send PIN via SMS"
data_entry_582 = "Allow users to e-sign using their Two-Factor Authentication 6-digit PIN in place of their password."
data_entry_583 = "Used specifically when performing an e-signature on data entry forms or when utilizing the 'File Upload' field enhancement feature when uploading a file on a data entry form (often used for 21 CFR Part 11 compliance for FDA trials). NOTE: This feature cannot be used with the Duo Two-Factor option."
data_entry_584 = "Notice: It has been detected that <u>you will not be able to use your password</u> to e-sign above but instead you will only be able to e-sign using your Two-Factor Authentication 6-digit PIN."
data_entry_585 = "If one wishes to allow survey respondents to enter their responses in a repeating fashion in survey mode alone, you can enable the '<b>Repeat the Survey</b>' optional setting near the bottom of the Survey Settings page (in the survey termination options section) *after* an instrument has been set as a repeating instrument. So it is one additional step to do after enabling the instrument itself as a repeating instrument. When the repeat survey setting is enabled, a button will be displayed at the end of the survey so that the respondent can choose to enter another response for the survey, thus allowing them to take the survey multiple times in a row. In this way, they will be able to enter as many responses for that same survey as they need, such as filling out questions about multiple family members or entering medication information for multiple meds. Alternatively, <b>Automated Survey Invitations (ASIs)</b> and <b>Alerts & Notifications</b> may be set up to sent repeatedly on a recurring interval as a way to get respondents to take a repeating survey. For more information on repeating surveys, see"
data_entry_586 = "This is a MyCap annotation used with slider fields. The format must be <code>@MC-FIELD-SLIDER-BASIC=[MIN]:[MAX]:[STEP]</code>, in which [MIN], [MAX] and [STEP] are positive integers. Example: <code>@MC-FIELD-SLIDER-BASIC=0:10:1</code> is scale from 0 to 10 step by increments of 1, where the slider cannot have more than 13 steps.     See <a href=\"http://researchkit.org/docs/Classes/ORKScaleAnswerFormat.html\" target=_blank><u>documentation</u></a>."
data_entry_587 = "This is a MyCap annotation used in a File Upload field. There are no parameters needed for this action tag, so it should be used literally as just <code>@MC-FIELD-FILE-IMAGECAPTURE</code>.  See <a href=\"http://researchkit.org/docs/Classes/ORKImageCaptureStep.html\" target=\"_blank\"><u>documentation</u></a> for details.  Note that the Research Kit properties <code>templateImage</code>, <code>templateImageInsets</code>, <code>accessibilityInstructions</code>, and <code>accessibilityHint</code> are not implemented."
data_entry_588 = "This is a MyCap annotation used in a File Upload field. The format must be @MC-FIELD-FILE-VIDEOCAPTURE=[MAX DURATION IN SECONDS]:[AUDIO MUTE(YES/NO)]:[FLASH MODE(AUTO/ON/OFF)]: [DEVICE POSITION(BACK/FRONT/UNSPECIFIED)].  Example: <code>@MC-FIELD-FILE-VIDEOCAPTURE=20:YES:OFF:BACK</code> is video capture, 20 seconds max duration, audio is muted, camera flash is OFF, use camera on BACK of the device.  Note that REDCap file upload fields have a size limit of 35MB by default and video capture generates large files. See <a href=\"http://researchkit.org/docs/Classes/ORKVideoCaptureStep.html\" target=\"_blank\"><u>documentation</u></a> for details."
data_entry_589 = "This is a MyCap annotation used in any field type. <code>@MC-FIELD-HIDDEN</code> hides a field only when viewed in the MyCap mobile app,  whereas REDCap's <code>@HIDDEN</code> annotation hides a field from both REDCap and MyCap.  Example: If you have a calculated field that you want to appear in REDCap but not in MyCap, then use the <code>@MC-FIELD-HIDDEN</code> annotation."
data_entry_590 = "This is a MyCap annotation used with text or notes fields. Use the device's camera to scan a barcode. Contents will be stored in your Text Box or Notes Box field. Barcode symbologies supported:  <a href=\"https://en.wikipedia.org/wiki/Aztec_Code\" target=\"_blank\">Aztec</a>,  <a href=\"https://en.wikipedia.org/wiki/Code_39\" target=\"_blank\">CODE39</a>,  <a href=\"https://en.wikipedia.org/wiki/Code_39\" target=\"_blank\">CODE39MOD43</a>,  <a href=\"https://en.wikipedia.org/wiki/Code_93\" target=\"_blank\">CODE93</a>,  <a href=\"https://en.wikipedia.org/wiki/Code_128\" target=\"_blank\">CODE128</a>,  <a href=\"https://en.wikipedia.org/wiki/Data_Matrix\" target=\"_blank\">DataMatrix</a>,  <a href=\"https://en.wikipedia.org/wiki/EAN-8\" target=\"_blank\">EAN8</a>,  <a href=\"https://en.wikipedia.org/wiki/International_Article_Number\" target=\"_blank\">EAN13</a>,  <a href=\"https://en.wikipedia.org/wiki/Interleaved_2_of_5\" target=\"_blank\">Interleaved2of5</a>,  <a href=\"https://en.wikipedia.org/wiki/ITF-14\" target=\"_blank\">ITF14</a>,  <a href=\"https://en.wikipedia.org/wiki/PDF417\" target=\"_blank\">PDF417</a>,  <a href=\"https://en.wikipedia.org/wiki/QR_code\" target=\"_blank\">QR</a>,  <a href=\"https://en.wikipedia.org/wiki/Universal_Product_Code#UPC-E\" target=\"_blank\">UCP-E</a>"
data_entry_591 = "A required MyCap Text field appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will be populated with the ID of the task result. NOTE: for use only in the MyCap Mobile App."
data_entry_592 = "A required MyCap Text field with \"Date\" validation type appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will be populated with the date the user started the task. NOTE: For use only in the MyCap Mobile App."
data_entry_593 = "A required MyCap Text field with \"Date\" validation type appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will be populated with the date the user completed the task. NOTE: For use only in the MyCap Mobile App."
data_entry_594 = "A required MyCap Text field with \"Date\" validation type appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will be populated the date the task was scheduled, if appropriate. <code>.OneTime</code> and <code>.Infinite</code> tasks will not have a schedule date.     NOTE: For use only in the MyCap Mobile App."
data_entry_595 = "A required MyCap Drop-down field appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will get selected with the status of the task result. Possible values are (0=Deleted, 1=Completed, 2=Incomplete).     NOTE: For use only in the MyCap Mobile App."
data_entry_596 = "A required MyCap Text Box field appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will be populated with any available supplemental data. This will be in JSON format.     NOTE: For use only in the MyCap Mobile App."
data_entry_597 = "A required MyCap File field appended to any MyCap-enabled instrument on projects with MyCap enabled. When participants submit a task in the MyCap Mobile App, this field will be uploaded with backup/restoration data file.     NOTE: For use only in the MyCap Mobile App."
data_entry_598 = "This is a MyCap annotation used with slider fields. The format must be <code>@MC-FIELD-SLIDER-CONTINUOUS=[MIN]:[MAX]:[MAX FRACTIONAL DIGITS]</code>, in which [MIN], [MAX] and [MAX FRACTIONAL DIGITS] are positive integers. Example: <code> @MC-FIELD-SLIDER-CONTINUOUS=0:100:0</code> is scale from 0 to 100 with no fractions. See <a href=\"http://researchkit.org/docs/Classes/ORKContinuousScaleAnswerFormat.html\" target=\"_blank\"><u>documentation</u></a>. A REDCap slider will default to this if no annotation is specified. Note: REDCap slider fields do not accept fractions."
data_entry_599 = "NOTICE: Because some data values on this page have been modified but not saved yet, the resulting PDF may contain both saved and yet-to-be-saved values. If this is understood, click OK to proceed."
data_entry_600 = "Miscellaneous File Attachments"
data_entry_601 = "Field should be hidden by branching logic but is shown because it has a value"
data_entry_602 = "We're sorry, but your current web browser (<b>Internet Explorer</b>) is not compatible with this web page.  You'll need to switch to <b>Firefox</b>, <b>Google Chrome</b>, or <b>Microsoft Edge</b> to use this page. Thanks for understanding!"
data_entry_603 = "Please supply reason for data changes"
data_entry_604 = "When added to a File Upload field or Descriptive Text field, in which an image or PDF has been uploaded or attached to the field, a preview button will appear next to the download link to allow users/participants to view the image or PDF without having to download the file. Supported file types are: PDF, BMP, GIF, JPG/JPEG/JFIF/PJEPG/PJP, PNG, SVG, and TIF/TIFF. (Note: The preview button will not be added for the @INLINE action tag but only for @INLINE-PREVIEW.)"
data_entry_605 = "Toggle preview of this file"
data_entry_606 = "If you are having trouble viewing the PDF or if your browser does not support viewing multi-page PDFs, you may open the PDF <b>in a new tab</b> to view it:"
data_entry_607 = "This is a MyCap annotation used with text fields. This field captures install date of MyCap participant when participant joins project from MyCap mobile app. NOTE: for use only in the MyCap Mobile App."
data_entry_608 = "This is a MyCap annotation used with text fields. MyCap uses this field to match a participant code to a record in the project."
data_entry_609 = "(Place a mark on the scale above)"
data_entry_610 = "Media"
data_entry_611 = "When applied to a multiple-choice field, this action tag will hide all choices <b>except</b> for the ones listed in its argument. This action tag is useful if you wish to only show a subset of choices depending on some logic (e.g., depending on data access groups) via the <code>@IF</code> action tag. The format must follow the pattern <code>@SHOWCHOICE='??'</code>, in which the coded values should be inside single or double quotes for the choice(s) you wish to show. If more than one choice needs to be shown, then provide all the coded values separated by commas. For example, to show the choice 'Monday (1)', you would have <code>@SHOWCHOICE='1'</code>, but if you wanted to additionally show 'Tuesday (2)', you would have <code>@SHOWCHOICE='1,2'</code>.<br>NOTE:<ul><li>If a choice <i>not shown</i> has already been selected for a given record, then the choice will still be shown on the survey or form for that record/event.</li><li>Hidden choices will still appear in reports and data exports.</li><li>This action tag can only be utilized for the following field types: Checkbox, Radio, Drop-down, Yes-No, and True-False.</li><li>This action tag does not work with a matrix of fields.</li><li>This action tag will take precedence over the <code>@HIDECHOICE</code> action tag.</li><li>This action tag supports piping into its argument.</li></ul>"
data_entry_612 = "Hides one or more choices of a multiple choice field. This action tag is useful if you wish to retire a particular choice after utilizing it for a while in data collection, thus allowing you to hide the choice from that point afterward without orphaning any of the choice's data, which would happen if you simply deleted the choice. The format must follow the pattern <code>@HIDECHOICE='??'</code>, in which the coded values should be inside single or double quotes for the choice(s) you wish to hide. If more than one choice needs to be hidden, then provide all the coded values separated by commas. For example, to hide the choice 'Monday (1)', you would have <code>@HIDECHOICE='1'</code>, but if you wanted to additionally hide 'Tuesday (2)', you would have <code>@HIDECHOICE='1,2'</code>.<br>NOTE:<ul><li>If the hidden choice has already been selected for a given record, then the choice will not be hidden on the survey or form for that record/event.</li><li>Hidden choices will still appear in reports and data exports.</li><li>This action tag can only be utilized for the following field types: Checkbox, Radio, Drop-down, Yes-No, and True-False.</li><li>This action tag works only in limited fashion with a matrix of fields, in which it will simply hide the checkbox/radio for a field in the matrix but still display the column for that choice in the matrix.</li><li>This action tag supports piping into its argument.</li></ul>"
data_entry_613 = "The File Version History allows you to maintain previous versions of a file for a File Upload field on a form or survey. If a new version of a file needs to be uploaded for the field, instead of deleting the current file before adding the new one, you may simply upload a new file (via the 'Upload new version' link), in which all older versions will be kept and will be accessible for viewing/download in the Data History popup for the field. This features provides the convenience of accessing older versions of the file instead of having to delete them. (Note: Older versions of a file will not be accessible anywhere else in the project except the Data History popup. For instance, they will not be included in the zip file of all files uploaded for a given record or for the whole project.) Also, the Data History popup must be enabled (above) in order to use the File Version History."
data_entry_614 = "Invalid characters in new record name. Please change it and try again."
data_entry_615 = "This is a MyCap annotation used with text fields. This field captures install date (in UTC format) of MyCap participant when participant joins project from MyCap mobile app. NOTE: for use only in the MyCap Mobile App."
data_entry_616 = "This is a MyCap annotation used with text fields. This field captures timezone of MyCap participant when participant joins project from MyCap mobile app. NOTE: for use only in the MyCap Mobile App."
data_entry_617 = "The instrument cannot be locked, unlocked, or e-signed because the entire record is locked. You will need to first unlock the record before you can perform one of those actions."
data_entry_618 = "Select instruments/events:"
data_entry_619 = "Bulk Record Delete"
data_entry_621 = "You may use this page to delete multiple records from the project or alternatively to delete data for multiple instruments across multiple records.  To perform either of these two actions, you must have \"Delete Records\" privileges. For the partial delete option, you must additionally have \"View & Edit\" instrument-level  privileges for the instrument that you select. Make your selections below, and then click the \"Delete\" button."
data_entry_622 = "Fetch all records for this project and select those which you would like to delete."
data_entry_623 = "This process may take some time if you have many records."
data_entry_624 = "This option has to be defined for longitudinal projects with multiple arms."
data_entry_625 = "Enter a comma-separated or return-separated list of record names."
data_entry_626 = "Valid list entered"
data_entry_627 = "Fetch Records"
data_entry_628 = "Deleted {0} record(s)"
data_entry_629 = "Deleted forms {0}<br>for {1} record(s)"
data_entry_630 = "Select records from a list"
data_entry_631 = "Enter a custom list of records"
data_entry_632 = "No records exist in the project."
data_entry_633 = "Completely delete selected record(s)"
data_entry_634 = "Step 1: Choose between deleting entire records or deleting data from specific instruments of selected records"
data_entry_635 = "Step 2: Choose between entering a custom list of records to delete or individually selecting records from a list"
data_entry_636 = "Select the instruments to delete for the records specified below in Step 2."
data_entry_637 = "Step 3: {0} records to delete"
data_entry_638 = "Delete entire records"
data_entry_639 = "Partial delete (instrument-level data only)"
data_entry_640 = "Confirm Permanent Deletion"
data_entry_641 = "Deleting data for {0} instruments across {1} record(s)"
data_entry_642 = "Deleting {0} record(s)"
data_entry_643 = "Invalid records:"
data_entry_644 = "Searching for records will only search the current page"
data_entry_645 = "Navigating to the {0} page will forfeit all currently selected records; would you still like to proceed?"
data_entry_646 = "If you wish to permanently delete the record(s) from the project, type the word"
data_entry_647 = "Check the checkbox next to each record you wish to delete below."
data_entry_648 = "Search records..."
data_entry_649 = "Please be advised that all deletions made here are PERMANENT and IRREVERSIBLE."
data_entry_651 = "You may delete multiple records from the project or alternatively delete data for multiple instruments across multiple records."
data_entry_652 = "Some records in the list are invalid. Please fix them, and try again."
data_entry_653 = "You must type \"DELETE\" first."
data_entry_654 = "You must select at least one form to delete."
data_entry_655 = "Multi-record actions"
data_entry_656 = "Select instruments:"
data_entry_657 = "Enter"
data_entry_658 = "Select"
data_entry_659 = "<u>Note</u>: Selecting all instruments will not actually delete the records, but will leave the records with a gray form status for all instruments."
data_entry_660 = "Enable the Bulk Record Delete page in all projects for users with \"Delete Records\" privileges in the project."
data_entry_661 = "If enabled, users with \"Delete Records\" privileges in a project will be able to delete multiple records at a time or specific instruments of data for a set of selected records."
data_export_tool_01 = "SPSS Instructions for Non-Windows Operating Systems"
data_export_tool_04 = "Form: "
data_export_tool_05 = "Data export was successful!"
data_export_tool_07 = "SPSS Statistical Software"
data_export_tool_08 = "Download and save all 3 files on the right to a common location. First, double-click on the Pathway Mapper (.bat) file, which will run quickly and invisibly. (If you are not using a Windows operating system, such as Mac or Linux, please see the <i>Additional Instructions</i>.) Now double-click on the *.sps file, which will open SPSS. When the file is loaded and displayed, choose Run-->All from the top menu options. This action will launch the script that will automatically read in all data and manipulate data fields with labels, option values, etc."
data_export_tool_08b = "Additional instructions"
data_export_tool_08c = "Because the Pathway Mapper (.bat) file will only work on Windows operating systems, additional steps are required to correctly map the path of the SPSS syntax file to the CSV data file. In order for SPSS to read the data file, you must manually provide SPSS with the full file path of the CSV file (after downloading it to your computer). Your folder path might look similar to this: "
data_export_tool_08d = "Once you have the folder location of the CSV file, double-click the syntax file to open it in SPSS. In the syntax editor in SPSS, enter the path onto the first line of the syntax code so that NAME is now set to the full path of the file on your computer. The first line of the SPSS syntax file will look as follows: "
data_export_tool_08e = "But after appending the folder path to the file name, it will look as follows (the added folder path is in red):"
data_export_tool_08f = "Your file name and folder path will look different from the example here. Once you have completed these steps, choose Run-->All from the top menu options in SPSS to load the data. "
data_export_tool_09 = "R Statistical Software"
data_export_tool_10 = "Instructions: Use command read.csv('filename') to read in data file."
data_export_tool_11 = "SAS Statistical Software"
data_export_tool_14 = " Instructions: Download both files to common location and double-click on *.do file. This action will launch the script that will automatically read in all data and manipulate data fields with labels, option values, etc."
data_export_tool_17 = "If you are using a version of Microsoft Excel prior to Excel 2007, due to limitations the data will only be read to 255 columns when opened."
data_export_tool_52 = "Select All"
data_export_tool_53 = "Deselect All"
data_export_tool_85 = "All dates within your data have been <b>DATE SHIFTED to an unknown value between 0 and "
data_export_tool_86 = "days</b>. Although all dates were shifted by the same amount within each individual record to maintain internal consistency, the shifting amount is different for each record."
data_export_tool_87 = "Given that you have limited export rights, you may NOT modify the options below, except the Date fields option."
data_export_tool_88 = "Deselect all options"
data_export_tool_89 = "De-identification options"
data_export_tool_91 = "The options below allow you to limit the amount of sensitive information that you are exporting out of the project. Check all that apply."
data_export_tool_92 = "Known Identifiers:"
data_export_tool_94 = "(tagged in Data Dictionary)"
data_export_tool_96 = "(converts record name to an unrecognizable value)"
data_export_tool_97 = "Free-form text:"
data_export_tool_98 = "Remove unvalidated Text fields "
data_export_tool_99 = "(i.e. Text fields other than dates, numbers, etc.)"
data_export_tool_100 = "Remove Notes/Essay box fields"
data_export_tool_103 = "Shift all dates by value between 0 and"
data_export_tool_104 = "days "
data_export_tool_105 = "(shifted amount determined by algorithm for each record)"
data_export_tool_106 = "What is date shifting?"
data_export_tool_118 = "You may download the survey results in CSV (comma-separated) format, which can be opened in Excel. You have the choice of downloading the data either with the full headers and answer labels or just with the answer codes (i.e. raw data)."
data_export_tool_119 = "Send data file (raw)"
data_export_tool_120 = "Send data file (labels)"
data_export_tool_123 = "The data for all records in this project may be downloaded in a single PDF file. This file contains the actual page format as you would see it on the data entry page or survey and includes all data for all records for all data collection instruments. Click the icon to the right to begin downloading the file."
data_export_tool_124 = "Note: If your project has a large amount of fields/questions or records/responses, the resulting PDF file may be very large both in file size and in page length. Please be patient if the file takes time to download."
data_export_tool_125 = "Return Codes for Surveys (for Save & Return Later feature)"
data_export_tool_126 = "Since there exist one or more surveys in this project with the Save & Return Later feature enabled, you may download a file containing the return codes for any incomplete survey responses, which also contains the entire data set (CSV raw format) for context. You may need to use this file to retrieve a return code if a survey participant has misplaced the code given to them on the survey page. Click the icon to the right to begin downloading the file."
data_export_tool_127 = "NOTE: Since this file contains the Return Codes for incomplete responses, please be careful if you plan to distribute this file, as it may allow others to edit incomplete survey responses."
data_export_tool_128 = "Remove all date and datetime fields"
data_export_tool_129 = "Date and datetime fields:"
data_export_tool_138 = "Export Data Access Group name for each record (if record is in a group)?"
data_export_tool_139 = "Export survey identifier field and survey timestamp field(s)?"
data_export_tool_140 = "Additional export options"
data_export_tool_143 = "Also shift all survey completion timestamps by value between 0 and"
data_export_tool_149 = "Download PDF with all data"
data_export_tool_150 = "Download ZIP file with uploaded files for all records"
data_export_tool_151 = "ZIP file of uploaded files (all records)"
data_export_tool_152 = "Note: If your project has a large amount of 'File Upload' fields/questions or records/responses, the resulting ZIP file may be very large in file size. Please be patient if the file takes time to download."
data_export_tool_153 = "Uploaded files for all records in this project may be downloaded in a single ZIP file. This file contains any files uploaded for 'File Upload' fields/questions on a survey or data entry form. The ZIP file will contain a folder of all the files organized by record name and variable/field name and also contains an index.html file that serves as a table of contents for all the files. After downloading the ZIP file, extract all the files/folders to a directory on your local computer, after which you may double-click the index.html file inside to view a listing of the files using your web browser, or you may view the files directly by looking in the 'documents' folder. Click the icon to the right to begin downloading the ZIP file."
data_export_tool_154 = "Although the project does contain 'File Upload' fields/questions, no files have been uploaded yet, so there is nothing to download. You may return later and try again after some files have been uploaded."
data_export_tool_158 = "Download PDF of instrument(s)"
data_export_tool_159 = "Sorry, but there are no files to download for records in this project."
data_export_tool_160 = "Close window"
data_export_tool_161 = "ERROR: There are no 'File Upload' fields in this project."
data_export_tool_162 = "Uploaded Files"
data_export_tool_163 = "Files uploaded to"
data_export_tool_164 = "all records"
data_export_tool_165 = "record"
data_export_tool_166 = "in the REDCap project named"
data_export_tool_167 = "as of"
data_export_tool_168 = "Original Filename"
data_export_tool_169 = "Filename"
data_export_tool_170 = "Date Uploaded"
data_export_tool_171 = "PDF of data collection instruments containing saved data (all records)"
data_export_tool_172 = "CSV / Microsoft Excel"
data_export_tool_173 = "Hash the Record ID field"
data_export_tool_174 = "Make custom selections"
data_export_tool_175 = "Select one or more instruments/events below for all records."
data_export_tool_176 = "Select one or more instruments below for all records."
data_export_tool_178 = "Include the Data Access Group name for each record (if record is in a group)?"
data_export_tool_179 = "Include the survey identifier field and survey timestamp field(s)?"
data_export_tool_180 = "You do not have user privileges to view this report!"
data_export_tool_181 = "De-identified means that all free-form text fields will be removed, as well as any date/time fields and Identifier fields."
data_export_tool_183 = "The data export was successful, and your data is now ready to be downloaded. Click the download icon(s) below on the right to download your data file. If exporting to a specific statistical analysis package, you will additionally need to download the syntax file that is provided for that stats package. For more details, follow the instructions in the box below."
data_export_tool_184 = "Click icon(s) to download:"
data_export_tool_185 = "Given that you have limited export rights, you may NOT uncheck the option below to 'Remove All Identifier Fields'."
data_export_tool_187 = "Stata Statistical Software"
data_export_tool_189 = "Download all records with Return Codes"
data_export_tool_191 = "Show data for all events for each record returned"
data_export_tool_193 = "What does this setting do?"
data_export_tool_194 = "For example, if the project contains one event to capture demographics information and also contains subsequent visits (events) to capture measurements for vitals, one could set a filter of [sex] = '1' (Female). So if the checkbox setting was left CHECKED (the default setting), it would only return records where the person was female, and the results would contain *all* events (demography and all visits) for each of those records. However, if the checkbox was UNCHECKED in that situation, then not only would it remove the records where the person was male, but it would additionally remove the visit events for the female records, thus returning only the demography event for the female records. In this way, having the checkbox UNCHECKED not only filters out some of the records, but it may also remove some of the events in the records that are returned."
data_export_tool_195 = "<b>SUMMARY:</b> In most cases, this checkbox setting will be left CHECKED unless you have very specific intentions for unchecking it. If you are still not quite sure how you might use this setting, then it is recommended that you leave it CHECKED."
data_export_tool_197 = "CDISC ODM (XML)"
data_export_tool_198 = "You may download CDISC ODM file containing the data in XML format. The XML file may be imported into another system that supports CDISC ODM, or into another REDCap project using the Data Import Tool or the Import Records API method."
data_export_tool_199 = "Export Entire Project"
data_export_tool_200 = "REDCap Project (XML)"
data_export_tool_201 = "The entire project (all records, instruments, fields, and project attributes) can be downloaded as a single XML file (CDISC ODM format)."
data_export_tool_202 = "The entire project (all records, events, arms, instruments, fields, and project attributes) can be downloaded as a single XML file, which is in CDISC ODM format (ODM version 1.3.1)."
data_export_tool_203 = "This XML file can be used to create a clone of the project (including its data, optionally) on this REDCap server or on another REDCap server (it can be uploaded on the Create New Project page). Because it is in CDISC ODM format, it can also be used to import the project into another ODM-compatible system."
data_export_tool_208 = "Entire project (metadata & data)"
data_export_tool_209 = "(metadata & data)"
data_export_tool_210 = "Export entire project as REDCap XML file (containing metadata & data)"
data_export_tool_213 = "Other Export Options"
data_export_tool_214 = "Download a backup of this project."
data_export_tool_215 = "Download metadata only (XML)"
data_export_tool_216 = "Download metadata & data (XML)"
data_export_tool_218 = "Include all files uploaded for File Upload and Signature fields in the XML file? NOTE: This can make the export very large and may prevent it from completing if the project contains many files or very large files."
data_export_tool_219 = "Include all uploaded files and signatures?"
data_export_tool_220 = "NOTICE: No records exist yet in this project, so there is no PDF file to download."
data_export_tool_221 = "Sorry, but there are no files to download for this record."
data_export_tool_222 = "Show data for all events or repeating instruments/events for each record returned"
data_export_tool_223 = "Show data for all repeating instruments/events for each record returned"
data_export_tool_224 = "Advanced data formatting options"
data_export_tool_225 = "Set the delimiter used to separate values in the CSV data file (only valid for CSV Raw Data and CSV Labels export formats):"
data_export_tool_226 = "You may choose to force all data values containing a decimal to have a specified decimal character (comma or period/full stop). This will be applied to all calculations and number-validated text values in the export file."
data_export_tool_227 = "tab"
data_export_tool_228 = "(semi-colon)"
data_export_tool_229 = "(pipe)"
data_export_tool_230 = "(caret)"
data_export_tool_231 = "NOTE: Your data formatting selections above will be remembered in the future and will be pre-selected upon your next export."
data_export_tool_232 = "Force all numbers into a specified decimal format?"
data_export_tool_233 = "Set CSV delimiter character"
data_export_tool_234 = "Use fields' native decimal format (default)"
data_export_tool_235 = "- default"
data_export_tool_236 = "Use period/full stop ( . ) as decimal for all numbers"
data_export_tool_237 = "Use comma ( , ) as decimal for all numbers"
data_export_tool_238 = "Include the following in the XML file:"
data_export_tool_239 = "User Roles"
data_export_tool_240 = "Surveys and survey settings"
data_export_tool_241 = "'Clinical Data Pull' Field Mappings"
data_export_tool_242 = "<b>NOTE REGARDING MISSING DATA CODES:</b> Please be aware that since you are exporting Missing Data Codes in your data, the CSV data might not load correctly in this statistical analysis package and might throw an error. You might need to manually modify the syntax file before loading it into the stats package in order to allow your Missing Data Codes to be accepted for certain data types, such as date fields. Otherwise, you might want to try exporting your data without the Missing Data Codes."
data_export_tool_243 = "DATA EXPORTS: Please be aware that if you are exporting Missing Data Codes in your data into a statistical analysis package, the CSV data might not load correctly in this statistical analysis package and might throw an error. You might need to manually modify the syntax file before loading it into the stats package in order to allow your Missing Data Codes to be accepted for certain data types, such as date fields. Otherwise, you might want to try exporting your data without the Missing Data Codes."
data_export_tool_244 = "Download and save both files on the right to a common location. Double-click the syntax file to open it in SAS. In the syntax editor in SAS, enter the full path of the data CSV file on your computer into the second line of the .sas syntax file. For example, you will need to add something similar to the red text seen below. Your file name and folder path will look different from the example below. Once you have completed these steps, choose Run (or Run-->Submit) from the top menu options in SAS to load the data."
data_export_tool_245 = "The code above should be changed to something like the following:"
data_export_tool_246 = "Clinical Data Mart settings and revisions"
data_export_tool_247 = "Non-Windows users only:"
data_export_tool_248 = "FILE:"
data_export_tool_249 = "NOTICE: When downloading a PDF file containing data for all records, a copy of that downloaded PDF will be archived and stored in the File Repository."
data_export_tool_250 = "Data export details:"
data_export_tool_251 = "Tableau Connector Instructions"
data_export_tool_252 = "Tableau Export: Extract all records into Tableau via the REDCap API"
data_export_tool_255 = "NOTICE: It is required to have an API token generated for the project in order to use this feature."
data_export_tool_256 = "Why Tableau?"
data_export_tool_257 = "<b>Tableau</b> is a powerful and fastest growing data visualization tool used in the Business Intelligence Industry. It helps in simplifying raw data in a very easily understandable format. Tableau helps create the data that can be understood by professionals at any level in an organization. <br><b>Tableau</b> is a visual analytics engine that makes it easier to create interactive visual analytics in the form of dashboards. These dashboards make it easier for non-technical analysts and end users to convert data into understandable, interactive graphics."
data_export_tool_258 = "A REDCap user with an API token can have data from their REDCap project downloaded to their <b>Tableau Desktop instance (v10.0+)</b>. Please follow the below steps to download data via the Tableau Web Data Connector."
data_export_tool_259 = "In Tableau 10.0+, go to Connect -> To a Server -> More and find \"Web Data Connector\""
data_export_tool_260 = "Copy the URL below as the \"web data connector URL\" in the dialog, and press Enter:"
data_export_tool_261 = "In Tableau, enter your project API token into the text box and select/enter other options, as desired."
data_export_tool_262 = "Options available for customizing the extract are:"
data_export_tool_263 = "Raw data or labels"
data_export_tool_264 = "Include Data Access Group yes/no"
data_export_tool_265 = "Subset of fields: specify a comma or space-separated list export field names"
data_export_tool_266 = "Subset of records: specify a REDCap filter logic expression"
data_export_tool_267 = "Click \"Submit\", and your project data will be downloaded into Tableau."
data_export_tool_268 = "The web data connector will be executed and create a Tableau Data Source in your Tableau workbook."
data_export_tool_269 = "Click \"Update Now\" to extract your project data into the Data Source."
data_export_tool_270 = "Tableau Web Data Connector for REDCap"
data_export_tool_271 = "You may load the REDCap project data into Tableau using the selections in the form below. Select the desired data format and enter your API token, then click \"Submit\". If you do not have an API token, you will need to obtain one for yourself on the API page in the desired project. If you do not have access to the API page in the project, then someone with User Rights privileges in the project will need to grant you access to that page."
data_export_tool_272 = "Enter your API Token for the REDCap Project"
data_export_tool_273 = "Raw data or labels?"
data_export_tool_274 = "Raw"
data_export_tool_275 = "Variable name or field label?"
data_export_tool_276 = "Variable"
data_export_tool_277 = "Include Data Access Group?"
data_export_tool_278 = "Export field names (optional)"
data_export_tool_279 = "Comma or space-separated list of export field names"
data_export_tool_280 = "Record filter (optional)"
data_export_tool_281 = "REDCap-style filter logic expression"
data_export_tool_282 = "Error: could not download tableau connector code at"
data_export_tool_283 = "REDCap Data"
data_export_tool_284 = "View export instructions"
data_export_tool_285 = "Export blank values for gray Form Status?"
data_export_tool_286 = "All Form Status fields with a gray status icon can be exported either as a blank value or as \"0\" (Incomplete). Hint: Blank values are recommended if the data will be imported back into REDCap, in which this preserves the gray status icons for all the imported records."
data_export_tool_287 = "Export gray Form Status fields with value of \"0\""
data_export_tool_288 = "Export gray Form Status fields with blank value"
data_export_tool_289 = "Form Display Logic settings"
data_export_tool_290 = "Remove All Identifier Fields"
data_export_tool_291 = "Privileges for Viewing and Exporting Data"
data_export_tool_292 = "Given that you have 'De-Identified' or 'Remove All Identifier Fields' export rights for one or more data collection instruments, some fields may be automatically removed from the exported data based on your instrument-level Data Export Rights. Additionally, if you check any of the checkboxes for the settings below, that de-identification setting will be applied to all remaining fields in the resulting data export."
data_export_tool_293 = "This feature enables Tableau (v10.0+) users to connect Tableau to a REDCap project using an API token. Project data can be exported on demand and be available for use within Tableau to produce summaries and visualizations. Click the button to the right and follow the instructions to export your data into Tableau."
data_export_tool_294 = "NOTICE: You are not able to download the export files here because you have either none or partial data export rights to one or more fields contained within the data export file."
data_export_tool_295 = "How to cite publications"
data_export_tool_296 = "and grants"
data_export_tool_297 = "Please cite your institution/organization's grant:"
data_export_tool_298 = "Please cite the <b>official REDCap publications</b>."
data_export_tool_299 = "When publishing manuscripts relating to this REDCap project, we ask that in your publication you please cite the items listed below that have been utilized in this project. Thank you!"
data_export_tool_300 = "Since this project utilizes one or more data collection instruments downloaded from the <b>REDCap Shared Library</b>, please cite the RSL manuscript."
data_export_tool_301 = "View citation and template methods language"
data_export_tool_302 = "Citation"
data_export_tool_303 = "View citation"
data_export_tool_304 = "Since this project utilizes one of the <b>Clinical Data Interoperability Services (CDIS)</b>, such as Clinical Data Pull (CDP) or Clinical Data Mart (CMD), please cite the CDIS manuscript."
data_export_tool_305 = "Since this project utilizes the <b>REDCap Mobile App</b>, please cite the RMS manuscript."
data_export_tool_306 = "Since this project utilizes <b>MyCap</b>, please cite the MyCap manuscript."
data_export_tool_307 = "Since this project utilizes the <b>e-Consent Framework</b>, please cite the e-Consent manuscript."
data_export_tool_308 = "MyCap Mobile App Data and task settings"
data_export_tool_309 = "<b>IMPORTANT:</b> There are some miscellaneous file attachments in this project whose download link <b>*might be hard-coded*</b> throughout parts of this project, such as inside the text of field labels, project dashboards, survey invitations, etc. If this is true and a copy of this project is created, those download links in the new project will still be associated with and point to the files in the old project. Please review the files below (you might consider copy->pasting this info to keep for later), and once you have created a new project, <b>it is recommended that you replace these links in the new project with the same file using the file attachment upload option in the rich text editor</b>. The re-uploading process will associate the newly-uploaded files with the new project. To continue, click the \"I acknowledge this\" button below."
data_export_tool_310 = "Warning about miscellaneous file attachments"
data_export_tool_311 = "Where file was uploaded"
data_export_tool_312 = "I acknowledge this... Please continue"
data_export_tool_313 = "When building a report using Step 3 (filtering) for a project that is longitudinal and/or has repeating instruments or repeating events, any filters defined in the report will be applied to each record as a whole, which is the default behavior when the 'Show data for all events and repeating instruments/events for each record returned' checkbox is CHECKED. But if it is UNCHECKED, it will additionally apply the filters to each event and/or each repeating instance within each record returned, in which some (or all) of the events or repeating instances in the records returned could get removed from the results. So if CHECKED, then *all* events or repeating instances will be returned for each record, but if UNCHECKED, then some events or repeating instances in each record *may* get removed (depending on the filter that is specified)."
data_history_01 = "Date/Time of Change"
data_history_03 = "Data Changes Made"
data_history_04 = "Reason for Data Change(s)"
data_history_05 = "No data exists for this field"
data_history_06 = "Date/Time of Upload"
data_import_tool_04 = "Download your Data Import Template"
data_import_tool_11 = "All multiple choice fields (e.g., dropdown, radio) must have the raw coded value (rather than the choice label) entered in those cells, or else it cannot be processed."
data_import_tool_20 = "Upload File"
data_import_tool_24 = "Your document was uploaded successfully and is ready for review."
data_import_tool_24b = "You are now required to view the Data Display Table below to approve all the data before it is officially imported into the project. Follow the instructions below."
data_import_tool_25 = "The data you uploaded from the file is displayed in the Data Display Table below. Please inspect it carefully to ensure that it is all correct. After reviewing it, <b>click the 'Import Data' button at the bottom of this page</b> to import this data into the project."
data_import_tool_27 = "(Red text)"
data_import_tool_28 = "DATA DISPLAY TABLE"
data_import_tool_29 = "Import Data"
data_import_tool_33 = "KEY for Data Display Table below"
data_import_tool_35 = "Black text"
data_import_tool_36 = "New Data"
data_import_tool_37 = "Gray text"
data_import_tool_38 = "Existing data (will not change)"
data_import_tool_39 = "Data that will be overwritten"
data_import_tool_41 = "error"
data_import_tool_43 = "warning"
data_import_tool_44 = "Your file is currently being uploaded. Please wait."
data_import_tool_45 = "The file is also being analyzed for any possible errors."
data_import_tool_46 = "This could take several minutes."
data_import_tool_48 = "There was an error uploading your file."
data_import_tool_49 = "Please try again or contact "
data_import_tool_50 = " for assistance."
data_import_tool_51 = "Errors were detected in the import file that prevented it from being loaded."
data_import_tool_52 = "There are"
data_import_tool_53 = "There is"
data_import_tool_54 = "errors"
data_import_tool_56 = "(shown in red in the error table below)"
data_import_tool_58 = "warnings"
data_import_tool_60 = "(shown in orange)"
data_import_tool_61 = "in this dataset. Please "
data_import_tool_63 = "review the warnings below before importing the data."
data_import_tool_64 = "Your data is currently being imported."
data_import_tool_65 = "Please wait till the process has completed."
data_import_tool_66 = "Do you wish to import the new data (displayed above) into the project?"
data_import_tool_67 = "(Click the button below to import the data.)"
data_import_tool_68 = "NOTHING TO IMPORT:"
data_import_tool_69 = "All the data from the uploaded file already exists in the project."
data_import_tool_70 = "The data you uploaded from the file was successfully imported into the project. If you wish to import more data, you may use the box above to select another file on your computer."
data_import_tool_76 = "When you have done this, upload the file again."
data_import_tool_83 = "The value of"
data_import_tool_84 = "must be an integer."
data_import_tool_85 = "must be numeric."
data_import_tool_86 = "must be a 10-digit phone number."
data_import_tool_87 = "Email address is not properly formatted."
data_import_tool_90 = "Invalid date format. (NOTE: Dates must be imported here only in Y-M-D or M/D/Y format, regardless of the specific date format designated for this field.)"
data_import_tool_97 = "ERROR DISPLAY TABLE"
data_import_tool_98 = "Field Name"
data_import_tool_99 = "Value"
data_import_tool_100 = "Error Message"
data_import_tool_102 = "Instructions for Data Review"
data_import_tool_104 = "The directory"
data_import_tool_105 = "is NOT writable on this server. That directory must exist and must be writable in order for this module to function."
data_import_tool_106 = "Since you have been assigned to a Data Access Group, you are only able to import data for your group."
data_import_tool_110 = "Record format:"
data_import_tool_112 = "Rows"
data_import_tool_113 = "Columns"
data_import_tool_114 = "Please select a file first"
data_import_tool_116 = "Microsoft help page"
data_import_tool_117 = "for further instruction."
data_import_tool_118 = "Your CSV data file can be either of two formats, in which each record can be saved as a ROW or as a COLUMN. To designate which, please select it using the record format drop-down in the green box. Selecting the incorrect format will result in errors and not allow the import to complete."
data_import_tool_132 = "Please supply a reason for the data changes for EACH existing record in the text boxes."
data_import_tool_133 = "Import Successful!"
data_import_tool_134 = "The record ID field"
data_import_tool_135 = "could not be found in cell A1 of the uploaded CSV file, so REDCap has no way to tell which record is which. Please make sure that variable is in A1 and that all relevant variable names are in Row 1."
data_import_tool_136 = "could not be found in cell A1 or A2 of the uploaded CSV file, so REDCap has no way to tell which record is which. Please make sure that variable is in A1 or A2 and that all relevant variable names are in Column A."
data_import_tool_137 = "Time is not properly formatted as HH:MM (military format)."
data_import_tool_138 = "Vanderbilt medical record number is not properly formatted. It should be 4- to 9-digit number (excluding leading zeros)."
data_import_tool_144 = "existing record"
data_import_tool_145 = "new record"
data_import_tool_150 = "Invalid datetime format. (NOTE: Dates must be imported here only in Y-M-D H:M[:S] or M/D/Y H:M[:S] format, regardless of the specific date format designated for this field.)"
data_import_tool_153 = "must be a 5 or 9 digit U.S. ZIP Code"
data_import_tool_154 = "Duplicate value for the Secondary Unique Field"
data_import_tool_155 = "This value cannot be imported because another record already has this same value for this field. The value can never duplicate in other records."
data_import_tool_159 = "Your user privileges do NOT allow you to create new records. You may only edit existing records. Since your uploaded data file contains records that do not yet exist in this project, you will not be allowed to import them. Please remove the following records from your file and try uploading it again:"
data_import_tool_160 = "<b>Uploaded files must be in CSV file format only.</b> If your file is saved as an XLS, XLSX, or similar format, please try opening the file in Excel, then save the file again but as a CSV file. If you are having difficulty doing this, please see the"
data_import_tool_161 = "cannot be modified because it has been set as this project's randomization field, which can never be modified for any record. This field MUST be removed from the uploaded data file."
data_import_tool_162 = "This field"
data_import_tool_163 = "has already been randomized, thus this field"
data_import_tool_164 = ", which is a randomization strata field, cannot be modified for this record. You MUST remove this field's value for this record from the uploaded data file."
data_import_tool_165 = "exists on an instrument that is not designated for the event named"
data_import_tool_166 = "You are not allowed to import data for this field into this event."
data_import_tool_171 = "Illegal use of 'redcap_data_access_group' field!"
data_import_tool_172 = "You are currently in a Data Access Group, which means that you can only edit records belonging to your group, and also that any new records you create get added to your group automatically. Using the 'redcap_data_access_group' field as a means to add or attribute a record to a group can ONLY be done by someone that is NOT in a Data Access Group. Please remove that column from your data import file and try again."
data_import_tool_173 = "Trying to assign multiple Data Access Groups per record!"
data_import_tool_174 = "It appears that you may have mistakenly been trying to assign a single record to two or more different Data Access Groups, which is not allowed. Please go back in your data import file and make sure that each record is only assigned to one single Data Access Group. The following is a list of those records:"
data_import_tool_176 = "How to assign records to Data Access Groups:"
data_import_tool_177 = "Since this project has Data Access Groups and since you are not in a group, you are able to assign or re-assign records to groups. You may assign records to groups by utilizing the '<b>redcap_data_access_group</b>' field in your data import file, in which you will provide a <b>unique group name</b> for each record. A list of all the unique names for each Data Access Group are listed on the"
data_import_tool_178 = "How to import records for events:"
data_import_tool_179 = "In order to import records for longitudinal projects such as this one, you must use the '<b>redcap_event_name</b>' field in your data import file, in which you will provide a <b>unique event name</b> for each record. This will tell it which event that the data belongs to for that record. A list of all the unique names are listed on the"
data_import_tool_180 = "If the 'redcap_event_name' field is not specified for every record being imported, it will display an error."
data_import_tool_183 = "record was created or modified during the import."
data_import_tool_184 = "records were created or modified during the import."
data_import_tool_185 = "is part of a matrix of fields that has ranking enabled, in which the field has the same value as another field in the same matrix (either a saved value or a value being imported), which is prohibited by the ranking functionality. You will need to change the value of this field or the other field having the same value in the matrix."
data_import_tool_186 = "Format for date/datetime values:"
data_import_tool_187 = "Format for min/max validation values for date and datetime fields:"
data_import_tool_188 = "Invalid date format. (NOTE: Dates must be imported here only in Y-M-D or D/M/Y format, regardless of the specific date format designated for this field.)"
data_import_tool_189 = "Invalid datetime format. (NOTE: Dates must be imported here only in Y-M-D H:M[:S] or D/M/Y H:M[:S] format, regardless of the specific date format designated for this field.)"
data_import_tool_190 = "Invalid date format. (NOTE: Dates must be imported here only in Y-M-D format, regardless of the specific date format designated for this field.)"
data_import_tool_193 = "Invalid date format. (NOTE: Dates must be imported here only in Y-M-D H:M[:S] format, regardless of the specific date format designated for this field.)"
data_import_tool_194 = "Invalid date format. (NOTE: Dates must be imported here only in M/D/Y H:M[:S] format, regardless of the specific date format designated for this field.)"
data_import_tool_195 = "Invalid date format. (NOTE: Dates must be imported here only in D/M/Y H:M[:S] format, regardless of the specific date format designated for this field.)"
data_import_tool_196 = "is a field that belongs to a PROMIS computer adaptive test (CAT) instrument. No data can be imported for any field on an adaptive instrument. Please remove this field/value from the data import file and try again."
data_import_tool_197 = "Calculated fields cannot be imported because they will be calculated automatically during the import process. All calculated fields will simply be ignored during the import."
data_import_tool_198 = "Format for the minimum validation value is incorrect because it does not follow the expected format:"
data_import_tool_199 = "Format for the maximum validation value is incorrect because it does not follow the expected format:"
data_import_tool_200 = "The data is not in the specified format."
data_import_tool_201 = "No data was provided."
data_import_tool_202 = "The dataFormat parameter provided ("
data_import_tool_203 = ") is not a valid option. Only the following options are valid:"
data_import_tool_204 = "The type parameter provided ("
data_import_tool_205 = "The dateFormat parameter provided ("
data_import_tool_207 = "The overwriteBehavior parameter provided ("
data_import_tool_208 = "The data_access_group parameter provided ("
data_import_tool_209 = ") is not a valid option."
data_import_tool_210 = "The following values of event_id are invalid:"
data_import_tool_211 = "The record name cannot be empty."
data_import_tool_212 = "The record id field ("
data_import_tool_213 = ") is missing."
data_import_tool_214 = "The record event name is missing."
data_import_tool_215 = "The record name ("
data_import_tool_216 = ") cannot contain a plus sign (+), ampersand (&), pound sign (#), or apostrophe."
data_import_tool_217 = "The records listed below occur more than once. Please remove any duplicates and try again:"
data_import_tool_218 = "The following fields were not found in the project as real data fields:"
data_import_tool_219 = "The following values of redcap_event_name are invalid:"
data_import_tool_220 = "The following Data Access Group are invalid for the redcap_data_access_group field:"
data_import_tool_221 = "This field is located on a form that is locked. You must first unlock this form for this record."
data_import_tool_222 = "The value is not a valid category for"
data_import_tool_223 = "should not be less than the field minimum"
data_import_tool_224 = "is less than the field minimum"
data_import_tool_225 = "should not be greater than the field maximum"
data_import_tool_226 = "is greater than the field maximum"
data_import_tool_227 = "is a checkbox field and thus can only have a value of '1' (checked) or '0' (unchecked)."
data_import_tool_229 = "CHECKBOX RENAME ERROR: Although this field does exist in the database, it is a 'checkbox' field type, and checkboxes must be converted to a new variable name format to be imported, as follows: field name + triple underscore + coded value. For example, if coded value '2' (Asian) is checked off for field 'race', then the field name should be 'race___2' and the value should be '1' (1 for checked, 0 for unchecked). Please rename this field."
data_import_tool_230 = "This field name does not exist in the project."
data_import_tool_231 = "Allow blank values to overwrite existing saved values?"
data_import_tool_233 = "Record names must be 100 characters or less in length. The following record name is too long and thus cannot be imported:"
data_import_tool_236 = "Are you sure you wish to REPLACE EXISTING SAVED VALUES WITH BLANK VALUES (i.e., blank cells) from your uploaded CSV file? This means that any cell in the CSV file that is empty/blank (i.e., has no value) will overwrite an existing value for the given record (if the record already has a value for that field)."
data_import_tool_237 = "Warnings were detected in the file that was uploaded."
data_import_tool_238 = "Invalid date format. (NOTE: Dates must be imported here only in M/D/Y format or Y-M-D format, regardless of the specific date format designated for this field.)"
data_import_tool_239 = "Invalid date format. (NOTE: Dates must be imported here only in D/M/Y format or Y-M-D format, regardless of the specific date format designated for this field.)"
data_import_tool_240 = "The XML file could not be processed because it appears not to be valid XML or is missing certain basic components."
data_import_tool_241 = "This module may be used for importing data into this project from a CSV file or alternatively from an XML file in CDISC ODM format. Below are the steps you will need to follow in order to import your data successfully into this project."
data_import_tool_242 = "CSV import"
data_import_tool_243 = "CDISC ODM (XML) import"
data_import_tool_244 = "Upload your CDISC ODM (XML) file:"
data_import_tool_245 = "No, ignore blank values in the file"
data_import_tool_246 = "Yes, blank values in the file will overwrite existing values"
data_import_tool_248 = "CDISC ODM (Operational Data Model) is a specific XML data format, ODM is a vendor neutral, platform independent format for interchange and archival of data. Data can be imported into and exported out of REDCap projects in CDISC ODM format."
data_import_tool_249 = "Below you may import data into this project from an CDISC ODM (XML) file that was produced from a REDCap export or from another ODM-compatible system outside of REDCap. NOTE: The XML must be ODM version 1.3.X."
data_import_tool_250 = "On this page, you may import the metadata (and also data, optionally) to create a new project from an CDISC ODM (XML) file that was produced from a REDCap export or from another ODM-compatible system outside of REDCap. NOTE: The XML must be ODM version 1.3.X. If the ODM file originates from another system outside REDCap, REDCap will do its best to attempt to convert the data types and other attributes in the file to REDCap-equivalent data types and attributes, although they might not be exactly alike."
data_import_tool_251 = "The following records cannot be modified because they do not belong to your Data Access Group:"
data_import_tool_252 = "Trying to import repeat instance/instrument fields!"
data_import_tool_253 = "The fields 'redcap_repeat_instrument' and 'redcap_repeat_instance' are reserved for when 'Repeating Instruments and Events' have been enabled on the Project Setup page. This project does not have that feature enabled, so you may not import data with those fields."
data_import_tool_254 = "The following values for 'redcap_event_name' are not valid unique event names for this project, so you will need to fix them and then reimport this data:"
data_import_tool_255 = "should not have a value. This is a Repeating Event, which must always have a blank value for the redcap_repeat_instrument field. Please remove this value from the data import file and try again."
data_import_tool_258 = "OTHER ERROR:"
data_import_tool_259 = "must be the unique form name of a Repeating Instrument. It currently does not match the unique form name of any Repeating Instruments. Please fix this in the data import file and try again."
data_import_tool_260 = "does not exist on the Repeating Instrument named"
data_import_tool_261 = "You are not allowed to import data for this field into this Repeating Instrument."
data_import_tool_262 = "exists on a Repeating Instrument named"
data_import_tool_263 = "However, the fields 'redcap_repeat_instance' and/or 'redcap_repeat_instrument' for this row of data have no value, which are both required for importing data into a Repeating Instrument. You are not allowed to import data for this field into a non-repeating instrument."
data_import_tool_264 = "A field validation type is required in order to have a minimum or maximum validation value. The following cells are missing a validation type:"
data_import_tool_266 = "No, use the record name provided"
data_import_tool_268 = "tentative new record"
data_import_tool_269 = "Please select an XML file first"
data_import_tool_270 = "NOTE: Since you elected to force record auto-numbering, listed below are the record names you submitted and also what they were renamed to during the import process. Since the uploaded record names are not stored anywhere in REDCap, it is not possible to download the table below, but instead <b>you may copy and paste the table below</b> to Excel or other program to keep for reference."
data_import_tool_271 = "Uploaded record name"
data_import_tool_272 = "Saved record name"
data_import_tool_274 = "This field is located on a repeating instrument; however, no value has been provided for the field 'redcap_repeat_instrument' in the data file for this item. Please provide a value for redcap_repeat_instrument, which will be the unique form name of the field's instrument."
data_import_tool_275 = "required key not present"
data_import_tool_276 = "event '%s' is not available in project '%s'"
data_import_tool_277 = "instrument '%s' is not available in project '%s'"
data_import_tool_278 = "This field is located on a survey that was completed using the e-Consent Framework. Once a survey response has been completed via the e-consent process, its data values cannot be modified. You will not be able to import this value for this record-event-survey-instance."
data_import_tool_279 = "Values being imported into a repeating instrument/event cannot have the 'redcap_repeat_instance' field with a value of '0'. It must have a numeric value greater than '0'. The following records cannot be imported until this is changed:"
data_import_tool_281 = "cannot have a value since this instrument or event is not a repeating instrument or repeating event, respectively. The redcap_repeat_instance field must be left blank for this row of data."
data_import_tool_282 = ") with event"
data_import_tool_283 = "cannot be imported. This is because this event is a repeating event, but the field 'redcap_repeat_instance' could not be found in the data import fields. In order to import data for a repeating event, the field 'redcap_repeat_instance' is required in the imported data set."
data_import_tool_284 = ") with redcap_repeat_instance"
data_import_tool_285 = "cannot be imported. This is because the field 'redcap_repeat_instrument' could not be found in the data import fields or because it has a blank value. In order to import data for a repeating instrument, the field 'redcap_repeat_instrument' is required in the imported data set."
data_import_tool_286 = "must have a numeric value between '1' and '32767' for any Repeating Event or Repeating Instrument. Please add a valid numeric value to redcap_repeat_instance in the data import file and try again."
data_import_tool_287 = "This project is current in Analysis/Cleanup status and its data is currently set to 'Read-only/Locked', so no data can be saved in this project."
data_import_tool_288 = "This record has been locked at the record level."
data_import_tool_289 = "No value within this record can be modified."
data_import_tool_290 = "This field is locked and cannot be modified."
data_import_tool_291 = "Century assumed from 2-digit year as"
data_import_tool_292 = "Minutes missing and assumed to be :00 for"
data_import_tool_293 = "Seconds missing and assumed to be :00 for"
data_import_tool_294 = "Minutes missing from value and assumed to be :00 for"
data_import_tool_295 = "Century assumed from 2-digit year as"
data_import_tool_296 = "TIP: If importing repeating instances for a repeating event or repeating instrument, you may <u>auto-number the instances</u> by providing a value of '<b>new</b>' for the 'redcap_repeat_instance' field in the dataset you are importing. This is useful because it allows you to import such data without the need to determine how many instances already exist for a given repeating event/instance prior to the import."
data_import_tool_297 = "Pseudo-calc fields (i.e., fields with the @CALCDATE or @CALCTEXT action tag) cannot be imported because they will be calculated automatically during the import process. All calculated fields and pseudo-calc fields will simply be ignored during the import."
data_import_tool_298 = "This field is an ontology auto-suggest field, and while it is allowable to import data for this field, it is generally advised against since this value might not display correctly if viewed afterward on a report or in the data entry interface."
data_import_tool_299 = "must be an integer"
data_import_tool_300 = "This field represents a Missing Data Code for a checkbox field; however, other checkbox options for this same field have a Missing Data Code set for them, which is not valid. Only one Missing Data Code can be used per field. Please remove the other Missing Data Codes so that there exists only one for this checkbox field."
data_import_tool_301 = "<b>NOTICE:</b> The 'new' value option for auto-numbering instances does NOT work for 'eav' type data but only for 'flat' type."
data_import_tool_302 = ") has a value of 'new' for 'redcap_repeat_instance', which is not allowed for 'eav' type data. The 'new' value for 'redcap_repeat_instance' can only be used when type=flat."
data_import_tool_303 = "Some values cannot be imported because they exist multiple times in the data currently being imported. Each value for this field must be unique and cannot duplicate another value. Duplicate values found in the imported data:"
data_import_tool_304 = "Copy to all"
data_import_tool_305 = "<b>ERROR:</b><br>You did not upload an XML file. Please upload a file with XML file extension."
data_import_tool_306 = "<b>ERROR:</b><br>You did not upload a CSV (comma delimited) file. Please upload a file with CSV file extension."
data_import_tool_307 = "This record cannot be imported because it already exists in the project and belongs to another Data Access Group."
data_import_tool_308 = "ERROR: It appears that the uploaded data file is not on the correct format and thus cannot be processed. Check to make sure you uploaded the correct file."
data_import_tool_309 = "You may import the data immediately in real time, or alternatively you may import the data using an asynchronous background process. The background process is better for large data files but overall may take longer to import. The background process will email you after your data has been fully imported. If any errors occur during the background import process, you will be able to view all the errors with the option to re-download the data that failed to import, thus allowing you to fix the data and attempt to import it again."
data_import_tool_310 = "Import in real time"
data_import_tool_311 = "Import as background process (better for large data sets)"
data_import_tool_312 = "ERROR: An unknown error occurred while REDCap was parsing the CSV data file that was uploaded. Check to make sure it is the correct file."
data_import_tool_313 = "<b>SUCCESS!</b> Your CSV data file was successfully uploaded. REDCap will now begin importing its data using a background process. You will be notified via email at"
data_import_tool_314 = "once your entire file has been imported fully. If any errors were found in the file, details will be provided to allow you to fix the data (if you wish) and upload it again."
data_import_tool_315 = "Your data import has completed!"
data_import_tool_316 = "Your REDCap data import began on {0}, and it completed on {1}. {3} of the {2} records submitted were successfully imported. A total of {4} errors occurred during the import."
data_import_tool_317 = "View the results of your data import"
data_import_tool_319 = "You may import a modified version of a CSV data export file, or you can obtain a blank CSV data import template that you can save locally and add data that you wish to import."
data_import_tool_320 = "(with records in row format), or alternatively download the template with records in"
data_import_tool_321 = "column format"
data_import_tool_322 = "Choose your upload settings below, and select the data file located on your device. Then click the 'Upload File' button to begin the upload process. The data file will be checked for errors to ensure that all the data is in the correct format before it is fully imported into the project. By default, the data will be imported in real time; however, you may choose to import the data using a background process in which you will be notified via email once your data has been successfully imported."
data_import_tool_323 = "Add data to the file, and save it."
data_import_tool_324 = "CSV delimiter of data file:"
data_import_tool_325 = "Choose an import option"
data_import_tool_327 = "Overwrite data with blank values?"
data_import_tool_328 = "File format settings"
data_import_tool_329 = "Records in file are formatted as"
data_import_tool_330 = "Select your CSV data file"
data_import_tool_331 = "Setting this to YES will allow blank values (i.e., empty cells) in your CSV data file to overwrite saved values, thus erasing existing data in the project."
data_import_tool_332 = "View background imports"
data_import_tool_333 = "Display the data comparison table?"
data_import_tool_334 = "No, do not display uploaded data (faster)"
data_import_tool_335 = "Yes, display uploaded data prior to importing"
data_import_tool_336 = "Displaying the data comparison table is often helpful because it allows you to confirm the data is all correct prior to importing it. Additionally, if a record already  exists, it will display the previous value (that will be overwritten) compared with the new value you are about to import. The downside is that displaying the data comparison table can  sometime take a while to render and make the process slower if you are importing a large amount of data values."
data_import_tool_337 = "Failed"
data_import_tool_338 = "Processing"
data_import_tool_339 = "Queued"
data_import_tool_340 = "File was uploaded and will be processed soon"
data_import_tool_341 = "- {0} errors occurred"
data_import_tool_342 = "Note: Since the background process imports each record separately, any error occurring for a record would prevent all data from being imported for that particular record.  Records with no errors would have been imported successfully.  Any records that had errors (and thus were not able to be imported) can be re-downloaded, along with their error messages, on the Data Import Tool page using the link below.  You may download them, fix their data, and re-import them, if you wish."
data_import_tool_343 = "Before you can import the CSV data file using a background process, you must first confirm that the file is truly the intended file.  Displayed below are the file name, file size, and the first two lines of the file. If this is the correct file, click Confirm. If not, then choose another file to upload."
data_import_tool_344 = "Confirm the data file is the correct file"
data_import_tool_345 = "First two lines (or more) of the file:"
data_import_tool_346 = "Status"
data_import_tool_347 = "Upload Time"
data_import_tool_348 = "Completion Time"
data_import_tool_349 = "Original Filename"
data_import_tool_350 = "Uploader"
data_import_tool_351 = "Records Provided"
data_import_tool_352 = "Records Imported"
data_import_tool_353 = "Total Import Time (minutes)"
data_import_tool_354 = "Errors"
data_import_tool_355 = "View details"
data_import_tool_357 = "View details of this import"
data_import_tool_358 = "<b>This background import process contained {0} errors, and thus {1} records were not able to be imported.</b> Below, you may download two separate files: one that contains a detailed list of all the errors for the import and one that contains all the data for the records that could not be imported (from the originally uploaded file). You may use these files, if you wish, to correct the data and then retry importing the CSV data file again."
data_import_tool_362 = "The file you selected is larger than 1 MB, which is fairly large for a CSV file. Given this, it is recommended that you use the background process for importing your data (rather than importing it all in real time). If you do not use the background process, importing your data might take a very long time, and in some cases, might fail due to its size."
data_import_tool_363 = "File is large. Consider using the background process."
data_import_tool_364 = "Yes, use background process"
data_import_tool_365 = "No, import in real time"
data_import_tool_366 = "No, let the import continue"
data_import_tool_368 = "The background import process has been successfully cancelled."
data_import_tool_369 = "Sorry, but you are not the one who uploaded the data file. Only the user who started the background import process (or a REDCap administrator) has the ability to cancel it."
data_import_tool_370 = "Download list of all errors"
data_import_tool_371 = "Download records/data that did not import"
data_import_tool_372 = "Sorry, but you are not the one who uploaded the data file. Only the user who started the background import process (or a REDCap administrator) has the ability to download the files above."
data_import_tool_373 = "Record (Tentative Name)"
data_import_tool_374 = "Refresh table"
data_import_tool_375 = "Paused"
data_import_tool_376 = "correct any errors, save the file, and then select the CSV file above before you click the Upload File button."
data_import_tool_377 = "Be sure the Variables/Field Names are not changed or an error may occur."
data_import_tool_378 = "These coded values can be found in the"
data_import_tool_379 = "The fields listed below from your data import file are not valid Field Variables in the project, and thus they cannot be imported. Please choose another data file or alternatively fix the existing data file, and then try again."
data_import_tool_380 = "Before the background import process begins, please supply a reason for the data changes being made. Note: This will be applied to *every existing record* in the data import file."
data_import_tool_381 = "Please supply a reason for the data changes being made."
data_import_tool_382 = "NOTICE: This option is disabled because the 'Reason for Changes' feature is enabled in the project."
data_import_tool_383 = "Initializing"
data_import_tool_384 = "Record names cannot contain BR tags, line breaks, or carriage return characters. The following record name contains a BR tag, line break, or carriage return, and thus cannot be imported:"
data_import_tool_385 = "Yes, use record auto-numbering for each record provided"
data_import_tool_386 = "Auto-number/overwrite record IDs?"
data_import_tool_387 = "Rename Imported Records?"
data_import_tool_388 = "Because this project has record auto-numbering enabled (every new record is assigned the next sequential record name/id), you have two options for your import."
data_import_tool_389 = "<ul><li><b>Option 1</b>: Use the record name/id provided in the import file. If a record with the same record name/id already exists, the data in the import file will be used to <b>update</b> that record. If the record name/id in the import file does <b>not</b> already exist, it will be imported as a <b>new</b> record using the record name/id provided in the import file.</li><li><b>Option 2:</b> Rename the imported records. When this option is chosen, every record in the import file will be treated as a <b>new</b> record. The record name/id in the import file (which <b>must</b> be provided) will be changed to the next available record name/id.</li></ul>"
data_import_tool_390 = "Halt import"
data_import_tool_391 = "Halt this background import?"
data_import_tool_392 = "This background data import is currently being processed, but you may halt it if you wish. Please note that halting it will not undo changes to any data values that have      been imported thus far, but it will prevent further data from being imported."
data_import_tool_393 = "Yes, halt it now"
data_import_tool_394 = "You have not entered a \"reason for data changes\" for {0} records. Please supply a reason in the text box for each before you can continue."
database_mods_01 = "Project Modification Module"
database_mods_03 = "Based on the drafted version of the project fashioned by the project users, the project fields that are to be added, deleted, or modified are displayed in the table below so that all changes to the project may be scrutinized before these changes are committed permanently. You will need to determine if any problems exist in the new drafted version of the project that might need to be addressed before proceeding. If everything looks correct, and you wish to go ahead with the changes, click the Commit Changes at the bottom of the page. To reject the changes made, click the Reject Changes button, which will place the project back in Draft Mode for the users to continue modifying or correcting any errors."
database_mods_04 = "Review Drafted Changes"
database_mods_05 = "The project fields that have been be added, deleted, or modified while in Draft Mode are displayed in the table below so that you may view all drafted changes before they are committed permanently by a REDCap administrator."
database_mods_07 = "Would you like to permanently commit the drafted changes to the project as shown above?"
database_mods_08 = "COMMIT CHANGES TO PROJECT?"
database_mods_09 = "Are you sure you wish to commit these changes to the project?"
database_mods_10 = "These changes will be permanent."
database_mods_11 = "REJECT CHANGES TO PROJECT?"
database_mods_12 = "Are you sure you wish to reject these changes? If so, the project will be placed back into DRAFT MODE in order for users to make more edits or undo any mistakes."
database_mods_14 = "Are you sure you wish to erase all changes made in DRAFT MODE? If so, the project will be taken out of Draft Mode, and all drafted changes will be deleted."
database_mods_15 = "was replaced with"
database_mods_16 = "The following variable/field names were duplicated. Please rename these field names so that they only appear once."
database_mods_17 = "Each row MUST have a variable/field name, but the following cells have a field name missing: "
database_mods_18 = "Variables/field names cannot begin with a number. Remove the numeral from the beginning of the following field names:"
database_mods_19 = "Variables/field names cannot have a triple underscore (___). Remove the triple underscore from the following field names:"
database_mods_20 = "Variables/field names cannot begin with an underscore character. Remove the underscore character from the beginning of the following field names:"
database_mods_21 = "Variables/field names must consist of ONLY lower-case letters, numbers, and underscores."
database_mods_22 = "Variables/field names are recommended to be less than 26 characters in length. You may want to shorten the following variable names:"
database_mods_23 = "Variables/field names cannot be more than 100 characters in length. Shorten the following variable names:"
database_mods_24 = "This is an illegal variable name and cannot be used. Please change the variable name in the following cells: "
database_mods_25 = "Variables/field names must consist of ONLY lower-case letters, numbers, and underscores: "
database_mods_26 = "Each row MUST have a form name, but the following cells have a form name missing: "
database_mods_27 = "Form names must consist of ONLY lower-case letters, numbers, and underscores: "
database_mods_28 = "Form names must consist of ONLY lower-case letters, numbers, and underscores, and cannot begin with a number."
database_mods_29 = "Form names must be sequential and cannot repeat again after being used for another form. Rename the following form names beginning with the values listed below:"
database_mods_30 = "Form names are recommended to be less than 50 characters in length. You may want to shorten the following form names:"
database_mods_31 = "Form names cannot be more than 64 characters in length. Shorten the following form names:"
database_mods_32 = "Variables/field names cannot be named [form_name]+'_complete', in which [form_name] corresponds to an existing Form Name in column B. Please change the following variable names:"
database_mods_33 = "Suggestion: replace with"
database_mods_34 = "The only valid field types are"
database_mods_35 = "and must all be lower-case. The following are invalid field types listed in your data dictionary:"
database_mods_36 = "Each row MUST have a field type, but the following cells have a field type missing: "
database_mods_37 = "Each 'calc' field must have an equation in column F, but the following cells have an equation missing: "
database_mods_38 = "There is a syntactical error in the 'calc' field equation for the following cells: "
database_mods_39 = "Each multiple choice field (radio, drop-down, checkbox, etc.) must have choices listed in column F, but the following cells have choices missing: "
database_mods_40 = "Multiple choice fields have been found where a coded value is duplicated in the choices column (F). All multiple choice fields must have a unique coded value for every option. Please remove any duplications for the coded values in the following cells: "
database_mods_41 = "For security purposes, 'sql' field types can ONLY be added or modified by REDCap administrators. You may continue the upload if you remove the variables listed below, or you may ask a REDCap administrator to look them over to approve them and then upload this data dictionary for you."
database_mods_42 = "It appears that you have modified an 'sql' field. For security purposes, 'sql' field types can ONLY be added or modified by REDCap administrators. For the variables listed below, you will need to either set the field's value in column F back to its existing value in your data dictionary or ask a REDCap administrator to look them over to approve them and then upload this data dictionary for you."
database_mods_44 = "There are illegal characters inside the square brackets in a 'calc' field equation."
database_mods_45 = "There are variables used in calculated field equation(s) that are not listed as real variables in column A. All variables used in calculations must exist in column A. Below are the variables not found in column A."
database_mods_46 = "It is recommended that each row have a field label in order to distinguish fields, but the following cells have a field label missing: "
database_mods_47 = "Drop-down and radio button fields will typically have more than one choice listed. An error may exist for the following cells, which only have one choice listed: "
database_mods_48 = "The only valid validation types are"
database_mods_49 = "and must all be lower-case. The following are invalid validation types in your data dictionary:"
database_mods_50 = "Only 'text' field types may have validation. The following validation types should be removed from your data dictionary or else their field type should be changed to 'text': "
database_mods_51 = "Validation types must consist of lower-case letters."
database_mods_52 = "The only valid value for the Identifier column is 'y' or 'Y'. The following invalid values were automatically removed from your data dictionary and replaced with a blank:"
database_mods_53 = "There is a syntactical error in the branching logic for the following cells: "
database_mods_54 = "There are illegal characters inside the square brackets of some branching logic."
database_mods_55 = "There are variables used in the branching logic that are not listed as real variables in column A. All variables used in branching logic must exist in column A. Below are the variables not found in column A."
database_mods_56 = "for variable"
database_mods_57 = "The only valid value for the Required Field column is 'y' or 'Y'. The following invalid values were automatically removed from your data dictionary and replaced with a blank:"
database_mods_59 = "Your data dictionary could NOT be uploaded because of the errors listed below. Please correct these errors and try uploading your data dictionary again."
database_mods_60 = "Errors found in your Data Dictionary:"
database_mods_61 = "Allowable warnings found in your Data Dictionary:"
database_mods_62 = "Below is a listing of the changes to be committed to this project."
database_mods_65 = "Section Header"
database_mods_66 = "Field Type"
database_mods_68 = "Choices or Calculations"
database_mods_69 = "Field Note"
database_mods_70 = "Text Validation Type"
database_mods_71 = "Text Validation Min"
database_mods_72 = "Text Validation Max"
database_mods_73 = "Identifier?"
database_mods_74 = "Branching Logic"
database_mods_75 = "Required Field?"
database_mods_76 = "There are currently no changes to show"
database_mods_77 = "*Possible data loss if field type changes. Check if okay."
database_mods_78 = "*Data MIGHT be lost due to deleted choice(s)"
database_mods_79 = "*Possible label mismatch because of label changes. Check if okay."
database_mods_80 = "Fields to be ADDED:"
database_mods_81 = "none"
database_mods_82 = "Fields to be DELETED:"
database_mods_83 = "KEY for Comparison Table below"
database_mods_84 = "White cell = no change"
database_mods_85 = "Yellow cell = field changed (Black text = new value,"
database_mods_86 = "Gray text = current value"
database_mods_87 = "Green cell = new project field"
database_mods_88 = "Fields to be added:"
database_mods_89 = "Total resulting field count:"
database_mods_90 = "Fields to be deleted:"
database_mods_91 = "Existing field count:"
database_mods_92 = "Changing record ID field:"
database_mods_93 = "The current record ID field (i.e. the first field on the first form), to which all existing data records are connected, has either been moved from the first field position or deleted from the Data Dictionary."
database_mods_94 = "Current record ID field:"
database_mods_95 = "Record ID field from uploaded Data Dictionary:"
database_mods_96 = "To prevent the introduction of any data errors, the field must be added back to the first field position in the Data Dictionary."
database_mods_97 = "Forms to be DELETED:"
database_mods_98 = "Forms to be ADDED:"
database_mods_101 = "The fields listed below are being utilized by DTS and will likely cause issues if the Drafted Changes made here are committed. If you wish to make these changes, you will additionally need to update the DTS Admin page with these changes immediately afterward. If this is not done, errors will occur the next time DTS attempts to pull data from the external system."
database_mods_102 = "DTS fields being deleted:"
database_mods_103 = "DTS fields whose field type is being changed:"
database_mods_105 = "Image/File Attachment"
database_mods_106 = "The only valid values for the Custom Alignment column are"
database_mods_107 = "The following invalid values were automatically removed from your data dictionary and replaced with a blank:"
database_mods_108 = "Stop Actions"
database_mods_109 = "The first field must be a 'text' field type. It will automatically be set as a 'text' field in the following cell:"
database_mods_110 = "Total field count AFTER the changes below are committed:"
database_mods_111 = "Total field count BEFORE the changes below are committed:"
database_mods_112 = "Fields to be modified:"
database_mods_114 = "Will these changes be automatically approved?"
database_mods_115 = "It appears that some of your multiple choice fields have choices that do not have a raw value explicitly defined but instead only contain a label. For multiple choice fields, both a raw value AND a label should be defined for each choice. Thus the cells listed below will have one or more of its raw values automatically supplied:"
database_mods_118 = "The following fields cannot be deleted because they are being utilized in the randomization module:"
database_mods_120 = "Matrix group names must consist of ONLY lower-case letters, numbers, and underscores: "
database_mods_121 = "Matrix group names cannot be more than 60 characters in length. Shorten the following matrix group names:"
database_mods_122 = "Matrix group names must be sequential and cannot repeat again after being used for another group. Rename the following matrix group names beginning with the values listed below:"
database_mods_123 = "The cells listed below appear to be in a matrix group, but all the fields in this matrix group do not have the same multiple choice options. Please make sure that all fields in this group have the EXACT same choices in column F."
database_mods_124 = "The choices should be:"
database_mods_125 = "Fields that are part of a matrix group can ONLY be a radio or checkbox field. The fields below need to be changed so that the field is either of those field types."
database_mods_126 = "Fields that are part of a matrix group must be ALL radio buttons or ALL be checkbox fields. The fields below have been automatically converted to match the field type of other fields within the same matrix group."
database_mods_127 = "will be automatically changed to"
database_mods_128 = "Descriptive fields cannot be designated as 'required'. The 'required' designation for the following variables were automatically removed from your data dictionary and replaced with a blank:"
database_mods_130 = "Total potentially critical issues:"
database_mods_131 = "Details regarding all changes made in Draft Mode:"
database_mods_132 = "Matrix Group Name"
database_mods_133 = "*Deleted options are okay since those options have no data."
database_mods_134 = "Deleted fields that contain data:"
database_mods_136 = "OPTIONAL: Notify user of any issues before committing changes?"
database_mods_137 = "Compose confirmation email"
database_mods_138 = "COMMIT CHANGES"
database_mods_139 = "Reject Changes"
database_mods_140 = "Remove All Drafted Changes"
database_mods_141 = "Confirm production changes to your project"
database_mods_142 = "(user that requested changes)"
database_mods_143 = "Dear REDCap user,"
database_mods_144 = "We received your request for making production changes to the REDCap project named"
database_mods_147 = "Sincerely,"
database_mods_148 = "Your REDCap administrator"
database_mods_149 = "ADMINISTRATOR ACTIONS:"
database_mods_150 = "Send Email"
database_mods_151 = "Below is a pre-filled confirmation email that you may use to send to the user who requested the production changes for this project. It has been pre-filled for your convenience, but you may modify the email subject and/or message however you wish. "
database_mods_153 = "*Label changes are okay since those options have no data."
database_mods_154 = "Multiple choice fields can only have coded values (in the choices in column F) that are numeric or alpha-numeric (lower case or upper case, with or without underscores), thus they cannot have codings that contain spaces or other characters. Please make the following corrections: "
database_mods_155 = "The only valid value for the Matrix Ranking column is 'y' or 'Y'. The following invalid values were automatically removed from your data dictionary and replaced with a blank:"
database_mods_156 = "If ranking is used for a matrix of fields, each field in the matrix must have the same value (either 'Y' or blank/null) for the Matrix Ranking column. Listed below are the matrix group names that have one or more fields in the matrix with a ranking value that differs from the other fields in the matrix:"
database_mods_157 = "The following fields have been modified or deleted. Since these fields belong to a computer adaptive test (CAT), the field and its attributes cannot be modified in any way. Please set these fields back to their original values for all attributes:"
database_mods_158 = "It appears that fields have been added to a data collection instrument that is a computer adaptive test (CAT). No fields should ever be added to this adaptive instrument. Please remove any extra fields that might have been added to one or more of the following adaptive instruments (see instrument name below in Column B of data dictionary):"
database_mods_159 = "(field was deleted)"
database_mods_160 = "Row"
database_mods_161 = "Record ID field was changed!"
database_mods_169 = "Mobile App:"
database_mods_170 = "user has"
database_mods_171 = "users have"
database_mods_172 = "initialized this project in the REDCap Mobile App. Please note that they *may* be affected by these changes and may not be able to successfully import their data from the app afterward. You may want to have them first sync all their data back to the server before committing the changes displayed on this page."
database_mods_173 = "records affected"
database_mods_174 = "records/events affected"
database_mods_175 = "records have orphaned data that will be restored"
database_mods_176 = "records/events have orphaned data that will be restored"
database_mods_177 = "Show all text"
database_mods_178 = "(open all 'show more' text)"
database_mods_179 = "Since there are records in this project, changing the Record ID field could have disastrous consequences, such as orphaning all your existing records. This is almost never recommended after data collection has begun."
database_mods_180 = "Commit all the drafted changes listed above."
database_mods_181 = "Keep the drafted changes made thus far, but place it back in Draft Mode for users to make more changes."
database_mods_182 = "Erase all the drafted changes made, and revert back to before Draft Mode was enabled."
database_mods_183 = "DELETE ALL DRAFT MODE CHANGES?"
database_mods_184 = "This project is not currently in draft mode (although it may have been in draft mode recently and then taken back out of draft mode). There are no modifications to review or approve."
database_mods_186 = "Open the To-Do List"
database_mods_187 = "Requires Response:"
database_mods_188 = "These changes WILL modify and/or delete existing data. So we ask 2 things of you:"
database_mods_189 = "These changes MIGHT modify and/or delete existing data. So we ask 2 things of you:"
database_mods_190 = "1. Please review a summary of all pending changes to your project at this link:"
database_mods_191 = "2. Once you've reviewed the pending changes at the link above, please <b style='color:red;'>reply to this email</b> and let us know which of the following options you wish us to take:"
database_mods_192 = "Commit the changes"
database_mods_193 = "Reject Changes"
database_mods_194 = "Keep the drafted changes made thus far, but place it back in Draft Mode for you to make more changes."
database_mods_196 = "Erase all the drafted changes made, and revert back to before Draft Mode was enabled."
database_mods_197 = "Please note: The choice you select above applies to all the changes you submitted. There's not a way to reject some changes and commit others, for example."
database_mods_198 = "You may also respond to this email if you have any questions. You will be notified automatically after the changes are processed. Thanks!"
database_mods_199 = "Choices should not contain a leading or trailing '|' symbol."
database_mods_200 = "This field is a survey completion timestamp field, which is not a real field in the project and cannot be imported. Its value will be ignored."
database_mods_201 = "Variables/field names cannot end with an underscore character. Remove all underscores from the end of the following field names:"
database_mods_202 = "Potentially critical issues in modified fields that contain data:"
database_mods_203 = "The placeholder Descriptive field for an e-Consent Form has been deleted or moved to another instrument:"
date_shift_01 = "Date Shifting for De-Identification"
date_shift_02 = "What is date shifting?"
date_shift_03 = "As part of the de-identification options in REDCap, all dates in the project may be shifted back in time up to"
date_shift_04 = "days so that they do not reflect the actual dates. When you choose to have all dates shifted, they will be shifted by a consistent length of time for each record, thus preserving the interval between dates. For example, if a subject, Mary, had three sequential appointments with dates of April 2, April 15, and April 26, when the dates are shifted, each appointment will remain in order sequentially with the same interval between appointments November 16, November 29, and December 10."
date_shift_05 = "Date shifting leaves the project record intact and will not effect the actual saved dates in the project. It merely alters the dates in their resulting format when performing a data export in REDCap (if the date shifting option is enabled). The shifted dates will always be the same for each record when performing a data export. The dates are shifted back in time up to"
date_shift_06 = "days, in which the shifted value is based on the"
date_shift_07 = "using a complex algorithm. Because the shifted value is based on the record name, the amount that dates are shifted is unique for each record, but the shifted amount is the same within each record to maintain internal consistency."
date_shift_08 = "Why is date shifting important?"
date_shift_09 = "Date shifting is important for de-identification because dates, like name and social security number, are identifiers that can be used for identifying an individual and thus possibly exposing confidential personal information. Date shifting prevents any dates from being used as identifiers for each project record while preserving the interval between dates."
define_events_03 = "This application allows you to define 'events' for your project that allow for the <b>utilization of data collection forms multiple times for any given project record</b> (often used when collecting longitudinal data)"
define_events_04 = ", as well as for <b>generating new schedules</b> to display on the"
define_events_05 = ". An 'event' may be a temporal event in the course of your project, such as a participant visit or a task to be performed. After events have been defined, "
define_events_06 = "you may use them and their Days Offset value to generate schedules. For data collection purposes, you will additionally "
define_events_07 = "you will "
define_events_08 = "need to designate the data collection instruments that you wish to utilize for any or all events, thus allowing you to use a form for multiple events for the same project record. You may <b>group your events into 'arms'</b>, in which you may have one or more arms/groups for your project. Each arm can have as many events as you wish. You may use the table below to create new events and/or arms, or modify existing ones. (One arm and one event will be initially defined as the default for all projects.)"
define_events_10 = "Events cannot be modified in production status except by a REDCap administrator."
define_events_11 = "For help with this, you may contact"
define_events_14 = "STEP #1:"
define_events_15 = "To add new events below, provide an <b>Event Name</b> and the <b>Days Offset</b> for that event, and then click the"
define_events_16 = "Add new event"
define_events_17 = "button. If your events are temporal (e.g., visits, tasks), you may use the Days Offset to provide a timeframe of all your events relative to the time of the first event defined. "
define_events_18 = "If you will be using the"
define_events_19 = "Scheduling module"
define_events_20 = "the Days Offset will be used to generate a schedule based on a start date that you provide, and then that new schedule will be added to the Calendar. The Offset Range may be used to help you stay within a range of days, if needed, when scheduling is being done by changing it to a value other than 0. "
define_events_21 = "If your events are not temporal but are ordered, you may still use the Days Offset simply as a means of ordering your events."
define_events_22 = "STEP #2:"
define_events_25 = "page, where you may select which data collection instruments that you wish to utilize for each event you defined."
define_events_26 = "To get you started, we have already added one event for you below. You may edit this event and also add as many events as you need."
define_events_27 = "Enter a value in units of years, months, or weeks to calculate its equivalent value in days."
define_events_28 = "Years"
define_events_29 = "Months"
define_events_30 = "Weeks"
define_events_31 = "Days"
define_events_32 = "Rounded to nearest whole number"
define_events_33 = "Convert a unit to days"
define_events_35 = "Day Offset was entered incorrectly!"
define_events_37 = "Deleting any events below will result in data loss. Please proceed with caution."
define_events_38 = "Add New Arm"
define_events_39 = "Arm name:"
define_events_40 = "Arm number:"
define_events_41 = "Please provide both an Arm name and Arm number"
define_events_42 = "Rename Arm"
define_events_43 = "DELETE ARM"
define_events_44 = "Deleting Arm"
define_events_45 = "will also delete ALL events associated with Arm"
define_events_47 = "Delete Arm"
define_events_48 = "Event #"
define_events_49 = "Days Offset"
define_events_50 = "Offset Range"
define_events_51 = "Min / Max"
define_events_53 = "No events have been defined for this Arm"
define_events_56 = "Days"
define_events_57 = "Convert from other units"
define_events_58 = "Descriptive name for this event"
define_events_59 = "Processing... Please wait"
define_events_60 = "Don't forget to designate your instruments once you have defined your events."
define_events_62 = "(Used by DTS)"
define_events_63 = "Some of the events below are being utilized by DTS. If you intend to delete any event used by DTS, you will additionally need to delete the event on the DTS Admin page immediately afterward, or else errors will likely occur the next time DTS attempts to pull data from the external system."
define_events_64 = "WARNING: This project uses automated Data Transfer Services (DTS)"
define_events_65 = "Unique event name"
define_events_66 = "(auto-generated)"
define_events_67 = "The unique event name, which is auto-generated from the user-defined event name, can be used in branching logic, calculated fields, and for importing data via the REDCap API, among other places. For using it in branching logic or calculated fields, see the Help & FAQ page."
define_events_68 = "The arm number could not be added/changed because the arm number entered already exists. Please try again using another arm number."
define_events_69 = "VIDEO: How to define events (5 min)"
define_events_70 = "To add new events below, provide an <b>Event Name</b> for that event, and then click the"
define_events_71 = "Once events have been added, you can easily change their order by dragging and dropping the event using the up-down arrow icon on the far left for a given row in the table."
define_events_72 = "Once you have defined your events on this page, you may navigate to the"
define_events_73 = "Upload or download arms/events"
define_events_74 = "Upload arms (CSV)"
define_events_75 = "Download arms (CSV)"
define_events_76 = "Upload events (CSV)"
define_events_77 = "Download events (CSV)"
define_events_78 = "Upload or download instrument mappings"
define_events_79 = "Upload instrument-event mappings (CSV)"
define_events_80 = "Download instrument-event mappings (CSV)"
define_events_81 = "Additionally, please keep in mind that <b>renaming events</b> could cause disastrous effects if any unique event names are utilized in conditional logic, branching logic, calculations, reports filters, data quality rules, etc."
define_events_82 = "Please note that this is an UNRECOVERABLE CHANGE. Any data that is saved for this arm and its events will be PERMANENTLY LOST when deleting this arm. Are you sure you wish to do this?"
descriptive_popups_01 = "Descriptive Popups"
descriptive_popups_02 = "Add New Popup"
descriptive_popups_03 = "Edit Popup"
descriptive_popups_04 = "Popup Summary"
descriptive_popups_05 = "Popup Description"
descriptive_popups_06 = "This page can be used to create and manage inline descriptive popups. Descriptive popups are custom popups of text that become visible after hovering over a specific word or phrase on a data entry form or survey. They have two main components: 1) the link text, which should match a word or phrase used on a form or survey, and 2) the custom text for the popup content. You may set a descriptive popup to work on all instruments/surveys (default) or on specific ones. Descriptive popups are a great way to convey extra information on a form or survey without the text taking up space on the page."
descriptive_popups_07 = "Link Color"
descriptive_popups_08 = "View Summary"
descriptive_popups_09 = "Loading..."
descriptive_popups_10 = "Link Text"
descriptive_popups_11 = "Settings"
descriptive_popups_12 = "Action"
descriptive_popups_13 = "Display on Surveys"
descriptive_popups_14 = "Display on Data Entry Forms"
descriptive_popups_15 = "Display on First Match Only"
descriptive_popups_16 = "Survey Pages"
descriptive_popups_17 = "All pages"
descriptive_popups_18 = "Link Details"
descriptive_popups_19 = "Main Display Options:"
descriptive_popups_20 = "Activate on specific page numbers (for surveys only)"
descriptive_popups_21 = "Return to Descriptive Popup List"
descriptive_popups_22 = "Text that will be displayed as a hyperlink (should match an existing word or phrase on the form/survey)"
descriptive_popups_23 = "Popup Text"
descriptive_popups_24 = "Rich text to be displayed as the popup's content"
descriptive_popups_25 = "Link text cannot be empty!"
descriptive_popups_26 = "Popup description cannot be empty!"
descriptive_popups_27 = "All instruments"
descriptive_popups_28 = "You may select specific instruments on which to enable this descriptive popup. If no instruments are selected, then this popup will be active for all instruments in the project."
descriptive_popups_29 = "You may use the field below to define on which survey pages this popup should be active. If no survey page numbers are specified, this popup will apply to all pages for the selected survey instrument(s). Pages for each instrument must be defined on a new line and page numbers must be comma-separated, e.g., {0}."
descriptive_popups_30 = "Save"
descriptive_popups_31 = "Click on the picker to select a color:"
descriptive_popups_32 = "Create New Descriptive Popup"
descriptive_popups_33 = "Edit Descriptive Popup: {0}"
descriptive_popups_34 = "Additional Options:"
descriptive_popups_35 = "Activate on specific instruments/surveys"
descriptive_popups_36 = "Are you sure you would like to delete this descriptive popup?"
descriptive_popups_37 = "Confirm your selections"
descriptive_popups_38 = "View an example of a descriptive popup."
descriptive_popups_39 = "When someone moves their mouse over the link text, the descriptive popup will appear directly below it."
design_02 = "VIDEO: How to use this page"
design_03 = "Changes Made Successfully!"
design_04 = "The field changes included in the uploaded Data Dictionary have been committed."
design_05 = "Since the project is still in Draft Mode, these changes will not officially take effect until the drafted changes are submitted for review."
design_07 = "This module will allow you to create new data collection instruments/surveys or edit existing ones. Changes may be made by either using the <b>Online Designer</b> or <b>Upload Data Dictionary</b> (see tabs above), in which you may use either method or both. The Online Designer may help you get some initial fields/forms built quickly or to make quick edits, but using the Data Dictionary file may be more helpful if you will be adding a large number of fields for this project."
design_08 = "Working …"
design_10 = "The project is currently in PRODUCTION status, and thus changes cannot be made in real time to the project as when in Development status. However, changes to the project may be drafted in DRAFT MODE, after which such changes will be reviewed and approved by a REDCap administrator. Once those changes are approved, you will then receive an email confirmation informing you that those changes have taken effect on your production project."
design_11 = "Would you like to enter DRAFT MODE to begin drafting changes to the project? "
design_14 = "Since this project is currently in PRODUCTION, changes will not be made in real time."
design_16 = "SUBMIT CHANGES FOR REVIEW?"
design_17 = "Once you click Submit to finalize these changes, you must wait for your changes to be reviewed and approved, after which you will receive an email confirmation informing you that the changes have been made effective on the project."
design_18 = "view a detailed summary of all drafted changes"
design_19 = "REVIEW CHANGES?"
design_20 = "As an Administrator, you may review and approve changes made to the project. To do so, navigate to the"
design_21 = "Project Modification Module"
design_22 = "Awaiting review of project changes"
design_23 = "Your drafted changes to the project were submitted and will first be reviewed and approved by a REDCap administrator. When the changes have been approved, you will receive an email notification stating that those changes have taken effect on your production project."
design_24 = "If you have any questions regarding this, please contact"
design_25 = "Online Designer"
design_27 = "While in development status, all field changes will take effect immediately in real time"
design_37 = "REDCap Instrument Library"
design_42 = "Are you sure you wish to delete the data collection instrument named"
design_43 = "and all its fields?"
design_44 = "Delete the selected form?"
design_45 = "This page allows you to build and customize your data collection instruments one field at a time. You may add new fields or edit existing ones. New fields may be added by clicking the"
design_47 = "buttons. You can begin editing an existing field by clicking on the"
design_48 = "<b>Edit</b> icon. If you decide that you do not want to keep a field, you can simply delete it by clicking on the"
design_49 = "<b>Delete</b> icon. To reorder the fields, simply <b>drag and drop</b> a field to a different position within the form below."
design_51 = "This new data collection instrument will NOT be saved until at least one field has been added to the form."
design_52 = "Instrument name missing! Please edit instrument name."
design_54 = "Current instrument:"
design_55 = "Preview instrument"
design_56 = "Return to edit view"
design_57 = "Add New Field"
design_58 = "You may add a new project field to this data collection instrument by completing the fields below and clicking the Save button at the bottom. When you add a new field, it will be added to the form on this page. For an overview of the different field types available, you may view the"
design_60 = "Select a Type of Field"
design_61 = "Field Type:"
design_63 = "Notes Box (Paragraph Text)"
design_64 = "Calculated Field"
design_65 = "Multiple Choice - Radio Buttons (Single Answer)"
design_66 = "Multiple Choice - Drop-down List (Single Answer)"
design_67 = "Checkboxes (Multiple Answers)"
design_68 = "File Upload (for users to upload files)"
design_69 = "Begin New Section (with optional text)"
design_71 = "Choices (one choice per line)"
design_72 = "How do I manually code the choices?"
design_73 = "You may manually define the coded value for each choice by entering the coded number and a comma before the choice label (see example below)."
design_74 = "Female"
design_75 = "Male"
design_76 = "Not reported"
design_79 = "Please remove two-byte characters"
design_80 = "ONLY letters, numbers, and underscores"
design_81 = "Validation?"
design_83 = "None"
design_86 = "Integer"
design_89 = "Phone"
design_96 = "Minimum:"
design_97 = "Maximum:"
design_98 = "Required?*"
design_99 = "No"
design_100 = "Yes"
design_101 = "[Disabled]"
design_102 = "* Prompt if field is blank"
design_103 = "Identifier?"
design_104 = "Field Note"
design_106 = "The directory"
design_107 = "is NOT writable on this server. That directory must exist and must be writable in order for this module to function."
design_109 = "This module may be used for making changes to the project, such as adding new fields or modifying existing fields, by using an offline method called the Data Dictionary. The Data Dictionary is a specifically formatted CSV file within which you may construct your project fields and afterward upload the file here to commit the changes to your project."
design_110 = "Click the 'Browse' or 'Choose File' button below"
design_111 = "to select the file on your computer, and upload it by clicking the 'Upload File' button."
design_113 = "REMINDER:"
design_114 = "Before you download this file, please remember that the Data Dictionary demonstration file is NOT your current Data Dictionary used for your project but is merely an example of how to format your own Data Dictionary."
design_115 = "Data Dictionary demonstration file"
design_116 = "or you may view the"
design_117 = "Data Dictionary Tutorial Video (10 min)"
design_118 = "Steps for making project changes:"
design_119 = "Download the current"
design_121 = "Download"
design_122 = "with drafted changes"
design_123 = "Edit the Data Dictionary"
design_124 = "Upload the Data Dictionary using the form below"
design_125 = "The changes will be made to the project after the Data Dictionary has been checked for errors"
design_126 = "<b>Upload your Data Dictionary file</b> (CSV file format only)"
design_127 = "Upload File"
design_128 = "Please select a file first"
design_129 = "Your file is currently being uploaded. Please wait."
design_130 = "The file is also being analyzed for any possible errors."
design_131 = "This could take several minutes."
design_132 = "<b>Data Dictionaries must be in CSV file format only.</b> If your file is saved as an XLS, XLSX, or similar format, please try opening the file in Excel, then save the file again but as a CSV file. If you are having difficulty doing this, please see the"
design_134 = "for further instruction."
design_137 = "There was an error uploading your file."
design_138 = "Please try again or contact"
design_140 = "for assistance."
design_141 = "Your document was uploaded successfully and awaits your confirmation below."
design_142 = "You are now required to review any warnings below and then click the button at the bottom of the page to officially commit the field changes to the project. Follow the instructions below."
design_143 = "No errors or warnings were found in the document."
design_144 = "The uploaded data dictionary <b>contains"
design_145 = "fields</b>, which will replace the"
design_146 = "fields that currently exist in"
design_147 = "the project"
design_148 = "Draft Mode"
design_149 = "(excluding 'Form Status' fields, which are automatically generated by REDCap)."
design_153 = "Are you ready to commit the changes to the project from the uploaded Data Dictionary?"
design_154 = "(Click the button below to submit the changes.)"
design_155 = "Your submission is being analyzed."
design_156 = "Please wait till the process has completed."
design_157 = "This could take several minutes."
design_158 = "For unknown reasons, the Data Dictionary could not be uploaded successfully to the project. Please try uploading it again, and check with your REDCap administrator if this issue persists."
design_159 = "<b>Administrator message:</b> The following queries failed..."
design_160 = "Please wait..."
design_163 = "Calculation Equation"
design_164 = "SQL Query ('select' query only)"
design_165 = "How do I format the equation?"
design_166 = "Does the field contain identifying information (e.g., name, SSN, address)?"
design_167 = "If you wish, you may now"
design_168 = "before they are submitted for review."
design_169 = "Modify"
design_170 = "Delete"
design_171 = "Add"
design_172 = "Move"
design_174 = "Share"
design_175 = "When you have finished making changes, click the button below to finalize this draft and submit it for approval. You will be notified by email when your changes have been committed to the project."
design_177 = "You may make changes below while the project is in Draft Mode, which will not affect the existing structure of the project, but all edits will need to be reviewed and approved by a REDCap administrator after you have finalized your changes."
design_181 = "Slider / Visual Analog Scale"
design_184 = "Yes - No"
design_185 = "True - False"
design_186 = "True"
design_187 = "False"
design_196 = "Link"
design_198 = "(Images wider than 600 pixels will be downsized to fit page.)"
design_200 = "Document was successfully uploaded!"
design_201 = "Sorry, but Section Headers cannot be the last field on a data entry form."
design_202 = "DELETE ATTACHMENT?"
design_203 = "Are you sure you want to remove this document?"
design_204 = "[Attachment not found]"
design_205 = "Attachment:"
design_206 = "Please note that making changes to a REDCap project using DTS can cause issues, which may prevent DTS from working properly. Such changes include deleting fields, forms, or events, among other things. Please speak with your REDCap administrator about this first before making any changes, although you may continue here to enter Draft Mode, if you wish."
design_207 = "Do you still wish to enter Draft Mode?"
design_208 = "the instrument named"
design_209 = "to upload it to the REDCap Shared Library"
design_210 = "Set up Stop Actions for this Survey Question"
design_211 = "[End Survey]"
design_212 = "Custom Alignment"
design_213 = "Right / Vertical"
design_214 = "Right / Horizontal"
design_215 = "Left / Vertical"
design_216 = "Left / Horizontal"
design_217 = "Small reminder text displayed underneath field"
design_218 = "Align the position of the field on the page"
design_219 = "It appears that your data dictionary contains the Field Units column, which is no longer supported in REDCap. Field Units were used in the past ONLY when exporting data for the R statistical analysis package. Please remove the Field Units column from your data dictionary and upload it again. (The Section Header column should now be in column C instead.) If you had defined Field Units for any fields in the past, those values remain and will continue to be preserved in the future (unless the field is deleted), but no new values for Field Units can be added or modified for any fields henceforth because the Field Units feature has been deprecated."
design_220 = "ERROR: Remove the Field Units column"
design_221 = "Question Number"
design_222 = "Displayed only on the survey page"
design_225 = "Add/Edit Branching Logic"
design_226 = "Branching Logic may be employed when fields/questions need to be hidden under certain conditions. If branching logic is defined, the field will only be visible if the conditions provided are true (i.e. show the field only if...). You may specify those conditions in the text box below for the Advanced Branching Logic Syntax or by choosing the Drag-N-Drop Logic Builder method, which allows you to build your logic in a much easier fashion by simply dragging over the options you want. You may switch back and forth between each method if you wish, but please be aware that since the advanced logic allows for greater complexity, it may not be able to be switched over to the Drag-N-Drop method if it becomes too complex."
design_227 = "Show the field ONLY if..."
design_229 = "Displaying field choices for the following data collection instrument:"
design_230 = "Choose method below for the following field:"
design_231 = "Advanced Branching Logic Syntax"
design_232 = "Clear logic"
design_233 = "Drag-N-Drop Logic Builder"
design_234 = "Field choices from other fields"
design_235 = "(drag a choice below to box on right)"
design_236 = "Drag"
design_237 = "Drop"
design_238 = "ALL below are true"
design_239 = "ANY below are true"
design_241 = "Rename"
design_242 = "Delete"
design_243 = "Saved!"
design_244 = "Instrument name"
design_246 = "NOTE: Please be aware that branching logic and calculated fields will not function on this page. They only work on the survey pages and data entry forms."
design_248 = "Create"
design_249 = "a new instrument from scratch"
design_250 = "What is the REDCap Shared Library?"
design_251 = "If your REDCap project is in production status, then you can also share any of your own data collection instruments that you have created by uploading individual instruments to the Shared Library, after which they will be accessible and downloadable by any REDCap user in the world. You can share individual instruments to the Shared Library, which makes your instrument accessible to REDCap users everywhere, but if you are instead wanting to share an entire project or multiple instruments at once to an individual, such as a colleague, then it might be better to simply export the Data Dictionary to send to them. (NOTICE: Copyrighted material may not be shared unless you are the owner.)"
design_252 = "The REDCap Shared Library is a global repository of data collection instruments that can be downloaded and used in your REDCap projects. If you navigate to the Shared Library, you may view any of the library's instruments on the library web page or as a PDF. It will allow you import any instrument from the library into your REDCap project. To begin searching for instruments in the Shared Library, click the 'Download' button on the Online Designer page."
design_255 = "Submit Changes for Review"
design_256 = "Remove all drafted changes"
design_257 = "Do you wish to remove and discard all the changes you have made to your data collection instruments while in Draft Mode? If so, they will be discarded and your project will be taken out of Draft Mode."
design_258 = "For help setting up your Data Dictionary, you may also see the instructions listed on the"
design_259 = "Once your file has been uploaded, changes will NOT immediately be made but will be displayed and checked for errors to ensure that all the formatting in your Data Dictionary is correct before official changes are made to the project."
design_260 = "If you wish to view an example of how your Data Dictionary may be formatted, you may download the"
design_261 = "Need some help?"
design_262 = "(see the"
design_263 = "for help)"
design_264 = "The project has been taken out of Draft Mode, and all changes made in Draft Mode have been deleted."
design_265 = "Remove all changes made in Draft Mode?"
design_266 = "Download PDF of all instruments"
design_267 = "Enable auto naming of variable based upon its Field Label?"
design_268 = "Enable auto variable naming?"
design_269 = "<b>NOTE: Best practices suggest that it is best to leave auto naming disabled so that you may define your own variable names manually.</b> Please be advised that if you enable the auto variable naming feature, you may end up with undesirable variable names that may make statistical analysis of your data difficult, tedious, or confusing."
design_270 = "It is recommended that variables be named so that they are sufficiently descriptive yet succinct. For example, the question 'What is your gender?' might have its variable manually defined by a user as 'gender'. Whereas with auto variable naming enabled, the variable would instead end up as 'what_is_your_gender', which is less concise and unnecessarily long."
design_271 = "If you are not interested in manually defining your variable names, either because you will not be performing serious data analysis or for other reasons, you are free to enable the auto naming by clicking the 'Enable' button below."
design_272 = "ERROR! Only Administrators are allowed to add or modify 'sql' fields."
design_273 = "NOTICE: The field you just deleted is being used in either the branching logic or calculation equation of one or more fields. Below is a list of fields (with their variable and label) that are using the deleted field. You will need to modify the branching logic or calculation equation of ALL the fields listed below or else it will throw an error on your data entry form/survey when entering data because that field no longer exists."
design_274 = "Remove the deleted field variable"
design_275 = "from the branching logic or calculation equation of the following fields:"
design_276 = "Changes Were Made Automatically"
design_277 = "The changes you just submitted were made <u>AUTOMATICALLY</u>."
design_278 = "Why were my changes made automatically?"
design_279 = "Your changes were made automatically either because your project currently contains no records OR because it was found that the changes you made in Draft Mode did not contain any potential critical issues (e.g., deleting fields, re-coding multiple choice field options)."
design_280 = "They were committed immediately and have already taken effect. Thus you will NOT have to wait for a REDCap admin to approve your changes because the changes have already been made. None of your existing data (if any) was affected by your changes."
design_281 = "Your changes were made automatically because they were all considered minor and did not involve the modification of existing fields (e.g., adding new fields, reordering fields)."
design_282 = "Under these conditions, REDCap will automatically approve your changes immediately without you having to wait for a REDCap admin to approve them."
design_283 = "Why weren't my changes made automatically?"
design_284 = "Your changes were not made automatically because your project currently contains one or more records AND because it was found that the changes you made in Draft Mode contained potential critical issues (e.g., deleting fields, re-coding multiple choice field options)."
design_285 = "Your changes were not made automatically because those changes included the modification of existing fields."
design_286 = "Given those conditions, REDCap will NOT automatically approve your changes immediately, and thus you will have to wait for a REDCap admin to approve them. Thank you for your patience."
design_287 = "<b>NOTE:</b> Please be advised that if your changes made in Draft Mode meet certain qualifications, those changes may get automatically approved, which means that they will be made immediately rather than having to wait for a REDCap admin to approve them."
design_288 = "Your changes were made automatically either because your project currently contains no records OR because they were all considered minor and did not involve the modification of existing fields (e.g., adding new fields, reordering fields)."
design_289 = "Your changes were made automatically because it was found that the changes you made in Draft Mode did not contain any potential critical issues (e.g., deleting fields, re-coding multiple choice field options)."
design_290 = "Your changes were not made automatically because your project currently contains one or more records AND because it was found that the changes you made in Draft Mode included the modification of existing fields."
design_291 = "Your changes were not made automatically because it was found that the changes you made in Draft Mode contained potential critical issues (e.g., deleting fields, re-coding multiple choice field options)."
design_292 = "No, an admin will have to review these changes."
design_293 = "The choices listed below did not appear to have a raw value listed but only had a label, so a raw value has been provided for them automatically. If you are not satisfied with these auto generated values, you may change them before saving your changes for this field. The choices in the 'Choices' text box have automatically been modified to reflect these changes."
design_294 = "Raw values for choices were added automatically"
design_296 = "The only acceptable raw values are 1) an integer, or 2) a text string containing only letters, numbers, and underscores."
design_300 = "Matrix group name:"
design_302 = "Matrix Group:"
design_303 = "What is a matrix group name?"
design_304 = "A matrix group name is required in order for REDCap to know how to display fields together as a group in matrix/grid format on a survey or form. The group name is required. If not provided, then you must change the field back to a normal radio or checkbox field via the Field Type drop-down. <b>In order for different fields to be displayed in the same matrix/grid together, they must be given the same matrix group name.</b> Otherwise they will get rendered as separate matrix groups."
design_305 = "The Choices textbox has now been pre-loaded with the choices from the matrix group you just selected. You should *NOT* alter these values."
design_307 = "Add Matrix of Fields"
design_309 = "Add Field"
design_310 = "You may add or edit a matrix (i.e. grid) of project fields on this data collection instrument by completing the fields below. By providing all necessary info below and clicking Save, the new matrix of fields will be added to the form on this page. A Field Label and Variable name must be provide for each field in the matrix, and you must also set the Choices (i.e. matrix column headers) and answer format (Single Answer vs. Multiple Answers) for the entire matrix."
design_311 = "Very Poor"
design_312 = "Average"
design_313 = "Excellent"
design_314 = "Add another row"
design_315 = "Sorry, but you must leave at least one field row here. You are not allowed to remove them all."
design_316 = "Matrix Rows"
design_317 = "Matrix Column Choices"
design_318 = "Other Matrix Info"
design_319 = "Single Answer (Radio Buttons)"
design_320 = "Edit Field"
design_321 = "Edit Matrix of Fields"
design_324 = "Delete an entire matrix group of fields?"
design_330 = "Are you sure you wish to remove this section header?"
design_338 = "Please select a field"
design_339 = "Multiple Answers (Checkboxes)"
design_340 = "Answer Format:"
design_341 = "Each row represents a different field with its own label and variable name."
design_342 = "Question Number"
design_343 = "Matrix group to be moved:"
design_347 = "The field was successfully moved to a new location"
design_348 = "The matrix of fields were successfully moved to a new location"
design_349 = "on this data collection instrument."
design_350 = "on another data collection instrument named"
design_351 = "View this field on the other data collection instrument"
design_352 = "View this matrix on the other data collection instrument"
design_353 = "NOTICE: Record identifier field was changed!"
design_355 = "View a matrix example"
design_356 = "Matrix examples"
design_357 = "REDCap can display a matrix group of fields as either Single Answer (Radio Buttons) or Multiple Answers (Checkboxes). The first matrix below displays a group of fields as radio buttons, while the second matrix displays a group as checkboxes. Using a section header is optional when building a matrix. The field labels on the left-hand side of each field will always be given the same width, but the width of each individual choice column will vary depending on how many choices exist. Thus the more choices you have, the narrower each choice column will be."
design_358 = "Read more about matrix fields on the Help & FAQ."
design_359 = "Examples of Matrix Fields in REDCap"
design_360 = "NOTICE: Field's section header was merged with another section header"
design_361 = "The field you just moved had a section header immediately before it, and the field following it had a section header as well. Since two section headers cannot be adjacent to each other, those two section headers have now been automatically merged together."
design_362 = "NOTICE: Field's section header was removed"
design_363 = "The field you just moved had a section header immediately before it. Since that field was the last field on the form prior to moving it, the section header had to be automatically removed since it had no place to go."
design_365 = "Enabled as"
design_366 = "Drag instrument up or down to move it"
design_367 = "Click to modify instrument"
design_368 = "Add new fields/questions to the instrument or modify existing ones."
design_369 = "Download instrument as PDF"
design_370 = "The project must first be in Draft Mode before you can upload your Data Dictionary. Click the 'Enter Draft Mode' button near the top of the page to move the project into Draft Mode."
design_371 = "INSTRUMENT WAS MOVED!"
design_372 = "FIELD WAS MOVED!"
design_373 = "The data collection instrument was successfully moved. The page will now reload to show the change."
design_374 = "The project must first be in Draft Mode before you make modifications to any data collection instruments. Click the 'Enter Draft Mode' button near the top of the page to move the project into Draft Mode."
design_375 = "Can only modify instrument in Draft Mode"
design_376 = "Enter Draft Mode"
design_377 = "The Online Designer will allow you to make project modifications to fields and data collection instruments very easily using only your web browser."
design_378 = "Below you have the options to modify an existing instrument, delete an instrument, create a new instrument, download an instrument as a PDF document, or reorder your instruments."
design_379 = "In order to make any modifications to your instruments listed below, you must first move the project into Draft Mode by clicking the 'Enter Draft Mode' button above."
design_380 = "Add instrument here"
design_381 = "New instrument name:"
design_382 = "Please provide a name for the new data instrument"
design_383 = "Data instruments cannot begin with a number. Please try again."
design_384 = "However, whether in Draft Mode or not, you are allowed to download the PDF or modify survey settings for any instruments below."
design_385 = "The project is now in Draft Mode. When you have finished making changes to your instruments, click the 'Submit Changes for Review' button so that your changes may be approved."
design_387 = "Set up"
design_388 = "The Data Dictionary that you just uploaded did NOT contain any fields. It will not be accepted unless there is at least one field defined in the Data Dictionary. Please make sure that you are uploading the correct file and try again."
design_389 = "Instrument actions"
design_390 = "Survey related options"
design_392 = "* This field will NOT be displayed on the survey page."
design_393 = "You may now begin adding fields to your data collection instrument below using the Online Designer. Alternatively, you may build your fields in the Data Dictionary (offline method) by clicking its tab above."
design_394 = "Ready to add fields"
design_397 = "Yes, delete it"
design_398 = "The data collection instrument and all its fields have been successfully deleted!"
design_399 = "The data collection instrument could NOT be deleted because some of the fields that exist on that instrument are being used by the randomization module."
design_400 = "WARNING: Record identifier field was changed!"
design_401 = "Okay"
design_402 = "Since this instrument is enabled as a survey, would you also like to change the survey title to"
design_403 = "The survey title is currently"
design_404 = "Also change survey title?"
design_405 = "Yes, also change survey title"
design_406 = "The survey title has now been changed to"
design_407 = "Survey title changed!"
design_408 = "Unfortunately, you will not be able to select"
design_409 = "in the survey drop-down list because the survey listed in the 'Info' box of the Automated Invitation pop-up has already been set to be triggered by completing the survey you just selected from the drop-down. In other words, it would create a circular loop in which neither survey could ever be taken by a participant because their invitations are supposed to be triggered by each other. This is a paradox and is not possible. You will need to select another survey from the drop-down list."
design_410 = "NOTICE: Cannot select that survey"
design_411 = "(define criteria)"
design_412 = "CALCULATION ERROR"
design_413 = "The following fields listed in your calculation equation do not exist in this project and thus cannot be used. These fields must be removed from the calculation equation before you can continue."
design_414 = "Please enter a value for the variable name."
design_415 = "Delete section header?"
design_416 = "Copy field?"
design_417 = "Copy field"
design_418 = "Do you wish to copy the field(s)"
design_419 = "The new field(s) will be added immediately after this one."
design_420 = "NOTE: All fields on this data entry form have now been deleted, so you will now be directed back to the previous page."
design_421 = "NOTE: Since the field you just deleted was the last field on the form AND because a Section Header came directly before the field, that Section Header was automatically removed since Section Headers cannot exist at the very bottom of the form. Our apologies for this inconvenience."
design_422 = "The field could NOT be deleted because it is being used by the randomization module."
design_423 = "NOTICE: Deleted field used in calculation equation or branching logic"
design_425 = "NOTICE: Please a field type for this matrix of fields."
design_426 = "NOTICE: Please provide some choices that will be used for this matrix's column headers."
design_427 = "NOTICE: Please provide a matrix group name for this matrix."
design_429 = "The variable name cannot be changed because this variable name is already in use while the project is in Production status. Renaming the variable would cause permanent data loss."
design_434 = "This field is the record ID field, which is the first field in the project. This field is special because it is used to store the names of the records in your project. Thus the record ID field cannot be deleted or moved but only edited. If you wish, you may change its field label or even its variable name."
design_436 = "View detailed summary of all drafted changes"
design_437 = "While your changes are pending, you may still"
design_438 = "Administrators: Change how this works"
design_439 = "Your branching logic cannot be saved as-is because security measures in REDCap consider it to be invalid syntax. This may be if you are attempting to use specialized JavaScript code or other 'hacks' that have not been officially sanctioned or approved for use in REDCap. You may 1) leave the branching logic as it is without changing it, 2) remove the branching logic altogether for this field, or 3) replace it with other branching logic that follows the correct syntax. To learn more about proper branching logic syntax, see the "
design_440 = "While your existing branching logic is syntactically valid, the changes to the logic that you are trying to save are NOT valid. A syntax error exists in your branching logic, so you will need to fix it and try again. For further assistance, see the"
design_441 = "ADMINISTRATORS ONLY: <b>Your branching logic was successfully saved.</b> However, please note that there appears to be a syntax error in the branching logic that you just saved. This may be if you are attempting to use specialized JavaScript code or other 'hacks' that have not been officially sanctioned or approved for use in REDCap. While this is acceptable since you are an Administrator, you may want to check to make sure that your branching logic works correctly on the data entry form or survey where the field is located."
design_442 = "There are custom functions used in some branching logic that are not official REDCap functions and are thus not allowed. These unrecognized functions must be removed from the branching logic. Below are the functions found that are not allowed."
design_443 = "There are custom functions used in some branching logic that are not official REDCap functions and are thus not normally allowed. Since you are an Administrator, the unrecognized functions listed below will be allowed here."
design_444 = "There are syntax errors in some branching logic. This may occur if illegal characters or illegal functions are used in the branching logic. Please remove all syntax errors. Below are the fields that contain syntax errors in their branching logic."
design_445 = "There are syntax errors in some branching logic and are thus not normally allowed. Since you are an Administrator, the branching logic for the fields listed below will be allowed here, although you may want to check to make sure these aren't actual errors."
design_446 = "There are syntax errors in some branching logic and are thus not normally allowed because security measures in REDCap consider it to be invalid syntax. Since you are not changing the existing branching logic for the fields listed below, the branching logic will be allowed here for the following fields."
design_447 = "There are custom functions used in some calc field equations that are not official REDCap functions and are thus not allowed. These unrecognized functions must be removed from the calc field equation. Below are the functions found that are not allowed."
design_448 = "There are custom functions used in some calc field equations that are not official REDCap functions and are thus not normally allowed. Since you are an Administrator, the unrecognized functions listed below will be allowed here."
design_449 = "There are syntax errors in some calc field equations. This may occur if illegal characters or illegal functions are used in the calc field equation. Please remove all syntax errors. Below are the calc fields that contain syntax errors in their equation."
design_450 = "There are syntax errors in some calc field equations and are thus not normally allowed. Since you are an Administrator, the equation for the calc fields listed below will be allowed here, although you may want to check to make sure these aren't actual errors."
design_451 = "There are syntax errors in some calc field equations and are thus not normally allowed because security measures in REDCap consider it to be invalid syntax. Since you are not changing the existing equation for the calc fields listed below, the equation will be allowed here for the following fields."
design_452 = "Your calculated field's equation has NOT yet been saved. While all other attributes of the field have been saved, the equation will only be saved when there are no longer any errors in the equation. Click the Close button to re-open the Edit Field pop-up."
design_453 = "ADMINISTRATORS ONLY: <b>Your calc field was successfully saved.</b> However, please note that there appears to be a syntax error in the equation that you just saved. This may be if you are attempting to use specialized JavaScript code or other 'hacks' that have not been officially sanctioned or approved for use in REDCap. While this is acceptable since you are an Administrator, you may want to check to make sure that your calculation works correctly on the data entry form or survey where the field is located."
design_454 = "Matrix Header Text (optional)"
design_455 = "*Note: Adding section header text here will start a new page on the survey."
design_456 = "How to use Piping"
design_457 = "The 'Piping' feature in REDCap allows you to inject previously collected data into text on a data collection form or survey, thus providing greater precision and control over question wording. It can also be used in other ways, such as for customizing survey invitations (e.g., by including the respondent's name in the email) or survey completion text (e.g., thanking your respondent by name after completing a survey). To see Piping in action, you may"
design_458 = "Where can Piping be used?"
design_459 = "Piping can be used in many different places in REDCap. Below is a list of all the places where Piping may be utilized to insert a data value *INTO* text."
design_460 = "Slider field labels (i.e. text displayed above slider bar)"
design_461 = "Matrix field column headers"
design_462 = "Option labels for multiple choice fields (radio, drop-down, checkbox)"
design_463 = "How to use Piping here"
design_464 = "Survey invitation emails (sent via Participant List or Automated Invitations) - includes both subject and message"
design_465 = "How do I utilize Piping?"
design_466 = "Setting up Piping is very simple. Piping does *not* have to be enabled in any way in order to use it. <b>All you need to do to pipe a data value into any of the valid places listed above is insert into your text the variable name inside square brackets</b>. For example, if we have a survey question that asks 'What is your first name?', in which the variable name for that question is 'first_name', then the following question may be set up as <b>'[first_name], what is your date of birth?'</b>. If the user entered 'John' as their first name, then text for the next question would literally read as <b>'John, what is your date of birth?'</b>. In the same way, you could use [first_name] in your survey's survey completion text when the survey is completed, in which <b>'Thanks for taking our survey, [first_name]!'</b> would be displayed to the respondent as <b>'Thanks for taking our survey, John!'</b>."
design_467 = "If you have a longitudinal project, you may utilize cross-event Piping if you wish. In the same way that cross-event calculations and branching logic are set up, you simply prepend the variable name inside square brackets with the unique event name inside square brackets. For example, if you collected a person's first name on the event named 'Enrollment', which has the unique event name 'enrollment_arm_1', then you could set up piping as <b>'[enrollment_arm_1][first_name], what is your date of birth?'</b>. Thus it will pipe the first name value only from the 'Enrollment' event and not any other event, whereas <b>if the unique event name is not prepended to a variable in a longitudinal project, it will pipe the data value from the current event</b>."
design_468 = "How to use Piping in the survey invitation"
design_470 = "From what field types can data be piped?"
design_472 = "EXAMPLE"
design_473 = "Before:"
design_474 = "After:"
design_475 = "Setup:"
design_476 = "view a live demo of Piping on a survey"
design_477 = "NOTICE: Renamed field is used in calculation equation or branching logic"
design_478 = "NOTICE: The field you just renamed is being used in either the branching logic or calculation equation of one or more fields. Below is a list of fields (with their variable and label) that are using the renamed field. You will need to modify the branching logic or calculation equation of ALL the fields listed below or else it will throw an error on your data entry form/survey when entering data. Otherwise, you could just rename the field back to its original variable name to avoid this issue."
design_479 = "Replace the renamed field variable"
design_480 = "from the branching logic or calculation equation of the following fields:"
design_481 = "Sorry, but drafted changes can ONLY be submitted for review when the project is in PRODUCTION status. If you wish the submit your drafted changes, you will first need to move the project back to production status using the Other Functionality tab on the Project Setup page."
design_482 = "Codebook"
design_483 = "The Codebook is a human-readable, read-only version of the project's Data Dictionary and serves as a quick reference for viewing the attributes of any given field in the project without having to download and interpret the Data Dictionary. Note: Checkbox fields have their coded values displayed both in the format defined by users in the Online Designer/Data Dictionary as well as in the extended format seen in data imports and exports (i.e., field___code)."
design_484 = "Variable / Field Name"
design_485 = "Show the field ONLY if:"
design_486 = "Min:"
design_487 = "Max:"
design_488 = "Slider labels:"
design_489 = "Calculation:"
design_490 = "Custom alignment:"
design_491 = "Question number:"
design_492 = "Stop actions on"
design_493 = "Instrument:"
design_494 = "Field Attributes (Field Type, Validation, Choices, Calculations, etc.)"
design_495 = "Ranking:"
design_496 = "What is a ranked matrix of fields?"
design_497 = "Allow only 1 choice to be selected per column (radio buttons only)"
design_499 = "A ranked matrix of fields is a matrix that can be used to 'rank' the choices within it so that no two fields in the matrix can have the same selected value for a given column. For example, if ranking is enabled for a matrix and a user then selects a choice for one field that has already been selected for another field, it will automatically deselect the value for that other field and display a quick message saying 'value removed!' to denote that the value was removed for the other field. This prevents any two fields in the matrix from having the same selected value."
design_500 = "NOTE: Ranking can ONLY be used for a RADIO BUTTION MATRIX. It cannot be used for a checkbox matrix since they allow for more than one choice to be selected per field."
design_501 = "RECOMMENDATION: For best results when using a ranked matrix, it is best to have the same number of fields and options."
design_502 = "Matrix"
design_503 = "- ranking"
design_504 = "Matrix Ranking"
design_506 = "Custom text displayed at top of Survey Queue"
design_507 = "Cannot modify adaptive instrument!"
design_508 = "This instrument cannot be modified in any way because it is an computer adaptive test (CAT), which means that its questions are dynamically generated using a service outside of REDCap. You may, however, rename or delete the instrument."
design_509 = "(Adaptive)"
design_512 = "Choices (not modifiable)"
design_513 = "Inside the URL for a survey's 'Redirect to a URL' setting"
design_514 = "NOTICE: Calculation was changed - Data is affected!"
design_515 = "It appears that you just modified the calculation equation of a calculated field that contains saved data for one or more records. This means that any saved values for this field have now been invalidated. You may fix them all very easily by navigating to the Data Quality page on the left-hand menu, then executing Rule H on the Data Quality page, and then clicking the 'Fix calcs now' button in the popup for that rule, which will fix all saved values that have been affected by the calculation change."
design_516 = "NOTICE: Calculation equation was changed!"
design_517 = "Please note that one or more calculated fields that have data values stored for them had their calculation modified in the changes that were just approved. This means that any data saved for those calc fields is now invalid and incorrect. However, you or another user may fix all those data values very easily by navigating to the Data Quality page on the left-hand menu, then executing Rule H on the Data Quality page, and then clicking the 'Fix calcs now' button in the popup for that rule, which will fix all saved values that have been affected by the calculation change."
design_519 = "You may choose from one of existing set of choices from other multiple choice fields in this project. Click the 'Use' button next to each to import that set of choices into the current field's Choices text box."
design_520 = "Use"
design_521 = "There are no existing choices to show."
design_522 = "Copy existing choices"
design_523 = "You are not allowed to delete all your data collection instruments. You must keep at least one instrument. Since you only have one instrument in your project, you may thus not delete it. If you wish to replace the instrument, then you should add a new instrument, and then afterward delete this one."
design_524 = "WARNING: Cannot delete only instrument!"
design_525 = "NOTICE: Since record auto-numbering is enabled in this project, you may not set the field validation to anything other than 'Integer'."
design_526 = "They were committed immediately and have already taken effect."
design_527 = "Field Annotation"
design_529 = "Field annotations can be used to add explanatory notes or commentary about a given field. This can be used for several purposes, such as for the bookkeeping of a project's field structure (as metadata about the given field) for reference purposes regarding what the field represents or how it should be used (during data entry, analysis, etc.). Field annotations are not displayed on any page but are merely for reference. Field annotations can also be used to map the field to various standards (e.g., CDISC, SNOMED, LOINC) using whatever notation the user sees fit (e.g., using a simple ID code for the standard or a complex XML structure containing information about how to transform the data to the standard). Since it is just an annotation for reference purposes, REDCap will not do anything with the field annotation text on its own, but the annotation can be obtained by users at any time for any purpose (typically accessed via the Data Dictionary download or via the API metadata export). Summarily, field annotations do not have a specifically defined purpose, so users may use them in whatever way they so choose."
design_530 = "Upload"
design_531 = "instrument ZIP file from another project/user or"
design_533 = "external libraries"
design_534 = "a new instrument from the official"
design_535 = "Upload instrument ZIP"
design_536 = "Select a REDCap instrument ZIP file on your computer that you downloaded from an"
design_537 = "The file you selected is not a ZIP file (i.e., its file name does not end with '.zip'). Please try again to select a valid instrument ZIP file."
design_538 = "ERROR: The file 'instrument.csv' could not be found in the top-level directory of the ZIP file you uploaded. The ZIP file you uploaded does not appear to be a valid instrument ZIP file."
design_540 = "To view your uploaded instrument in the instrument list, close this pop-up."
design_541 = "ERROR: The following variables were duplicated inside the 'instrument.csv' file in your uploaded instrument ZIP file, so the upload process could not be completed. The variable names must be unique and cannot be duplicated:"
design_542 = "External Instrument Libraries"
design_543 = "You may download a REDCap data collection instrument as a ZIP file from an external REDCap instrument library in order to add the instrument to your project. These instrument ZIP files may additionally include attachment files for Descriptive fields in the instrument."
design_544 = "Loading list of external libraries..."
design_545 = "Go to this library"
design_546 = "The list could not be loaded, so please click the button below to visit the webpage listing all the external instrument libraries."
design_547 = "View all external instrument libraries"
design_548 = "external instrument library"
design_549 = "Listed below are various external instrument libraries where a data collection instrument may be downloaded and uploaded into REDCap as an instrument ZIP file."
design_550 = "NOTE: These third-party websites are *not* affilliated with REDCap in any way, nor is REDCap responsible for their content. These organizations have made assurances that the instruments distributed on their website do not violate copyright law in any way."
design_551 = "Import"
design_552 = "or from another project/user, and then click the Upload button below. Once it has been successfully uploaded, it will be added as the last data collection instrument in the project."
design_553 = "Once an instrument ZIP file has been download from a library, <b>click the Upload instrument ZIP button</b> on this page to import the instrument into your project."
design_554 = "Choose action"
design_555 = "Download instrument ZIP"
design_556 = "Copy instrument"
design_557 = "To copy the instrument"
design_558 = ", enter the name of the new instrument below. Also, since all variable/field names must be unique and cannot duplicate, this instrument's variables must be renamed when copied to the new instrument. Please enter a suffix that will be appended to all new variable names."
design_559 = "New instrument name:"
design_560 = "Suffix appended to variable names:"
design_562 = "Please enter a new instrument name and a suffix for new variable names."
design_563 = "SUCCESS! The instrument was successfully copied. The page will now reload to reflect the changes."
design_564 = "Instrument copied!"
design_565 = "Please be aware that due to variable name conflicts, the variables below had to be renamed on the new instrument. If the variables were also used inside any branching logic or calculations, they were replaced there with their new name as well."
design_566 = "renamed to"
design_567 = "DISCLAIMER: By uploading your instrument ZIP file here, you hereby represent and warrant that to the best of your knowledge, you are not uploading any copyrighted material of a third party to which you do not have an expressed written license or consent from the owner of the said copyright."
design_568 = "Custom record locking text (if defined, displayed at bottom of form)"
design_573 = "Sorry, but a video URL cannot be added until the image/file attachment is first removed for this field."
design_575 = "Embedded Video URL"
design_576 = "Display format of attachment on page:"
design_577 = "Attach an image, file, or embedded audio"
design_578 = "IMPORTANT NOTICE: It is your responsibility as a REDCap user to ensure that you do not upload any videos or files that contain confidential or sensitive information (e.g., PHI or PII), as well as copyrighted material, to third-party websites such as YouTube, Vimeo, etc. REDCap is not responsible for anything that you upload to third-party websites."
design_579 = "Embedded Video Display"
design_580 = "Inline"
design_581 = "Inside popup"
design_583 = "Enable searching within a biomedical ontology"
design_584 = "choose ontology to search"
design_585 = "[Error: No choices available]"
design_586 = "Ontology search is not enabled!"
design_587 = "The biomedical ontology search feature has not yet been enabled in REDCap. Before you can utilize the feature, a REDCap Administrator must first enable it for the REDCap system."
design_588 = "<b>Administrators:</b> To enabled the feature, you must"
design_589 = "create a new BioPortal account"
design_590 = "and then obtain the API token provided to you after creating your account. Then enter the API token below, and click the 'Save BioPortal Token' button. Once the token is saved, it will operate for the whole system. This is a one-time process that will never have to be repeated."
design_591 = "Save token"
design_592 = "BioPortal Token:"
design_593 = "BioPortal token saved!"
design_594 = "Your BioPortal token has been successfully saved. The biomedical ontology search feature will now be functional in all REDCap projects."
design_595 = "ERROR: The value entered is not a valid BioPortal API token! Please try again."
design_596 = "Descriptive Text (with optional Image/Audio/File Attachment)"
design_597 = "Descriptive Text (with optional Image/Video/Audio/File Attachment)"
design_598 = "Once enabled for a field, as you begin to type in the text field, it will display a list of choices below it with keyword matches from the given ontology (see the illustration below). When a value is chosen from the list, it will place that value into the text field. The *only* values that be saved for the field are values from the search list; thus you will not be able to type any free-form text into the field unless it is a valid value from the search list. NOTE: The raw value that ultimately gets saved for the field will be the 'notation' (often an alpha-numeric code) for the given ontology, whereas the associated label will not get stored as the raw value but can be seen next to the raw value in a report and also in a CSV Labels data export."
design_599 = "Below is a screenshot of the search feature in action as a user begins to type in the text field."
design_600 = "An ordinary text field on a survey or data entry form can have a special feature enabled that provides auto-suggest functionality for real-time searching within biomedical ontologies, such as RxNorm, ICD-9, ICD-10, Snomed CT, LOINC, etc. There are over 400 ontologies available from which you may choose."
design_601 = "To enable the ontology search feature for a given text field, simply choose an ontology from the drop-down list in the Add/Edit Field popup, and click Save. You can even test the search feature here in the Online Designer to see it in action."
design_602 = "Enable auto-complete for this drop-down"
design_603 = "For any given drop-down field, you may enable the auto-complete feature, which transforms the drop-down into a combobox that functions as a normal drop-down list but has the additional capability of employing a text search on the options in the drop-down to help you find an option much more quickly. Instead of having to scroll through the whole drop-down list to find a particular option to select, you can just type a few characters of the option you want to select, and it will return a short list of matching options. The auto-complete feature is most useful if your drop-down list is very long with lots of options. Note: Even though you are able to hand-enter text into the text field when searching the autocomplete drop-down, it will not allow you to save a value unless it is a valid option in the drop-down list."
design_604 = "Enabling the auto-complete feature for drop-downs"
design_606 = "What are Action Tags?"
design_608 = "All available action tags and their descriptions:"
design_609 = "Hides the field on the survey page, the data entry form, and in the REDCap mobile app. Field will stay hidden even if branching logic attempts to make it visible."
design_610 = "Hides the field only on the data entry form (i.e., not on the survey page). Field will stay hidden even if branching logic attempts to make it visible."
design_611 = "Hides the field only on the survey page (i.e., not on the data entry form). Field will stay hidden even if branching logic attempts to make it visible."
design_612 = "Makes the field read-only (i.e., disabled) on the survey page, the data entry form, and in the REDCap mobile app so that its value cannot be changed."
design_613 = "Makes the field read-only (i.e., disabled) only on the data entry form (i.e., not on the survey page or mobile app) so that its value cannot be changed."
design_614 = "Makes the field read-only (i.e., disabled) only on the survey page (i.e., not on the data entry form or mobile app) so that its value cannot be changed."
design_616 = "Edit field in Online Designer"
design_617 = "Return to Codebook"
design_618 = "Return to list of instruments"
design_619 = "Edit branching logic in Online Designer"
design_624 = "Masks the value of a Text field so that the true value is not visible on the webpage after it has been entered (like password fields on login pages)"
design_625 = "Hides the field only on the form ONLY on the REDCap Mobile App. Field will stay hidden even if branching logic attempts to make it visible."
design_626 = "Makes the field read-only (i.e., disabled) on the form ONLY on the REDCap Mobile App so that its value cannot be changed."
design_629 = "Allows a Text Box field to capture the latitude of the user, in which the user will be prompted on the webpage to allow or deny this. Once the value is captured, it will not be changed when visiting the page at a later time. The field will be disabled and will not allow users to edit the value, but it will allow them to remove the value altogether. NOTE: While the GPS value will be very accurate when captured on a mobile device, it will not be nearly as accurate when using a browser on laptops and desktop computers."
design_630 = "Allows a Text Box field to capture the longitude of the user, in which the user will be prompted on the webpage to allow or deny this. Once the value is captured, it will not be changed when visiting the page at a later time. The field will be disabled and will not allow users to edit the value, but it will allow them to remove the value altogether. NOTE: While the GPS value will be very accurate when captured on a mobile device, it will not be nearly as accurate when using a browser on laptops and desktop computers."
design_631 = "Use this value"
design_632 = "A data dictionary cannot be uploaded at this time because currently the project's drafted changes are awaiting review by an administrator."
design_633 = " Allows the REDCap Mobile App to capture the value of a barcode or QR code by scanning it with the device's camera. NOTE: For use only in the REDCap Mobile App."
design_634 = "Text Box (Short Text, Number, Date/Time, ...)"
design_635 = "Drag event up or down to move it"
design_636 = "Arm number"
design_637 = "The arm name for arm number"
design_638 = "is missing."
design_639 = "is not numeric or is less than one."
design_640 = "Errors occurred while processing your uploaded file, and thus it could not be successfully uploaded. Please fix the following errors and try again:"
design_641 = "One or more components are missing in your input data. The following attributes are required:"
design_642 = "The unique event name"
design_643 = "does not exist in the project."
design_644 = "The arm number"
design_645 = "The event's Days Offset"
design_646 = "is not numeric."
design_647 = "The event's Offset Range Min"
design_648 = "The event's Offset Range Max"
design_649 = "The event name"
design_650 = "must be less than or equal to 30 characters in length."
design_651 = "The arm name"
design_652 = "must be less than or equal to 50 characters in length."
design_653 = "The instrument name (i.e., the unique form name)"
design_654 = "Confirm"
design_655 = "Survey auto-continue is enabled"
design_656 = "NOTICE: Each matrix row must have a variable name, so please add a variable name where appropriate."
design_657 = "Compatibility notice for embedded audio"
design_658 = "Please note that the embedded audio option for attachments is not 100% compatible for all audio file types across all web browsers. This is not a limitation in REDCap, but is simply a compatibility issue across web browsers. <b>The most compatible audio file types to use are MP3 and WAV.</b> Other audio types may work on some browsers but not in others. Unfortunately, there is not always an easy way to know what audio file will work for which browser, especially as operating systems and web browsers evolve over time. <b>Recommendation: Always test the embedded audio option to make sure it works as intended for the given audio file you uploaded.</b> If the audio file appears to be incompatible with most web browsers, then it is recommended that you change the attachment display option to 'Link' instead of 'Audio file' for greatest compatibility."
design_659 = "Sets a field's initial value. This allows a field to have a specified default value when viewing the field on a survey or data entry form that has not yet had any data saved for it (i.e., when the form status icon is gray or when a survey page has not had any data entered yet). The format must follow the pattern @DEFAULT=\"????\", in which the desired default value should be inside single or double quotes. For checkbox fields, simply separate multiple checkbox values with commas - e.g., @DEFAULT='1,3,6'. For text fields, you may even perform Piping inside the default value to pipe data from another field in the project - e.g., @DEFAULT='Name: [first_name] [last_name], DOB: [dob]'. NOTE: The default value does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms. NOTE: If being used on a date or datetime field, the date value inside the quotes must be in Y-M-D format - e.g., @DEFAULT='2007-12-25' - regardless of the field's set date format. TIP: To pipe the value of one multiple choice field into another multiple choice field, make sure you append ':value' to the variable being piped - e.g., @DEFAULT='[my_dropdown:value]'."
design_661 = "In the REDCap Mobile App, it sets a field's value to the app username of the current mobile app user - i.e., their username in the mobile app, which is not necessarily the same as their REDCap server username that can be captured using @USERNAME. NOTE: For use only in the REDCap Mobile App."
design_662 = "Hides the 'Now' or 'Today' button that is typically displayed to the right of date, time, and date/time fields."
design_663 = "Stop Actions (for survey questions only):"
design_664 = "The survey participant will be prompted to end the survey when ANY choices checked below are selected for this question on the survey. Stop Actions will not be enabled on the form when viewing in REDCap as an authenticated user, but only become enabled when a participant views this data collection instrument as a survey."
design_665 = "Left label (bottom, if vertical):"
design_666 = "Middle label:"
design_667 = "Right label (top, if vertical):"
design_668 = "Labels displayed above slider (optional):"
design_669 = "TIP: Make your sliders vertical with RV or LV alignment."
design_671 = "Custom Event Label"
design_672 = "A Custom Event Label can optionally be added to any event in your project. Custom Event Labels are similar to Custom Record Labels, in which they allow you to display data (via piping) from a given event in the event's table header when viewing the Record Home Page of a record. For example, if each event represents a single visit of a person, then if you are collecting the date in a field called 'visit_date' on each event, then you can set the Custom Event Label as '[visit_date]' for all those visit events. This will provide useful context for each event when viewing all the events of the record. You can also get more advanced with the piping by using multiple fields and even static text. For example, '[visit_date], [weight] kg'."
design_673 = "using Field Annotation"
design_674 = "Choices Change Summary"
design_675 = "Existing Label"
design_676 = "Draft Value"
design_677 = "Draft Label"
design_678 = "The table below lists the values and labels of each choice for this multiple choice field, displaying which choices have been added, deleted, or remain unchanged in Draft Mode. Also, the column on the far right displays how many records have a saved value for the given choice."
design_679 = "Existing Value"
design_680 = "Unchanged"
design_681 = "Altered"
design_682 = "Removed"
design_683 = "Added"
design_684 = "Number of records having this value"
design_685 = "Data dictionary snapshot"
design_686 = "Snapshot by"
design_687 = "Last snapshot:"
design_688 = "Create snapshot of instruments"
design_689 = "A snapshot of your current data dictionary (CSV file of all fields and instruments) can be saved and stored by simply clicking the 'Create snapshot of instruments' button on this page. All snapshots can be accessed and downloaded at any time on the Project Revision History page. There is no limit to how many snapshots can be created. Creating a snapshot can be useful to allow you to revert all your fields back to a specific point in time, if desired, by taking the snapshot from the Revision History page and uploading it on the Data Dictionary Upload page. Additionally, whenever data dictionaries are uploaded into the project (even via API metadata import), a snapshot of the current data dictionary is taken before committing the new data dictionary. This allows you to remain worry-free that your fields/forms will be preserved automatically, even in the case of an accident occurring (e.g., wrong data dictionary was uploaded)."
design_690 = "Commit Changes"
design_691 = "A snapshot of your project's current Data Dictionary will be created automatically during the Data Dictionary upload process before committing the new Data Dictionary. The snapshot can later be accessed and downloaded from the Project Revision History page."
design_692 = "Snapshot note:"
design_693 = "Hide data dictionary snapshots"
design_694 = "Show data dictionary snapshots"
design_695 = "Development status (current)"
design_699 = "Preview"
design_700 = "Send test email"
design_701 = "Repeat survey option is enabled"
design_702 = "Can be used only for File Upload and Signature fields. If the project is initialized in the REDCap Mobile App, this will cause any image files uploaded to a record to be sent to the app so that they are viewable in the app when editing the record. NOTE: For use only in the REDCap Mobile App."
design_703 = "Is used to specify a short hint that describes the expected value of a Text field or Notes field (e.g. a sample value or a short description of the expected format). The placeholder is displayed inside the field before a value is entered. The format must follow the pattern @PLACEHOLDER='????', in which the text to be displayed should be inside single or double quotes."
design_704 = "Test calculation with a record:"
design_705 = "Test logic with a record:"
design_706 = "Result:"
design_707 = "Your logic could not be evaluated. Please try again."
design_708 = "No value"
design_709 = "True (show field)"
design_710 = "False (hide field)"
design_711 = "Clear calculation"
design_712 = "Invalid calculation"
design_713 = "Invalid logic"
design_714 = "True (display survey in queue)"
design_715 = "False (hide survey in queue)"
design_716 = "True (condition is true)"
design_717 = "False (condition is not true)"
design_718 = "Valid"
design_719 = "Project successfully deleted!"
design_720 = "Your project was deleted immediately because it was determined that the project contained no records. So there was no need to send a request to the REDCap administrator. The project has now been successfully deleted. You will now be redirected back to the My Projects page."
design_721 = "Tap the slider above to set a response"
design_722 = "Change the slider above to set a response"
design_723 = "To start using Action Tags, navigate to the Online Designer in a project, and when adding or editing a field, add the tag into the Action Tag/Field Annotation text box in the Edit Field popup."
design_724 = "Action Tags are an excellent way to customize the data entry experience for surveys and forms. They are special terms that begin with the '@' sign that can be placed inside a field's Field Annotation when adding or editing a field. Each action tag has a corresponding action that is performed for the field when displayed on data entry forms and survey pages. Below is a comprehensive list of all available action tags that you may use. You can use as many as you want for a single field, but if you do use more than one tag for a field, make sure to put a space or line break between them. Because the action tags are used as part of the Field Annotation, they are not displayed anywhere on the page."
design_729 = "<b>WARNING: REMOVE DUPLICATE CODINGS</b> - Some choices have duplicate codings (raw values), which is typically undesirable. Please review the duplicates below, as you will want to change the coding for one of the duplicates so that each has its own unique coding. If this field is saved with any duplicate codings, only the last duplicate will be saved and the other(s) will be lost."
design_730 = "Changes to the DRAFT have been made successfully!"
design_731 = "Branching logic:"
design_732 = "e-Consent Framework Notice:"
design_733 = "It appears that you are utilizing e-Consent version for the survey instruments listed below, in which these instruments have been modified (i.e., fields added, deleted, or modified). Because these instruments are being modified, it is HIGHLY recommended that you change the e-Consent version for these surveys immediately after your submitted changes are approved."
design_734 = "Modified surveys using e-Consent version:"
design_737 = "A review of REDCap Field Variables and Field Notation"
design_738 = "In REDCap, all fields on data collection instruments will have a corresponding 'field name' or 'variable name' that is unique to it. A field's variable name can be defined in the Online Designer or in the Data Dictionary when adding/modifying a field in the project. The variable name can be utilized in various places and functionality in REDCap, such as in conditional logic, calculations, and piping. REDCap variable names are referenced by placing square brackets [ ] around it - e.g., <b>[variable_name]</b>. And if the project is longitudinal, in certain contexts you may need to additionally provide the unique event name, which must also be in brackets and prepended to the variable name, in order to target that field on a particular event - e.g., <b>[event_2_arm_1][variable_name]</b>. The usage of variable names inside brackets is often referred to as REDCap Field Notation."
design_739 = "An introduction to Smart Variables"
design_740 = "In REDCap Field Notation, variable names always point to data fields in the project. However, another type of entity exists called 'Smart Variables' that allow you to reference information other than data fields. Smart Variables are context-aware and thus adapt to many different situations in which they can know who the current user is, what event is currently being viewed, whether or not an instrument is being viewed as a survey or data entry form, etc. In this way, Smart Variables are dynamic (and thus 'smart') because they adapt to the current context in which they are used. Smart Variables are easily distinguishable from field variable names because Smart Variables will have dashes and colons whereas field variable names cannot."
design_741 = "How and where to use Field Notation & Smart Variables"
design_742 = "Field notation (whether referencing variable names or using Smart Variables) can be utilized in many places throughout REDCap. This makes it very powerful to use for a variety of purposes. Regardless of where it is utilized, the format of variable names in field notation is always the same. If a variable is used on its own, it will simply be [variable], and if you wish to specify that field variable for a specific event (for longitudinal projects), you must prepend the unique event name - e.g., [event][variable]. If you are referencing a specific repeating instance of the field, you append (not prepend) the repeat instance number in brackets - e.g., [variable][2], in which the format is the same for both repeating instruments and repeating events. If you are referencing the second instance of a repeating event, for example, you would use the format [event][variable][2]. If you are wanting to determine if a certain option for a checkbox field is checked or not, you may include the checkbox option value inside parentheses which follow the variable name inside the brackets - e.g., [my_checkbox(4)]. All these components can be used together, if needed, such as if you want to reference checkbox option 3 that exists on the fifth instance of a repeating instrument on 'Event 1' - e.g., [event_1_arm_1][my_checkbox(3)][5]."
design_743 = "On their own - e.g., <i>[record-dag-name]</i>"
design_744 = "In conjunction with field variables - e.g., <i>[previous-event-name][weight_measurement]</i>"
design_745 = "In conjunction with other Smart Variables - e.g., <i>[previous-event-name][survey-url:prescreening_survey]</i>"
design_746 = "Smart Variables can be used..."
design_747 = "Learn about"
design_748 = "How to use"
design_749 = "Calculated fields - using mathematical operations to calculate a numerical result"
design_751 = "Piping - using field notation to insert values into labels on a survey/form or inside a survey invitation"
design_752 = "Field notation and Smart Variables can be used for..."
design_754 = "Piping from Checkbox fields"
design_755 = "Piping from Checkbox fields is slightly different than with other field types because checkboxes allow for multiple saved values. There are options to display a list of checked choices, unchecked choices, or a specific choice."
design_756 = "If you are piping the answer *FROM* a multiple choice field (radio, drop-down), it will display the option label (not the coded data value) into the location where the field is piped. For example, if you had a drop-down question that said 'What is your favorite ice cream?' with the choices 'Chocolate', 'Vanilla', and 'Strawberry' (all coded as 0, 1, 2, respectively), then after selecting 'Chocolate', the next question would read 'On a scale of 1 to 10, how much to you like Chocolate?'. But for non-multiple choice fields, such as Text, Notes, Slider fields, it will pipe the literal data value. <b>If you wish to pipe the value (not the label) of a multiple choice field, append ':value'</b> to the variable name inside brackets - e.g., [race:value]. Note: The usage of ':value' must be used if piping inside the <b>@DEFAULT Action Tag if you would like to pipe the value of a multiple choice field</b> as the default value of a field."
design_757 = "Appending ':checked' will display a comma-delimited list of choice labels that have been checked - e.g., 'Sunday, Tuesday, Thursday'. Note: If neither ':checked' nor ':unchecked' is appended to the variable, then it will default to ':checked'."
design_758 = "Appending ':unchecked' will display a comma-delimited list of choice labels that have NOT been checked - e.g., 'Monday, Wednesday, Friday, Saturday'."
design_759 = "If a coded value of the checkbox is included inside parentheses after the variable name - e.g., [my_checkbox:(2)] - then it will output the word 'Checked' or 'Unchecked' regarding whether or not that specific choice has been checked off."
design_760 = "Please note that while the checkbox piping options listed above will return the text labels, you may also <b>append ':value' to the variable to return the raw value</b> instead of the label. For example, [my_checkbox:checked:value] and [my_checkbox:unchecked:value] might return '1, 3, 5' and '2, 4, 6, 7', respectively, and [my_checkbox(2):value] will return 1 or 0 if checked or not checked, respectively."
design_761 = "(utilized in logic, calcs, and exports)"
design_762 = "Loads the current user's date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field."
design_763 = "Loads the current user's date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the user's local time, which is derived from their device/computer and might be different from the server if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field."
design_765 = "ADMINISTRATOR NOTE: Since you are a REDCap administrator, please be advised that you may also use Smart Variables inside the query of a dynamic SQL Field that is displayed on a survey or data entry form. You may see the SQL Field instructional popup in the Online Designer for tips on how to do this."
design_766 = "NOTE: While Smart Variables can be utilized in Data Quality rule logic, in many cases they will cause Data Quality rules to take much longer to complete."
design_767 = "Conditional logic - includes branching logic, advanced filters for reports, and logic for Survey Queue, Data Quality rules, Custom Record Status Dashboards, and Automated Survey Invitations"
design_768 = "NOTICE: Only the first"
design_769 = "records can be displayed in this list"
design_770 = "Since the project is in production, you are not permitted to un-designate an instrument for an event (only a REDCap admin may do this). The following rows must be re-added to the CSV upload mapping file:"
design_771 = "-- select ontology service --"
design_772 = "Ontology Service"
design_774 = "Expand"
design_775 = "Expand all instruments"
design_776 = "Collapse"
design_777 = "Collapse all instruments"
design_778 = "Cannot modify instrument!"
design_779 = "This instrument cannot be modified in any way because it is a PROMIS instrument, which means that its questions are generated from an external REDCap server. You may, however, rename or delete the instrument."
design_780 = "Dictionary"
design_781 = "Designer"
design_782 = "Project Home and Design"
design_783 = "Use the Rich Text Editor"
design_784 = "For any field on an instrument, you may optionally utilize the rich text editor for styling your field labels or section headers with many text-formatting options. The rich text editor allows you to change the color of text (including background color), create tables, add text of varying sizes, bullet lists, and more. For any field labels that were originally created without the rich text editor, you may optionally enable the rich text editor for any field by clicking the 'Use the Rich Text Editor' checkbox. It may also be disabled afterward at any time just the same. Note: The PDF export of your instruments will *not* reflect all the styling of the rich text editor, so keep in mind that line breaks and paragraphs should be represented well in PDFs, but other text-formatting options, such as large text, bullet points, and colors are not able to be translated into the PDF export of the instrument. This is a current limitation in REDCap."
design_785 = "Loads the REDCap server's date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the REDCap server's local time, which might be different from the user's local time if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field."
design_786 = "Loads the current UTC/GMT date+time into a blank Text field - similar to the @TODAY tag but additionally includes the time portion. If the field has validation, the value will adjust to match the date format. NOTE: The time used will be the current UTC/GMT time, which might be different from the user's local time if in another timezone. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field."
design_787 = "Loads the REDCap server's date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field."
design_788 = "Loads the current UTC/GMT date into a blank Text field - similar to the @NOW tag but without the time portion. If the field has validation, the value will adjust to match the date format. Also, do not use this tag on fields with branching logic because it will always prompt the user to erase the value, so look at using @HIDDEN instead if you wish to hide the field."
design_789 = "Enabled as survey"
design_790 = "Hides the field only in the downloaded PDF of one or more instruments (including blank PDFs, PDFs with data, and compact PDFs with data). Note: Other @HIDDEN action tags will not hide fields inside PDF exports, so @HIDDEN-PDF must be used specifically to hide fields in PDFs."
design_791 = "This page can only be accessed when the project is in Development or Production status."
design_792 = "* You should NOT use identifiers (e.g., MRN, SSN) for the record ID field."
design_793 = "Field is embedded elsewhere on page"
design_794 = "How to embed a field elsewhere"
design_795 = "Field Embedding"
design_796 = "WARNING: It appears that the field"
design_797 = "has mistakenly been embedded inside its own labels, which will cause the Field Embedding not to work correctly. A field cannot be embedded in itself but only inside other fields. Please correct this and re-save the field."
design_799 = "ERROR: The field"
design_800 = "has already been embedded on this page. Fields cannot be embedded more than once."
design_801 = "is embedded elsewhere on this page, but it currently has the field"
design_802 = "embedded inside it here. Fields cannot be embedded in other fields that are also embedded. You should remove the field"
design_803 = "from here so that Field Embedding will function correctly."
design_804 = "How to embed a field"
design_805 = "The 'Field Embedding' feature in REDCap is the ultimate way to customize your surveys and data collection instruments to make them look exactly how you want. Field Embedding allows you to reposition field elements on a survey page or data entry form so that they get embedded in a new location on that same page. Embedding fields gives you greater control over the look and feel of your instrument. For example, you may place fields in a grid/table for a more compact user-friendly page, or you can position some fields close together in a group if they are related. See the screenshots below for examples of what field embedding looks like and how to utilize this powerful feature."
design_806 = "What is Field Embedding?"
design_807 = "The steps below illustrate the basic template for embedding a field."
design_808 = "First, create the field. <b>The field must exist first before it can be embedded elsewhere.</b> Note: You do not necessarily have to add a Field Label to the field because that label will ultimately be hidden when the field gets relocated elsewhere on the page. This is true for a field's Field Note and '*must provide value' text (if required) as well, in which none of those text labels will get moved with a field when it is embedded."
design_809 = "Place the REDCap variable name of the field you wish to embed <b>inside braces/curly brackets</b> - e.g., {date_of_birth} - and place it in the Field Label, Field Note, Section Header, or Choice Label of another field <u>on that same instrument</u>. Field embedding will not work across instruments but only on the current instrument/survey being viewed. If on a multi-page survey, then the embedded field must be on the same survey page as its host field. <b>We encourage you to utilize the rich text editor heavily to get the field to look exactly how you want.</b>"
design_810 = "Example of setting up an embedded field in the Online Designer using a table in a Descriptive field's Field Label"
design_811 = "Test it. Create a test record, and go view the instrument to check that the embedded field looks like you wanted. If not, keep tweaking it using the rich text editor. The 'Preview Instrument' button in the Online Designer may also be used to view how the instrument might look when embedding fields, but it is a much more limited and less accurate representation than when viewing the instrument itself for a test record."
design_812 = "Recommendations and limitations for usage"
design_813 = "Field embedding will only relocate the actual input element (e.g., the text box, radio buttons). <b>It will not relocate the field label or field note</b>, although it *will* relocate the choice label for radio/checkbox fields so that the radio/checkbox choices maintain their labels. Additionally, <b>the original location of the field being embedded will be completely hidden after it is relocated</b>, which means that the field's true field label, field note, etc. will never actually be seen on the survey/instrument. It is recommended to add a Field Label even if the field is being embedded because the label will still be needed when viewing a report."
design_814 = "For field embedding to work, you must <b>place the variable name in braces/curly brackets { }</b> - e.g., {date_of_birth}. This is different from piping, which uses square brackets [ ]."
design_815 = "<b>Field embedding does not work in the REDCap Mobile App</b>. If a project with embedded fields is loaded into the mobile app, it will not look how it does on a REDCap survey/instrument webpage."
design_816 = "<b>Do not nest embedded fields:</b> A field cannot be embedded inside itself (i.e., in its own Field Label), and a field cannot be embedded in another field's Field Label or Field Note if that field is also embedded elsewhere. If these are done, an error message will appear when viewing the instrument in most cases. A field *can* be embedded into a Choice Label of a multiple choice field (with the exception of drop-down fields) that is also embedded elsewhere; this would be considered compound embedding."
design_817 = "<b>Adding the field icons:</b> The usual icons pertaining to a field's Data History, Field Comments, and (if enabled) Missing Data Codes can be displayed on a data entry form (but not on a survey) next to the embedded field's new location by <b>appending <code>:icons</code> to the variable name inside the braces/curly brackets</b> - e.g., {last_name:icons}. The icons do not appear by default but only when the ':icons' signifier is attached."
design_818 = "<b>The most common place to embed a field is in the Field Label of a Descriptive field.</b> Descriptive fields are merely blocks of text, so they are excellent for using the rich text editor to build tables or complex structures for placing your text and embedded fields."
design_819 = "<b>Fields may be embedded only in the following places: the Field Label, Field Note, Section Header, or Choice Label of another field <u>on the same instrument</u>, or if on a multi-page survey, the embedded field must be on the same survey page as its host field.</b> Note: Fields cannot be embedded into drop-down labels, survey instructions, survey acknowledgment text, survey queue text, or into any outgoing emails/invitations/alerts."
design_820 = "NOTICE: One or more data collection instruments in this project are utilizing Field Embedding to reposition fields on the instrument. However, please keep in mind that the Twilio functionality for surveys does not support Field Embedding. <b>The Field Embedding feature works when taking a survey or data entry form in webpage format only</b>, not in SMS or voice call format."
design_821 = "cannot be embedded on this page because it exists on a different instrument or different survey page. Fields may only be embedded on the page on which they are located."
design_823 = "The Record ID field (the first field in the project) cannot be embedded because it is a special field."
design_824 = "<b>Branching logic:</b> If a field is embedded and has branching logic, the branching logic for that field will operate as it normally does, in which the embedded field will be hidden when its branching logic evaluates to FALSE. Additionally, if the host field contains branching logic that causes it to be hidden, then all fields embedded within it will be hidden as well (since they are considered part of the host field). When the host field is being hidden, if any of the embedded fields inside the host field have a value, then the user viewing the data entry form (surveys are excluded) will be given the 'Erase current value of the field?' prompt for each embedded field. In this case, if the user responds to the prompt with 'Cancel' in regard to erasing the value of *any* of the embedded fields, then the host field will not be hidden but will remain visible."
design_826 = "<b>Delete</b> all selected fields"
design_827 = "How to modify multiple fields together"
design_829 = "Modify multiple fields"
design_830 = "<b>Copy</b> all selected fields"
design_831 = "Learn how to customize your instrument or survey by using"
design_832 = "Also download with other delimiters:"
design_833 = "appears to be embedded inside itself on this page. This is not allowed."
design_834 = "must be less than or equal to 100 characters in length."
design_835 = "must be less than or equal to 255 characters in length."
design_837 = "Evaluates logic that is provided inside a @CALCTEXT() function for Text Box fields *only* and outputs the result as text, typically performed with an if(x,y,z) function - e.g., @CALCTEXT(if([gender]='1', 'male', 'female')). NOTE: It is important to realize that a field with @CALCTEXT will not be editable on the survey page or data entry form, and the field will function almost exactly like a normal calculated field, in which its value may get updated via a data import, when running Data Quality rule H, or in real-time during normal data entry on a form or survey. If desired, it is possible to return the value as a number - e.g., @CALCTEXT(if([age] >= 18, 'adult', 5*[other_field])). Also, while it is possible to use static text (in quotes), field variables, or Smart Variables as the return values of the IF function - e.g., @CALCTEXT(if([age] >= 18, [dob], [event-label]) - it is NOT possible to pipe field variables or Smart Variables <u>inside quotes</u> for the return values."
design_839 = "Special Functions"
design_840 = "List of functions that can be used in Branching Logic, Calculations, Report filtering, Data Quality Module, Automated Survey Invitations, etc."
design_841 = "REDCap logic can be used in a variety of places, such as Branching Logic, Calculations, Report filtering, Data Quality Module, Automated Survey Invitations, and more. Special functions can be used in the logic, if desired. A complete list of ALL available functions is listed below."
design_842 = "CONDITION, VALUE if condition is TRUE, VALUE if condition is FALSE"
design_843 = "If/Then/Else conditional logic"
design_844 = "Return a value based upon a condition. If CONDITION evaluates as a true statement, then it returns the first VALUE, and if false, it returns the second VALUE. E.g. if([weight] > 100, 44, 11) will return 44 if \"weight\" is greater than 100, otherwise it will return 11."
design_845 = "Function"
design_846 = "Name/Type of Function"
design_847 = "Notes / Examples"
design_848 = "Calculate the difference between two dates or datetimes. Options for 'units': 'y' (years, 1 year = 365.2425 days), 'M' (months, 1 month = 30.44 days), 'd' (days), 'h' (hours), 'm' (minutes), 's' (seconds). The parameter 'returnSignedValue' must be either <i>true</i> or <i>false</i> and denotes whether you want the returned result to be either signed (have a minus in front if negative) or unsigned (absolute value), in which the default value is <i>false</i>, which returns the absolute value of the difference. For example, if [date1] is larger than [date2], then the result will be negative if returnSignedValue is set to <i>true</i>. If returnSignedValue is not set or is set to <i>false</i>, then the result will ALWAYS be a positive number. If returnSignedValue is set to <i>false</i> or not set, then the order of the dates in the equation does not matter because the resulting value will always be positive (although the + sign is not displayed but implied)."
design_849 = "If the \"decimal places\" parameter is not provided, it defaults to 0. E.g. To round 14.384 to one decimal place: round(14.384,1) will yield 14.4"
design_850 = "If the \"decimal places\" parameter is not provided, it defaults to 0. E.g. To round up 14.384 to one decimal place: roundup(14.384,1) will yield 14.4"
design_851 = "If the \"decimal places\" parameter is not provided, it defaults to 0. E.g. To round down 14.384 to one decimal place: rounddown(14.384,1) will yield 14.3"
design_852 = "Use caret ^ character and place both the number and its exponent inside parentheses. NOTE: The surrounding parentheses are VERY important, as it will not function correctly without them. For example, (4)^(3) or ([weight]+43)^(2)"
design_853 = "Returns the absolute value (i.e. the magnitude of a real number without regard to its sign). E.g. abs(-7.1) will return 7.1 and abs(45) will return 45."
design_854 = "Returns the minimum value of a set of values in the format min([num1],[num2],[num3],...). NOTE: All blank values will be ignored and thus will only return the lowest numerical value. There is no limit to the amount of numbers used in this function."
design_855 = "Returns the maximum value of a set of values in the format max([num1],[num2],[num3],...). NOTE: All blank values will be ignored and thus will only return the highest numerical value. There is no limit to the amount of numbers used in this function."
design_856 = "Returns the mean (i.e. average) value of a set of values in the format mean([num1],[num2],[num3],...). NOTE: All blank values will be ignored and thus will only return the mean value computed from all numerical, non-blank values. There is no limit to the amount of numbers used in this function."
design_857 = "Returns the median value of a set of values in the format median([num1],[num2],[num3],...). NOTE: All blank values will be ignored and thus will only return the median value computed from all numerical, non-blank values. There is no limit to the amount of numbers used in this function."
design_858 = "Returns the sum total of a set of values in the format sum([num1],[num2],[num3],...). NOTE: All blank values will be ignored and thus will only return the sum total computed from all numerical, non-blank values. There is no limit to the amount of numbers used in this function."
design_859 = "Returns the standard deviation of a set of values in the format stdev([num1],[num2],[num3],...). NOTE: All blank values will be ignored and thus will only return the standard deviation computed from all numerical, non-blank values. There is no limit to the amount of numbers used in this function."
design_860 = "Returns the logarithm of the number provided for a specified base (e.g. base 10, base \"e\"). If base is not provided or is not numeric, it defaults to base \"e\" (natural log)."
design_861 = "Is value a number?"
design_862 = "Returns a boolean (true or false) for if the value is an integer OR floating point decimal number."
design_863 = "Is value an integer?"
design_864 = "Returns a boolean (true or false) for if the value is an integer (whole number without decimals)."
design_865 = "Does text CONTAIN another text string?"
design_866 = "Returns a boolean (true or false) for if \"needle\" exists inside (is a substring of) the text string \"haystack\". Is case insensitive. E.g. contains(\"Rob Taylor\", \"TAYLOR\") will return as TRUE and contains(\"Rob Taylor\", \"paul\") returns FALSE. NOTE: This function will *not* work for calculated fields but *will* work in all other places (Data Quality, report filters, Survey Queue, etc.)."
design_867 = "Does text NOT CONTAIN another text string?"
design_868 = "The opposite of contains(). Returns a boolean (true or false) for if \"needle\" DOES NOT exist inside (is a substring of) the text string \"haystack\". Is case insensitive. E.g. not_contain(\"Rob Taylor\", \"TAYLOR\") will return as FALSE and not_contain(\"Rob Taylor\", \"paul\") returns TRUE. NOTE: This function will *not* work for calculated fields but *will* work in all other places (Data Quality, report filters, Survey Queue, etc.)."
design_870 = "Does text START WITH another text string?"
design_871 = "Returns a boolean (true or false) if the text string \"haystack\" begins with the text string \"needle\". Is case insensitive. E.g. starts_with(\"Rob Taylor\", \"rob\") will return as TRUE and starts_with(\"Rob Taylor\", \"Tay\") returns FALSE. NOTE: This function will *not* work for calculated fields but *will* work in all other places (Data Quality, report filters, Survey Queue, etc.)."
design_872 = "Does text END WITH another text string?"
design_873 = "Returns a boolean (true or false) if the text string \"haystack\" ends with the text string \"needle\". Is case insensitive. E.g. ends_with(\"Rob Taylor\", \"Lor\") will return as TRUE and ends_with(\"Rob Taylor\", \"Tay\") returns FALSE. NOTE: This function will *not* work for calculated fields but *will* work in all other places (Data Quality, report filters, Survey Queue, etc.)."
design_874 = "Is a field's value blank/null or is it a Missing Data Code?"
design_875 = "Returns a boolean (true or false) if the field value is blank/null/'' or if the value is a Missing Data Code, in which Missing Data Codes have been explicitly defined in the project on the Project Setup page under Additional Customizations. E.g. isblankormissingcode([age]), in which if 'age' has a value of 'UNK' (which might be a Missing Data Code in a project), then it will return TRUE. And if the field has any non-blank/non-null value that is also not a Missing Data Code, it will return FALSE."
design_876 = "Functions to use with Text values"
design_877 = "Functions to use with Numbers"
design_878 = "Returns the leftmost characters"
design_879 = "Returns the leftmost characters from a text value. For example, left([last_name], 3) would return 'Tay' if the value of [last_name] is 'Taylor'."
design_880 = "Returns the rightmost characters"
design_881 = "Returns the rightmost characters from a text value. For example, right([last_name], 4) would return 'ylor' if the value of [last_name] is 'Taylor'."
design_882 = "Returns the number of characters"
design_883 = "Returns the number of characters in a text string. For example, length([last_name]) would return '6' if the value of [last_name] is 'Taylor'."
design_884 = "Finds one text value within another"
design_885 = "Finds one text value within another. Is case insensitive. The \"needle\" may be one or more characters long. For example, find('y', [last_name']) would return '3' if the value of [last_name] is 'Taylor'. The value '0' will be returned if \"needle\" is not found within \"haystack\"."
design_886 = "Returns characters from a text string starting at a position"
design_887 = "Returns a specific number of characters from a text string starting at the position you specify. The second parameter denotes the starting position, in which the beginning of the text value would be '1'. The third parameter represents how many characters to return. For example, mid([last_name], 2, 3) would return 'AYL' if the value of [last_name] is 'TAYLOR'."
design_888 = "Combines the text from multiple text strings"
design_889 = "Combines/concatenates the text from multiple text strings into a single text value. For example, concat([first_name], ' ', [last_name]) would return something like 'Rob Taylor'. Each item inside the function must be separated by commas. Each item might be static text (wrapped in single quotes or double quotes), a field variable, or a Smart Variable."
design_890 = "Converts text to uppercase"
design_891 = "Converts text to uppercase. For example, upper('John Doe') will return 'JOHN DOE'."
design_892 = "Converts text to lowercase"
design_893 = "Converts text to lowercase. For example, lower('John Doe') will return 'john doe'."
design_894 = "Removes spaces from the beginning and end of text"
design_895 = "Removes any spaces from both the beginning and end of a text value. For example, trim(' Sentence with spaces on end. ') will return 'Sentence with spaces on end.'."
design_896 = "Listed below are some examples of common use cases where these functions might be used."
design_897 = "Practical examples for common use cases"
design_898 = "Calculate a person's age based on date of birth."
design_899 = "Calculate the number of days separating today's date and a date/datetime field's value in the past or future."
design_900 = "Calculate a person's BMI (in metric units of 'cm' and 'kg') and rounding to the first decimal place."
design_901 = "Calculate a person's BMI (in English units of 'lb' and 'in') and rounding to the first decimal place."
design_902 = "Remove a prefix and dash from the beginning of a record name (e.g., convert '4890-2318' to '2318')."
design_903 = "Convert a person's first and last name into a username-looking format (e.g., convert 'John' and 'Doe' to 'john_doe'). We may want to trim the values just in case there were spaces accidentally entered."
design_904 = "Add leading zeros to an integer, in which the number near the end of the equation represents the maximum length of the result after adding the leading zeros (i.e., converts '7' to '007'). Note: The amount of 0s listed in '00' should be at least one less than the value of the number near the end (e.g., if '4', then we need '000'; if '3', then '00')."
design_905 = "NOTICE: The Biomedical Ontologies service that fuels the ontology search feature in REDCap is provided by BioPortal (https://bioportal.bioontology.org) using their public API web service. The BioPortal web service is operated and maintained independently of REDCap, and any changes or updates made to the BioPortal service (such as adding new ontologies or updating/deprecating existing ontologies) is performed completely by BioPortal. Neither REDCap nor Vanderbilt (who creates and maintains REDCap), have any say or jurisdiction in this process. If you have a specific question about the BioPortal API web service or about a specific feature or ontology that they maintain, you may contact them directly via email at support@bioontology.org."
design_906 = "Import from Field Bank"
design_907 = "Using the Field Bank, search for fields in various catalogs below by selecting a catalog and entering specific keyword. When reviewing the resultsup of your search, click the \"Add Field\" button for the field to add that field to the current data collection instrument."
design_908 = "Please select a catalog above and enter a search keyword."
design_909 = "Classification:"
design_910 = "Keyword:"
design_911 = "Clear All"
design_912 = "Minimum Length:"
design_913 = "Maximum Length:"
design_914 = "Minimum Value:"
design_915 = "Maximum Value:"
design_917 = "fields found for"
design_918 = "Remove classification filter"
design_919 = "Remove keyword filter"
design_920 = "Searching catalog..."
design_921 = "Loading list of catalogs..."
design_922 = "By Default, Field Label will be assigned from <b>Default Question Text</b>. <br>You may select any option you found suitable for you from <b>Preferred Question Texts</b>."
design_923 = "Choose alternative field label"
design_924 = "Default field label"
design_925 = "Alternative field labels"
design_926 = "All Classifications"
design_928 = "Click to expand"
design_929 = "Click to collapse"
design_930 = "NLM Classifications List"
design_931 = "Select a catalog of fields to search:"
design_932 = "REDCap Catalog of Common Data Fields"
design_933 = "NIH CDE Repository"
design_934 = "Data type:"
design_935 = "Select a catalog to search:"
design_936 = "(click to view all classifications)"
design_937 = "Enable the Field Bank in the Online Designer?"
design_938 = "If disabled here, the 'Import from Field Bank' button will be hidden in the Online Designer for all users."
design_939 = "The Field Bank allows users to import fields from various standardized catalogs when building their instruments via the Online Designer."
design_940 = "The custom min/max value of a slider must be an integer (positive or negative) or a blank value."
design_941 = "Display number value?"
design_942 = "Min/max range values:"
design_943 = "NOTICE: Sorry, but the instrument"
design_944 = "exists only in Draft Mode and not in the live version of the project. Therefore it is not possible to download the Instrument ZIP file for this instrument. Please return to the"
design_945 = "Custom text to display on survey page when offline:"
design_946 = "Please note that there are other Stop Action settings on the Survey Settings page for a given instrument, such as the ability to set custom text when a survey ends via Stop Action."
design_948 = "Sets a field's value to static text or dynamic/piped text whenever a data entry form or survey page is loaded, in which it will <u>always overwrite</u> an existing value of the field. The format must follow the pattern @SETVALUE=\"????\", in which the desired value should be inside single or double quotes. For text fields, you may pipe and concatenate values from other fields in the project - e.g., @SETVALUE='Name: [first_name] [last_name], DOB: [dob]'. For checkbox fields, simply separate multiple checkbox values with commas - e.g., @SETVALUE='1,3,[other_field:value]'. NOTE: The piped value does *not* get applied during any data imports (via API or Data Import Tool) but only operates when viewing survey pages and data entry forms. <u>NOTE: A field with @SETVALUE will have its value updated ONLY when the page loads, which means that its value will not be updated in real-time if you modify other fields on the same page that are piped into the @SETVALUE tag.</u> NOTE: If being used on a date or datetime field, the date value inside the quotes must be in Y-M-D format - e.g., @SETVALUE='2007-12-25' - regardless of the field's set date format. NOTE: The only difference between @SETVALUE and @DEFAULT is that @DEFAULT is only applied when an instrument has no data yet, whereas @SETVALUE will always be applied on an instrument, meaning that @SETVALUE will ALWAYS overwrite the value if a field value already exists. TIP: To pipe the value of one multiple choice field into another multiple choice field, make sure you append ':value' to the variable being piped - e.g., @SETVALUE='[my_dropdown:value]'. (In earlier versions of REDCap, the @SETVALUE action tag went by the name @PREFILL, which still works equivalently to @SETVALUE for backward compatibility purposes.)"
design_949 = "Sorry, but events can only be renamed by REDCap administrators when a project is in production status. Renaming an event could cause drastic consequences if the unique event name is used in any calculations, branching logic, report filters, or other conditional logic throughout the project. Please contact your local REDCap administrator if you need to rename an event, and they can do that for you."
design_950 = "Sorry, but arms can only be renamed by REDCap administrators when a project is in production status. Renaming an arm could cause drastic consequences if a unique event name from the arm is used in any calculations, branching logic, report filters, or other conditional logic throughout the project. Please contact your local REDCap administrator if you need to rename an arm, and they can do that for you."
design_953 = "Previous instrument"
design_954 = "Next instrument"
design_955 = "Learn how to use..."
design_956 = "The new instrument was successfully created. The page will be reloaded to reflect this change."
design_957 = "<b>IMPORTANT NOTE:</b> By default, no users in the project have access to this new instrument yet. So <u>after your current Draft Mode changes are approved</u>, please remember to grant View/Edit rights to all relevant users/roles or coordinate with a User Rights manager on the project to open up access to this instrument."
design_960 = "<b>ERROR:</b><br>You may have saved your Data Dictionary in Microsoft Excel 2003 (XLS) or 2007 (XLSX) format, but it needs to be in CSV format when uploading here. To fix this, try opening it in Excel, then save the file again as CSV (comma delimited format). Then try uploading it again."
design_961 = "<b>ERROR:</b><br>You did not upload a CSV (comma delimited) file. Please upload a file with CSV file extension."
design_962 = "or open the"
design_963 = "The data entry forms listed below are controlled by Form Display Logic."
design_964 = "Form Display Logic is an advanced feature that provides a way to use conditional logic to disable specific data entry forms that are displayed on the Record Status Dashboard, Record Home Page, or the form list on the left-hand menu. You might think of it as 'form-level branching logic'. Form Display Logic can be very useful if you wish to prevent users from entering data on a specific form or event until certain conditions have been met. The forms will still be displayed on the page, but they will be disabled in order to prevent users from accessing them. Below you may define as many conditions as you want. A form may be selected in multiple conditions, but if so, please note that <u>the form will be enabled if at least one of the conditions is met</u>. The Form Display Logic does not impact data imports but only operates in the data entry user interface to enable/disable forms. Additionally, Form Display Logic is not utilized by the Survey Queue at all but can affect the behavior of the Survey Auto-Continue feature if the checkbox for it is enabled below."
design_965 = "Keep forms enabled if they contain data"
design_966 = "Only disable empty forms (those with a gray form status icon)."
design_968 = "Add another condition"
design_969 = "(You may select multiple forms by clicking them)"
design_970 = "...when the logic below is <i>TRUE</i>."
design_971 = "<b>NOTICE:</b> One or more forms have been selected in multiple conditions, which is allowable. Please note that in this case the form will be enabled if <u>at least one of the conditions is met</u>. Below is list of forms utilized in multiple conditions:"
design_972 = "Are you sure you want to remove all conditions?"
design_973 = "Enable support for Survey Auto-Continue"
design_974 = "When collecting data via survey, any currently hidden forms will be skipped over when the \"Auto-continue to next survey\" option is being used."
design_975 = "Condition"
design_976 = "Keep the following forms enabled..."
design_977 = "Delete all conditions"
design_983 = "[All Events]"
design_984 = "Optional Settings:"
design_985 = "Form Display Logic"
design_986 = "Form options:"
design_987 = "Your Form Display Logic settings have been successfully saved."
design_988 = "One or more forms have not been selected. Please select AT LEAST one form to enable in the drop-down list or alternatively click the red X to remove condition."
design_989 = "One or more logic condition have been left blank. Please enter logic condition or alternatively click the red X to remove condition."
design_990 = "[collapsed]"
design_991 = "<b>IMPORTANT NOTE IF YOU CREATED NEW INSTRUMENTS IN DRAFT MODE:</b> By default, no users in the project have access to newly created instruments. So please remember to grant View/Edit rights to all relevant users/roles or coordinate with a User Rights manager on the project to open up access to any instruments that were just created while in Draft Mode."
design_992 = "View list of selected forms"
design_993 = "Selected forms for this condition"
design_994 = "Listed below are all the selected forms/events for the current condition:"
design_995 = "Nothing has been selected for this condition."
design_996 = "Contains embedded fields"
design_998 = "Tip for min/max limits:"
design_999 = "Also edit Branching Logic for OTHER fields?"
design_1000 = "NOTE: It is advised that you do not use @CALCTEXT or @CALCDATE inside the @IF action tag because the @CALC action tags operate in many contexts that @IF does not, thus resulting in unexpected results."
design_1001 = "This same exact branching logic is shared by multiple fields. Would you like to automatically update the branching logic of ALL the other fields (even those on other instruments) that have the exact same branching logic? <b>NOTE: Clicking YES will update the other fields' branching logic immediately.</b>"
design_1002 = "<b>IMPORTANT NOTE:</b> By default, ALL users in the project will automatically have access to this new instrument. So <u>after your current Draft Mode changes are approved</u>, if you do not want users to access this new instrument, please remember to grant No Access rights to all relevant users/roles or coordinate with a User Rights manager on the project to set No Access rights to this instrument."
design_1003 = "<b>IMPORTANT NOTE IF YOU CREATED NEW INSTRUMENTS IN DRAFT MODE:</b> By default, ALL users in the project have full access to newly created instruments. So if you do not want users to access the new instruments, please remember to grant No Access rights to all relevant users/roles or coordinate with a User Rights manager on the project to set No Access rights to any instruments that were just created while in Draft Mode."
design_1004 = "NOTICE: This project is configured to use the Protected Email Mode."
design_1005 = "Note that the Protected Email Mode will not apply to alerts that utilize sendgrid template emails because these emails cannot be fully rendered in the REDCap web application."
design_1006 = "Display only the red asterisk"
design_1007 = "Sets a field's value to the username of the current REDCap user. If this is used on a survey, the value will be '{0}'. Once the value is captured, it will not be changed when visiting the page at a later time."
design_1008 = "Adds the rich text editor toolbar to a Notes field to allow users/participants to control the appearance (via styling and formatting) of the text they are entering into the field. To ensure all rich text controls are displayed, set <b>Custom Alignment</b> to one of the <b>Left</b> options."
design_1009 = "Additionally, all users have been automatically given 'De-Identified' data export rights to any new instruments created."
design_1018 = "Collecting survey data in a repeating fashion can be done efficiently and with minimal setup by using a repeating survey, which is a survey that is enabled as a repeating instrument or (if a longitudinal project) a survey instrument utilized on a repeating event. However, it can sometimes be difficult to know which features to use with repeating surveys to collect repetitive survey data most effectively. The information below presents multiple data collection options for repeating surveys. Each option has its own pros and cons that should be weighed carefully based on your situation. It is important to point out that the options below are not mutually exclusive and can be used in combination together for multiple surveys within a project."
design_1019 = "Automated Survey Invitations (ASIs)"
design_1021 = "Click the 'Automated Invitations' button for the repeating survey in the Online Designer, and then fill out the 'How many times to send it' section in the ASI popup to designate how often and how many times the invitations should be repeated."
design_1022 = "Different ways to collect data for a repeating survey"
design_1023 = "\"Repeat the survey\" button<br>at end of survey"
design_1024 = "Utilize the \"Repeat the survey\" button that can be enabled to appear at the end of the survey to allow participants to keep adding new repeating instances over and over again for the survey."
design_1025 = "Click the buttons below to set up or modify automated survey invitations."
design_1026 = "Data Collection Strategies for Repeating Surveys"
design_1027 = "Repeating instruments only"
design_1028 = "Both (repeating instruments and instruments on repeating events)"
design_1030 = "Utilize an alert that will be repeatedly sent at an a recurring interval, in which the alert will contain a specially-formatted survey link for the repeating survey."
design_1031 = "Utilize an Automated Survey Invitation that will be repeatedly sent at an a recurring interval."
design_1032 = "Activation process and usage"
design_1033 = "Enable the \"Repeat the survey\" option on the Survey Settings page, and participants will be able to enter multiple instances' worth of data in a back-to-back fashion (i.e., in one sitting), in which the \"Repeat the survey\" button will be displayed at the end of the survey. Additionally, if you are utilizing the Survey Queue feature, and the participant has been given their survey queue link, they will be able to enter new repeating survey instances whenever they wish on the survey queue page."
design_1034 = "Does it work with repeating instruments and/or repeating events?"
design_1035 = "Create an alert on the Alerts & Notifications page, and then fill out the 'Send it how many times?' section in the alert popup to designate how often and how many times the notifications should be repeated. The message of the alert must contain the Smart Variable <code>[survey-link]</code> and *MUST* be appended with <code>[new-instance]</code>. For example, if the unique instrument name of your repeating survey is \"daily_survey\", then you would use <code>[survey-link:daily_survey][new-instance]</code>. This will create a survey link in the alert that will always point to a new, not-yet-created instance of the repeating survey."
design_1036 = "No, this works with the web interface only."
design_1037 = "Yes, SMS and voice calls can both be used for sending out the survey link for an ASI."
design_1038 = "Requires an email to be sent?"
design_1039 = "No. Emailing is not required. However, if you are utilizing the Survey Queue, you may optionally need to send the participant their survey queue link using a recurring alert, in which the survey queue will be the landing page for the participant before they enter the survey each time."
design_1040 = "Yes"
design_1041 = "Yes, SMS and voice calls can both be used for sending out the survey link for an alert."
design_1042 = "Common uses"
design_1043 = "Surveys where the participant is emailed at a regular interval, such as with a daily, weekly, or monthly survey. For example, a COVID-19 daily symptom-tracking survey."
design_1044 = "Surveys where some information must be entered multiple times, such as filling out questions about multiple family members or entering medication information for multiple meds."
design_1045 = "Reminder: Never pipe private info (e.g., PII, PHI) into emails."
design_1046 = "Sorry, but empty instruments are not allowed to be copied. Please add at least one field to the instrument, and then you will be able to copy the instrument."
design_1048 = "Special note: If you wish to use any of the text string functions below in branching logic or calculated fields, keep in mind that these functions should NOT be used on date or datetime fields that have MDY or DMY date formatting. They are okay to use with YMD-formatted dates/datetimes, and they are okay to use with any date formatting outside of branching logic or calc fields (e.g., data quality rules, report filter logic, ASI conditional logic). <u>If you wish to use these functions with date/datetime fields in branching and calcs, make sure the field has YMD date format.</u>"
design_1049 = "Opens the Codebook in a new browser tab"
design_1050 = "NOTICE: One or more fields in this project utilize the <b>@IF action tag</b>. However, the REDCap Mobile App currently does not support the @IF action tag.  Thus, those fields unfortunately might not function in the Mobile App the same as they do on survey pages or data entry forms in this project."
design_1051 = "WARNING: The field"
design_1052 = "is utilized in more than one event and/or is utilized on a repeating instrument or repeating event. Any update to this field on any event or repeating instance will change the value of this field in ALL events and repeating instances."
design_1053 = "Inline image/PDF"
design_1054 = "How to use Piping in the URL"
design_1056 = "Branching logic syntax error(s):"
design_1057 = "Syntax error(s) exist in the calculation equation:"
design_1058 = "You must fix all errors listed before you can continue."
design_1059 = "- Odd number of double quotes exist"
design_1060 = "- Odd number of single quotes exist"
design_1061 = "- Square bracket is missing"
design_1062 = "- Parenthesis is missing"
design_1063 = "(unless using SMS and voice calls)"
design_1064 = "Hide forms that are disabled"
design_1065 = "All forms that are disabled will also be hidden (not visible) on the Data Collection menu and on the Record Home Page."
design_1066 = "You may pipe a value from another field to set dynamic range limits - e.g., <code class='fs10'>[visit_date]</code> or <code class='fs10'>[event_1_arm_1][age]</code>. You may also use the word <code class='fs11'>today</code> or <code class='fs11'>now</code> (not wrapped in quotes) for date/time fields."
design_1067 = "Filter action tags"
design_1068 = "Also search in descriptions"
design_1069 = "Filter smart variables"
design_1070 = "This action tag is provided by an external module: <b>{0:ModuleName}</b> ({1:ModuleVersion})"
design_1071 = "The @DOWNLOAD-COUNT action tag provides a way to automatically count the number of downloads for a File Upload field or a Descriptive field attachment. It can be used on a Text field or Notes field so that its value will be incremented by '1' whenever someone downloads the file for either a File Upload field or a Descriptive field attachment. The variable name of the File Upload field or Descriptive field whose downloads are to be counted should be provided inside the @DOWNLOAD-COUNT() function. For example, the Text field 'my_download_count' might have its action tag defined as @DOWNLOAD-COUNT(my_upload_field), in which 'my_upload_field' is the variable of a File Upload field. Whenever the file is downloaded on a data entry form, survey page, or report, the value of the field with this action tag will be incremented by '1'. If that field has no value or has a non-integer value, its value will be set to '1'. NOTE: The download count field must be in the same context as the File Upload field or a Descriptive field. This means that in a longitudinal project the two fields must be on the same event, and in a repeating instrument context, they must be on the same repeating instrument. Also, if @DOWNLOAD-COUNT is used for a field where PDFs are uploaded and displayed inline on the page (via @INLINE or @INLINE-PREVIEW), users/participants clicking the download/down-arrow icon (which is generated by the browser, not by REDCap) for the inline PDF will unfortunately *not* get counted as a download by REDCap; thus, the downloads are only counted when clicking the file download link on the page."
design_1072 = "Joins the text from multiple text strings with a separator"
design_1073 = "This works exactly like <code>concat</code> but inserts the <code>separator</code> in between each concatenated item. For example, <code>concat_ws(\" and \", [veggie1], [veggie2], \"Tomatoes\")</code> might result in \"Peas and Carrots and Tomatoes\"."
design_1074 = "Replaces parts of a text value with a specified replacement text value"
design_1075 = "Finds text (\"search\") inside another text (\"haystack\") and replaces all found occurrences with the given text (\"replace\"). For example, assuming [field1] has a value of \"Paul Taylor, Rob Taylor\", <code>replace_text([field1], \"Taylor\", \"Harris\")</code> would result in \"Paul Harris, Rob Harris\". Note: This function performs a case-sensitive replacement. Additionally, you can search for line breaks (e.g. in Notes fields) with \"\n\"."
design_1076 = "Modulo"
design_1077 = "Returns the remainder of the (integer) division (modulo) <code>dividend/divisor</code>. Both values must be integers. E.g. mod(10,4) will result in 2 because 2 is the remainder of 10 divided by 4."
design_1078 = "Returns \"e\" (Euler's Number) raised to the power of a number: e^x. Note: The value of the exponent x must be a number. E.g. exponential(1) will return 2.718281828459045."
design_1079 = "Exponential of e"
design_1080 = "<b>Potential issue:</b> It appears that you have moved one or more fields to another instrument. Please be advised that if data has already been collected for the fields that you just moved, their data might become orphaned (not accessible anymore) if the instrument they were moved to exists on another event. Please double check your instrument-event mappings to ensure that this does not cause data loss. If this action has orphaned some data, you can always move the field back to its original instrument again, after which its data will then return."
design_1081 = "Please note, this field is utilized for MyCap participant information (such as participant code or join date). If you remove this field, you may lose MyCap participant information."
design_1082 = "Keep checked to include this table in printout"
design_1083 = "Escaping text: If @CALCTEXT is outputting text wrapped in apostrophes or quotes, in which the text itself contains an apostrophe or quote, respectively, you will need to \"escape\" the character by putting a backslash directly in front of it.    For example, <code>if([field]='2', 'Courtney Howell has an \"@CALCTEXT\" tattoo.', 'No tattoo.')</code> is fine without escaping if you put quotes inside apostrophes, but <code>if([field]='4', 'The user\'s guide', 'something else')</code> requires escaping."
design_1084 = "Optional media to embed or attach:"
design_1085 = "Embed media (video, website, survey, etc.)"
design_1086 = "Provide media URL"
design_1087 = "Display format of media:"
design_1088 = "NOTE: You may use Piping in the URL of the media text box."
design_1089 = "<b>Embedding an external video:</b> You can display an embedded video on a data entry form or survey page by simply providing the video's URL (web address) in the 'Embed media' text box. You may have the video be displayed inline on the page, or you may instead have it initially hidden but displayed after clicking a button. Any video can be set to full-screen mode, if desired. Unlike the attachment option for Descriptive fields, which implies uploading a file into REDCap, an embedded video will not be hosted by REDCap but will be hosted on another server elsewhere on the web and streamed to the user's web browser. YouTube and Vimeo videos are the most compatible video streaming services, and you can obtain the URL for such videos on those websites."
design_1090 = "<b>Embedding a website:</b> You can display another website on a data entry form or survey page by providing the URL in the 'Embed media' text box.  This option is best used with the display format of ‘inline’ to have the website appear embedded within the survey or form.  The URL may be another data entry form or survey page within the same project, a data entry form or survey within another project, or a URL internal/external of REDCap.  If the embedded media is in a different project or outside of REDCap entirely, you may directly enter the URL into the 'Embed media' text box to have it appear on the data entry form or survey.  If the embedded media is within the same project, smart variables such as [survey-url:instrument] or [form-url:instrument] will function and connect the data entry forms or surveys to the current record."
design_1091 = "Works with SMS and Voice Calls?"
design_1092 = "Note: If you wish to insert a line break between choices for horizontally-aligned choices, you may use the {0} tag."
design_1093 = "A potential duplicate condition was detected. Please review your setup or press 'Okay' to proceed with your current setup."
design_1094 = "<b><u>Obtaining date components:</u></b> When piping a date or datetime field, you may specifically obtain the year, month, or day component of its date value  by appending the ':year', ':month', or ':day' option, respectively, such as <code>[dob:year]</code> or <code>[visit_date:month]</code>.  Note: The month or day component will contain a leading zero if the resulting value is less than 10."
design_1095 = "Returns the year"
design_1096 = "Returns the year component of a date/datetime field - e.g., year([dob])."
design_1097 = "Returns the month"
design_1098 = "Returns the month component of a date/datetime field - e.g., month([visit_datetime])."
design_1099 = "Returns the day"
design_1100 = "Returns the day component of a date/datetime field - e.g., day([visit_date])."
design_1101 = "Functions to use with Dates or DateTime values"
design_1102 = "Hint: While the name of this project's data table is <code>{0}</code>, it is recommended that you do not reference the data table by name,  but instead use the Smart Variable <code>[data-table]</code> for the current project  or use <code>[data-table:1234]</code>, in which 1234 is the PID belonging to another project."
design_1103 = "Collapse this table"
design_1104 = "Expand this table"
design_1105 = "Repeating event"
design_1106 = "Repeating instrument"
design_1107 = "Collapse all additional tables"
design_1108 = "Expand all additional tables"
design_1109 = "Toggle print inclusion for all tables"
design_1110 = "Media URL:"
design_1111 = "Display format:"
design_1112 = "LIMITATION: Please note that the conditional logic used below will be evaluated at the record level and not within the context of an event or a repeating instance,  which means that it is not possible to use relative instance or relative event Smart Variables - i.e., those with the name 'current', 'next', or 'previous', such as [next-instance] or [previous-event-name]."
design_1113 = "NOTE: The unique group name is auto-generated from the name of the data access group, so there is no way to set the unique group name manually.    If you are attempting to create a new DAG, you should leave the unique_group_name and data_access_group_id fields blank in your upload file."
design_1114 = "Note: You may use \"now\" or \"today\" (wrapped in quotes) instead of a field variable in the function."
design_1115 = "Note: Empty values will be skipped. Thus, in the given example, if <code>[veggie1]</code> has no value, the resulting output would be \"Carrots and Tomatoes\"."
design_1116 = "To copy the variable name to the clipboard, click here:"
design_1117 = "<b>Copy</b> the field name to the clipboard"
design_1118 = "Move field(s) to newly created instrument"
design_1119 = "CREATE NEW INSTRUMENT AND ..."
design_1120 = "[No existing fields]"
design_1121 = "When viewing this page, collapse:"
design_1122 = "all fields"
design_1123 = "all additional tables"
design_1124 = "Save & <b>split</b> matrix into separate fields"
design_1125 = "Split Matrix of Fields?"
design_1126 = "Are you sure you want to split this matrix into separate fields?"
design_1127 = "NOTE: The field above is the record ID field and thus cannot be deleted or moved. It can only be edited."
design_1128 = "<b>Convert</b> to matrix group<br><small>Note: Fields must be adjacent to each other, of type radio or checkbox, and not already part of a matrix group</small>"
design_1129 = "Convert field(s)?"
design_1130 = "Do you wish to convert the field(s) <b>'{0}'</b> to a matrix group?<br><br><b>Note: Only the choices for <u>the first field</u> listed above will be preserved.</b> Additionally, this action will remove all field notes from the fields and will also remove all section headers (except for the first field's section header, if it exists)."
design_1131 = "Convert field(s)"
design_1132 = "Split matrix"
design_1133 = "Conversion to matrix group failed."
design_1134 = "Clear selection"
design_1135 = "<b>Edit</b> Branching Logic"
design_1136 = "<b>Edit</b> Action Tags"
design_1137 = "Field {0:CurrentIndex} of <b>{1:Total}</b> selected fields"
design_1138 = "<b>Set</b> fields to be identfiers"
design_1139 = "<b>Set</b> fields to <b>not</b> be identfiers"
design_1140 = "<b>Set</b> fields to be required"
design_1141 = "<b>Set</b> fields to <b>not</b> be required"
design_1142 = "Quick-modify field(s)"
design_1143 = "<b>Move</b> all selected fields<br><small>Note: Certain combinations of fields cannot be moved together; matrix group fields can only be moved within their matrix group</small>"
design_1144 = "The field(s) could not be updated due to an unspecified error. Please try again after reloading the Online Designer."
design_1145 = "Remove identifiers?"
design_1146 = "Please confirm that the <b>'Identifier'</b> status should be removed from these fields:<br><b>{0}</b>"
design_1147 = "Remove 'Identifier' status"
design_1148 = "Remove required?"
design_1149 = "Please confirm that the <b>'Required'</b> status should be removed from these fields:<br><b>{0}</b>"
design_1150 = "Remove 'Required' status"
design_1151 = "<b>Edit</b> Matrix"
design_1152 = "<b>Move</b> Matrix"
design_1153 = "<b>Delete</b> Matrix"
design_1154 = "<b>Edit</b> Section Header"
design_1155 = "<b>Copy</b> Section Header"
design_1156 = "<b>Delete</b> Section Header"
design_1157 = "Copy section header?"
design_1158 = "Do you wish to copy the section header of field <b>'{0}'</b> to another field on this form?<br><br>Please select the target field:<br>"
design_1159 = "Copy section header"
design_1160 = "<b>Edit</b> Field"
design_1161 = "<b>Copy</b> Field"
design_1162 = "<b>Move</b> Field"
design_1163 = "<b>Delete</b> Field"
design_1164 = "<b>Edit</b> Survey Stop Action"
design_1165 = "Field Name:"
design_1166 = "Edit Branching Logic?"
design_1167 = "In what way would you like to edit the <b>Branching Logic</b> of the following fields?"
design_1168 = "Apply"
design_1169 = "<b>Clear</b> Branching Logic from all fields"
design_1170 = "<b>Copy</b> the Branching Logic of the <b>current</b> field ({0}) to the other fields"
design_1171 = "Add the following <b>new</b> Branching Logic to all selected fields:"
design_1172 = "Edit Action Tags?"
design_1173 = "In what way would you like to edit the <b>Action Tags / Field Annotation</b> of the following fields?"
design_1174 = "<b>Clear</b> Action Tags / Field Annotations from all fields"
design_1175 = "<b>Copy</b> the Action Tags / Field Annotation of the <i>current</i> field ({0}) to all the other selected fields"
design_1176 = "<b>Add</b> the following <i>new</i> Action Tags or annotations to all selected fields (these will be appended to any existing tags):"
design_1179 = "<b>Edit</b> the Action Tags / Field Annotation of the <i>current</i> field ({0})"
design_1180 = "Choose how to modify the fields selected for the Quick-modify popup"
design_1181 = "Select all fields<br>(from top to bottom)"
design_1182 = "Select towards the top<br>(from current field)"
design_1183 = "Select towards the bottom (from current field)"
design_1184 = "Include all fields between the first and last selected fields"
design_1185 = "Include/Exclude | Direction:"
design_1186 = "The new field(s) will be added immediately after the original field(s)."
design_1187 = "Include all fields between the current field and the next selected field above."
design_1188 = "Include all fields between the current field and the next selected field below."
design_1189 = "Reset exclusions"
design_1190 = "Radio-type fields"
design_1191 = "Checkbox fields"
design_1192 = "Text boxes with email validation"
design_1193 = "Descriptive fields"
design_1194 = "Dropdown fields"
design_1195 = "Notes fields"
design_1196 = "File upload fields"
design_1197 = "Calc fields"
design_1198 = "Date, Time, and Datetime fields"
design_1199 = "SQL fields"
design_1200 = "Signature fields"
design_1201 = "Text fields (any validation)"
design_1202 = "Fields in a matrix group"
design_1203 = "Slider fields"
design_1204 = "Reset inclusions"
design_1205 = "Text boxes with any phone validation"
design_1206 = "Text boxes with any number validation"
design_1207 = "Add new selections"
design_1208 = "Replace existing selections"
design_1209 = "How to modify the selection:"
design_1210 = "The buttons on the top row let you choose the direction to expand the selection to, relative to the currently selected field. The options include: Both directions (the default behavior), towards the top, or towards the bottom; or you select all between the first and last selected fields, or up or down from the current field to the next selected field above or below, respectively.<br><br>The inclusion/exclusion buttons allow you to limit selection to certain field types, such as, e.g., text boxes with email validation. Pick any combination that matches your need. Use the buttons at the start of the rows to reset the inclusion/exclusion criteria.<br><br>Finally, hit the 'Add' button to expand the selection to the selected fields, or the 'Replace' button to replace the current selection with fields matching the set criteria."
design_1211 = "Fields marked as required"
design_1212 = "Fields marked as identifiers"
design_1213 = "Add fields matching the set criteria to the already selected fields."
design_1214 = "Replace any already selected fields with fields matching the set criteria."
design_1215 = "This page allows you to build and customize your data collection instruments one field at a time. You may add new fields or edit existing ones. New fields may be added by clicking the Add Field buttons. You can begin editing an existing field by clicking on the <b style='white-space:nowrap'>{0:Icon} Edit</b> icon. If you decide that you do not want to keep a field, you can simply delete it by clicking on the <b style='white-space:nowrap'>{1:Icon} Delete</b> icon. To reorder the fields, simply use the <span style='white-space:nowrap'>{2:Icon} icon</span> to <b>drag and drop</b> a field to a different position within the form below (you may also click this icon to see extended move options). Checking the checkbox in the right upper corner of each field will add the field to the multi-field selection, allowing you to quickly modify several fields at once."
design_1216 = "<b>NOTE:</b> While in development status, all field changes will take effect immediately in real time."
design_1217 = "To copy, move, or delete multiple fields at the same time, hold the Ctrl or Cmd key on your keyboard and click the field to reveal the <b style='white-space:nowrap'><i class='fa-solid fa-wrench icon-online-designer-wrench'></i> Quick</b><b>-modify field(s)</b> feature."
design_1218 = "Modifying the selection resulted in no fields being selected any longer"
design_1219 = "[FIELD {0} IS CURRENTLY LOCATED HERE]"
design_1220 = "<b>Copy</b> Matrix"
design_1221 = "<b>Move</b> Field (inside its matrix group)"
design_1222 = "Copy field(s)?"
design_1223 = "Copy field(s)"
design_1224 = "Do you wish to copy the field(s) '<b>{0}</b>'? The new field(s) will be added immediately after the original field(s)."
design_1225 = "Do you wish to copy the field(s) '<b>{0}</b>'? Please specify where the copied fields will be added:"
design_1226 = "Each new field will be added <b>immediately after its original field</b>."
design_1227 = "The new field(s) will be added after the <b>last selected field</b> (<i>'{0}'</i>)."
design_1228 = "Replace the selection with the newly created fields"
design_1229 = "Copy matrix group?"
design_1230 = "Do you wish to copy the matrix group '<b>{0}</b>'? The new matrix group will be added immediately after the original matrix group."
design_1231 = "Copy matrix group"
design_1232 = "Move matrix field within its matrix group?"
design_1233 = "You may move matrix fields to a location within their matrix group only. Choose from the drop-down below the location to which you wish to move the matrix fields."
design_1234 = "Matrix field(s) to be moved:"
design_1235 = "Move the matrix of fields so that it will be located immediately <b>after</b> the following field:"
design_1236 = "Successfully moved the field(s) to a new location within the matrix group."
design_1237 = "Successfully moved the field(s) to a new location on this data collection instrument."
design_1238 = "-- Insert at the top of this form --"
design_1239 = "-- Insert at the top of the matrix group --"
design_1240 = "Successfully moved the field(s) to the top of form '<b>{0}</b>'."
design_1241 = "Successfully moved the field(s) to a new location on another data collection instrument named {0}."
design_1242 = "Move field(s) to another location?"
design_1243 = "Move matrix of fields to another location?"
design_1244 = "Move the field(s) so that it will be located immediately <b>after</b> the following field:"
design_1245 = "Field(s) to be moved:"
design_1246 = "You may move the field(s) listed below to any location on the current or another data collection instrument. Choose from the drop-down below the location to which you wish to move this field."
design_1247 = "You may move the matrix of fields listed below to any location on the current or another data collection instrument. Choose from the drop-down below the location to which you wish to move this matrix of fields. <i>Note:</i> If the matrix contains a section header, the section header will be moved with the matrix."
design_1248 = "Delete field(s)?"
design_1249 = "Are you sure you wish to delete the field(s) '<b>{0}</b>'?"
design_1250 = "Are you sure you wish to delete the field(s)?"
design_1251 = "Are you sure you wish to delete the matrix group named '<b>{0}</b>'? This will permanently DELETE ALL THE FIELDS in this group. Are you sure?"
design_1252 = "The variable name '<b>{0}</b>' already exists in this project and thus cannot be duplicated. Please enter another value."
design_1253 = "Variable names are recommended to be no more than 26 characters in length because of the risk of them being truncated during analysis in a statistical software package. However, it is allowable to keep it as its current value, if you wish."
design_1254 = "{0} was set as the raw value for <b>{1}</b>"
design_1255 = "'{0}' already exists as a variable name for another field for this matrix group. Please enter another variable name."
design_1256 = "This matrix cannot yet be saved because a variable name is duplicated."
design_1257 = "Branching logic in surveys causes question numbers to display incorrectly when using question auto numbering because it hides the entire question. Thus, the question numbering for this survey has now been automatically set to 'custom numbered' to prevent this issue."
design_1258 = "SUCCESSFULLY MOVED"
design_1259 = "Clear"
design_1260 = "Move to previous selected field"
design_1261 = "Move to next selected field"
design_1262 = "<b>Set</b> custom alignment"
design_1263 = "<b>Edit</b> choices<br><small>Note: The selection must consist of only 'choice'-fields</small>"
design_1264 = "<b>Set</b> text box validation<br><small>Note: This only applies to fields of type 'Text Box'</small>"
design_1265 = "<b>Edit</b> sliders<br><small>Note: The selection must consist of only slider fields</small>"
design_1266 = "<b>Edit</b> field notes"
design_1267 = "Custom survey question number. Click to edit."
design_1268 = "Edit choices?"
design_1269 = "In what way would you like to edit the <b>Choices</b> of the following fields?"
design_1270 = "<b>Copy</b> the choices of the <i>current</i> field (<b>{0}</b>) to all the other selected fields (Note: If a matrix field is targeted, the new choices will be set for the entire matrix group; will not apply to yes/no and true/false fields):"
design_1271 = "The requested field is not a 'choice' field or has no choices."
design_1272 = "<b>Append</b> the following <i>new</i> choices to all selected fields. Note: These will be appended after any existing choices; when codes are duplicated, the previous existing choice will be overwritten; if a matrix field is targeted, this applies to the entire matrix group; will not apply to yes/no and true/false fields):"
design_1273 = "<b>Edit</b> the choices of the <i>current</i> field (<b>{0}</b>)"
design_1274 = "<b>Convert</b> the field types of all selected fields to:"
design_1275 = "Code"
design_1276 = "Label"
design_1277 = "Choices Editor"
design_1278 = "Check to mark rows for manipulation"
design_1279 = "The Choices Editor provides a way to edit choices for checkbox, radio, and dropdown fields. Choices consist of a code (that gets stored in the backend and usually is exported) and a label (that is displayed on data entry forms and surveys). You can add, edit, or delete choices, copy and paste choices from, e.g., Excel, as well as download a CSV of the current choices. The editor will validate the choices."
design_1280 = "Insert a new choice before"
design_1281 = "Insert a new choice after"
design_1282 = "Delete selected choices"
design_1283 = "Showing page {0} of {1}"
design_1284 = "<b>Copy</b> all choices to the clipboard"
design_1285 = "<b>Paste</b> choices<br><small>Note: The pasted choices will be appended to the end of the current choices</small>"
design_1286 = "<b>Move</b> all marked choices <b>up</b> by one position"
design_1287 = "<b>Move</b> all marked choices <b>down</b> by one position"
design_1288 = "<b>Mark</b> all currently selected rows"
design_1289 = "<b>Unmark</b> all currently selected rows"
design_1290 = "<b>Delete</b> all currently marked choices"
design_1291 = "<b>Download</b> a CSV file with all choices"
design_1292 = "Code<br><small>The only acceptable raw values are 1) an integer, or 2) a text string containing only letters, numbers, and underscores</small>"
design_1293 = "Label"
design_1294 = "<b>Get</b> choices from another field in this project"
design_1295 = "INVALID CHOICES"
design_1296 = "Before the choices can be saved, some issues must be resolved. Please review and correct the following errors:"
design_1297 = "Clean up table (removes blank rows and fills missing codes/labels)"
design_1298 = "Invalid code value"
design_1299 = "The code has been changed to '{0}'."
design_1300 = "The only acceptable raw values are 1) an integer, or 2) a text string containing only letters, numbers, and underscores"
design_1301 = "<b>Undo</b> the last change"
design_1302 = "Some code values have been changed to meet the requirements. See browser console (F12) for details."
design_1303 = "There were some issues with the added choices. Some choices may have been incomplete, lacking either code or label, or had codes that already existed. Any fully identical choices have been dropped. Please check the table carefully."
design_1304 = "Filter choices"
design_1305 = "No choices found matching the filter criteria."
design_1306 = "Show:"
design_1307 = "Overlaid"
design_1308 = "On Side"
design_1309 = "Line breaks are not permitted in choice labels. It has been replaced with <code><br></code>."
design_1310 = "Choices from field '<b>{0}</b>' on instrument '<i>{1}</i>'"
design_1311 = "You may choose from one of existing set of choices from other fields in this project. Click the <b>Use</b> button next to each to import that set of choices into the Choice Editor. The choices will be appended to the end of the current list of choices."
design_1312 = "There are some issues with the choices as coded currently. Please carefully review the highlighted cells!"
design_1313 = "Note: You can use the {0:Icon} <b>Clean up</b> tool to automatically fix some of these issues."
design_1314 = "Some choices do not have a code."
design_1315 = "Some choices do not have a label."
design_1316 = "Some identical labels are present with different codes."
design_1317 = "Some codes occur more than once."
design_1318 = "There are duplicate code/label pairs."
design_1319 = "Note: This will not apply to yes/no and true/false fields. Furthermore, matrix fields cannot be converted to drop-down lists."
design_1320 = "Note: Some options may not be available depending on the field type of the current and other selected fields."
design_1321 = "Go to field:"
design_1322 = "Select a field to go to"
design_1323 = "No matching fields found"
design_1324 = "You can quickly move to (and select a field) by using the '{0:LinkStart}Go to field{1:LinkEnd}' widget (keyboard shortcut: {2:ShortcutKey} or {3:ShortcutKey})."
design_1325 = "Moving field: {0}"
design_1326 = "Moving matrix group: {0}"
design_1327 = "<b>Move</b> Section Header"
design_1328 = "Moving section header: {0}"
design_1329 = "Move section header to another location?"
design_1330 = "You may move the section header located before the field listed below to a different location on the current or another data collection instrument. Choose from the drop-down below the location to which you wish to move this section header. It will be inserted before the chosen field. If there already is a section header before the chosen field, the section headers will be merged (the moved section header will be appended to the end of the existing section header). Fields with existing section headers are marked with an asterisk (*)."
design_1331 = "Current location:"
design_1332 = "Move the section header so that it will be located immediately <b>before</b> the following field:"
design_1333 = "Move section header"
design_1334 = "Move field(s)"
design_1335 = "<b>NOTICE:</b> The section header you just moved was merged with another section header that was located before the target field."
design_1336 = "Successfully moved the section header to the new location on this instrument."
design_1337 = "Successfully moved the section header to the new location on a different instrument."
design_1338 = "View the section header on the other data collection instrument"
design_1339 = "The action of reordering the fields could not complete. The form was reloaded to undo the changes. We apologize for the inconvenience."
design_1340 = "Since it is not allowed to have two Section Headers adjacent to each other, the Section Headers were merged instead."
design_1341 = "Yes/No fields"
design_1342 = "True/False fields"
design_1343 = "The field has been copied"
design_1344 = "The fields have been copied"
design_1345 = "The matrix group of fields has been copied"
design_1346 = "SUCCESS"
design_1347 = "As a way to select more fields on this instrument to use with the Quick-modify popup, click the icons below to select different types of fields that might exist on this page, then <b>click the Add or Replace buttons to apply your selections</b> to the Quick-modify popup."
design_1348 = "Consider creating a DD Snapshot (see button at top of page) before making lots of field changes."
design_1349 = "Use the Choices Editor"
design_1350 = "<i>Note:</i> When no Action Tags are listed above, then all Action Tags will be deactivated or reactivated, respectively."
design_1351 = "<b>Note: New drag and drop behavior.</b> This icon (within the button list of a field or section header), in addition to showing the 'Move' dialog when clicked, now serves as the drag handle for elements in the table. To drag a field or section header, keep the mouse button pressed on the icon and start draging. A thick blue line will mark the drop location."
design_1352 = "Dismiss"
design_1353 = "<b>Deactivate</b> the Action Tags listed above in all selected fields"
design_1354 = "<b>Reactivate</b> the Action Tags listed above in all selected fields"
design_1355 = "Validation type:"
design_1356 = "Performs a date calculation by adding or subtracting a specified amount of time from a specified date or datetime field and then provides the result as a date or datetime value - e.g., @CALCDATE([visit_date], 7, 'd'). The first parameter inside the @CALCDATE() function should be a text field with date, datetime, or datetime_seconds validation, in which you may specify (if needed) the event and repeating instance - e.g., @CALCDATE([baseline_event][visit_date], 7, 'd').  Alternatively, the first parameter could be logic, such as an if() statement, that results in a date or datetime field/value.  The second parameter represents the offset number amount that should be added or subtracted. It can be a decimal number or integer. Tip: To subtract (i.e., go backwards in time), use a negative number. The third parameter represents the units of the offset amount, which will be represented by the following options: 'y' (years, 1 year = 365.2425 days), 'M' (months, 1 month = 30.44 days), 'd' (days), 'h' (hours), 'm' (minutes), 's' (seconds). The unit option must be wrapped in quotes or apostrophes. NOTE: Both the source field and the result field must be a text field with date, datetime, or datetime_seconds validation. It is important to realize that a field with @CALCDATE will not be editable on the survey page or data entry form, and the field will function almost exactly like a normal calculated field, in which its value may get updated via a data import, when running Data Quality rule H, or in real-time during normal data entry on a form or survey."
design_1357 = "Field Navigator"
design_1358 = "Scroll to Section Header:"
design_1359 = "Empty – {0}"
design_1360 = "Additionally, you may use 'now' or 'today' as the first parameter for @CALCDATE, but it will use the server time, not the user's current time on their device."
design_1361 = "Field Types video"
design_1362 = "<b>IMPORTANT USER RIGHT INFO:</b> Keep in mind that user privileges are not applied during piping, so even if a user has 'No Access' Data Viewing Rights for the instrument of a piped field,  any user will be able to view the data of the piped field regardless of where the field is being piped. In this way, piping essentially bypasses data viewing privileges. So keep this in mind when designing your project."
designate_forms_04 = "This page may ONLY be used if multiple events have been defined. To be able to utilize this page, you will need to"
designate_forms_05 = "define more 'events'"
designate_forms_06 = "for this project."
designate_forms_07 = "Since you have defined multiple events on the"
designate_forms_09 = "page, you may now select which data collection instruments that you wish to utilize for each event by using the table below. This allows you to enter data on any data collection form multiple times for any given project record. Any and all data collection instruments can thus be used for any event defined."
designate_forms_10 = "Click the"
designate_forms_11 = "Begin Editing"
designate_forms_12 = "button to change the relationships below by designating which forms you wish to utilize for which events. When you are finished making changes, click the"
designate_forms_13 = "Save"
designate_forms_14 = "button to finalize your changes."
designate_forms_18 = "Arm name:"
designate_forms_21 = "Saving..."
designate_forms_22 = "Some of the data collection instruments for events below are being utilized by DTS. If you intend to re-designate any instrument for an event used by DTS, you will additionally need to make these same updates on the DTS Admin page immediately afterward, or else errors will likely occur the next time DTS attempts to pull data from the external system."
designate_forms_23 = "VIDEO: How to designate instruments (3 min)"
designate_forms_24 = "NOTICE: Since this project is in production, only REDCap administrators are allowed to uncheck any instruments that are already designated."
docs_07 = "successfully edited"
docs_08 = "successfully added"
docs_09 = "successfully deleted"
docs_10 = "data entry cancelled - not saved"
docs_11 = "Editing existing"
docs_13 = "Adding new"
docs_19 = "File name:"
docs_22 = "file"
docs_23 = "Name/Label"
docs_24 = "Document"
docs_25 = "Upload Date"
docs_26 = "Document Filename"
docs_27 = "Document Size (MB)"
docs_28 = "The File Repository allows users to store, organize, and share files used for this project. Folders and subfolders can be created, and there is no limit  to number of folders that can be created or the number of files that can be stored within them. If you are using Data Access Groups or user roles in the project,  you may limit access to a new folder so that it is DAG-restricted and/or role-restricted.  All deleted files will go to the Recycle Bin where they can be restored/undeleted for up to 30 days, after which they will be permanently deleted."
docs_29 = "User Files"
docs_30 = "Data Export Files"
docs_31 = "Upload New File"
docs_32 = "Editing File"
docs_33 = "To upload a new file to the repository, in the fields below specify the file on your computer and provide a name/label for the file. Then click the"
docs_34 = "button."
docs_35 = "There are no data export files to download"
docs_36 = "Filter by:"
docs_37 = "Last Export"
docs_38 = "All Exports/Types"
docs_39 = "Displaying files (by most recent):"
docs_40 = "Time exported:"
docs_41 = "Exported by:"
docs_42 = "No files have been uploaded yet"
docs_43 = "Filter by file type:"
docs_44 = "ALL"
docs_45 = "Action"
docs_46 = "DELETE FILE? Are you sure you wish to delete this file?"
docs_47 = "File did not upload! "
docs_49 = "There was an error uploading the file."
docs_50 = "Since Data Access Groups have been created in this project, please be aware that any files manually uploaded here (i.e. files listed under User Files) will be available to ALL project users, regardless of whether they or you have been assigned to a Data Access Group or not."
docs_51 = "Since you have been assigned to a Data Access Group, you are only able to download data export files from users from your group."
docs_52 = "Syntax & Data"
docs_53 = "Send file?"
docs_54 = "Send data file"
docs_55 = "Send syntax file"
docs_56 = "Date uploaded:"
docs_57 = "File size:"
docs_58 = "Download"
docs_61 = "Email this document securely"
docs_63 = "The file may have been too large."
docs_64 = "Because you do not have full Data Export privileges for this project, you will not be able to view any data export files here that have been saved from previous exports. Another user will have to grant you full Data Export rights in order to do so."
docs_65 = "You may have exceeded the maximum file upload size for the File Repository, which is"
docs_66 = "Since you belong to a Data Access Group, you are only able to download files for records assigned to your group."
docs_67 = "You may not download this file since you do not have *Full Data Set* Data Export privileges."
docs_68 = "all records"
docs_69 = "only e-Consent files"
docs_70 = "all files"
docs_71 = "Download all (zip)"
docs_72 = "Delete File"
docs_73 = "PDF Export (all records)"
docs_74 = "uploaded"
docs_75 = "Click to download"
docs_76 = "File"
docs_77 = "Name"
docs_78 = "Size"
docs_79 = "Time Uploaded"
docs_80 = "Comments"
docs_81 = "Upload Error!"
docs_82 = "File did not upload:"
docs_83 = "Drag and drop files here to upload"
docs_84 = "ERROR: You attempted to upload"
docs_85 = "files. You may only upload up to 10 files at a time. Please try uploading fewer files in a batch."
docs_86 = "Rename file"
docs_87 = "Change the filename of the following file:"
docs_88 = "New filename:"
docs_89 = "NO ACCESS: The current folder is associated with a Data Access Group or User Role to which you do not belong. You cannot access the files in this folder."
docs_90 = "Since Data Access Groups exist in this project, please be aware that any files uploaded here will be available to ALL project users unless the files have been uploaded into a DAG-restricted folder."
docs_91 = "DAG-Restricted:"
docs_92 = "All Files"
docs_93 = "No files or subfolders exist in this folder."
docs_94 = "Search in current folder"
docs_95 = "Create folder"
docs_96 = "Click to view record"
docs_97 = "Delete folder?"
docs_98 = "DELETE FOLDER? Are you sure you wish to delete this empty folder?"
docs_99 = "Folder:"
docs_100 = "Sorry, but the folder below cannot be deleted because it still has files in it. You must first <u>remove all files from the folder</u> before you are able to delete it."
docs_101 = "Cannot delete folder!"
docs_102 = "Rename folder"
docs_103 = "New folder name:"
docs_104 = "Change the name of the following folder:"
docs_105 = "Time of Export"
docs_106 = "You may create a new folder in the current directory. Once the folder has been created, you may navigate into it and upload files there."
docs_107 = "New folder name:"
docs_1078 = "ERROR: The folder name"
docs_1079 = "could not be created because a folder with that same name already exists in this directory. You should create a new folder with a different name instead."
docs_1080 = "ERROR: You may not rename this folder to "
docs_1081 = "because a folder with that same name already exists in this directory. You should rename it to a different name instead."
docs_1082 = "Limit access by Data Access Group? (optional)"
docs_1083 = "users in all DAGs"
docs_1084 = "Make folder accessible to"
docs_1085 = "Role-Restricted:"
docs_1086 = "Limit access by User Role? (optional)"
docs_1087 = "users in all roles"
docs_1088 = "Restore deleted file?"
docs_1089 = "Restore"
docs_1090 = "RESTORE FILE? Are you sure you wish to restore this file?"
docs_1091 = "The file was successfully restored and is now viewable and downloadable in its original folder location prior to being deleted."
docs_1092 = "Recycle Bin"
docs_1093 = "NOTE: If this file existed in a folder which was also subsequently deleted, then restoring this file <u>will also restore the folder in which it was located</u> (and also any parent folders)."
docs_1094 = "Time Deleted"
docs_1095 = "Time until permanent deletion from Recycle Bin"
docs_1096 = "Restore file"
docs_1097 = "Deleted by"
docs_1098 = "Restored by"
docs_1099 = "Share the file"
docs_1100 = "Preview:"
docs_1101 = "Preview of file is not available"
docs_1102 = "Copied!"
docs_1103 = "Share a public link to view the file"
docs_1104 = "View file"
docs_1105 = "Copy link"
docs_1106 = "You may share this file with others simply by providing them with the public link, which will take them to a landing page where they can download the file or view a preview of the file (if an image or PDF). Or alternatively, you may use the Send-It feature to email one or more recipients a password-protected download link."
docs_1107 = "Send the file securely using Send-It"
docs_1108 = "Send-It via email"
docs_1109 = "A password-protected download link can be emailed to one or more recipients using the REDCap Send-It feature. You may optionally choose to receive a confirmation once the file has been downloaded by the recipient(s) and also set the download link to expire after a set number of days."
docs_1110 = "You may copy the public link below to share it with others. Please note that anyone in possession of the public link will be able to freely view and download the file."
docs_1111 = "You can not upload the file because doing so will exceed the project storage limit of"
docs_1112 = "You may consider deleting some files to free up storage space."
docs_1113 = "You can not restore the file because doing so will exceed the project storage limit of"
docs_1114 = "File Repository: Users are able to share files via public links"
docs_1115 = "If enabled, users will be able to share files in the File Repository with others by generating a public link that is unique to the file. Anyone in possession of the link will be able to access and download the file at any time."
docs_1116 = "You may share this file with others simply by using the Send-It feature to email one or more recipients a password-protected download link."
docs_1117 = "Sorry, but folders can't be deleted this way. They must instead be deleted individually by clicking the X on the right-hand side of each folder. We have unchecked all folders automatically just now if you still wish to delete multiple files or else if you wish to download or move multiple files and/or folders."
docs_1118 = "DELETE MULTIPLE FILES?"
docs_1119 = "Are you sure you wish to delete all the files currently selected on the page? Total files to be deleted:"
docs_1120 = "One or more files must first be selected. Try again."
docs_1121 = "used"
docs_1122 = "The total amount of file storage being utilized (includes only user-uploaded files and excludes files in the starred folders, such as the Recycle Bin, Data Export Files, and e-Consent PDFs)"
docs_1123 = "The files were successfully deleted!"
docs_1124 = "Uploaded by"
docs_1125 = "Sorry, but the filename you entered is taken. Another file in the same folder already has that name. You must try renaming the file to a different filename that is not yet taken."
docs_1126 = "filename already exists"
docs_1127 = "One or more files/folders must first be selected. Try again."
docs_1128 = "MOVE FILES/FOLDERS?"
docs_1129 = "Move to selected location"
docs_1130 = "Want to move the files/folders to a different folder location? Select a folder location in the drop-down below to which you wish to move the selected files and folders."
docs_1131 = "[Top-level directory]"
docs_1132 = "Move files/folders to"
docs_1133 = "The files/folders were successfully moved!"
docs_1134 = "[CURRENT LOCATION]"
docs_1135 = "ERROR: The file cannot be uploaded."
docs_1136 = "ERROR: The file cannot be uploaded because its file type is not permitted."
docs_1137 = "Restricted file types for uploaded files"
docs_1138 = "Provide a list of all disallowed file types/extensions (e.g., exe) in order to prevent users from uploading files of these types into REDCap (often for security purposes). This setting will be applied to all places throughout REDCap where users are allowed to upload files. Please delimit each file type using a comma, semi-colon, or line break. Note: You do not need to provide different case sensitive variations for each file type."
docs_1139 = "Edit comment"
docs_1141 = "New comment:"
docs_1142 = "If you wish to modify the comment for the file"
docs_1143 = ", edit the text below and click Save."
docs_1144 = "Permanently delete file? (admins only)"
docs_1145 = "NOTE: This will permanently delete the file instantly. Only REDCap administrators are allowed to do this."
docs_1146 = "File was successfully deleted!"
docs_1147 = "Please do not leave the page while files are uploading"
docs_1148 = "NOTICE: Please keep in mind that if this file is deleted, any links used for downloading this file (such as in a field label, project dashboard, survey invitations, etc.), will become dead links, thus preventing anyone from downloading the file again."
docs_1149 = "Files stored here in the 'Miscellaneous File Attachments' folder are auto-added when users upload file attachments into the rich text editor in this project, such as when composing a survey invitation, adding a field label, or creating a project dashboard, among other things. <b>Please be careful not to delete any files here unless you are absolutely sure that the file is no longer being used.</b> Deleting a file here that is used elsewhere in the project will cause the file's download link to no longer function and become a dead link."
docs_1150 = "I understand"
docs_1151 = "Source:"
docs_1152 = "ERROR: Cannot change file extension!"
docs_1153 = "Sorry, but you are not allowed to change the file extension of the file. You cannot change it to have the following extension:"
docs_1154 = "Download file list"
draft_mode_02 = "The drafted changes that you requested for the production project titled"
draft_mode_03 = "have been approved. The changes have now fully taken effect on the project."
draft_mode_04 = "Processed by"
draft_mode_05 = "(REDCap Administrator)"
draft_mode_06 = "The email listed below did not send to"
draft_mode_07 = "Project Changes were Approved"
draft_mode_08 = "Only REDCap Administrators may use this page!"
draft_mode_09 = "Project Changes Committed / User Notified"
draft_mode_10 = "The changes have now been officially committed to the project, and a notification email has been sent to"
draft_mode_11 = "who requested the project changes."
draft_mode_12 = "Project Changes Rejected / User Notified"
draft_mode_13 = "The changes were NOT committed to the project, and a notification email regarding the rejection of these changes has been sent to"
draft_mode_14 = "Project Changes Removed / User Notified"
draft_mode_15 = "The changes were NOT committed to the project but were removed. The project has been returned back as it was before entering Draft Mode, and a notification email regarding the removal of the drafted changes has been sent to"
draft_mode_16 = "Project changes were Rejected"
draft_mode_17 = "have been REJECTED. This may have occurred for a number of reasons, such as if the changes would cause loss of previously collected data. The project has been returned back to Draft Mode where more changes can be made and then submitted for approval again."
draft_mode_18 = "If you have any questions regarding this, please contact"
draft_mode_19 = "Project changes were REMOVED"
draft_mode_20 = "have been DELETED, and the project was reset back to before it entered Draft Mode. All changes to fields made in Draft Mode have been removed. This may have occurred for a number of reasons, such as if the changes would cause loss of previously collected data. If you wish to make changes to the project, you may begin again by putting the project back into Draft Mode."
draft_mode_21 = "Your assistance is required to review the drafted changes for the production project titled"
draft_mode_22 = "Click the link below to navigate to the page for reviewing and approving the drafted changes for this project."
draft_mode_24 = "These changes were requested by"
draft_mode_28 = "Review & approve changes for"
draft_mode_29 = "Review & Approve Project Changes"
draft_mode_31 = "Please note: If you added new instruments to your project, the default Data Viewing Rights and Data Export Rights for new instruments will be 'No Access' for all users/roles. If you wish to change that, you will need to go to the User Rights application and make that change for each user/role."
draft_mode_32 = "Please note: If you added new instruments to your project, the default Data Viewing Rights and Data Export Rights for new instruments will be 'View & Edit/Full Data Set' for all users/roles. If you wish to change that, you will need to go to the User Rights application and make that change for each user/role."
draft_mode_33 = "Please note: If you added new instruments to your project, the default Data Viewing Rights for new instruments will be 'View & Edit/Full Data Set' for all users/roles, and the default Data Export Rightsfor new instruments will be 'De-Identified' for all users/roles. If you wish to change that, you will need to go to the User Rights application and make that change for each user/role."
edit_project_02 = "Your changes have been saved!"
edit_project_07 = "Move to Production status"
edit_project_08 = "Move the project to production status so that real data may be collected."
edit_project_09 = "Move Project To Production Status?"
edit_project_11 = "Bring the project back online so that data collection may continue."
edit_project_17 = "Since only REDCap administrators can move a project to production, clicking the button below will send a request to a REDCap admin, who will move it to production status for you. An email will be sent to your address"
edit_project_18 = "when this has been done."
edit_project_19 = "Request Admin to Move to Production Status?"
edit_project_20 = "Email to REDCap administrator could not be sent."
edit_project_29 = "Actions:"
edit_project_31 = "All data has now been deleted from the project!"
edit_project_36 = "Erase All Data?"
edit_project_37 = "<b>Are you sure you wish to erase all the data in this project?</b> This will delete all data (including any survey responses), calendar events, documents uploaded onto forms/surveys, and all data export files stored in the File Repository. NOTE: File attachments for fields/questions will NOT be deleted, nor will survey logos, survey participants in the Participant List, or files uploaded by users in the File Repository."
edit_project_38 = "Modify Project Settings"
edit_project_41 = "Require a 'reason' when making changes to existing records?"
edit_project_43 = "Use auto-numbering for naming new project records?"
edit_project_44 = "This option will remove the ability for users to name new records manually and will instead provide a link that will auto-generate a new unique record name, which will be numerical and will increment from the highest numerical record value in the project. If no records exist, it will begin with '1'."
edit_project_47 = "TYPE"
edit_project_48 = "DELETE"
edit_project_49 = "BELOW"
edit_project_50 = "You may completely remove this project, in which all its data will be permanently deleted also."
edit_project_51 = "Deleting the project named"
edit_project_52 = "What is the REDCap API?"
edit_project_53 = "Enable the Data History popup for all data collection instruments?"
edit_project_54 = "If enabled, an icon will appear next to every field on a data collection instrument. When the icon is clicked, the history of all data entered into that field for that record will be listed chronologically and will display all previous values, who changed the value at each instance, and the time it was changed."
edit_project_55 = "Have you checked the"
edit_project_56 = "page to ensure all identifier fields have been tagged?"
edit_project_58 = "Project status:"
edit_project_60 = "-- select field --"
edit_project_61 = "Designate a Secondary Unique Field"
edit_project_63 = "FIELD CONTAINS DUPLICATE VALUES!"
edit_project_64 = "This field may NOT be selected as the secondary unique field because two or more records already contain duplicate values for the field. No values of this field can duplicate across records. You will have to choose another field or remove any of these duplications first."
edit_project_66 = "Set a Custom Record Label"
edit_project_67 = "You may append other data and/or static text to any record name (e.g., Study ID) as the record is displayed on your data collection instruments, such as inside the drop-down lists when choosing a record and at the top of the page after being selected. Simply provide the text you wish to display below, and place any variable names inside square brackets [ ], after which the data collected for those variables for that record will replace the variable in the text."
edit_project_68 = "Custom Record Label:"
edit_project_69 = "Example: if ([last_name], [first_name]) where entered, then for record '102' it would display '102 (Doe, Jon)'."
edit_project_71 = "-- select field to order records by --"
edit_project_72 = "Order the records by another field"
edit_project_73 = "The default setup is that all records are ordered by their record name (e.g., Study ID) when displayed in the drop-down lists on your data collection instruments, but you may alternatively order the drop-down lists by the values of another field in the project (e.g., last name), if desired. If you wish to order the records by another field, select the field below."
edit_project_77 = "(Administrators Only)"
edit_project_78 = "This can only be done while the project is still in development or you can send a request to delete the project while in production to a REDCap administrator."
edit_project_79 = "Move back to Development status"
edit_project_80 = "Moved to production too soon? You may move the project back to development status, if needed."
edit_project_81 = "NOTE: Since the project is currently in Draft Mode, all drafted changes will be discarded when moving back to development. So if you do not want to lose the current drafted changes, then first finish making changes to then fields in Draft Mode and then have them submitted for approval before continuing here."
edit_project_82 = "Are you sure you wish to move the project back to development status?"
edit_project_83 = "WARNING: Since the project is currently in Draft Mode, all drafted changes will be discarded. Do you still wish to proceed?"
edit_project_84 = "Cannot move project back to development while using DTS!"
edit_project_85 = "Because of dependency issues with the REDCap Data Transfer Services (DTS), in which projects must be in production in order to be utilized by DTS, this project cannot be moved back to development status."
edit_project_86 = "<b>NOTE:</b> Since multiple events are defined for this project (i.e. it is longitudinal), the data will only be pulled from the first Event of the currently selected Arm."
edit_project_87 = "The API token below is <b>ONLY for you</b> and will work <b>ONLY with this project</b>. This token allows special access to REDCap data and <b>should NOT be shared with others</b>. If you think your token has been compromised, then please contact your REDCap administrator immediately <i>AND</i> either delete or regenerate your token by using the buttons below."
edit_project_88 = "Use the button below to request an API token for this project from your REDCap administrator. You will need a different token for each project you would like to access. Please note that your REDCap administrator is emailed every time a token is requested."
edit_project_89 = "Your API token request failed!"
edit_project_90 = "Your API token request was successfully sent to a REDCap administrator. You will receive an email notification when they have approved your request. Thank you!"
edit_project_91 = "requests an API token"
edit_project_92 = "for the project named"
edit_project_93 = "Click here to approve the API token request"
edit_project_94 = "Event names for"
edit_project_96 = "Delete your API token for this project"
edit_project_97 = "Generate a new API token for this project"
edit_project_98 = "API token deletion failed!"
edit_project_99 = "API token deletion succeeded!"
edit_project_100 = "API token regeneration failed!"
edit_project_101 = "API token regeneration succeeded! You will now see your new token displayed on this page."
edit_project_106 = "Erase all API tokens"
edit_project_107 = "You may erase all API tokens for this project. No one will be able to access this project via the API until new tokens are created."
edit_project_108 = "Current number of tokens"
edit_project_109 = "Erase All API Tokens?"
edit_project_110 = "<b>Are you sure you wish to erase all API tokens for this project?</b> No one will be able to access this project via the API until new tokens are created."
edit_project_111 = "Are you sure you wish to delete your API token?"
edit_project_112 = "<b>Are you sure you want to delete your API token for this project?</b> This will remove your API access to this project and you will need to request a new API token in order to reinstate access."
edit_project_113 = "Are you sure you wish to regenerate your API token?"
edit_project_114 = "<b>Are you sure you want to regenerate your API token for this project?</b> Your existing API token will be deactivated and you will need to use the new token for API access."
edit_project_115 = "The following user(s) have API tokens for this project:"
edit_project_116 = "Delete token"
edit_project_117 = "Finished using the API for this project? If so, please delete your token for security reasons."
edit_project_118 = "Regenerate token"
edit_project_119 = "Think someone else knows your token? If so, please regenerate your token for security reasons."
edit_project_120 = "Completed steps"
edit_project_122 = "Data Entry Trigger"
edit_project_124 = "URL of website:"
edit_project_125 = "Example:"
edit_project_126 = "Sorry, but the web address you entered does not appear to be a proper URL (e.g., http://google.com). Please fix it and try again."
edit_project_127 = "View more details"
edit_project_128 = "In the HTTP Post request, the following parameters will be sent by REDCap in order to provide a context for the record that has just been created/modified:"
edit_project_129 = "The unique ID number of the REDCap project (i.e. the 'pid' value found in the URL when accessing the project in REDCap)."
edit_project_130 = "The unique name of the current data collection instrument (all your project's unique instrument names can be found in column B in the data dictionary)."
edit_project_131 = "The name of the record being created or modified, which is the record's value for the project's first field"
edit_project_132 = "The unique event name of the event for which the record was modified (for longitudinal projects only)."
edit_project_133 = "The unique group name of the Data Access Group to which the record belongs (if the record belongs to a group)."
edit_project_134 = "The status of the record for this particular data collection instrument, in which the value will be 0, 1, or 2. For data entry forms, 0=Incomplete, 1=Unverified, 2=Complete. For surveys, 0=partial survey response and 2=completed survey response. This parameter's name will be the variable name of this particular instrument's status field, which is the name of the instrument + '_complete'."
edit_project_135 = "If the names of your records (i.e. the values of your first field) are considered identifiers (e.g., SSN, MRN, name), for security's sake it is highly recommended that you use an encrypted connection (i.e. SSL/HTTPS) for the URL you provide for the Data Entry Trigger."
edit_project_136 = "Enable the Data Entry Trigger for all projects?"
edit_project_137 = "If enabled here, users can set this up in the Additional Customizations pop-up on their project's Project Setup page."
edit_project_138 = "Test"
edit_project_139 = "If you wish to permanently delete this REDCap project, type the word"
edit_project_140 = "in the box below and click the button. Please ensure that this is truly what you wish to do before continuing here."
edit_project_142 = "REDCap API documentation"
edit_project_143 = "NOTE: This feature does not work for longitudinal projects (such as this one)."
edit_project_144 = "The base web address to REDCap (URL of REDCap's home page)."
edit_project_145 = "The base web address to the current REDCap project (URL of its Project Home page)."
edit_project_147 = "Erase all data"
edit_project_149 = "Remove unused Clinical Data Pull data"
edit_project_151 = "Are you sure you wish to remove all the unused cached data from the external source system?"
edit_project_154 = "All the unused Clinical Data Pull data from the external source system has been successfully removed."
edit_project_155 = "NOTE: Since the project is not accessible, this popup window cannot be closed. However, you may click the button below to return to the My Projects page."
edit_project_156 = "Settings displayed to Administrators only:"
edit_project_160 = "The Data Entry Trigger is an advanced feature. It provides a way for REDCap to trigger a call to a remote web address (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 in this project (it is *not* triggered by data imports - including API imports and Mobile App imports - but only by normal data entry on surveys and data entry forms). Its main purpose is for notifying other remote systems outside REDCap at the very moment a record/response is created or modified, whose purpose may be to trigger some kind of action by the remote website, such as making a call to the REDCap API."
edit_project_161 = "Copy or Back Up the Project"
edit_project_162 = "Back Up the Project"
edit_project_166 = "YES, Move to Production Status"
edit_project_167 = "Make an exact duplicate of this project."
edit_project_168 = "All project fields will be copied over, and you will be prompted to set the title and info for the new project. You may choose to copy or not copy the existing data in the current project to the new one."
edit_project_171 = "Sorry, but since you do not have any data export permissions, you will not be able to download any data from this project, but only the metadata."
edit_project_172 = "The entire project (all instruments, fields, and project attributes) can be downloaded as a single XML file (CDISC ODM format). This XML file can be used to create a clone of the project on this REDCap server or on another REDCap server (it can be uploaded on the Create New Project page). Because it is in CDISC ODM format, it can also be used to import the project into another ODM-compatible system."
edit_project_173 = "NOTE: The exported XML file does *not* contain the project's logging history (audit trail), but if you wish to obtain it, you may freely download it any time at the top of the Logging page."
edit_project_174 = "Keep ALL data saved so far."
edit_project_175 = "Copy the Project"
edit_project_176 = "Keep existing data or delete?"
edit_project_178 = "Are you sure you wish to leave the DEVELOPMENT stage? If you proceed, the project will be moved to PRODUCTION status so that real data may be collected. If you select the 'Delete ALL data' option below, all current collected data, calendar events, and uploaded documents will be deleted, otherwise all will remain untouched as the project is moved to production."
edit_project_179 = "Request pending"
edit_project_180 = "Once in production, you will not be able to edit the project fields in real time anymore. However, you can make edits in Draft Mode, which will be auto-approved or else might need to be approved by a REDCap administrator before taking effect."
edit_project_181 = "The repeat instance number of the current instance of a repeating event OR repeating instrument. Note: This parameter is only sent in the request if the project contains repeating events/instruments *and* is currently saving a repeating event/instrument."
edit_project_182 = "The unique instrument name of the current repeating instrument being saved. Note: This parameter is only sent in the request if the project contains repeating instruments *and* is currently saving a repeating instrument. Also, this parameter will not be sent for repeating events (as opposed to repeating instruments)."
edit_project_183 = "Use the button below to generate an API token for this project. You will need a different token for each project you would like to access."
edit_project_184 = "Require users to enter a reason (200 character max) in a text box when making any data changes to an already existing record on a data collection instrument. The prompt is triggered when clicking the Save button on the page. Any 'reasons' entered can then be viewed anytime afterward on the Logging page. Note: If the instrument does not yet have any data collected for it, then a reason will not be required (this includes importing data via the Data Import Tool). This feature is only triggered when adding, editing, or deleting data for an instrument that contains previously-collected data for one or more fields on the instrument."
edit_project_185 = "Explore the"
edit_project_186 = "Learn how to use"
edit_project_187 = "<b>NOTE:</b> Since multiple events are defined for this project (i.e. it is longitudinal), <b>you must prepend the unique event name to the variable name</b> in brackets - e.g., [baseline_arm_1][last_name]. Smart Variables can also be used here - e.g., [first-event-name][last_name]."
edit_project_189 = "ERROR: Request not valid"
edit_project_190 = "NOTICE TO ADMINISTRATOR: The current sponsor request is no longer valid, and thus cannot be processed. This means it may have been deleted or may have already been processed by an administrator."
edit_project_191 = "Display the value of the Secondary Unique Field next to each record name displayed?"
edit_project_192 = "Display the field label of the Secondary Unique Field when displaying the value?"
edit_project_193 = "NOTICE TO ADMINISTRATOR: The current project request (i.e., to delete the project) is no longer valid, and thus cannot be processed. This means the request may have been deleted or cancelled by an administrator or by the requesting user."
edit_project_194 = "Please be aware that if you uncheck any of the instruments or events that have currently been set as a repeating instrument or repeating event, it could cause a lot of already-collected data to become orphaned indefinitely, which means the data will no longer be accessible through the user interface and also will no longer be seen in reports or data exports. However, if data is orphaned by accident in this way, then all the data can easily be restored/unorphaned by setting the repeating instrument/event settings back to the way they previously were."
edit_project_195 = "Move the project to Analysis/Cleanup status if data collection is complete. This will disable most project functionality, although all collected data will remain intact. Once in Analysis/Cleanup status, the project can be moved back to production status at any time."
edit_project_196 = "Move Project To Analysis/Cleanup Status?"
edit_project_197 = "Do you wish to set the status of the project to ANALYSIS/CLEANUP?"
edit_project_198 = "When utilizing the Clinical Data Pull, data from the external source system is encrypted and cached to be used during the adjudication process. Much of the data is never used, and once the data has been adjudicated, it is often never seen again by users in the project. For some compliance purposes and general best practices, it is recommended that all the unused cached source data be removed after the project is done collecting data and has been moved to Analysis/Cleanup status. You may click the button to the left to purge all the data from the source system that has been cached in this REDCap project."
edit_project_199 = "NOTICE: You cannot remove all the unused Clinical Data Pull data until the project is in Analysis/Cleanup status. Please move it to Analysis/Cleanup status and then try again. Thank you!"
edit_project_200 = "NOTICE: Project must first be placed into ANALYSIS/CLEANUP status!"
edit_project_201 = "Move to Analysis/Cleanup status"
edit_project_202 = "YES, Move to Analysis/Cleanup Status"
edit_project_203 = "Mark project as Completed"
edit_project_204 = "If you are finished with a project and wish to make it completely inaccessible, you may mark the project as 'Completed'. Doing so will take it offline and remove it from everyone's project list, after which it can only be seen again by clicking the <i>Show Completed Projects</i> link at the bottom of the <i>My Projects</i> page."
edit_project_205 = "Move back to Production status"
edit_project_206 = "Are you sure you wish to mark this project as 'Completed'? This will take the project offline, and you and other users will no longer be able to access it. The project and its data will remain in the system and cannot be modified. Only a REDCap administrator may return the project back to its previous status."
edit_project_207 = "Completed"
edit_project_208 = "Show Completed Projects"
edit_project_209 = "Hide Completed Projects"
edit_project_210 = "Project Status Management"
edit_project_211 = "Data Management"
edit_project_212 = "Once marked as Completed, no one in the project (except for REDCap administrators) can access the project, and only administrators may undo the Completion and return it back to an accessible state for all project users. Marking a project as Completed is typically only done when you are sure that no one needs to access the project anymore, and you want to ensure that the project and its data remain intact for a certain amount of time."
edit_project_216 = "You may erase all currently collected data in the project (including any survey responses), calendar events, documents uploaded onto forms/surveys, and all archived data export files stored in the File Repository, and any logged events that pertain to data collection."
edit_project_217 = "Delete ALL data in the project (including any survey responses), calendar events, documents uploaded onto forms/surveys, and all archived data export files stored in the File Repository, and any logged events that pertain to data collection."
edit_project_218 = "3) Optional custom logo to display in the email header and page header seen by the recipient. (Will be displayed above the custom text.)"
edit_project_219 = "Preview (displaying here at max 400 pixel width):"
edit_project_221 = "Upload custom logo:"
edit_project_222 = "The username of the REDCap user that is triggering the Data Entry Trigger. Note: If it is triggered by a survey page (as opposed to a data entry form), then the username that will be reported will be '{0}'."
edit_project_223 = "NOTICE TO ADMINISTRATOR: The current project request is no longer valid, and thus cannot be processed. This means the request may have been deleted or cancelled by an administrator or by the requesting user."
edit_project_224 = "This project currently contains <span style=\"color: red;\"><b>{0}</b> record(s)</span>."
edit_project_225 = "(Administrators only) If there appear to be records missing from the project or if some pages are not getting recent updates to data (in reports, record status dashboards, or elsewhere),  then the Record List Cache (a secondary list of all record names) or Rapid Retrieval (a page-level caching mechanism) might be out of sync and thus might need to be cleared.  Clearing these will cause the Record List Cache to regenerate and will clear all page-level caches in the project. (NOTE: This is normally not needed.)"
edit_project_226 = "The Record List Cache and Rapid Retrieval have been successfully cleared."
edit_project_227 = "Clear all record & page caches"
edit_project_228 = "NOTE: The new project will *not* contain the project's logging history (audit trail), but if you wish to obtain it, you may freely download it any time at the top of the Logging page."
email_admin_01 = "Request to Move Project to Production"
email_admin_03 = "The REDCap user"
email_admin_04 = "has requested that the following project be moved to production status:"
email_admin_05 = "To approve this request, follow the link below:"
email_admin_06 = "Approve request to MOVE TO PRODUCTION STATUS"
email_admin_07 = "Approved: Project Moved to Production"
email_admin_08 = "The following REDCap project has now been moved to production status, as requested:"
email_admin_09 = "Access your REDCap project"
email_admin_10 = "Request to Create New Project"
email_admin_11 = "has requested that the following project be created:"
email_admin_12 = "Approve request to CREATE NEW PROJECT"
email_admin_13 = "Request to Copy Project"
email_admin_14 = "has requested that the following project be copied:"
email_admin_15 = "Approve request to COPY PROJECT"
email_admin_17 = "has requested to delete the following project:"
email_admin_18 = "Approve request to DELETE PROJECT"
email_admin_19 = "Request to Delete Project: Completed"
email_admin_20 = "Your request to have the following REDCap project deleted has been completed successfully:"
email_admin_21 = "has requested to approve the following Data Mart Revision"
email_admin_22 = "Approve request to create NEW CLINICAL DATA MART REVISION"
email_admin_23 = "User CANCELLED Request to Move Project to Production"
email_admin_24 = "User CANCELLED Request to Delete Project"
email_admin_25 = "has CANCELLED their pending request for the following project to be moved to production status:"
email_admin_26 = "has CANCELLED their pending request for the following project to be deleted:"
email_users_01 = "Please enter both a Subject and Message for the email."
email_users_02 = "Email Users"
email_users_03 = "To email any of your users listed below, you may compose the email message and check the users that you wish to receive the email."
email_users_09 = "All users selected from User List below"
email_users_10 = "Subject"
email_users_12 = "Name"
email_users_15 = "User List"
email_users_17 = "Check All"
email_users_18 = "Uncheck All"
email_users_19 = "Active Users"
email_users_20 = "Non-Active Users"
email_users_24 = "Past Month"
email_users_25 = "Past 6 Months"
email_users_26 = "Past 12 Months"
email_users_27 = "Past 3 Months"
email_users_29 = "Note: Any users that have their account suspended will not be able to be emailed."
email_users_30 = "Active = Has logged in or used the API"
email_users_31 = "Table-based Users"
email_users_32 = "LDAP Users"
email_users_34 = "Currently Logged-in Users"
email_users_35 = "The code was successfully emailed to {0}"
email_users_36 = "REDCap Secure Messaging"
email_users_37 = "{0} has sent you a secure email message."
email_users_38 = "Read the message"
email_users_39 = "Learn about messages protected by REDCap."
email_users_40 = "Quick security check before viewing your email"
email_users_41 = "ERROR: Incorrect code was entered. Please try again!"
email_users_42 = "Send code to this address"
email_users_43 = "Submit code"
email_users_44 = "This is a public computer"
email_users_45 = "After receiving the code via email, enter it below."
email_users_46 = "Because you have not visited this page before or in a long time, we need to send you <u>a new email containing a security code</u> that will be used to verify your identify here. <b>Please select your email address from the list of all recipients below, and click the 'Send code' button</b>, which will send you a new email with a code. Then return to your inbox to retrieve that security code, and enter it below."
email_users_47 = "Because you have not visited this page before or in a long time, we just sent you <u>a new email containing a security code</u> that will be used to verify your identify here. Please return to your inbox right now to retrieve that security code, and then enter it below. Thanks!"
email_users_48 = "{0} files"
email_users_49 = "{0} file"
email_users_50 = "Check your inbox!"
email_users_51 = "Consider enabling the Protected Email Mode"
email_users_52 = "The Protected Email Mode prevents identifying data (PHI/PII) from being sent in outgoing emails for alerts, survey invitations, and survey confirmation emails. You can learn more about the Protected Email Mode in the Additional Customizations popup on this page, which is where it can be enabled for this project. (This feature is being suggested because it has detected that data from Identifier fields are being piped into the body of one or more of your alerts, survey invitations, or survey confirmation emails.)"
email_users_53 = "Email Logging"
email_users_55 = "Search all outgoing emails for this project"
email_users_56 = "Search emails"
email_users_57 = "Subject, body, sender, and recipient"
email_users_58 = "Subject and body"
email_users_59 = "Subject only"
email_users_60 = "Body only"
email_users_61 = "Sender and recipient"
email_users_62 = "Sender only"
email_users_63 = "Recipient only"
email_users_64 = "Click to view entire message"
email_users_65 = "No emails found"
email_users_66 = "Time sent"
email_users_67 = "Top"
email_users_68 = "matching results"
email_users_69 = "Search within a window of time from"
email_users_70 = "Summary email content and attributes"
email_users_71 = "(click icon on left to view full email)"
email_users_72 = "View msg"
email_users_73 = "Search for"
email_users_74 = "Pertaining to a specific record:"
email_users_78 = "Survey Invitations (only ASIs)"
email_users_79 = "Survey Invitations (only manually sent/scheduled)"
email_users_81 = "-- all types --"
email_users_82 = "(Unchecking this checkbox will store a cookie on this device.)"
email_users_83 = "Enable the Email Logging page in all projects for users with User Rights privileges in the project."
email_users_84 = "If enabled, users with User Rights privileges in a project will be able to opt-in to using the Email Logging page, which will allow them to search and access all outgoing emails for the project. This can be useful for troubleshooting potential issues related to emails. If this feature is disabled here, all outgoing emails will still be stored in the backend database, but they will not be accessible to users via the user interface."
email_users_85 = "NOTICE: You must first agree to the disclaimer before you may access and utilize this page."
email_users_86 = "Must agree to disclaimer before accessing page"
email_users_87 = "Before viewing and accessing this page, you must first agree that you understand the following important information and conditions. This page is only accessible by users having User Rights privileges in this project. The Email Logging feature allows users to search and view *all* outgoing emails related to this project, and this includes being able to view all aspects of any given email (i.e., the recipient(s), sender, subject, message body, attachment names)."
email_users_88 = "I understand and agree"
email_users_89 = "If you are using anonymous surveys in this project, keep in mind that viewing this page and the emails displayed therein <u>might inadvertently cause anonymous survey responses to be identifiable/de-anonymized</u>. Additionally, if the project is using Data Access Groups, you will <u>be able to view the emails related to all DAGs in this project</u> (and thus possibly any data piped into the body of those email). If you understand and agree to these conditions, click the button below. <u>Please note the act agreeing to this disclaimer will be documented on the project Logging page.</u>"
email_users_90 = "Please note that the search results on this page may not be complete for this project because the project was created prior to when the Email Logging feature was enabled, which was on"
email_users_91 = "Survey Invitations (all types)"
email_users_92 = "Re-send email"
email_users_93 = "If you wish to re-send this message to the recipient, click the button below. Please note that if the message contained any email attachments, those attachments will unfortunately not be able to be re-sent with the message."
email_users_94 = "The message was successfully re-sent to the original recipient!"
email_users_95 = "Confirm: Re-send the message?"
email_users_96 = "Email & SMS Logging"
email_users_97 = "Search emails and SMS messages"
email_users_98 = "Search all outgoing emails and SMS mesages for this project"
email_users_99 = "Your REDCap Secure Messaging code is <b>{0}</b>"
email_users_100 = "(This code will expire in {0} minutes)"
email_users_101 = "Enter code"
email_users_102 = "Project Owner = User with Design or User Rights privileges"
email_users_103 = "Quick filter groups"
email_users_104 = "Filter users by privileges/features"
email_users_105 = "Filter users by authentication type"
email_users_106 = "Filter users by activity"
email_users_107 = "Past week"
email_users_108 = "From"
email_users_109 = "To"
email_users_110 = "selected"
email_users_111 = "Show suspended users"
email_users_112 = "Search"
email_users_113 = "Send emails"
email_users_114 = "Message"
email_users_116 = "Users with API tokens"
email_users_117 = "Users with Mobile App rights"
email_users_118 = "Project Owners"
email_users_119 = "CDIS Users"
email_users_120 = "Username"
email_users_121 = "Name"
email_users_122 = "Email"
email_users_123 = "Per page"
email_users_126 = "Error"
email_users_127 = "Success"
email_users_128 = "Your emails have been scheduled and will be sent using a background process. You can leave this page."
email_users_129 = "Select Filtered"
email_users_130 = "Unselect Filtered"
email_users_131 = "Please confirm before sending"
email_users_132 = "Associate another email with your account..."
email_users_133 = "total"
email_users_134 = "visible"
email_users_135 = "All outgoing emails for this project can be searched and accessed below by any user having \"Email Logging\" privileges in this project. The Email Logging feature allows users to search and view *all* outgoing emails related to this project, which includes being able to view all aspects of any given email - i.e., the recipient(s), sender, subject, message body, and attachment names. Any email returned from a search may be viewed and (if desired) re-sent to the original recipient (e.g., in case they did not receive it). NOTE: If you are using anonymous surveys in this project, keep in mind that viewing this page and the emails displayed therein might inadvertently cause anonymous survey responses to be identifiable/de-anonymized. Additionally, if the project is using Data Access Groups, you will be able to view the emails related to all DAGs in this project (and thus possibly any data piped into the body of those emails)."
email_users_136 = "Survey Confirmation Emails"
esignature_01 = "E-signature and Locking Management"
esignature_02 = "The table below displays all existing records in the project with their status as locked or e-signed for all data collection instruments. It also will display any records that are entirely locked (i.e., locked at the record level, not at the instrument level). Instruments that do not allow locking (if specified on the Record Locking Customization page) will not be displayed below. If an instrument has been designated not to display the e-signature option but still allows locking, then it will display 'N/A' for that form's e-signature status. You may use the 'Actions' links to filter the table in various ways to show or hide rows based on criteria related to its locking or e-signature status. You may click the 'View Record' link to view that record on the data collection instrument, which will open in a new window. If you would like to export the table as a file in CSV format, simply click the link below."
esignature_04 = "SHOW ALL ROWS"
esignature_05 = "Show timestamp / user"
esignature_06 = "Hide timestamp / user"
esignature_07 = "Show locked"
esignature_08 = "Show not locked"
esignature_09 = "Show e-signed"
esignature_10 = "Show not e-signed (excludes N/A)"
esignature_11 = "Show both locked and e-signed"
esignature_12 = "Show neither locked nor e-signed (excludes N/A)"
esignature_13 = "Show locked but not e-signed (excludes N/A)"
esignature_14 = "All records"
esignature_18 = "Locked?"
esignature_19 = "E-signed?"
esignature_20 = "View record"
esignature_21 = "Before forms can be locked using an e-signature, you must enter your REDCap username and password so that they may be validated. After three consecutive unsuccessful attempts, you will automatically be logged out of REDCap, thus ending this session."
esignature_24 = "The username or password entered was incorrect! Please try again."
esignature_25 = "E-signatures are an extension of the record locking/unlocking functionality."
esignature_26 = "Once a data collection instrument has been locked for a given record in the project, a person with e-signature privileges may then apply an e-signature to that form, if they wish. The e-signature option appears as a check box that says"
esignature_28 = "which appears just above the Save buttons and immediately below the"
esignature_29 = "Locked"
esignature_30 = "check box."
esignature_31 = "How it works:"
esignature_32 = "Although locking a record prevents its data from being modified, the e-signature goes a step farther, and serves as the equivalent of a handwritten signature. If a record has been e-signed, then <b>it denotes that its data has been both locked (to prevent further changes) and authorized</b> (i.e. by a user with e-signature privileges). It is also important to note that <b>anyone with locking privileges (even if lacking e-signature authority) will negate the e-signature on a form when unlocking the record</b>, after which data changes can be made to the record. The e-signature can be re-applied after such data changes. For any given record, an e-signature can be saved and negated on a form an unlimited number of times. When saving an e-signature, a user will be asked to enter their username and password for verification. If the username/password verification fails three times in a row, the user will be automatically logged out of REDCap."
esignature_33 = "How to view the log of e-signature activity:"
esignature_34 = "Similar to the record locking functionality, the e-signature history is also stored in REDCap's data audit trail on the Logging page. If one wishes to view the historical record of e-signatures in the project, one may do so by filtering the audit log by 'Record locking & e-signatures' either for a specific record or for all records in the project."
esignature_35 = "(entire record)"
file_download_03 = "Either this file does not exist OR you do not have permission to download it."
file_download_04 = "The server folder"
file_download_05 = "does not exist! Thus it is not a valid directory for edoc file storage."
file_download_06 = "You may change the value for the edoc file directory in the"
file_download_08 = "The file"
file_download_09 = "does not exist"
file_download_10 = "Server error: DAV extension not loaded"
file_download_11 = "Could not open server connection"
file_download_12 = "could not be found in the REDCap temp directory"
file_download_13 = "<b>Administrator message:</b> If you are utilizing multiple web servers for REDCap using a load balancer, then there might be an issue with 'stickiness' (i.e., persistence), in which a user is being moved by the load balancer from one web server to another within a REDCap session. A 'stickiness' policy must be implemented on the load balancer to ensure that a REDCap user remains on the same web server during the entirety of their session."
folders_01 = "Hide Project Folders"
folders_02 = "Assign project to a Project Folder?"
folders_03 = "Project Folders"
folders_06 = "Select projects below to add to this folder"
folders_07 = "Folder Name"
folders_08 = "Text Color"
folders_09 = "Background Color"
folders_10 = "Edit Folder"
folders_11 = "Save"
folders_12 = "My Folders"
folders_13 = "No folders created yet. Add one above."
folders_14 = "Please enter a valid folder name"
folders_15 = "That folder already exists"
folders_16 = "Are you sure you want to delete this folder?"
folders_17 = "New Folder"
folders_18 = "Add"
folders_19 = "Hide projects already assigned"
folders_20 = "Organize Projects"
folders_21 = "Unorganized Projects"
folders_22 = "Edit Folder"
folders_23 = "Delete Folder"
folders_24 = "Select a folder"
folders_25 = "The box below is a sample of how the Project Folder will appear."
folders_26 = "Project Folders are a way to organize the projects on your My Projects page by putting them into groups. You may create new folders below and then assign your projects to them on the right. A project can be assigned to multiple folders at the same time. To reorder your folders, you can drag and drop them in the left-hand table. Note: Only you can see your folders; they are for your own personal organization."
folders_27 = "STEP 2: Assign Projects To Folders"
folders_28 = "STEP 1: Create Folders"
folders_29 = "You may edit the name of your Project Folder, as well as the text color and background color. Press the Save button to save your changes."
folders_30 = "Your new Project Folder has been created! You may now set its text color and background color. Press the Save button to save your changes."
folders_31 = "[ My Hidden Projects ]"
folders_32 = "If you wish to simply hide projects from your My Projects list, you may put them in the 'My Hidden Projects' folder, which will keep them in an always-collapsed folder at the bottom of the My Projects page."
form_renderer_02 = "What is this?"
form_renderer_06 = "by"
form_renderer_10 = "Assign record to a Data Access Group?"
form_renderer_11 = "Re-assign this record to another Data Access Group?"
form_renderer_13 = "belongs to another Data Access Group"
form_renderer_14 = "You cannot access this project record because it is already being used by another Data Access Group within this project. You will have to use a different record name if you wish to create a new project record."
form_renderer_15 = "Go back to the previous page"
form_renderer_18 = "Lock"
form_renderer_19 = "Expand"
form_renderer_20 = "reset"
form_renderer_21 = "View equation"
form_renderer_22 = "Disclaimer"
form_renderer_23 = "Upload file"
form_renderer_24 = "Remove file"
form_renderer_25 = "Send-It"
form_renderer_26 = "[The file upload feature is disabled]"
form_renderer_29 = "Now"
form_renderer_30 = "Save signature"
form_renderer_31 = "Add signature"
form_renderer_32 = "Signature (draw signature with mouse or finger)"
form_renderer_33 = "How to use this"
form_renderer_34 = "The entire record was locked by"
form_renderer_36 = "Only users with record-level locking/unlocking privileges may unlock this record in order to modify any of this record's data."
form_renderer_37 = "The entire record was locked at the record level on"
form_renderer_40 = "If you have instrument-level locking/unlocking privileges, you may unlock this instrument at the bottom of the page."
form_renderer_41 = "<b>Locked</b> on {0}"
form_renderer_42 = "<b>Locked by {0}</b> ({1}) on {2}"
form_renderer_43 = "Remove signature"
form_renderer_44 = "CANNOT UPLOAD FILE!"
form_renderer_45 = "We're sorry, but Apple does not support uploading files onto web pages in their Mobile Safari browser for iOS devices (iPhones, iPads, and iPod Touches) that are running iOS version 5.1 and below. Because it appears that you are using an iOS device on such an older version, you will not be able to upload a file here. This is not an issue in REDCap but is merely a limitation imposed by Apple. NOTE: iOS version 6 and above *does* support uploading of pictures and videos (but not other file types)."
form_renderer_46 = "You must first sign your signature"
form_renderer_47 = "You must first choose a file to upload"
form_renderer_48 = "The username or password that you entered is incorrect! Please try again."
form_renderer_49 = "You MUST provide a reason for deleting this file. Please try again."
form_renderer_50 = "Provide reason for deleting this file (reason will be logged):"
form_renderer_51 = "Are you sure you want to permanently remove this file?"
form_renderer_52 = "Delete file?"
form_renderer_53 = "<b>E-signed by {0}</b> ({1}) on {2}"
form_renderer_54 = "<b>The entire record was locked by {0}</b> ({1}) on {2}"
form_renderer_55 = "<b>Instrument locked by {0}</b> ({1}) on {2}"
form_renderer_56 = "The instrument '{0}' has been locked for record '{1}'."
form_renderer_57 = "The file \"<b>{0}</b>\" has been deleted."
form_renderer_58 = "Version {0} of the file has been deleted."
form_renderer_59 = "File deleted"
form_renderer_60 = "File was successfully uploaded!"
form_renderer_61 = "In order to use Send-It with this file, the current web page must first be saved by clicking the button at the bottom of the page."
form_renderer_62 = "E-signed by {0} on {1}"
form_renderer_63 = "Delete uploaded signature?"
form_renderer_64 = "Are you sure you want to permanently remove the uploaded signature?"
form_renderer_65 = "Share file with others via public download link or using Send-It"
form_renderer_66 = "Toggle full screen view"
form_renderer_67 = "Calculation equation for variable"
form_renderer_68 = "View trigger logic"
graphical_view_15 = "Print page"
graphical_view_23 = "Field"
graphical_view_24 = "Missing"
graphical_view_25 = "Min"
graphical_view_26 = "Max"
graphical_view_27 = "Mean"
graphical_view_28 = "Median"
graphical_view_29 = "StDev"
graphical_view_35 = "Refresh Plot"
graphical_view_36 = "Missing values"
graphical_view_37 = "Lowest values"
graphical_view_38 = "Highest values"
graphical_view_43 = "Select a data collection instrument to view"
graphical_view_44 = "- select an instrument -"
graphical_view_49 = "View as Bar Chart"
graphical_view_50 = "View as Pie Chart"
graphical_view_51 = "Unique"
graphical_view_52 = "Counts/frequency:"
graphical_view_53 = "Percentile"
graphical_view_60 = "Optional: Select a record to overlay onto the plots below"
graphical_view_61 = "DISPLAY OPTIONS"
graphical_view_65 = "Viewing options:"
graphical_view_66 = "Show plots & stats"
graphical_view_67 = "Show plots only"
graphical_view_68 = "Show stats only"
graphical_view_69 = "Total<br>Count"
graphical_view_71 = "Click to view all records with missing values"
graphical_view_72 = "You may click on <b>missing</b>, <b>highest values</b>, and <b>lowest values</b> to reveal the records for which      the value applies. Only fields that are numeric or categorical are shown. By clicking on a record, a new window is opened,      and you are able to edit the data on the form."
graphical_view_74 = "Sum"
graphical_view_75 = "(YOU selected this)"
graphical_view_76 = "(Selected for record"
graphical_view_77 = "Download image"
graphical_view_78 = "Modules/Services Configuration page"
graphical_view_79 = "Total records: {0}"
grid_14 = "You cannot access this project record because it is already being used by another Data Access Group within this project. You will have to use a different record if you wish to create a new project record."
grid_15 = "Go back to the previous page"
grid_30 = "NEW"
grid_31 = "Choose an existing"
grid_35 = "Enter a new or existing"
grid_36 = "Please note that"
grid_37 = "also exists on another arm."
grid_38 = "You may view an existing record/response by selecting it from the drop-down lists below."
grid_39 = "(survey)"
grid_41 = "The grid below displays the form-by-form progress of data entered for the currently selected record. You may click on the colored status icons to access that form/event."
grid_42 = "Record Home Page"
grid_43 = "Add new instance"
grid_45 = "Repeating Instruments"
grid_46 = "Current instance:"
grid_48 = "Collapse/uncollapse table"
grid_49 = "Collapse/uncollapse repeating event columns"
grid_50 = "(Uncollapse all tables)"
grid_51 = "Choose action for record"
grid_52 = "Delete all data on event:"
grid_53 = "View Record Home Page"
grid_54 = "Record {0} belongs to another Data Access Group"
grid_55 = "<b>Record \"{0}\" is a new {1}.</b> To create the record and begin entering data for it, click any gray status icon below."
grid_56 = "If you wish, you may modify the events below by navigating to the {0:DefineMyEvents} page."
grid_57 = "Arm {0}:"
grid_58 = "(MyCap)"
grid_59 = "(survey + MyCap)"
help_01 = "RETURN TO PREVIOUS PAGE"
help_10 = "How to Use Calculated Fields"
home_01 = "REDCap and all its projects are currently OFFLINE and are not accessible to normal users. You can return the REDCap system back to ONLINE status in the "
home_03 = "Create a new REDCap Project"
home_04 = "You may begin the creation of a new REDCap project on your own by completing the form below and clicking the Create Project button at the bottom."
home_05 = "<b>Your project will not be created immediately</b>, but your request will be quickly reviewed by a REDCap administrator, after which you will be notified via email when the project has been created."
home_07 = "as you begin to build and design them. When you are ready to begin entering real data in the project, you may move it to <b>Production status</b>"
home_09 = ", although it may be brought back to Production status at any time when you are ready to begin collecting data again."
home_12 = "Request Sent!"
home_13 = "Your request for a new REDCap project has been sent to a REDCap administrator."
home_14 = "You will soon receive an email from them at your address"
home_15 = "confirming that your project has been created."
home_16 = "Your request has been sent to a REDCap administrator to copy the following REDCap project:"
home_17 = "Request Approved / User Notified"
home_18 = "The user's request for a new REDCap project has been approved, and a confirmation email has been sent to them at their address"
home_19 = "The user's request to copy a REDCap project has been approved, and a confirmation email has been sent to them at their address"
home_20 = "No project id specified."
home_21 = "Home"
home_22 = "My Projects"
home_26 = "Send-It"
home_28 = "New DTS Adjudications"
home_29 = "No new items to adjudicate"
home_30 = "Project Title"
home_31 = "Records"
home_32 = "Fields"
home_33 = "Status"
home_37 = "There are no projects to display"
home_38 = "You do not have access to any projects"
home_39 = "Type"
home_43 = "The user's request for their REDCap project to be moved to production status has been approved. Their project is now in production, and a confirmation email has been sent to them at their address"
home_44 = "Since you are an Administrator, you will see any projects that have been set as template projects designated with a star"
home_45 = "Also listed is the project type, which designates if the project is in <b>classic</b>"
home_46 = "or <b>longitudinal</b>"
home_47 = "data collection format."
home_49 = "Send Request"
home_50 = "Create Project"
home_53 = "If you wish, you may navigate to the"
home_54 = "user's new project"
home_55 = "Your request has been sent to a REDCap administrator to delete the following REDCap project:"
home_56 = "confirming that your project has been deleted."
home_57 = "NOTICE: Authentication not enabled yet"
home_58 = "We noticed that you are attempting to set your password. We're sorry, but you cannot set your password yet because a REDCap administrator needs to first enable authentication on the Security & Authentication page in the REDCap Control Center. (Currently, authentication is not enabled, so *anyone* can access this website without logging in.) Once the administrator has enabled authentication in REDCap, you can return here via the 'Set your new REDCap password' link in your email. Only then will you be able to use that link to set your password and log in."
home_59 = "Listed below are the REDCap projects to which you currently have access. Click the project title to open the project."
home_60 = "Newly created projects begin in <b>Development status</b>"
home_61 = "New Project"
home_62 = "Training Videos"
home_63 = "to designate the project as officially collecting data. When you are finished collecting data or if you wish to stop collection, the project may be set to <b>Analysis/Cleanup status</b>"
home_64 = "Collapse All"
home_65 = "PID"
index_09 = "Contact"
index_19 = "Current Users"
index_22 = "Records in project"
index_23 = "Data exports"
index_24 = "Logged events"
index_25 = "Most recent activity"
index_26 = "Project status"
index_27 = "Project Statistics"
index_30 = "Enabled"
index_35 = "Expires"
index_36 = "Data Entry Person"
index_37 = "never"
index_38 = "REDCap and all its projects are currently OFFLINE and are not accessible to normal users. You can return the system back to ONLINE status in the"
index_48 = "This project is currently OFFLINE and is not accessible to normal users. You can return it back to ONLINE status in the"
index_51 = "This is the total amount of server space used from documents uploaded either on data collection instruments or on the File Repository page, which includes all data export files saved also. It does not include space used by actual data in the project."
index_52 = "No upcoming events"
index_53 = "Upcoming Calendar Events"
index_54 = "(next 7 days)"
index_56 = "Space usage for docs"
index_70 = "The tables below provide general dashboard information, such as a list of all users with access to this project, general project statistics, and upcoming calendar events (if any)."
index_72 = "Currently, Double Data Entry is enabled, but it will not function correctly since the first data collection instrument in your project is being used as a survey. This issue must be resolved before going forward. The three methods of resolving this issue are to 1) disable the use of surveys in this project (see the top of the Project Setup page), 2) delete the first survey via the Survey Settings button in the Online Designer, or 3) inform your REDCap administrator to disable the Double Data Entry module for this project."
index_73 = "Download list of users (CSV)"
info_01 = "Welcome to REDCap!"
info_06 = "Training Resources"
info_08 = "Please note that any publication that results from a project utilizing REDCap should cite grant support"
info_10 = "If you are collecting data for the purposes of human subjects research, review and approval of the project is required by your Institutional Review Board."
info_11 = "If you require assistance or have any questions about REDCap, please contact"
info_12 = "REDCap Features"
info_15 = "Fast and flexible"
info_19 = "Export data to common analysis packages"
info_28 = "Auto-validation, calculated fields"
info_29 = "file uploading"
info_30 = "branching/skip logic, and survey stop actions."
info_35 = "REDCap provides automated export procedures for seamless data downloads to Excel and common statistical packages (SPSS, SAS, Stata, R), as well as a built-in project calendar, a scheduling module, ad hoc reporting tools, and advanced features, such as branching logic, file uploading, and calculated fields."
info_36 = "Learn more about REDCap by watching a"
info_37 = "brief summary video (4 min)"
info_38 = "If you would like to view other quick video tutorials of REDCap in action and an overview of its features, please see the"
info_41 = "Piping"
info_43 = "Collect data offline using an app on a mobile device when there is no WiFi or cellular connection, and then later sync data back to the server."
info_44 = "REDCap is a secure web platform for building and managing online databases and surveys. REDCap's streamlined process for rapidly creating and designing projects offers a vast array of tools that can be tailored to virtually any data collection strategy."
info_45 = "e-Consent"
info_46 = "Perform informed consent electronically for participants via survey."
info_47 = "Build online surveys and databases quickly and securely in your browser"
info_48 = "Create and design your project using a secure login from any device. No extra software required. Access from anywhere, at any time."
info_49 = "Go from project creation to starting data collection in less than one day. Customizations and changes are possible any time, even after data collection has begun."
info_50 = "Advanced instrument design features"
info_51 = "Diverse and flexible survey distribution options"
info_52 = "Use a list of email addresses or phone numbers for your survey respondents and automatically contact them with personalized messages, and track who has responded. Or create a simple link for an anonymous survey for mass email mailings, to post on a website, or print on a flyer."
info_53 = "Data quality"
info_54 = "Use field validation, branching/skip logic, and Missing Data Codes to improve and protect data quality during data entry. Open data queries to automatically identify and resolve discrepancies and other issues real-time. "
info_55 = "Custom reporting"
info_56 = "Create custom searches for generating reports to view aggregate data. Identify trends with built-in basic statistics and charts."
info_57 = "Export your data as a PDF or as CSV data for easy analysis in SAS, Stata, R, SPSS, or Microsoft Excel."
info_58 = "Secure file storage and sharing"
info_59 = "Upload and share any type of file with anyone in the world through the File Repository feature or Send-It tool. Also works with exports and other built-in file uploading features."
info_60 = "Data-based triggers and alerts"
info_61 = "Send real-time alerts and notifications to your team or other stakeholders via email, text, or phone based on certain data being entered or specific questions having a particular answer."
info_62 = "Connect to other resources"
info_63 = "Use built-in features ("
info_64 = ") to move data to/from your project. Build your own custom software development features to connect your project to other systems."
info_65 = "This project is currently OFFLINE and is not accessible to normal users."
info_66 = "Collect data remotely from participants using this participant-facing mobile application for iOS and Android. Capture survey responses, as well as mobile-sensing or active tasks that are performed by participants using mobile device sensors, and data are automatically sent back to the REDCap server as soon as it is completed and internet connection is available."
lang_updater_02 = "Language File Creator/Updater"
lang_updater_03 = "This page can be used for creating new language files for the text used within REDCap or for cleaning up and updating existing language files used in previous versions of REDCap. These REDCap language files are text files saved with an INI file extension and have strings of text (paragraphs, phrases, or words) mapped to specific variables in the language file. To translate REDCap's English text into a new language, follow Option #1 below. To update the text of an existing language file with any new text from the current version of REDCap, use Option #2 to streamline the process. Before utilizing either option, you may want to check if someone has already performed a translation you might want by navigating to the REDCap Community website"
lang_updater_04 = "Obtain the English language file to begin a new translation"
lang_updater_05 = "If you wish to begin creating a new language file for REDCap, you will need to take the English text and translate it all into the desired language. To do so, follow these steps:"
lang_updater_06 = "Click the button immediately below, copy the text from the text box, and paste it into a text editor (e.g., WordPad, Notepad++)"
lang_updater_07 = "Translate all the English text"
lang_updater_08 = "On your computer, save the file as an INI file with the name of the language"
lang_updater_09 = "Place the file in your web server folder named"
lang_updater_10 = "Share your translation with the REDCap Consortium by uploading it as an attachment on the REDCap Community website"
lang_updater_11 = "currently contains"
lang_updater_12 = "language variables"
lang_updater_13 = "Translate all English in this file, save the file"
lang_updater_14 = ", then place the file in"
lang_updater_15 = "Select an existing language file to update for this version of REDCap"
lang_updater_16 = "REDCap streamlines the process of updating your language files by automatically merging them with the newest English text and rendering them out for you in merged fashion."
lang_updater_17 = "Simply click the buttons below to have your existing translated text merged with the newest English text for any given language file."
lang_updater_18 = "Then you will simply need to translate only the English portion of the file and replace that language file on your web server."
lang_updater_19 = "has"
lang_updater_20 = "new variables to be translated."
lang_updater_21 = "No language files were found!"
lang_updater_22 = "GO BACK"
lang_updater_23 = "Instructions for updating"
lang_updater_24 = "There are"
lang_updater_25 = "language variables that need to be translated in the text box below. "
lang_updater_26 = "language variables that cannot be used from the existing"
lang_updater_27 = "language file, and thus have been removed from the output below. Follow the steps below to update the language file on your server."
lang_updater_28 = "Copy the text from the text box below and paste it into a text editor (e.g., WordPad, Notepad++). All untranslated text will appear together at the top of the text box, and any text already translated will appear at the very bottom of the text box."
lang_updater_29 = "Translate all the English text into"
lang_updater_30 = "Save the file as"
lang_updater_31 = "on your computer"
lang_updater_32 = "Place the file in the following folder on your web server (replacing the older version):"
lang_updater_33 = ", then replace the file in"
lang_updater_34 = "Below are the existing language variables from"
locking_02 = "This module may be used for customizing the Record Locking option and E-signature option on data collection instruments. The settings below are completely optional. Only users with Lock/Unlock user privileges can access this page, and they are the only ones who can lock and unlock records for a specific form. If they have the additional privilege, they may lock all forms at once for any given record. By default, any user with Lock/Unlock privileges will be able to see the Lock option at the bottom of the data collection instrument, although other users will not see this option. Once a form is locked for a record, the form will display (for all users) the time it was locked and the user who locked it, and all fields on the form will be disabled/read-only until someone with Lock/Unlock privileges unlocks the form."
locking_03 = "Below, you may set the Record Locking option"
locking_04 = "to be displayed"
locking_06 = "not be displayed"
locking_07 = "on any given form, if you wish, by checking/unchecking the checkboxes on the far left. By default, the Record Locking option will be displayed on all forms for those with appropriate rights. You may also provide custom text, if desired, to be displayed for the Lock option by entering it in the text box and clicking 'Save'. If you have set the option to display the Lock option but have not set any custom text, the following text will be displayed by default:"
locking_08 = "Lock this record for this form? If locked, no user will be able to edit this record on this form until someone with Lock/Unlock privileges unlocks it."
locking_09 = "If custom text has been set, it can be edited"
locking_10 = "or removed"
locking_11 = "at any time by clicking the icons on the right. If nothing is changed on this page from its original settings, then the Lock option will be displayed on all forms for any user with Lock/Unlock privileges, and will display the default text listed above."
locking_16 = "Display the Lock option for this instrument?"
locking_18 = "Also display E-signature option on instrument?"
locking_19 = "Lock Record Custom Text"
locking_20 = "Edit / Remove Custom Text"
locking_22 = "You have not defined any forms. You must first define some forms with fields on the"
locking_23 = "Online Designer and Data Dictionary Upload"
locking_25 = "Please try again."
locking_27 = "Please enter a value in the text box first."
locking_28 = "DELETE CUSTOM LOCKING TEXT?"
locking_29 = "Are you sure you wish to remove the label for the Lock Records feature for the form"
locking_30 = "I understand. Let me make changes."
locking_31 = "No thanks. Leave it the way it is."
locking_33 = "WARNING: IMPORTANT NOTE"
locking_34 = "While in production, any changes made on this page, such as disabling the e-signature option for a form, could have disastrous effects on a project's workflow or data integrity if the project is dependent upon these settings remaining constant throughout a portion of this project or for its entirety."
locking_35 = "Customize and Manage the Record Locking and E-signature Functionality"
locking_36 = "Customize & Manage Locking/E-signatures"
locking_37 = "Export all (CSV)"
locking_38 = "This module may be used for customizing the Record Locking option on data collection instruments. The settings below are completely optional. Only users with Lock/Unlock user privileges can access this page, and they are the only ones who can lock and unlock records for a specific form. If they have the additional privilege, they may lock all forms at once for any given record. By default, any user with Lock/Unlock privileges will be able to see the Lock option at the bottom of the data collection instrument, although other users will not see this option. Once a form is locked for a record, the form will display (for all users) the time it was locked and the user who locked it, and all fields on the form will be disabled/read-only until someone with Lock/Unlock privileges unlocks the form."
new_project_popup_02 = "Your new REDCap project has been created and is ready to be accessed."
new_project_popup_03 = "You may now begin exploring your project and the many features available to you. Below are some instructions to help you get started."
new_project_popup_16 = "COPY SUCCESSFUL!"
new_project_popup_17 = "Your REDCap project has been copied, and an exact duplicate was generated, which is already loaded and ready for you here."
project_settings_02 = "Online Status of Project"
project_settings_03 = "If 'offline', normal users will be denied access to project"
project_settings_04 = "OFFLINE"
project_settings_05 = "ONLINE"
project_settings_09 = "Names of Contact Persons (for reference)"
project_settings_18 = "Allows two project users to be set as Data Entry Person #1 and Data Entry Person #2 (using User Rights page), and allows them to create records with the same name and enter data for the same record without seeing one another's data. Only one person at a time can be set as person #1 or #2. All other users are considered Reviewers. Reviewers have the ability to merge a record created by person #1 and #2 after viewing differences and adjudicating those differences using the Data Comparison Tool, thus creating a third record in the set."
project_settings_29 = "Date Shifting De-Identification Option: Date Shift Range"
project_settings_30 = "Specify the maximum number of days for the date shift range. (Range will vary from 0 to the entered value when dates are exported using date shifting on the Data Export Tool page.)"
project_settings_31 = "Days"
project_settings_47 = "Custom text to display at top of Project Home page in project"
project_settings_48 = "Custom text to display at top of all Data Entry pages in project"
project_settings_50 = "Enable auto-calculations for calc fields?"
project_settings_51 = "If enabled (default), server-side auto-calculations will be performed for calc fields when data is imported (via Data Import Tool or API) or when saving a form/survey containing cross-form or cross-event calculations. If disabled, then calculations will only be done after being performed via JavaScript (client-side) on the data entry form or survey page on which they are located, and they will not be done on data imports."
project_settings_52 = "Tip: This setting should *only* be disabled if the auto-calculations are causing excessive slowdown when saving data. If disabled, then some calculations might not get performed, and if so, must then be fixed with Data Quality rule H."
project_settings_53 = "Enable/disable the Shared Library for this project?"
project_settings_54 = "Enable/disable Twilio SMS and Voice Call services for this project?"
project_settings_55 = "If disabled, then the Twilio option will always remain disabled and hidden for all users in this project."
project_settings_56 = "This text is not displayed anywhere in the project, and is simply used for bookkeeping purposes for this project."
project_settings_57 = "Set custom logo and text:"
project_settings_58 = "Miscellaneous project settings:"
project_settings_59 = "Prevent branching logic from hiding fields that have values"
project_settings_62 = "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. Thus they will be exempt from branching logic. This will prevent data from being erased as it normally does if fields are hidden by branching logic. NOTE: This setting affects both data entry forms and survey pages."
project_settings_63 = "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, whereas on survey pages it will automatically erase the value of the field being hidden without displaying the confirmation prompt, which has always been the default behavior for surveys."
project_settings_64 = "Edit Project Settings"
pwd_reset_01 = "Your password has not been set yet or has been reset. You will need to set your password here to whatever value you wish. Please enter your desired password below and click the 'Submit' button. Once your password has been set, you may use it with your username whenever you log in to REDCap. Please make sure that you write down or remember your new password for future use."
pwd_reset_05 = "Re-type password"
pwd_reset_06 = "Your password has already been set!"
pwd_reset_10 = "Set Your Password"
pwd_reset_14 = "Password mismatch! Please re-enter."
pwd_reset_15 = "The password you entered has been used as one of your last five (5) passwords."
pwd_reset_16 = "Your password must be changed after the following number of days from setting it:"
pwd_reset_17 = "It was not changed before this time and has thus expired. Please set a new password below."
pwd_reset_18 = "Please choose a password that you have not used as one of your previous five passwords."
pwd_reset_19 = "Please note that your REDCap password will expire soon"
pwd_reset_20 = "Password will expire soon"
pwd_reset_23 = "REDCap Password Recovery"
pwd_reset_24 = "Enter your REDCap username"
pwd_reset_25 = "The username"
pwd_reset_31 = "CANNOT RESET PASSWORD FOR"
pwd_reset_32 = "If you are not sure what to do now or are not sure where or how to reset your password for this account, please contact your"
pwd_reset_41 = "Forgot your password?"
pwd_reset_44 = "(Please do not refresh this page, as it will re-send the email with a new password.)"
pwd_reset_45 = "Go back to Login page"
pwd_reset_51 = "PAGE LOCKED!"
pwd_reset_52 = "You have failed to answer your password recovery question after 5 recent attempts. As a security precaution, you will be locked out of this page for the  next 30 minutes, after which you may then access the page normally again in order to attempt to recover your password."
pwd_reset_53 = "Your IP address ("
pwd_reset_54 = ") has been temporarily banned from accessing this page due to suspected abuse."
pwd_reset_56 = "The new password entered must be AT LEAST "
pwd_reset_59 = "Password must be at least "
pwd_reset_61 = " CHARACTERS IN LENGTH and must consist of AT LEAST "
pwd_reset_62 = "one letter, and one number."
pwd_reset_63 = "one lower-case letter, one upper-case letter, and one number."
pwd_reset_64 = "one lower-case letter, one upper-case letter, and either one number or one special character."
pwd_reset_65 = "one lower-case letter, one upper-case letter, one number, and one special character."
pwd_reset_66 = "characters long."
pwd_reset_67 = "Later"
pwd_reset_68 = "Change my password"
pwd_reset_69 = "It is advised that you change it before it expires."
pwd_reset_70 = "Click the button below to change it now. If your password expires, you will still be able to log in to REDCap, but you will be immediately forced to set a new password."
pwd_reset_71 = "You may use this page to reset your REDCap password. You must first provide your REDCap username, and if it is an authentic REDCap account, an email containing a link for resetting your password will be sent to the primary email address associated with your REDCap account, after which you will then be able log in to your account."
pwd_reset_73 = "If the username that you just entered"
pwd_reset_74 = "is a valid REDCap username, then an email containing a link for resetting your password has been sent to the primary email address associated with your REDCap account. <b>Please check your inbox</b> and follow the instructions in the email."
pwd_reset_75 = "Send password reset email"
pwd_reset_76 = "NOTICE: This user is suspended from the system and therefore cannot have their password reset until a REDCap administrator first unsuspends their account."
pwd_reset_78 = "The password for the user"
pwd_reset_79 = "cannot be reset in REDCap because it can only be reset using an outside authentication resource at your institution."
report_builder_01 = "Your report has been saved!"
report_builder_05 = "Edit Existing Report"
report_builder_08 = "COPY REPORT?"
report_builder_11 = "DELETE REPORT?"
report_builder_14 = "Create New Report"
report_builder_16 = "Name of Report:"
report_builder_19 = "Operator / Value"
report_builder_20 = "Order the Results"
report_builder_22 = "Ascending order"
report_builder_23 = "Descending order"
report_builder_25 = "First by"
report_builder_26 = "Then by"
report_builder_27 = "Save Report"
report_builder_28 = "Save Changes"
report_builder_29 = "Fields to include in report"
report_builder_30 = "Type variable name or field label"
report_builder_31 = "Filter"
report_builder_32 = "View full list of fields"
report_builder_34 = "contains"
report_builder_35 = "Filters"
report_builder_36 = "Additional Filters"
report_builder_38 = "Filter by event(s):"
report_builder_39 = "Filter by DAG(s):"
report_builder_42 = "Report name"
report_builder_43 = "View/Export Options"
report_builder_44 = "View Report"
report_builder_45 = "Management Options"
report_builder_46 = "Copy"
report_builder_47 = "My Reports & Exports"
report_builder_48 = "Export Data"
report_builder_49 = "(raw data)"
report_builder_50 = "(labels)"
report_builder_51 = "Exporting"
report_builder_52 = "You did not choose your desired export format. Please select the format in which you want to export your data, and then try again."
report_builder_54 = "STEP 2: Archive the export files in File Repository?"
report_builder_55 = "Exporting data..."
report_builder_56 = "Please wait while your data is being exported"
report_builder_57 = "Yes, store a back-up copy"
report_builder_58 = "No, do not store a back-up copy"
report_builder_59 = "Select your export settings, which includes the export format (Excel/CSV, SAS, SPSS, R, Stata) and if you wish to perform de-identification on the data set."
report_builder_60 = "Loading the report"
report_builder_61 = "Selected user roles"
report_builder_62 = "Custom user access"
report_builder_64 = "is checked"
report_builder_65 = "is not checked"
report_builder_66 = "(Choose specific users, roles, or data access groups who will have access)"
report_builder_67 = "Drag field up or down to move it"
report_builder_68 = "You have not provided a name for the report. Please enter a name and try again."
report_builder_69 = "No users have been given access to this report. Please select some users in the User Access section and try again."
report_builder_70 = "No fields have been selected to be included in this report. Please select some fields to include and try again."
report_builder_71 = "filters have a field selected, but either their corresponding operator or value is not defined. Please define both an operator and value for each filter field, or else you can remove the filter altogether. Then try again."
report_builder_72 = "The value you entered does not exist as a valid variable name in this project. Please re-enter it and try again."
report_builder_73 = "The report named"
report_builder_74 = "has been successfully saved."
report_builder_75 = "Drag report up or down to move it"
report_builder_76 = "Are you sure you wish to DELETE the report named"
report_builder_77 = "Are you sure you wish to COPY the report named"
report_builder_78 = "Stats & Charts"
report_builder_79 = "starts with"
report_builder_80 = "All data"
report_builder_81 = "Selected instruments"
report_builder_82 = "and/or events"
report_builder_83 = "(all records)"
report_builder_84 = "(all records and fields)"
report_builder_85 = "All instruments"
report_builder_86 = "ends with"
report_builder_87 = "No results were returned"
report_builder_88 = "does not contain"
report_builder_90 = "Use advanced logic"
report_builder_91 = "Use simple logic (choose fields from list)"
report_builder_92 = "Switch format:"
report_builder_93 = "Advanced filter logic:"
report_builder_94 = "Convert filters to advanced logic format?"
report_builder_95 = "If you convert your existing report filters to the advanced logic format, please note that they CANNOT BE CONVERTED BACK TO THEIR ORIGINAL FORMAT afterward as separate fields. Do you still wish to convert to advanced logic format?"
report_builder_96 = "Convert"
report_builder_97 = "If you switch back to using the simple logic format, please note that since the advanced filter logic cannot be converted into simple format, YOU WILL LOSE YOUR ADVANCED LOGIC. Do you still wish to switch back to simple logic format?"
report_builder_98 = "Erase logic and switch to simple format"
report_builder_99 = "Erase advanced filter logic?"
report_builder_100 = "Preview of logic after conversion:"
report_builder_101 = "choose instrument"
report_builder_102 = "Add all fields from selected instrument:"
report_builder_103 = "The field you chose already exists in the report. Fields cannot be displayed multiple times in a report. Please choose another field."
report_builder_104 = "Please choose a data collection instrument from the drop-down above to display the fields from that instrument."
report_builder_105 = "(Users in ANY groups selected below will have access)"
report_builder_106 = "(Records belonging only to ALL selections below will appear in the report)"
report_builder_107 = "View user access list"
report_builder_108 = "List of users with access based on selections"
report_builder_109 = "The table below lists all the users in this project who will have access to this report based upon your selections in the Custom User Access section."
report_builder_110 = "No users will have access"
report_builder_111 = "View a list of users who will have access to this report based on the selections above:"
report_builder_112 = "Displaying result"
report_builder_113 = "results returned"
report_builder_114 = "Choose export format"
report_builder_115 = "Rendering report... please wait"
report_builder_116 = "Below are some additional export options that are available for your project. Instructions for each type of export are provided. You may click the corresponding icon on the right to download the file for each."
report_builder_117 = "This module allows you to easily view reports of your data, inspect plots and descriptive statistics of your data, as well as export your data to Microsoft Excel, SAS, Stata, R, or SPSS for analysis (if you have such privileges). If you wish to export your *entire* data set or view it as a report, then Report A is the best and quickest way. However, if you want to view or export data from only specific instruments (or events) on the fly, then Report B is the best choice. You may also create your own custom reports below (if you have such privileges) in which you can filter the report to specific fields, records, or events using a vast array of filtering tools to make sure you get the exact data you want. Once you have created a report, you may view it as a webpage, export it out of REDCap in a specified format (Excel, SAS, Stata, SPSS, R), or view the plots and descriptive statistics for that report."
report_builder_118 = "You may create a new report by selecting the fields/variables below that you want to include in the report. You may add as many fields to your report as you wish, and you can choose which users may view this report. You will also need to provide a name for your report, which will then be displayed on the project's left-hand menu for anyone to whom you have given access. You can filter the results returned in the report in a variety of ways, including using complex AND/OR logic. When you are finished, click the Save Report button at the bottom. The new report will then be added to your list of reports, after which you may immediately begin viewing them or exporting them."
report_builder_119 = "How to use filters and AND/OR logic"
report_builder_120 = "In reports you can add as many filters as you wish, and you can get quite complex with the filter logic using multiple fields with AND and OR conditional logic. To add a filter, select a field that you wish to filter on, after which you will need to set both an operator and a value. If the field is multiple choice, it will auto load all of that field's choices in a drop-down so that you may choose one of the choices. Otherwise, if it is not a multiple choice field, it will instead provide a text box for entering the filter value."
report_builder_121 = "Using ANDs and ORs with multiple fields allow you to do more complex filtering. If you have two filters with an AND between them, for example, that means that it will apply both of them together when filtering, but if you use OR, it will return results that apply to just one or the other. In general, using AND will often constrict the results further by returning less data in the report than when using OR."
report_builder_122 = "There is no limit to how many times you may use a field as a filter in a single report. TIP: If you want to find instances in your data where a field's value is blank/null, then just leave the value text box blank. Conversely, to find instances where the field has a value (i.e., is non-blank), set the operator as 'not =' with a blank text box."
report_builder_123 = "If you have filtering that uses both OR and AND, it is very important to know the order in which REDCap evaluates the ORs and ANDs to ensure that your logic behaves how you expect. Essentially, all the ORs are evaluated for consecutive filter fields as a group, and all the groups are then evaluated as ANDs with each other. For example, it looks like (this OR this OR this) AND (this OR this OR this), in which all the ORs inside the parentheses are evaluated first and then those groups of ORs are then evaluated together using ANDs."
report_builder_125 = "Report ID"
report_builder_126 = "How to use the Report ID in API Report Export"
report_builder_128 = "We are sorry, but apparently the report is not able to be displayed. It may simply be that there is too much data trying to be displayed at once, in which it is causing REDCap to crash. If this error occurs again, it is recommended that you make the report smaller (fewer fields and/or perhaps fewer records) so that this error does not occur. Our apologies for this inconvenience."
report_builder_129 = "We are sorry, but apparently the data export is not able to complete successfully. It may simply be that there is too much data trying to be exported at once, in which it is causing REDCap to crash. If this error occurs again, it is recommended that you attempt to export a smaller data set (fewer fields and/or perhaps fewer records) so that this error does not occur. Our apologies for this inconvenience."
report_builder_130 = "Also allows user to view ALL reports (but not necessarily all data in the reports)"
report_builder_131 = "How to use Data Exports, Reports, and Stats"
report_builder_132 = "The report cannot be displayed because there appears to be an error in the filters in your report, or perhaps the filter logic is too long (Note: you should not have more than 900 field variables referenced in your logic). Please go to the Edit Report page to fix it."
report_builder_133 = "Choose who sees this report on their left-hand project menu"
report_builder_134 = "Employing user access controls for a report allows certain users to have the report appear on their left-hand project menu (below the Applications list) and thus allows the report to stay hidden and inaccessible for other users. Please note that any user that has 'Add/Edit Reports' user privileges will be able to view *all* reports in the project. This does not cause any user rights conflicts because reports do not give users access to any data to which they do not already have access. In other words, if a user was not given form-level access to a particular data collection instrument, then they will still not be able to view data from that instrument inside any report. The same goes if the user is assigned to a Data Access Group, in which case they will still only be able to view data from records in their own DAG. So even though a user may have 'Add/Edit Reports' privileges and may thus be able to view reports to which they have not been given explicit access, they will not be able to view data to which they do not already have access. So implementing user access for a report is not quite the same as setting someone's user privileges. Reports merely act as a window, so to speak, for viewing a subset of the data to which a user has access, in which user privileges are employed when viewing a report. But user access controls for a report merely provide a way to display the reports on certain users' left-hand project menu and thus are different from setting a user's user rights."
report_builder_135 = "User Access for Reports"
report_builder_136 = "Quick Add"
report_builder_137 = "To quickly add or remove fields for this report, check or uncheck their associated checkbox below. The fields will *automatically* be added/removed from the report as you check/uncheck them. The fields will be added to the end of the report as they are checked."
report_builder_138 = "Total fields selected:"
report_builder_139 = "Create report"
report_builder_140 = "based on the selections above"
report_builder_141 = "NOTE: This report has been pre-loaded with your custom selections, but it has *not* been saved yet."
report_builder_142 = "Live Filters"
report_builder_144 = "Live Filter"
report_builder_145 = "(blank value)"
report_builder_146 = "Note: Sorting works only within the page displayed, not over all pages in the report."
report_builder_147 = "It appears that your data is taking a long time to export. It *may* take more than 30 minutes to complete. Please do not try to stop and then restart the export, as it may cause the process to take even longer than usual. Thanks for your patience."
report_builder_148 = "Additional report options"
report_builder_149 = "Combine checkbox options into single column of only the checked-off options (will be formatted as a text field when exported to stats packages)"
report_builder_150 = "Displayed on page below report name"
report_builder_151 = "Live Filters can be selected on the report page for dynamically filtering data in real time. With the exception of the Record ID field, only multiple choice fields can be used as Live Filters (as well as Events, if longitudinal, and Data Access Groups, if any exist)."
report_builder_152 = "Edit Access:"
report_builder_153 = "View Access:"
report_builder_154 = "Choose who can edit and view this report"
report_builder_155 = "Choose who can edit, copy, or delete this report (requires user to have 'Add/Edit/Organize Reports' privileges)"
report_builder_156 = "Remove line breaks/carriage returns from all text data values (only applicable for CSV Raw and CSV Label data exports)"
report_builder_157 = "TIP:"
report_builder_158 = "Use [X-instance] Smart Variables to filter repeating data."
report_builder_159 = "Show only repeating instance data: <code>[current-instance] <> \"\"</code>"
report_builder_160 = "Show only the first repeating instance: <code>[current-instance] <> \"\" and [current-instance] = [first-instance]</code>"
report_builder_161 = "The report ID provided in the list of reports is displayed to the right of each report. The report ID may be referenced when piping a Smart Chart into text by appending <code>:reportID</code> inside the square brackets (e.g. <code>[bar-chart:status_field:178]</code> or when calling the API Report Export method for the REDCap API. The API Report Export method allows you to export all the data from REDCap for a given report programmatically by using a computer-to-computer call without having to log in to REDCap on a webpage in order to download the report data. The report ID must be provided explicitly in the API Report Export call. For more information on the API and the details of using this specific API method, please see the"
report_builder_162 = "Unique report name"
report_builder_163 = "Enabling this feature below will auto-generate a public link for viewing the report without needing to log in to REDCap."
report_builder_164 = "Report is publicly viewable by anyone with the public link"
report_builder_165 = "[Note: The report must be saved first before it can be made public. Please save it and return back here afterward.]"
report_builder_166 = "Request to enable report"
report_builder_167 = "A user is requesting that their report be made \"public\". This means that it would be publicly viewable by anyone with a link to the report (i.e., with no authentication required to view it). As an administrator, you may click the link at the bottom to approve their request, which will make their report public and then will notify the requester of the approval."
report_builder_168 = "APPROVE REQUEST to make the report public"
report_builder_169 = "Your public report request was successfully sent to a REDCap administrator. You will receive an email notification when they have approved your request. Thank you!"
report_builder_174 = "SUCCESS! The report was successfully set as \"public\". Please note that the report will no longer be modifiable while it is public. If you wish to modify this report in any way, you must first make it no longer public, make your changes to the report, and then make it public again."
report_builder_175 = "Report has been made public"
report_builder_176 = "As requested, your report below has been made PUBLIC for the project"
report_builder_177 = "You may access your report using the link below."
report_builder_178 = "ERROR: This is not a valid report in REDCap."
report_builder_179 = "You may create a short and easy to remember custom URL that redirects to your public report. <b>Enter the your desired custom URL</b> that you wish to redirect to your public report. When submitted, it will check if the URL has already been taken. If not, it will save the custom URL here in your project so that you may continue to use it."
report_builder_180 = "Create Custom Report Link"
report_builder_181 = "Are you sure you want to remove the custom report link?"
report_builder_182 = "SUCCESS! The custom report link was successfully removed."
report_builder_183 = "SUCCESS! The following custom report link was successfully created:"
report_builder_184 = "This report is no longer publicly available."
report_builder_187 = "NOTE: Please be advised that even though it has been removed and is no longer associated with this report, if anyone still possesses that custom link and attempts to use it, it will still function and will redirect to this report. However, you can generate another more preferable custom link for this report, if you wish."
report_builder_188 = "This report cannot be displayed at this public link because the report contains one or more fields that have been tagged as Identifier fields that could contain private/sensitive information."
report_builder_190 = "Make the report \"public\"?"
report_builder_191 = "Make report public"
report_builder_192 = "Request approval to make report public"
report_builder_193 = "In order to make this report \"public\" to allow the report to be accessed at a public link, you must first meet the requirements and also agree to the statements below by <u>checking their checkboxes after reading them</u>. Once that is completed, click the \"Make report public\" button at the bottom to finalize it."
report_builder_194 = "You have User Rights privileges in this project."
report_builder_195 = "You do NOT have User Rights privileges in this project."
report_builder_196 = "This report does not have any Identifier fields."
report_builder_197 = "This report contains one or more Identifier fields, which are not allowed in public reports. The following report field variables are Identifiers:"
report_builder_198 = "You have viewed this report to confirm it is the correct report you want to make public."
report_builder_199 = "You must view the report to confirm it is the correct report you want to make public: You have NOT viewed this report during your current REDCap session."
report_builder_200 = "to navigate to this report and view it. Once you have viewed the report, return back to this page before your session ends to continue."
report_builder_201 = "I understand that making this report \"public\" means that all data in the report will be fully accessible to anyone with the public link to the report."
report_builder_202 = "I understand that I am responsible if any private, sensitive, or identifying data in the report is exposed to persons who should not have access to such data."
report_builder_203 = "Sorry, but you do not meet the requirements above in order to make this report \"public\". Please review the information above to learn how."
report_builder_204 = "NOTICE: After the report has been made public, only users with User Rights privileges will be able to obtain the public link for the report, as the link will be displayed on this page, in the report list, and also on the report itself."
report_builder_205 = "Include the repeating instance fields (<code>redcap_repeat_instrument</code>, <code>redcap_repeat_instance</code>) in the report and data export?"
report_builder_206 = "In the report header, display the field label, variable, or both (not applicable for exports)?"
report_builder_207 = "Raw data value"
report_builder_208 = "In the report's data, display the field label, raw data value, or both for multiple choice fields (not applicable for exports)?"
report_builder_209 = "In order to make this report \"public\" to allow the report to be accessed at a public link, you must first meet the requirements and also agree to the statements below by <u>checking their checkboxes after reading them</u>. Once that is completed, click the \"Request approval to make report public\" button at the bottom to finalize it. <b>NOTE: This request will be sent to a REDCap administrator, who will need to approve it</b>, after which you will receive an email notification when the report once it has been approved."
report_builder_210 = "The user has been notified via email that their request has been approved."
report_builder_211 = "NOTICE TO ADMIN: As an administrator approving this request for a user, you must also go through each step above and check the checkboxes in order to approve this request for them, in which you must also agree to all the things to which the user has agreed."
report_builder_212 = "Report:"
report_builder_213 = "Because this report is currently set as \"public\", it cannot be modified. If you wish to modify this report in any way, you must first make it no longer public, make your changes to the report, and then make it public again."
report_builder_214 = "ERROR: Public reports cannot be modified. First, make the report no longer public before making changes to it."
report_builder_215 = "Request to make report public is pending"
report_builder_216 = "Rendering page... please wait"
report_builder_217 = "This report cannot be displayed at this public link because the report displays the Secondary Unique Field, which has been tagged as an Identifier field that could contain private/sensitive information. While that field is not a field in the report, its value is displayed next to the record ID field, which is displayed in the report."
report_builder_218 = "This report cannot be displayed at this public link because the report displays the Custom Record Label, which contains one or more fields that have been tagged as Identifier fields that could contain private/sensitive information. While those fields are not fields in the report, their values are displayed next to the record ID field, which is displayed in the report."
report_builder_219 = "(Note: If the report contains the record ID field and the Custom Record Label or Secondary Unique Field is enabled, ensure that those fields are not Identifiers also.)"
report_builder_220 = "Download Files (zip)"
report_builder_221 = "the report named"
report_builder_222 = "If you wish to do even more complex filtering, you may choose to switch the filtering format over to the 'Advanced Logic', which allows you to hand-type the filtering logic in a big text box. The filter logic is essentially the same kind of syntax as Branching Logic and Calculated field equations, in which you may use all the special functions, such as if(), datediff(), and various mathematical functions, in your filtering logic. REDCap will double check your hand-typed logic for any syntax errors, and it will not allow you to save the report until all errors have been resolved. When using the Advanced Logic, just make sure that your logic ultimately evaluates to either TRUE or FALSE and that it does *not* evaluate to a value, such as a number. For example, datediff([dob], 'today', 'y') is not valid because it will evaluate to a number, but datediff([dob], 'today', 'y') > 30 is valid because it will evaluate as either TRUE or FALSE. If the project is longitudinal, in certain contexts you may need to additionally provide the unique event name, which must also be in brackets and prepended to the variable name, in order to target that field on a particular event - e.g., [event_2_arm_1][variable_name]."
reporting_02 = "This module lists all changes made to this project, including data exports, data changes, and the creation or deletion of users."
reporting_04 = "Since you have been assigned to a Data Access Group, you are only able to view logging events from your group."
reporting_08 = "Filter by event:"
reporting_09 = "All event types (excluding page views)"
reporting_10 = "Data export"
reporting_12 = "Record created-updated-deleted"
reporting_13 = "Record created (only)"
reporting_14 = "Record updated (only)"
reporting_15 = "Filter by user name:"
reporting_16 = "All users"
reporting_17 = "Displaying events (by most recent):"
reporting_18 = "No logged events to display"
reporting_19 = "Time / Date"
reporting_21 = "Action"
reporting_22 = "List of Data Changes<br/>OR Fields Exported"
reporting_24 = "Update user"
reporting_25 = "Update record"
reporting_26 = "Create user"
reporting_27 = "Create record"
reporting_28 = "Data export"
reporting_29 = "Delete user"
reporting_30 = "Delete record"
reporting_31 = "Administrative<br/>Project Change"
reporting_33 = "Manage/Design"
reporting_34 = "Record locking & e-signatures"
reporting_35 = "Page Views"
reporting_36 = "Filter by record:"
reporting_37 = "All records"
reporting_38 = "Reason for<br/>Data Change(s)"
reporting_39 = "Uploaded Document"
reporting_40 = "Deleted Document"
reporting_41 = "Lock/Unlock Record"
reporting_43 = "Page View"
reporting_44 = "Action: "
reporting_45 = "Page accessed:"
reporting_46 = "Create Response"
reporting_47 = "Update Response"
reporting_48 = "recipient"
reporting_49 = "Field:"
reporting_50 = "User or role created-updated-deleted"
reporting_51 = "Filter by time range from"
reporting_52 = "Filter by records in a DAG:"
reporting_53 = "Current record"
reporting_54 = "Report Folders"
reporting_55 = "STEP 2: Assign Your Reports To Folders"
reporting_56 = "My Report Folders"
reporting_57 = "Hide reports already assigned"
reporting_58 = "Select reports below to add to this folder"
reporting_59 = "Report Folders are a way to organize your reports by putting them into groups. You may create new folders below and then assign reports to them on the right. A report can be assigned to multiple folders at the same time. To reorder your folders, you can drag and drop them in the left-hand table. Note: All users in this project will be able to see the folders so long as they have 'View Access' to at least one report in the folder."
reporting_60 = "Search reports by title"
reporting_61 = "Record deleted (only)"
reporting_63 = "Custom range"
reporting_64 = "By default, only the logged events from the <u>past week</u> are displayed below, but you may change the time range filter above."
reporting_65 = "Current page"
reporting_66 = "All pages using current filters"
reporting_67 = "All logging"
reporting_68 = "Export (CSV):"
reporting_69 = "No limit"
reporting_70 = "PDF Export with data"
rights_05 = "was successfully edited"
rights_06 = "was successfully added"
rights_07 = "was successfully deleted"
rights_09 = "Editing existing user"
rights_11 = "Adding new user"
rights_44 = "You may set the rights for the user below by checking the boxes next to the application tools to which you wish to grant them access. You may also grant them or deny them access to individual data collection instruments, if so desired. To save your selections, click the"
rights_45 = "button at the bottom of the page."
rights_47 = "No Access"
rights_48 = "De-Identified"
rights_49 = "Full Data Set"
rights_50 = "Double Data Entry"
rights_51 = "Reviewer"
rights_52 = "Person"
rights_54 = "Expiration Date"
rights_55 = "(if applicable)"
rights_61 = "Read Only"
rights_80 = "Email could NOT be sent to the new user, so it is displayed below if you wish to copy it and send it manually:"
rights_83 = "REDCap project password reset"
rights_88 = "You have been given access to the REDCap project named"
rights_89 = "Using your user name"
rights_90 = "you may log in to the project using the link below."
rights_91 = "REDCap project access granted"
rights_92 = "Since you have been assigned to a Data Access Group, you are only able to view/edit users from your group, and you are not allowed to add new users to this project."
rights_95 = "Expiration"
rights_96 = "Reports & Report Builder"
rights_97 = "Lock/Unlock Records"
rights_99 = "Create Records"
rights_100 = "Rename Records"
rights_101 = "Delete Records"
rights_104 = "The user"
rights_105 = "cannot be granted access because that person is not yet a REDCap user."
rights_107 = "Since you are a REDCap Administrator, you can create their username on the"
rights_108 = "User Controls page"
rights_109 = "in the REDCap Control Center."
rights_112 = "Notify user of their project access via email?"
rights_113 = "Users with locking privileges also have access to the E-signature and Locking Mgmt page on the left-hand Applications menu."
rights_115 = "Locking / Unlocking"
rights_116 = "Locking / Unlocking with E-signature authority"
rights_117 = "What is an E-signature?"
rights_119 = "Settings pertaining to project records:"
rights_122 = "REDCap project access granted"
rights_123 = "Explain these settings"
rights_124 = "Any user in the project may be given privileges to create records, rename records, and delete records. Each of these settings are explained in detail below. By default, any new users that are granted access to the project can create records, but cannot rename or delete records unless specifically designated by someone."
rights_130 = "Settings pertaining to record locking and E-signatures:"
rights_131 = "Watch video about locking"
rights_132 = "DTS (Data Transfer Services)"
rights_133 = "-- select user --"
rights_134 = "(Only modifiable by REDCap administrators)"
rights_135 = "Project Design and Setup"
rights_137 = "Edit survey responses"
rights_138 = "View & Edit"
rights_139 = "API Export"
rights_141 = "What is the REDCap API?"
rights_142 = "Setup"
rights_143 = "Dashboard"
rights_144 = "Randomize"
rights_145 = "What is randomization?"
rights_146 = "They will first need to have their REDCap account created by a REDCap administrator, after which you may then grant them access to this project and other projects also."
rights_148 = "Role name"
rights_149 = "Assign to group"
rights_150 = "or users assigned to a role"
rights_151 = "[No users assigned]"
rights_152 = "Edit role privileges"
rights_153 = "Edit user privileges"
rights_154 = "Add new user"
rights_155 = "Enter new role name"
rights_156 = "Assign to role"
rights_157 = "Editing existing user role"
rights_158 = "Create role"
rights_159 = "Creating new role"
rights_161 = "A role name was not entered. Please try again."
rights_162 = "Give them custom user rights or assign them to a role."
rights_163 = "A username was not entered. Please try again."
rights_164 = "You are not allowed to delete this role because it contains one or more users that have been assigned to it. If you wish to delete a role, you must first remove all users that have been assigned to the role, after which you may then delete it."
rights_165 = "Add with custom rights"
rights_166 = "has been successfully ASSIGNED to the user role"
rights_167 = "User assigned to role"
rights_168 = "Add new users:"
rights_169 = "Add new user roles to which users may be assigned."
rights_170 = "Create new roles:"
rights_171 = "never"
rights_172 = "User actions:"
rights_173 = "Re-assign to role"
rights_174 = "(click username to edit or assign to role)"
rights_175 = "Remove from role"
rights_176 = "has been successfully REMOVED from their user role."
rights_177 = "User removed from user role"
rights_178 = "Edit user privileges or assign to role"
rights_179 = "Enter new group name"
rights_180 = "Add Group"
rights_181 = "Assign"
rights_182 = "Create new groups:"
rights_183 = "Add new data access groups to which users may be assigned."
rights_184 = "Are you sure you wish to delete the group"
rights_185 = "Delete group?"
rights_186 = "You cannot assign a new user to a role because no roles have been created yet. You need to create a role first, after which you may assign a user to the role."
rights_187 = "Add user"
rights_190 = "Delete role"
rights_191 = "Remove user"
rights_192 = "Are you sure you wish to DELETE this role? If you do, all users assigned to the role will be given back their user privileges as they were prior to being assigned to the role."
rights_193 = "Are you sure you wish to REMOVE this user? If so, they will no longer be able to access the project."
rights_194 = "Are you sure you wish to REMOVE YOURSELF from this project? If so, YOU will no longer be able to access the project."
rights_195 = "Create user role"
rights_196 = "Edit user role"
rights_197 = "Delete user role"
rights_199 = "Role name:"
rights_200 = "Rename user role"
rights_201 = "Edit user expiration"
rights_202 = "New User Notification"
rights_203 = "Change user expiration:"
rights_204 = "Updated User Expiration"
rights_205 = "Cannot delete role containing users!"
rights_206 = "(click role name to edit role)"
rights_209 = "(click expiration date to edit)"
rights_210 = "(click DAG to assign user)"
rights_211 = "Copy role"
rights_212 = "Are you sure you wish to COPY this role? This will copy all the privileges of this role to a new role. Enter the name of the new role below and click the Copy Role button."
rights_213 = "New role name:"
rights_214 = "User's privileges will remain the same"
rights_215 = "Please note that since you removed the user from a role, that user will maintain the exact same user privileges that they had while in the role previously."
rights_216 = "This page may be used for granting users access to this project and for managing the user privileges of those users. You may also create roles to which you may assign users (optional). User roles are useful when you will have several users with the same privileges because they allow you to easily add many users to a role in a much faster manner than setting their user privileges individually. Roles are also a nice way to categorize users within a project. In the box below you may add/assign users or create new roles, and the table at the bottom allows you to make modifications to any existing user or role in the project, as well as view a glimpse of their user privileges."
rights_217 = "Remove from role or re-assign to other role"
rights_218 = "(e.g., Project Manager, Data Entry Person)"
rights_219 = "The reason that you cannot access this page *may* be because you are a Double Data Entry user. Since the Double Data Entry module prevents DDE user #1 and #2 from seeing each other's data, many modules in REDCap that display some data from many records at once are off limits to a Double Data Entry user (although such pages may be accessed by a Reviewer user in the project)."
rights_220 = "* User's API rights cannot be changed since user is assigned to a role."
rights_222 = "[No users from your group are assigned]"
rights_223 = "Cannot edit role"
rights_224 = "You are not allowed to edit this user role because users from *other* Data Access Groups are assigned to it AND/OR users that are not in *any* Data Access Group are assigned to it. While you may edit roles that contain only users from *your* Data Access Group, you are not allowed to edit roles containing users from other Data Access Groups or users not in Data Access Groups."
rights_226 = "User Access Dashboard"
rights_227 = "Expire"
rights_228 = "The User Access Dashboard is a reporting tool designed to assist you in the management of users that have been granted access to your REDCap projects. If you are able to view this dashboard, you have rights to the User Rights application for at least one project. A summary of all the projects in which you are able to grant other users access, or to edit their user privileges, is provided below. The list can be filtered by project status and project purpose. Please review the table regularly to ensure that each person listed still requires access to each project. If a user should no longer have access to a given project, you may click the radio button to delete that person from the project or expire that person's access to the project (default yesterday's date). You must click the button at the bottom of the page in order to implement any changes. Changes would then take effect immediately. If you prefer, these updates may still be done within individual projects, as before, but the tool will help streamline the process."
rights_229 = "users with API tokens"
rights_230 = "Last time the user accessed the project"
rights_231 = "Projects of all statuses"
rights_232 = "Only production projects"
rights_233 = "Only development projects"
rights_236 = "Including projects with 'Practice/Just For Fun' purpose"
rights_237 = "Excluding projects with 'Practice/Just For Fun' purpose"
rights_238 = "Reload page"
rights_239 = "(including you)"
rights_240 = "There are no projects to display for you that match the filter criteria above in which you have rights to edit user privileges via the project's User Rights page for a given project."
rights_241 = "You last accessed the User Access Dashboard"
rights_242 = "It is recommended that you access the User Access Dashboard at least once each calendar month to review which users still have access to your projects."
rights_243 = "ATTENTION REQUESTED:"
rights_244 = "You have not accessed the User Access Dashboard yet."
rights_245 = "Display notifications and/or send emails to prompt users to periodically view the User Access Dashboard, which allows users to review all their projects to assess if any users should be removed from them or have their access rights expired."
rights_246 = "Enabled: Notification on page"
rights_247 = "Enabled: Notification and warning on page"
rights_248 = "Enabled: Notification and warning on page + Monthly email reminder"
rights_249 = "Explanation of options for enabling the UAD:"
rights_250 = "UAD page is hidden and not accessible to users."
rights_251 = "Displays text on the My Projects page to remind users to visit the UAD page periodically."
rights_252 = "Displays text on the My Projects page to remind users to visit the UAD page periodically, and if the user has not visited the UAD during the current calendar month, it will display the notification in red to alert them to visit the UAD soon."
rights_253 = "Displays text on the My Projects page to remind users to visit the UAD page periodically, and if the user has not visited the UAD during the current calendar month, it will display the notification in red to alert them to visit the UAD soon. This option will also send an email reminder on the first weekday of every month to remind users to visit the UAD."
rights_254 = "NOTE: If the user does not have access to the User Rights page in any project, then they will not see these notifications and will not receive any emails regarding visiting the UAD."
rights_256 = "days ago"
rights_257 = "yesterday"
rights_258 = "earlier today"
rights_259 = "(Optional) Custom notification text:"
rights_260 = "Options for enabling the UAD:"
rights_261 = "How is the custom text used?"
rights_262 = "This can be used to modify the text notification displayed to users on the My Projects page. If notification text box is left empty, then the following text will be used by default:"
rights_263 = "You have"
rights_264 = "recommendations, which are pre-selected below."
rights_265 = "The users are pre-selected below because their REDCap account is suspended. However, they could possibly be un-suspended at any time, so it is recommended that you either expire their access or remove them from the project immediately to ensure they do not regain access to the project unintentionally."
rights_267 = "Suspended"
rights_268 = "YOU are the only user with access to this project"
rights_269 = "If a user's REDCap account is suspended, it means that the user cannot access ANY projects in REDCap and is ultimately locked out of the entire REDCap system indefinitely. The user may be suspended for various reasons (e.g., not having logged into REDCap in a long time, their user expiration time may have passed). A user's suspension status is potentially reversible, but only a REDCap administrator can unsuspend a user's account. If any of your projects on this page contain suspended users, it is recommended that you remove them from your project if you want to ensure that they do not regain access to the project at any point in the future. But for the time being, suspended users will not be able to access any of your projects."
rights_270 = "What does 'suspended' mean?"
rights_271 = "There is nothing to save. You have not selected any users to be deleted or expired from your projects. Please try again."
rights_272 = "Confirm before saving"
rights_273 = "Please review below the selections that you have made on this page to delete and/or expire users from your projects. If incorrect, then close this pop-up and make more changes before clicking the Save button again."
rights_274 = "total users will be deleted from your projects"
rights_275 = "total users will have their access expired in your projects"
rights_276 = "users were deleted from your projects"
rights_277 = "users had their access expired in your projects"
rights_278 = "Return to User Access Dashboard"
rights_279 = "This is the first time you have accessed the User Access Dashboard."
rights_280 = "fetch"
rights_281 = "[account suspended]"
rights_282 = "Action Requested: Log in to REDCap soon"
rights_283 = "This email concerns your REDCap user account"
rights_284 = "To better protect you and your data, REDCap now utilizes a higher level of internal security standards with regard to how your login information is stored in the system. As you know, security is of utmost importance in REDCap, and as part of improving these security standards, <b>we request one simple action from you: that you log in to REDCap soon</b>."
rights_285 = "We ask this because the act of logging in will automatically and invisibly upgrade your REDCap account to the new security standard. Once you have logged into REDCap successfully, please note that it will *not* announce to you that the security upgrade has occurred, but afterward you may either immediately log out or continue using REDCap as normal. Thank you for your help. If you have any questions about this email or its authenticity, please contact your REDCap administrator at"
rights_286 = "User Security"
rights_287 = "Users using weaker password hash:"
rights_288 = "Remind users to log in soon"
rights_289 = "Suspend these users now"
rights_290 = "Users using strong password hash:"
rights_291 = "For greater security, the internal password storage methods in REDCap were modified in REDCap 5.8.0. If you were using REDCap prior to that version, some of your users might still have their passwords stored using the weaker password hash. For a user's password hash to be upgraded to the stronger hash, they simply need to log into REDCap, which will immediately (and invisibly) upgrade their hash. Listed to the right are the number of Table-based users that have the weaker hash and the strong hash."
rights_292 = "You may use the action buttons in the yellow box to either notify your users to remind them to log in and/or you may suspend all your users that have a weaker password hash, which may be done if you have not been able to get them to log in. NOTE: Your REDCap installation is *not* considered insecure if you still have users with the weaker hash, but it is much better security-wise if they are all using the stronger hash. (NOTE: Suspended users are *not* included in the counts to the right.)"
rights_293 = "Send email reminder"
rights_294 = "By clicking the 'Send email reminder' button below, it will send an email reminder ONLY to your Table-based users that have a weaker password hash on their REDCap account, in which it will ask them to log into REDCap soon. You can see the content of the email that will be sent to the users in the box below. The email text cannot be modified."
rights_295 = "The users are now being sent an email asking them to log in soon."
rights_296 = "The users having the weaker password hash have been successfully suspended."
rights_297 = "By clicking the 'Suspend users' button below, it will suspend all the Table-based users that have a weaker password hash on their REDCap account. By suspending these users, it will increase the overall security of the system."
rights_298 = "Suspend users"
rights_299 = "Highest level privileges:"
rights_300 = "Other privileges:"
rights_303 = "Confirm Mobile App Privileges"
rights_304 = "Before enabling REDCap Mobile App privileges for this user, you must confirm that you understand the following things. Please be advised that regardless of this user's API export/import rights and Data Export rights, <b>when the user uses the mobile app, their mobile app privileges will automatically give the user 'Full Data Set' rights for Data Exports (if they have 'download data' privileges for the mobile app) and will give the user both API export and API import rights *ONLY FOR REQUESTS MADE BY THE MOBILE APP*.</b> When not using the mobile app, the user's rights will behave normally as they have been defined. NOTE: Since the mobile app requires full data export access and also requires the ability to make API exports and imports, the mobile app's privileges trump the normal user privileges during mobile app operations with the REDCap server. <b>However, unless a person is granted the extra user privilege to 'download data for all records to the app', then they will not be able to download any data to the app from the project on the REDCap server.</b>"
rights_305 = "Yes, I understand"
rights_306 = "Allow user to download data for all records to the app?"
rights_307 = "Allows user to collect data offline in the mobile app"
rights_308 = "What is the REDCap Mobile App?"
rights_309 = "Settings pertaining to the REDCap Mobile App:"
rights_310 = "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."
rights_311 = "User Rights in the REDCap Mobile App"
rights_312 = "It is important to note that the user privileges inside the REDCap Mobile App mimic a user's privileges in the project on the REDCap server with regard to data collection. For instance, if a user has 'No Access' Data Entry Rights for a specific data collection instrument, then the user will also not have access to that instrument in the app. There is an additional user privilege associated with the app that allows you to choose whether or not the user is able to download data (i.e., records in this project) to the mobile app on their device. For example, you may choose not to allow them to download record data to the app if this project contains very sensitive data (e.g., PHI)."
rights_313 = "WARNING: Please be aware that since this user has been using the REDCap mobile app, if you remove them from this project, then any data that they have collected for this project on the REDCap mobile app that has not been synced back to the server yet will be PERMANENTLY LOST."
rights_314 = "API Import/Update"
rights_315 = "Notify user via email?"
rights_316 = "User Rights mismatch"
rights_317 = "Please note that the role you are trying to assign yourself to does not have User Rights permissions, and thus it would prevent you from accessing the User Rights page. Try selecting another role, or modify the one you are trying to assign."
rights_318 = "Cannot delete DAGs with Randomization enabled"
rights_319 = "Since you have enabled the Randomization module and are using Data Access Groups to randomize by group/site, you will not be allowed to delete any Data Access Groups because that could cause serious issues if you have already uploaded your randomization allocation table and/or have begun to randomize records in this project."
rights_320 = "Note: Any projects that contain only one user (i.e., you) will *not* be displayed below."
rights_321 = "Once a user in this project is given 'REDCap Mobile App' privileges, they can navigate to the mobile app page on the left-hand menu and use it to set up this project inside the mobile app on their device. Once the mobile project is set up on the device, the user can collect data (which is stored locally on the device), and then at some point, sync that data back to this project on the REDCap server."
rights_322 = "To review which users still have access to your projects, visit the"
rights_323 = "Users with the ability to create records can create a new record on the Add/Edit Records page by entering a new record name into the text field or (if record auto-numbering is enabled) click the 'Add new record' button. If users do not have this privilege, they will not see the option to create new records, but will only be able to access and edit existing records."
rights_324 = "Renaming a record means that you are changing its record name to another value. Users with this user privilege will see the 'Rename record' option in the 'Choose action for record' on the Record Home Page after a record has been selected, in which they will be able to enter a new desired record name for that record. If a user attempts to rename a record to a value that matches the name of another record that already exists, they will be prevented from doing so."
rights_325 = "Users with the ability to delete records can permanently delete all data for a given record. This is done by clicking the 'Delete record' option in the 'Choose action for record' on the Record Home Page after a record has been selected. For longitudinal projects (i.e., with multiple defined events), this action will delete all data for all events (for the current arm). Once performed, there is no way to retrieve the data that was deleted. It is recommended that only the highest level users be given this user privilege since it causes permanent data loss."
rights_326 = "External Modules: Configuration Permissions"
rights_327 = "*Permissions based on user's Project Design/Setup rights"
rights_328 = "Privileges may be defined regarding whether the user can set or modify the configuration of an External Module that has been enabled on this project. Below are the currently enabled modules. NOTE: Only administrators may modify the module configuration permissions here."
rights_329 = "**Module does not have project-level configuration options"
rights_330 = "Sponsor Dashboard"
rights_334 = "Suspended?"
rights_335 = "Account Expiration"
rights_336 = "The Sponsor Dashboard can be utilized by users who have been designated as a user sponsor for another REDCap user. In many cases a sponsor is a secondary contact person for the user or someone that helps manage the account (or perhaps they requested that the account be created). The Sponsor Dashboard allows sponsors to manage their sponsored users by viewing various information about them, such as username, name, expiration, suspended status, and some general activity. The dashboard contains various functions to allow sponsors to make requests to REDCap administrators to help manage their sponsored users. Although sponsors may not perform the actions at the bottom of this page on their own, <b>an administrator can perform the action on their behalf when requested</b>."
rights_337 = "You must choose at least one user. Please check the checkbox next to one or more users."
rights_338 = "As an administrator, you may click the button to approve the sponsor's request."
rights_339 = "Process sponsor request:"
rights_340 = "Using one of the buttons below, make a request to a REDCap administrator for the selected users above."
rights_341 = "My Sponsored Users"
rights_342 = "You do not have any sponsored users to list on this page."
rights_343 = "If this module is enabled, any user that is listed as a User Sponsor for another REDCap user will be able to access their sponsored users using a link displayed near the top of the My Projects page. On their dashboard, sponsors will be able to make requests to administrators regarding their users, such as suspending users, setting/extending user expiration times, resetting passwords, and more."
rights_345 = "Default amount to set/extend user expiration times:"
rights_346 = "Regarding user expiration times, if a sponsor requests to extend a user's expiration time for their account, it will add the amount of days above to their existing expiration time. And if the sponsor is setting the expiration time (as opposed to extending it), then it will calculate the expiration time using the value above added to today's date."
rights_347 = "You may perform actions on multiple users at once by using one of the buttons below."
rights_348 = "The buttons at the bottom of this page will allow you to perform actions on multiple users, such as suspending users, extending their account expiration, etc."
rights_349 = "The changes have been made successfully to the selected users!"
rights_350 = "It appears that there is nothing to do. Perhaps some things have changed in the user accounts originally selected for this request so that now this request no longer necessary. If you are processing this request through the To-Do List, you should probably archive this request, or else contact the requester directly to ask about this."
rights_351 = "Hide suspended users"
rights_353 = "<b>NOTICE:</b> This user is a REDCap administrator. Since administrators always have maximum privileges, modifying the user rights below will have no effect on this user in this project, including their usage of the REDCap Mobile App."
rights_356 = "Add/Edit/Organize Reports"
rights_357 = "& Scheduling"
rights_358 = "The role name is missing. Please provide a name for this user role."
rights_359 = "Only analysis/cleanup projects"
rights_361 = "[Not assigned to a role]"
rights_362 = "View project as user:"
rights_363 = "-- select a user --"
rights_364 = "SUCCESS! You are now viewing this project as the user"
rights_365 = "This user's project user privileges will be applied to you within this project. The page will now reload to reflect this change."
rights_366 = "You are currently viewing this project as the user"
rights_367 = ", and their user privileges will be applied to you for the duration of this session."
rights_368 = "[Stop viewing as user]"
rights_369 = "SUCCESS! You are no longer viewing this project as another user. The page will now reload to reflect this change."
rights_370 = "Lock/Unlock *Entire* Records (record level)"
rights_371 = "(instrument level)"
rights_372 = "NOTE: It is important to note that instrument level locking and record level locking are independent features that are governed by separate user privileges (as seen above). You must have explicit permission to either one in order to perform that specific locking action. Also, record locking is a higher-level locking than instrument locking, which means that an entire record may be locked or unlocked while one or more instruments are currently locked, but an instrument cannot be locked or unlocked while the entire record is locked."
rights_373 = "Data Viewing Rights"
rights_375 = "Please note that giving a user 'Locking / Unlocking with E-signature authority' privileges will not immediately enable the E-signature functionality on all data collection instruments. To enable the E-signature feature on the desired instruments, click on the 'Customize & Manage Locking/E-signatures' link (left side menu) and update the settings on the 'Record Locking Customization' tab, where you will find each instrument listed with an option to 'Display E-signature Option'. Until these settings are updated, the E-signature option will remain hidden."
rights_376 = "Upload or download users, roles, and assignments"
rights_377 = "Upload users (CSV)"
rights_378 = "Download users (CSV)"
rights_379 = "You can upload a CSV file to grant new users access to this project and to modify the user privileges of existing users."
rights_380 = "Select your CSV file of users and their user rights to be added/modified:"
rights_381 = "users were added or updated. NOTE: If you just added a new user to the project, you can now optionally assign the user to a role."
rights_384 = "NOTE: Please keep in mind that while REDCap administrators may be added to a project using the Upload Users method, they will always have maximum rights in the project by virtue of being an admin, in which those rights will override any user privileges that have been manually set for them here."
rights_385 = "The field named"
rights_386 = "for user"
rights_387 = "is not a valid rights value."
rights_388 = "It must be 0 or 1."
rights_389 = "It must be 0, 1, 2 or 3."
rights_390 = "You can export a list of all users and their user privileges for this project. Note: If the user has been assigned to a user role, it will return the user with the role's defined privileges. This will return all the attributes below with regard to user privileges in the format specified. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), in which each form will have its own Form Rights value (see the key below to learn what each numerical value represents). Most user privilege attributes are boolean (0=No Access, 1=Access). Attributes returned:"
rights_391 = "Please note that the format of the uploaded CSV file must be in the exact format specific above, which can be most easily seen when viewing the downloaded CSV file of the user rights. Also, the field data_access_group_id exists in the export CSV only for reference, and if it is uploaded, it will be ignored during the import. If you wish to modify the user's DAG, you should set a new value for the field 'data_access_group' instead."
rights_392 = "CDIS: Allow the patient's email address to be imported from the EHR?<br>(only applicable for the Clinical Data Mart and Clinical Data Pull services)"
rights_393 = "For privacy reasons, you might wish to exclude the 'email address' field so that REDCap users cannot import a patient's email address from the EHR. If 'No' is selected, the email option will not appear in the EHR source field list when choosing which clinical data fields to import. Enabling this setting will make the email option visible to all CDIS services (Clinical Data Pull, Clinical Data Mart) in this project."
rights_395 = "(Hidden)"
rights_396 = "cannot have their user privileges modified because the user belongs to a user role. Users in roles cannot have their privileges modified via the 'Upload Users(CSV)' method."
rights_397 = "Assign user to a Data Access Group"
rights_398 = "Assign To DAG:"
rights_399 = "-- select role --"
rights_400 = "A role was not selected. Please try again."
rights_402 = "Last logged activity:"
rights_403 = "User Role ID"
rights_404 = "Unique Role Name"
rights_405 = "for user role"
rights_406 = "Invalid Unique Role Names:"
rights_407 = "Upload user roles (CSV)"
rights_408 = "Download user roles (CSV)"
rights_409 = "You can upload a CSV file to add new user roles to this project and to modify the user privileges of existing user roles."
rights_410 = "Select your CSV file of user roles and their user rights to be added/modified:"
rights_411 = "The Role Label is blank."
rights_412 = "You can export a list of all user roles and their user privileges for this project. This will return all the attributes below with regard to user role privileges in the format specified. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), This will return all the attributes below with regard to user role privileges in the format specified. Please note that the 'forms' attribute is the only attribute that contains sub-elements (one for each data collection instrument), in which each form will have its own Form Rights value (see the key below to learn what each numerical value represents). Most user privilege attributes are boolean (0=No Access, 1=Access). Attributes returned:"
rights_413 = "Please note that the format of the uploaded CSV file must be in the exact format specific above, which can be most easily seen when viewing the downloaded CSV file of the user roles."
rights_414 = "user roles were added or updated. NOTE: If you just added a new user role to the project, you can now optionally assign the user to a role."
rights_415 = "Upload user role assignments (CSV)"
rights_416 = "Download user role assignments (CSV)"
rights_417 = "Select your CSV file of User-Role Assignment to be added or modified:"
rights_418 = "You can assign users to any user role by uploading a CSV file. The format for the CSV upload file can be acquired by exporting the CSV file of your existing User-Role assignments. <b>NOTE:</b> If you wish to modify an existing mapping, you *must* provide its unique username and role name. If the 'unique_role_name' column is not provided, user will not assigned to any role."
rights_419 = "User role assignments were updated."
rights_420 = "You can export a list of all users and role assigned to user for this project.<br>Attributes returned:"
rights_421 = "Assign new user to role"
rights_422 = "Invalid usernames:"
rights_423 = "can not be updated"
rights_424 = "can not be added"
rights_425 = "User's Project Expiration"
rights_426 = "* Includes ability to delete all data on an instrument or on a repeating event."
rights_427 = "NOTE: Users that do not authenticate via Table-based authentication are not valid for a password reset, and thus it is not possible to check the time of their latest password reset. Only select users that log in via Table-based authentication can be selected for the 'Time of latest password reset' action."
rights_428 = "Data Export Rights"
rights_429 = "Data Viewing Rights pertain to a user's ability to view or edit data on pages in the project (e.g., data entry forms, reports). Users with 'No Access' Data Viewing Rights for a given instrument will not be able to view that instrument for any record, nor will they be able to view fields from that instrument on a report. Data Export Rights pertain to a user's ability to export data from the project, whether through the Data Exports page, API, Mobile App, or in PDFs of instruments containing record data. Note: Data Viewing Rights and Data Export Rights are completely separate and do not impact one another."
rights_430 = "Click the header text to set this privilege for all instruments"
rights_431 = "Basic Privileges"
rights_432 = "Show"
rights_433 = "Hide"
rights_434 = "suspended users"
rights_437 = "Manage MyCap Participants"
rights_439 = "External Modules API"
rights_440 = "Full Access"
rights_441 = "This page may be used for viewing the user privileges of users in this project. Since you have read-only privileges to this page, you may not add users, modify user privileges, add/edit roles, or other actions."
rights_442 = "Since you have been assigned to a Data Access Group, you are only able to view users from your group."
rights_443 = "User names can only contain letters, numbers, underscores, hyphens, periods, spaces, apostrophes, and @ symbols."
rights_444 = "This setting is active only when the global 'Allow individual projects to decide' option is selected in the CDIS settings page. If 'Yes' or 'No' is chosen at the global level, this setting is overridden."
rights_445 = "Remove from project"
rights_446 = "User to be removed from the project: <b>{0}</b>"
rights_447 = "Admin only: View user's account on Browse Users page"
scheduling_03 = "Create Schedule"
scheduling_04 = "View or Edit Schedule"
scheduling_05 = "The Schedule Generator will allow you to <b>generate a new schedule</b> based upon your Events and their Days Offset that have been defined on the"
scheduling_09 = "This page may ONLY be used if multiple events have been defined. To be able to utilize this page, you will need to"
scheduling_10 = "define more 'events'"
scheduling_11 = "for this project."
scheduling_12 = "You may generate a schedule for a new or existing"
scheduling_13 = "below by selecting a Start Date, which will be used as the starting point for projecting schedule dates using your Days Offset. Once scheduled, you may then view it on the"
scheduling_14 = ", after which, if desired, you may also perform data entry for that calendar event. You may create a new project record here while performing scheduling or you may choose a currently existing one that has not yet been scheduled."
scheduling_15 = "Add new"
scheduling_16 = "choose existing unscheduled"
scheduling_18 = "Start Date:"
scheduling_19 = "Select Arm:"
scheduling_20 = "Loading..."
scheduling_21 = "To view or edit the calendar events of a previously scheduled"
scheduling_22 = ", select it from the drop-down menu below."
scheduling_23 = "Select a previously scheduled"
scheduling_24 = "Since you are changing the date of this calendar event, you may want to adjust all events occurring after this one by the same amount. <b>Do you wish to adjust all later dates by this amount"
scheduling_25 = "days"
scheduling_26 = "This does NOT include Ad Hoc events."
scheduling_28 = "has already been scheduled!"
scheduling_29 = "Successfully Scheduled"
scheduling_30 = "was successfully scheduled for the dates and times below and has been added to the"
scheduling_31 = "You may now edit this schedule or add more information, such as changing the status (e.g., 'Cancelled', 'Confirmed') or adding descriptive notes, by clicking the <i>View or Edit Schedule</i> tab above."
scheduling_32 = "is NOT a date and thus was not scheduled."
scheduling_33 = "Schedule for"
scheduling_35 = "Print"
scheduling_39 = "belongs to another Data Access Group"
scheduling_40 = "You cannot schedule this record because it is already being used by another Data Access Group within this project. You will have to use a different record name is you wish to add a new"
scheduling_41 = "here."
scheduling_42 = "Projected Schedule for"
scheduling_43 = "The dates below have NOT yet been scheduled."
scheduling_44 = "The projected schedule below was automatically generated for"
scheduling_45 = "based on your pre-defined Events"
scheduling_46 = "for"
scheduling_48 = ". You may change the value of any dates generated below simply by clicking inside the date box and selecting a new date. Any dates generated below that fall on weekends will be listed in"
scheduling_49 = "red"
scheduling_50 = "Click the"
scheduling_51 = "button to finalize this schedule, which will then be added to the Calendar."
scheduling_53 = "Date / Day of Week"
scheduling_54 = "Range"
scheduling_55 = "REMOVE EVENT?"
scheduling_56 = "Are you sure you wish to remove this event from the projected schedule?"
scheduling_57 = "Remove"
scheduling_58 = "Saving..."
scheduling_59 = "Clicking the"
scheduling_60 = "button will additionally add"
scheduling_61 = "as a new"
scheduling_62 = "View/Edit Existing Schedule for"
scheduling_63 = "Below are the calendar events for"
scheduling_64 = "Dates that fall on weekends will be listed in"
scheduling_65 = "You may edit any calendar event by clicking the"
scheduling_66 = "Edit icon, remove an event by clicking the"
scheduling_67 = "Delete icon, or view the full details of the event by clicking the"
scheduling_68 = "View icon. You may also add a new unscheduled event at the bottom of the table by selecting a date and clicking the <i>Add</i> button."
scheduling_69 = "Status"
scheduling_70 = "Notes"
scheduling_71 = "Due Date"
scheduling_72 = "Scheduled"
scheduling_73 = "Confirmed"
scheduling_74 = "Cancelled"
scheduling_75 = "No Show"
scheduling_76 = "Ad Hoc"
scheduling_77 = "Expand"
scheduling_78 = "Read more"
scheduling_80 = "View Calendar Event"
scheduling_81 = "Add new Ad Hoc calendar event on"
scheduling_82 = "Print Schedule"
scheduling_83 = "select arm"
scheduling_84 = "has already been scheduled for this arm!"
scheduling_85 = "VIDEO: How to use the scheduling module"
scheduling_86 = "WARNING: Date out of range"
scheduling_88 = "Notice: The drop-down list of already scheduled records is not visible here because it would contain more than {0} options, which is too many to display on the page.  In order to view an already-scheduled record, it is recommended that you find the record on the Calendar page, in which you can view its schedule via the 'View Schedule' link in the calendar popup.  Alternatively, you can simply append the URL of this page with <code>&record=RECORD</code> (replacing RECORD with the name of the record you wish to view)."
sendit_01 = "You do not have permission to send this file!"
sendit_02 = "There was an error uploading the file."
sendit_03 = "File could not be loaded because it is too large"
sendit_04 = "Files must be smaller than"
sendit_05 = "for uploading."
sendit_06 = "One of the email addresses is not formatted correctly"
sendit_07 = "The email addresses below appear to be incorrectly entered. Please fix them and try again."
sendit_08 = "INCORRECT EMAILS:"
sendit_09 = "Sending file"
sendit_10 = "File successfully uploaded!"
sendit_11 = "The file"
sendit_12 = "was successfully uploaded, and the recipients listed below were sent an email with a password and unique link for downloading the file. The file will expire and become inaccessible on "
sendit_13 = "Recipients:"
sendit_14 = "Emails did NOT send to the following recipients:"
sendit_15 = "SEND ANOTHER FILE?"
sendit_17 = "Send-It is a secure data transfer application that allows you to upload a file (up to"
sendit_18 = "in size) and then allow multiple recipients to download the file in a secure manner."
sendit_19 = "Each recipient will receive an email containing a unique download URL, along with a second follow-up email with the password (for greater security) for downloading the file. The file will be stored securely and then later removed from the server after the specified expiration date. Send-It is the perfect solution for anyone wanting to send files that are too large for email attachments or that contain sensitive data."
sendit_20 = "Instructions for using Send-It:"
sendit_21 = "Fill out the form below to specify to whom you wish to send the file, as well as other custom information and settings. Each email address you enter below will receive a message stating that a file is available for download. The email will include a unique link and password, which the recipient will use to navigate to the webpage for downloading the file to their computer. If the file is very large, it may take several moments to upload, so please allow it to continue to upload until it notifies you of its completion."
sendit_23 = "(recipient emails)"
sendit_24 = "Separate email addresses with commas, semi-colons, or line breaks"
sendit_25 = "Email subject:"
sendit_27 = "Email message:"
sendit_28 = "Expiration:"
sendit_29 = "Specify the time after which the file will no longer be accessible for download"
sendit_30 = "Select a file:"
sendit_31 = "Max file size"
sendit_32 = "File:"
sendit_33 = "Receive confirmation?"
sendit_34 = "Get an email notification informing you when your file has been downloaded by <u>each</u> recipient."
sendit_36 = "The file has expired"
sendit_37 = "Invalid web address"
sendit_39 = "Could not open server connection"
sendit_40 = "Password incorrect"
sendit_41 = "File Download"
sendit_43 = "To download the file, enter the password that was emailed to you. The password would have arrived in a separate email following the original email containing the link to this page. Once you have entered the password, click the button to begin the file download. If the file is very large, it may take several moments to download, so please allow it to continue to download until it completes. The size of this file is"
sendit_44 = "Enter password:"
sendit_46 = "The file you uploaded,"
sendit_47 = ", was downloaded by"
sendit_48 = "Thank you for using"
sendit_49 = "Confirmation of file download"
sendit_50 = "Below is the password for downloading the file mentioned in the previous email."
sendit_51 = "has uploaded the file"
sendit_52 = "for you to download. This download will expire on"
sendit_53 = "A second follow-up email will be sent containing the password for retrieving the file at the link below."
sendit_54 = "To download the file, follow the link below or copy it into your web browser."
sendit_55 = "This file was sent using REDCap. To learn more about REDCap or to see if it is available at your institution, please visit"
sendit_56 = "wrote the following message:"
sendit_57 = "File available for download from"
sendit_58 = "SUCCESS! The file will begin downloading momentarily."
sendit_59 = "ERROR: The file you are attempting to upload is too large. It must be smaller than {0} MB in size. Please try again by uploading a smaller file."
shared_library_01 = "You do not have access rights for this page."
shared_library_02 = "Sharing your instrument to the REDCap Shared Library"
shared_library_03 = "shared and uploaded to"
shared_library_04 = "removed from"
shared_library_05 = "replaced in"
shared_library_06 = "The instrument was NOT successfully"
shared_library_07 = "the REDCap Shared Library"
shared_library_08 = "The instrument was successfully"
shared_library_09 = "Upload your Data Collection Instrument to the REDCap Shared Library"
shared_library_11 = "UPLOADED to"
shared_library_12 = "DOWNLOADED from"
shared_library_13 = "replacement"
shared_library_14 = "separate new"
shared_library_15 = "This data collection instrument has been PREVIOUSLY"
shared_library_16 = "Proceeding with this process will result in this instrument being uploaded to the library <b><u>as a"
shared_library_17 = "copy"
shared_library_18 = "This should ONLY be done if you have made significant changes to the instrument. "
shared_library_19 = "This will remove the existing instrument currently in the REDCap Shared Library and replace it with the one here."
shared_library_20 = "Additionally, if you no longer wish to share this instrument via the REDCap Shared Library, you may remove it here."
shared_library_21 = "REMOVE?"
shared_library_22 = "Are you sure you wish to permanently remove this instrument from the REDCap Shared Library? This will prevent it from being downloaded from the library by anyone else in the future."
shared_library_23 = "this instrument from the REDCap Shared Library"
shared_library_24 = "Information about your instrument"
shared_library_25 = "Instrument Title"
shared_library_27 = "Keywords"
shared_library_28 = "Acknowledgement"
shared_library_29 = "Terms of Use"
shared_library_30 = "Your Contact Information"
shared_library_34 = "Sharing Options"
shared_library_35 = "Share instrument with REDCap users from:"
shared_library_36 = "Any institution in the REDCap Consortium"
shared_library_38 = "Only"
shared_library_39 = "Viewing options for general public"
shared_library_40 = "(i.e. non-REDCap users)"
shared_library_41 = "Only other REDCap users will be able to download the instrument."
shared_library_42 = "Allow general public to see instrument and its info in search results"
shared_library_43 = "Make invisible to general public"
shared_library_44 = "Importing instrument from the REDCap Shared Library"
shared_library_45 = "The import of the instrument from the REDCap Shared Library did not complete successfully."
shared_library_46 = "The instrument was successfully imported from the REDCap Shared Library."
shared_library_47 = "Click the link below to refresh your instrument list on the left."
shared_library_48 = "Because your project is currently in production status, the new imported instrument has not yet been added to the project but has been added to your changes in Draft Mode. To officially add the instrument, you will need to click the 'Submit Changes for Review' button after following the link below."
shared_library_49 = "You have chosen to load a data collection instrument from the REDCap Shared Library. Please provide a name for your instrument and click the <i>Add</i> button to complete the import process, after which the instrument will be added to this REDCap project."
shared_library_50 = "downloaded from"
shared_library_51 = "uploaded to"
shared_library_52 = "This data collection instrument has been previously"
shared_library_53 = "Proceeding with this process will result in a new duplicate copy being downloaded from the library and added as a new instrument in the project."
shared_library_54 = "Please enter a new name for the instrument you are importing."
shared_library_55 = "the imported instrument with the name"
shared_library_56 = "If you do NOT wish to import the instrument, you may return back to the"
shared_library_57 = "REDCap Instrument Library"
shared_library_58 = "This instrument has already been imported and cannot be imported again."
shared_library_59 = "select an instrument"
shared_library_61 = "NOTE: Your data collection instrument will <u>not</u> appear immediately in the REDCap Shared Library, but there will be a slight time delay, as it must first be reviewed and approved before it is officially added to the library. Thank you for contributing to the REDCap Shared Library!"
shared_library_63 = "Provide a few sentences to describe your instrument and its contents."
shared_library_64 = "The name of your instrument as it will appear the Shared Library."
shared_library_65 = "Provide keywords (separated by spaces) that pertain to your instrument. These will assist other users in finding your instrument when performing keyword searches in the Shared Library. (e.g., diabetes child cardiology)"
shared_library_66 = "Provide any text here regarding the terms by which other users may use, modify, or distribute your instrument. This text will appear at the very end of the standard legal agreement, in which users will be forced to agree to it in order to download your instrument from the Shared Library."
shared_library_67 = "Provide any text describing who or what should be acknowledged when utilizing this instrument. This includes any organizations or individual authors who created the instrument, as well as any references to publications about instrument. The acknowledgement will be displayed at the bottom of the webpage in REDCap whenever the instrument is downloaded and utilized by a REDCap user."
shared_library_69 = "(already shared)"
shared_library_70 = "Before you can share your instrument to the REDCap Shared Library, you must first read the shared content agreement. Click the button below to display the agreement."
shared_library_71 = "Read the shared content agreement"
shared_library_72 = "Please provide a reason for removing this instrument."
shared_library_73 = "Reason for removal:"
shared_library_74 = "Provide a reason below for removing this instrument that you previously uploaded to the REDCap Shared Library. Everyone who has downloaded your instrument from the Shared Library will be notified via email that the instrument was removed, and that email will also include the reason that you provide here."
shared_library_75 = "PLEASE READ THIS SECTION BEFORE CONTINUING:"
shared_library_76 = "Before proceeding further, we want to be sure you fully understand the implications of sharing/contributing an instrument to the REDCap Shared Library. Please be aware of the following:"
shared_library_78 = "If the instrument you are about to share is published and <b>you do not own the copyright, please do not submit it</b>. Although if you wish, you may"
shared_library_79 = "Access to the instrument that you share <b>cannot be limited to just you or a group of colleagues</b>, although you may designate that your instrument be downloadable by REDCap users only at *your* institution (instead of the whole world)."
shared_library_80 = "If you are not serious about sharing an instrument but merely <b>want to test the instrument sharing feature on this page, then please do not submit</b> an instrument. This is *only* for individuals who definitely wish to share their instrument with REDCap users around the world (or just at their institution)."
shared_library_81 = "If you have read and understand the bullet points above, proceed below by clicking the button to read the shared content agreement so that you may then share your instrument. If you have questions about the REDCap Shared Library, please direct them to"
shared_library_82 = "make a suggestion"
shared_library_83 = "for a new instrument to be added to the library."
shared_library_85 = "The instrument you are downloading from the Shared Library contains an <b>auto-scoring feature</b>, which means that it behaves a little differently in REDCap than traditional instruments. For instance, once the instrument has been downloaded, you will not be able to modify any fields on the instrument at any time. The instrument will also be automatically enabled as a survey in this project, and if surveys have not yet been enabled for use in this project, then that too will be enabled. This auto-scoring instrument can only be taken in survey form. If the data entry form is viewed for this instrument, all fields will be displayed as read-only."
shared_library_86 = "The instrument you are downloading from the Shared Library is a <b>computer adaptive test (CAT)</b>, which means that its questions are generated dynamically using previous answers. Adaptive instruments behave a little differently in REDCap than traditional instruments. For instance, once the instrument has been downloaded, you will not be able to modify any fields on the instrument at any time. The instrument will also be automatically enabled as a survey in this project, and if surveys have not yet been enabled for use in this project, then that too will be enabled. This adaptive instrument can only be taken in survey form. If the data entry form is viewed for this instrument, all fields will be displayed as read-only."
shared_library_87 = "Language of the instrument's text"
shared_library_88 = "Enter new instrument name"
shared_library_89 = "The PROMIS Battery could not be found! Please return to the Shared Library and try again."
shared_library_90 = "the entire battery of instruments listed below (in the order displayed)."
shared_library_91 = "Battery:"
shared_library_92 = "When importing a battery, which comprises multiple instruments, all the instruments will be downloaded and added to the project in the order seen above. To maintain the proper validation of the battery after downloading the instruments, it is *extremely important* that the instruments remain in this same order in the project. Thus, it is your responsibility to ensure that these battery instruments do not get reordered or modified in any way if you wish to preserve their validation."
shared_library_93 = "The battery of instruments was successfully imported from the REDCap Shared Library."
shared_library_94 = "By uploading your instrument, you will be <b>sharing it with REDCap users all over the world (or just at your institution)</b>, in which it will be made available potentially to millions of users at thousands of other institutions within the REDCap consortium."
shared_library_95 = "You may share your data collection instrument with other REDCap users around the world by uploading it to the REDCap Shared Library. <u>Any REDCap user with design rights can add these shared library instruments into their own projects through the Import option in the Online Designer.</u> To successfully share the instrument, we ask that you please provide some preliminary information below, which will be sent to the REDCap Shared Library along with a copy of your data collection instrument. Thank you for sharing your instrument!"
shared_library_96 = "Please fill out all required fields for this instrument."
shared_library_97 = "I do NOT agree"
shared_library_98 = "I agree"
shared_library_99 = "Thank you for your library submission. Sometimes people submit instruments by mistake, so to improve efficiency in the review process, <u>please read and check the boxes</u> to indicate your understanding."
shared_library_100 = "If approved, REDCap users will be able to add this instrument into their projects via the Online Designer."
shared_library_101 = "This is not a method for survey distribution. Contact your local support team with any questions relating to that."
shared_library_102 = "Instruments that are copyrighted by someone else must be submitted through the recommendation link on the library page. Not here."
shared_library_103 = "No, please cancel my submission request"
shared_library_104 = "Yes, please add this instrument to the library collection"
system_config_01 = "System Values"
system_config_02 = "System Status"
system_config_03 = "If 'offline', normal users will be denied access to all pages."
system_config_04 = "SYSTEM OFFLINE"
system_config_05 = "SYSTEM ONLINE"
system_config_08 = "None (Public)"
system_config_09 = "Table-based"
system_config_12 = "Allow normal users to create new projects?"
system_config_13 = "Setting it to 'no' will allow only Administrators to create new projects and will provide a 'Request New Project' feature to users, where they can send a request to an admin that a project be created for them."
system_config_14 = "No, only Administrators can create new projects"
system_config_15 = "Yes, normal users can create new projects"
system_config_16 = "Allow normal users to move projects to production?"
system_config_17 = "Setting it to 'no' will allow only Administrators to move projects to production and will provide a 'Request To Move to Production' option to users, where they can request to an admin that a project be moved to production."
system_config_18 = "No, only Administrators can move projects to production"
system_config_22 = "Minutes, 0 = timer off"
system_config_27 = "Enabled"
system_config_28 = "Automatically send basic statistics to REDCap Consortium?"
system_config_30 = "No, send stats manually"
system_config_31 = "Yes, send stats automatically"
system_config_32 = "Login Page: Disable autocomplete feature in user's browser for username/password fields on REDCap login page?"
system_config_33 = "Disabling autocomplete increases security during login, especially for public computer usage."
system_config_34 = "Disable autocomplete"
system_config_35 = "Allow autocomplete"
system_config_38 = "Custom message when creating/copying project"
system_config_39 = "(Pop-up window of customized text that you wish your users to read to serve as notice/certification before creating or copying a project.)"
system_config_40 = "Custom message when moving project to production"
system_config_41 = "(Pop-up window of customized text that you wish your users to read to serve as notice/certification before moving a project to production.)"
system_config_44 = "Shibboleth Username Login Field"
system_config_45 = "None"
system_config_46 = "URL for Shibboleth Logout Page"
system_config_47 = "(Full URL with qualifiers)"
system_config_52 = "ENABLE SEND-IT: Enable the 'Send-It' application, which allows users to upload and send non-project files, as well as to send files uploaded into a project's File Repository or data entry pages (via 'File Upload' field types)?"
system_config_53 = "All files uploaded for Send-It will be deleted from the server at the time of expiration."
system_config_54 = "Enabled for all locations"
system_config_55 = "Enabled only for REDCap home page"
system_config_56 = "Enabled only for project file repository and forms"
system_config_61 = "If blank, then the following default path is used:"
system_config_63 = "For security reasons, it is recommended that you set this to a folder that is not accessible over the web."
system_config_64 = "Example:"
system_config_65 = "If blank, then uses server default"
system_config_67 = "Manually set the maximum file size (in MB) for files uploaded by users for Edoc files?"
system_config_68 = "How do I change my server default of"
system_config_69 = "Your web server's default maximum file upload size is determined by two values in your server's PHP.INI configuration file: 'upload_max_filesize' and 'post_max_size'. The lowest of either of these two values becomes your default maximum upload size. To change your upload max, open PHP.INI, modify one of these two values, then restart your web server."
system_config_70 = "Send-It upload max file size"
system_config_71 = "Manually set the maximum file size (in MB) for files uploaded by users for Send-It?"
system_config_72 = "Home Page Values"
system_config_77 = "Contact name to display on Home page"
system_config_78 = "Contact name email"
system_config_79 = "Grant name to display on Home page"
system_config_80 = "(If grant is funding REDCap)"
system_config_83 = "Footer Values for All Project Pages"
system_config_84 = "Footer Links"
system_config_85 = "To display links at the bottom of project pages, for each link enter its URL followed by a comma and then the link text. Separate each link with one link per line by hitting the Enter key (although some may spill over into multiple lines)."
system_config_86 = "Footer Text"
system_config_87 = "Custom text displayed at very bottom of page beneath the Footer Links."
system_config_88 = "Default Values for New Projects Created"
system_config_90 = "Language for text displayed within project"
system_config_92 = "REDCap Administrator for project(s)"
system_config_97 = "Name of Institution"
system_config_98 = "Name of Organization at Institution (if applicable)"
system_config_100 = "leave blank if none"
system_config_102 = "Max width: 650 pixels"
system_config_103 = "Allow normal users to edit their first name and last name on their Profile page once those values have been set?"
system_config_104 = "This feature may be used in environments that restrict users in certain ways (e.g., 21 CRF Part 11 environment). Normal users will still be able to edit their email address or (when using Table-based authentication) reset their password, and Administrators will still be able to edit their first/last name regardless."
system_config_105 = "Do not allow editing"
system_config_106 = "Allow editing"
system_config_107 = "If you wish to translate the English text in REDCap into a new language and create a new language file, you may go to the"
system_config_108 = "page and follow the instructions. To download any already translated language files in order to utilize them in REDCap, visit the"
system_config_109 = "Language files are located on the server at"
system_config_110 = "Allows users to download forms from the"
system_config_111 = "to import those forms into their project on the Online Designer page."
system_config_112 = "Language Displayed for Global Pages"
system_config_113 = "Since you are changing the global language value, you may also want to change the default value for new projects (see the top of the Default Project Settings page)."
system_config_114 = "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. For details on the capabilities of the REDCap API and how to use it, please see the"
system_config_115 = "keywords"
system_config_116 = "Keywords that will be used for querying which fields might be identifiers in the module"
system_config_117 = "Please delimit each keyword using a comma, semi-colon, or line break."
system_config_120 = "Number of failed login attempts before user is locked out for a specified amount of time, which is set below."
system_config_121 = "0 = Disabled"
system_config_122 = "Amount of time user will be locked out after having failed login attempts exceeding the limit set above."
system_config_123 = "Minutes, 0 = Disabled"
system_config_124 = "The REDCap DTS module allows data to be pushed into REDCap projects from external systems (e.g., electronic medical record system, electronic data warehouse) and provides an adjudication process whereby REDCap users approve all incoming data from DTS before it is officially saved in their REDCap project. DTS must be installed and configured beforehand in order for it to function when enabled on this page. Once enabled globally here, DTS can then be enabled for individual REDCap projects on the Edit Project Settings page. For installation and setup instructions, please contact the developers at Oregon Health & Science University that created DTS."
system_config_125 = "Enable the REDCap DTS module for this specific REDCap project. Once DTS has been installed, configured, and enabled for this project, a new link will appear on the My Projects page letting users know if there is any new data from the external system that needs to be adjudicated."
system_config_126 = "DTS cannot be enabled for any REDCap project until the global DTS setting has been enabled on the Modules Configuration page in the Control Center."
system_config_127 = "Login Logo"
system_config_128 = "URL for custom logo to be displayed when user logs in to REDCap (max width: 750 pixels)"
system_config_129 = "Display the custom logo and institution name at the top of every page for project?"
system_config_136 = "Enforce password re-use limit?"
system_config_137 = "If set to 'Yes', it will not allow users to use their 5 most recent passwords as the value of a new password."
system_config_138 = "Force users to change their password after a specified number of days."
system_config_139 = "Users will be prompted to change their password before the expiration occurs."
system_config_140 = "Days, 0 = Disabled"
system_config_142 = "NOTE: Tabled-based users will have their individual value set manually by an administrator when their account is created, so this primarily applies to external authentication methods (e.g., LDAP, Shibboleth)."
system_config_143 = "Display the Today/Now button for all date and time fields on forms/surveys?"
system_config_144 = "If enabled, a 'Today' button will be displayed to the right of all date fields, and a 'Now' button will be displayed to the right of all time, datetime, and datetime_seconds fields. Clicking the button will automatically set the field's value with the current date or time."
system_config_146 = "Yes, normal users can move projects to production"
system_config_155 = "All project types have been disabled!"
system_config_156 = "System-level User Settings"
system_config_158 = "Additional Shibboleth Authentication Settings:"
system_config_160 = "Auto logout time"
system_config_161 = "Users will get a two-minute warning before they are automatically logged out if they do not have any activity in REDCap after this amount of time."
system_config_162 = "Additional Table-based Authentication Settings:"
system_config_163 = "By default, allow new users to create projects or request that projects be created for them? (applies to all authentication methods)"
system_config_171 = "When this option is enabled, users creating a survey can set the option for survey respondents to view ALL survey results in aggregate graphical format and/or as descriptive statistics after the respondent has completed the survey. This option appears when a user clicks the Set Up Survey or Modify Survey Settings button on the Project Setup page."
system_config_172 = "Settings for graphical data and statistics display:"
system_config_174 = "NOTE: This option enables the module for every REDCap project."
system_config_176 = "Allow survey respondents to view aggregate survey results?"
system_config_178 = "SET LOCAL FILE STORAGE LOCATION:"
system_config_179 = "Upload max file size for 'file' field types on forms/surveys"
system_config_180 = "File Repository upload max file size"
system_config_181 = "Manually set the maximum file size (in MB) for files uploaded by users in the File Repository?"
system_config_182 = "ENABLE FILE UPLOADING FOR THE FILE REPOSITORY MODULE: Allows users to upload files into the File Repository."
system_config_183 = "If disabled, all data export files will still be stored in the File Repository. This setting only affects the ability for users to manually upload files to that location."
system_config_185 = "Allow users to edit survey responses?"
system_config_186 = "If enabled, users can be granted privileges (via the User Rights page) to edit survey responses that have been either partially or fully completed by a survey respondent."
system_config_187 = "If using a proxy server, please specify the proxy server hostname and port."
system_config_188 = "If using a non-standard port, then append a colon and port number to the end of the hostname. Also, make sure to prepend http:// or https:// to the hostname."
system_config_189 = "<b>NOTE:</b> If you wish to obtain an API token, which will allow you to make API requests, then someone must first grant you API user privileges on the User Rights page, after which you will then see a link called 'API' on the left-hand menu. That API page will provide instructions on how to request an API token."
system_config_190 = "Allow normal users to add or modify events and arms on the Define My Events page for longitudinal projects while in production status?"
system_config_191 = "NOTE: Even if set to 'Yes', Administrators will still be the only ones who can delete events while in production."
system_config_192 = "No, only Administrators can add/modify events in production"
system_config_193 = "Yes, normal users can add/modify events in production"
system_config_194 = "Custom login text"
system_config_195 = "HTML may be used in order to adjust the style of the text or to display links, images, etc."
system_config_196 = "Custom text to display on the login page (It will appear above the login form, and if a login logo is used, it will appear immediately below the logo.)"
system_config_198 = "Allow production Draft Mode changes to be approved automatically under certain conditions?"
system_config_199 = "This refers to when users submit their changes made in Draft Mode to a REDCap admin for approval. If certain conditions are met regarding their changes, REDCap will approve those changes automatically without an admin having to approve them."
system_config_200 = "Never (always require an admin to approve changes)"
system_config_201 = "Yes, if no existing fields were modified"
system_config_202 = "Yes, if project has no records OR if has records and no critical issues exist"
system_config_203 = "Yes, if project has no records OR if has records and no existing fields were modified"
system_config_204 = "Yes, if no critical issues exist"
system_config_205 = "NOTE: For all options above, a REDCap administrator is still required to review changes made in Draft Mode if any critical issues exist AND the project contains one or more records."
system_config_206 = "STORAGE LOCATION OF UPLOADED FILES: You may choose to store the files uploaded in REDCap in a local directory on your web server or on a <u>separate</u> server."
system_config_207 = "NOTE: The 'Local' option may also include a directory on a separate server (e.g., NFS, NAS) that is mapped as a local directory on your REDCap web server."
system_config_208 = "Local (on REDCap web server)"
system_config_209 = "External server using WebDAV (SSL supported)"
system_config_211 = "If using a separate server for storage via WebDAV, you must set up the configuration in"
system_config_213 = "If using 'Local' storage option, you may set an alternative location for storage of uploaded files (otherwise it will default to 'edocs' folder)."
system_config_214 = "File Upload Settings"
system_config_215 = "The settings below pertain to files uploaded by users in several different modules in REDCap. Please note that ALL uploaded files are stored on your local REDCap web server (or an external server, if not using 'Local' setting)."
system_config_216 = "ENABLE 'FILE UPLOAD' FIELD TYPES: Enable document uploading for individual project records on forms/surveys?"
system_config_217 = "If disabled, this choice will not appear as an available field type for users to utilize. Any 'File Upload' fields already created before being disabled will no longer be functional when viewed on forms/surveys."
system_config_219 = "'File Upload' Fields"
system_config_220 = "Explanation of options above:"
system_config_221 = "The options above go from most strict to least strict (top to bottom) with regard to when they allow automatical approval. If option 1 is selected, REDCap admins will always have to review and approve all production changes made by users. Option 2 will permit auto-approval ONLY if new fields are being added to the project (or if fields are simply reordered), while Option 3 will permit auto-approval if the project has no records OR if only new fields are being added (i.e. no existing fields were modified). Option 4 will NOT permit automatic approval if any critical issues exist (e.g., fields deleted, multiple choice options deleted, field type changed), while Option 5 will NOT permit automatic approval if BOTH the project has records AND critical issues exist. NOTE: If a project has no records, then the auto-approval process will behave just the same if using either option 3 or 5; however, options 3 and 5 behave very differently if a project does contain one or more records."
system_config_222 = "For details on each authentication method, see the"
system_config_223 = "REDCap Community website's authentication page"
system_config_224 = ", which describes them and lists how to install, configure, and enable each in REDCap."
system_config_225 = "When enabled, it will display the option to utilize the Randomization module for new or existing projects. When disabled, the option will remain completely hidden, and the Randomization module will stay hidden in each project and cannot be used."
system_config_226 = "Custom text to display at the top of the Help & FAQ page."
system_config_228 = "Authentication Method"
system_config_229 = "Used for all global pages and as default authentication for newly created projects"
system_config_230 = "Yes, display the logo and institution/organization name"
system_config_231 = "No, hide the logo and institution/organization name"
system_config_232 = "Domain allowlist for user email addresses"
system_config_233 = "You may limit the kinds of email addresses that users associate with their REDCap account by specifying one or more domain names (e.g., vanderbilt.edu) that will serve as an allowlist of the only acceptable domains that email addresses may have."
system_config_234 = "Separate each domain on a different line. See example below."
system_config_235 = "An error exists in the field 'Domain allowlist for user email addresses', in which the items listed below are not valid domain names. Please fix the invalid domain names below and try again. Remember that only one domain should be entered per line."
system_config_236 = "Invalid domains:"
system_config_237 = "Enable the use of surveys in projects?"
system_config_239 = "(Proxy setting is ONLY used for outgoing requests from the server.)"
system_config_240 = "Custom message to display to users when system is offline:"
system_config_241 = "View user info for"
system_config_242 = "AMAZON S3 STORAGE SETTINGS: If using 'Amazon S3' as your storage option, set the values for your AWS access key, secret key, and the name of the 'bucket' where all REDCap files should be stored in S3."
system_config_243 = "AWS Access Key:"
system_config_244 = "AWS Secret Key:"
system_config_245 = "Bucket:"
system_config_251 = "(see custom settings below)"
system_config_253 = "instructions for cURL/libcurl installation here"
system_config_254 = "CANNOT USE AMAZON S3 FOR FILE STORAGE!"
system_config_258 = "Show secret key"
system_config_259 = "HTTP compression of web pages"
system_config_260 = "This can make REDCap's pages load 2x-5x faster because it compresses the HTML output of each page."
system_config_264 = "NOTE: HTTP compression *cannot* be enabled on your server because it appears that you do not have the Zlib extension installed in PHP on your web server. To take advantage of this feature, you need to install the "
system_config_265 = "Rate Limiter:<br>Page hit threshold for a single IP address"
system_config_266 = "Maximum number of web requests per minute that are allowed from a single IP address when accessing a specific REDCap project (or a non-project page). If it is exceeded, that IP address will be permanently banned, thus preventing the user from accessing REDCap from that IP address again, and an administrator will be sent an email notification regarding this. This is to prevent bots or hackers from attempting an attack on the server."
system_config_267 = "requests per minute per IP"
system_config_268 = "Password recovery custom text"
system_config_270 = "If left blank, the following text will be displayed instead:"
system_config_275 = "Announcement text to display at top of Home page and My Projects page"
system_config_276 = "Informational text to display at bottom of Home page only"
system_config_277 = "Text will appear inside a gray box below the paragraph text at bottom of Home page."
system_config_278 = "This setting is most effectively used to make announcements to users so it is the first thing they see after logging in. Examples include upcoming server downtime, information about training classes, announcements of new REDCap features, etc."
system_config_290 = "Display Formats for Dates, Times, and Numbers (default setting for new users)"
system_config_291 = "Default Settings for New Users"
system_config_292 = "General User Settings"
system_config_293 = "Character encoding for exported files"
system_config_294 = "Used for PDFs and CSV export files in the project"
system_config_295 = "Default Encoding (ANSI or UTF-8, if detected)"
system_config_296 = "Japanese (Shift JIS)"
system_config_298 = "If not explicity using a language listed in the drop-down above, then use the Default Encoding option."
system_config_299 = "REDCap Hooks"
system_config_301 = "To utilize REDCap hooks, you must specify the full file path to your Hook Functions file, which is a PHP file on your REDCap web server that contains all your hook functions. You may place the Hook Functions file in any directory you wish, and you may name it anything you wish. Once you have created it, provide its full file path here so that REDCap may then begin to utilize any hook functions inside it. For more info on REDCap hooks, see the documentation by clicking the 'Plugin, Hook, & External Module Documentation' link on the left-hand menu"
system_config_302 = "Full path to your PHP file containing your REDCap hook functions"
system_config_303 = "Additional SAMS Authentication Settings:"
system_config_304 = "URL for SAMS Logout Page"
system_config_308 = "Custom Project Settings (will overwrite system values)"
system_config_309 = "All the fields below may be left blank, in which case the global/system-level value for each will be used in its place. But if you wish to override the global value with one for this specific project, then just add a value to the field below. This can be used to add a custom logo for a specific project, for example. The global value for each field is listed directly beneath it below."
system_config_310 = "Global value:"
system_config_311 = "[blank]"
system_config_312 = "URL for Custom Logo to be displayed at top of each project page (optional)"
system_config_314 = "PROMIS instruments"
system_config_315 = "The CATs are generated dynamically using the API software developed by the"
system_config_316 = "and are provided by the"
system_config_317 = "Test the service:"
system_config_318 = "If the test above fails, then it means your server cannot make contact with the CAT server hosted by Vanderbilt University. If you have a firewall that is blocking outbound requests, you may need to have it allow outbound requests for the following URL:"
system_config_319 = "ERROR: You cannot utilize a PROMIS computer adaptive test (CAT) because that feature has been disabled this installation of REDCap. In order to utilize PROMIS CATs, a REDCap administrator must enable this feature on the Modules/Services Configuration page in the REDCap Control Center."
system_config_320 = "REDCap could not communicate successfully with the Assessment Center API web service hosted by Vanderbilt University. Please notify your local REDCap administrator about this issue."
system_config_321 = "Administrator message: If you have a firewall that is blocking outbound requests from your REDCap web server, you may need to have it allow outbound requests for the following URL:"
system_config_322 = "NOTE: The data sent from REDCap to the Assessment Center API service hosted by Vanderbilt University is de-identified and cannot be connected back to any individual respondent."
system_config_323 = "Enable the service for displaying plots and generating statistics for this project module, or disable the module altogether."
system_config_324 = "Name of the server variable that contains the user's username that Shibboleth defines in PHP (e.g. $_SERVER['REMOTE_USER'])"
system_config_325 = "Set a Universal FROM Email address for ALL emails sent from REDCap (optional)"
system_config_326 = "Leave this blank (default) to have all emails sent from REDCap have the 'From' address be that of the sender. If an email address is provided above, then *all* emails will have it as the 'From' address (although all emails will still have the 'Reply-To' value as the sender). This option is useful if your SMTP email server refuses to send emails from an external domain address (e.g., Gmail, Yahoo)."
system_config_328 = "Enable the Field Comment Log by default in new projects?"
system_config_329 = "If enabled, any new project created will have the Field Comment Log initially enabled in the project. It can be disabled after the fact, if desired, in the Additional Customizations section of the project's Project Setup page."
system_config_330 = "The REDCap Mobile App is an app that can be downloaded onto a tablet or mobile device to allow REDCap data to be collected locally on that device without the need for an internet connection (either wifi or cellular signal). If a user downloads the app, they must explicitly be given mobile app privileges in a given REDCap project in order to set up the project on the app. Once a project has been set up on the app, data can be collected in an offline fashion and then later synced back to the REDCap server."
system_config_331 = "Two-step verification for REDCap login"
system_config_336 = "SMS Message"
system_config_337 = "Send an SMS text message containing your verification code to the phone number below (standard message and data rates apply)."
system_config_338 = "Email"
system_config_339 = "Send an email containing your verification code to your email account."
system_config_343 = "Sorry, but you did not enter a valid verification code. Please try again."
system_config_347 = "Invalid code!"
system_config_349 = "Send to"
system_config_350 = "Two-Factor Authentication"
system_config_352 = "Authentication Settings (System-level)"
system_config_353 = "Login Settings"
system_config_354 = "(recommended for improved security)"
system_config_362 = "Test Twilio credentials"
system_config_363 = "ERROR: One or more of the Twilio credentials is missing!"
system_config_364 = "Success! All the Twilio credentials were verified and are correct."
system_config_366 = "Your REDCap verification code is"
system_config_368 = "Sent!"
system_config_369 = "Failed!"
system_config_373 = "2) Open the app, and scan this QR code"
system_config_375 = "Before using this feature, you must first set up a Twilio account and obtain the required info below."
system_config_376 = "How do I do this?"
system_config_377 = "The 'SMS' option for two-factor authentication utilizes a third-party web service called Twilio. To use this feature, you must have a Twilio account, which must be funded with money (since there is a cost for each SMS message sent). Before you begin the setup steps for Twilio SMS on this page, you must <b>1) set up your own Twilio account</b> at"
system_config_378 = "Once your Twilio account has been created, you must <b>2) fund your account with some money</b> (using the Billing page in Twilio) and then <b>3) purchase a phone number</b> to be used for this REDCap project (see the Numbers page in Twilio)."
system_config_379 = "Once a phone number has been purchased for the account, obtain the Account SID and Auth Token for your account (see the API Credentials section on the main Account Settings page), and then enter the Account SID, the Auth Token, and the phone number into the 'Twilio configuration settings' on this page. And as a final measure, click the 'Test Twilio credentials' button, which will verify the credentials entered to ensure that they will work and send SMS messages successfully."
system_config_381 = "Additional Google OAuth2 Authentication Settings:"
system_config_382 = "Google API Client ID"
system_config_383 = "Google API Client Secret"
system_config_384 = "In order to use Google OAuth2 authentication, you must 1) go to the"
system_config_385 = "and create a new project on that webpage (you may name the project whatever you wish (e.g. \"REDCap Auth\"). Note: You may want to avoid logging in to that page using your personal Google account since you will be creating Google API credentials used by REDCap at your institution. 2.) Once you have created the new project on the Google Developers Console webpage, select 'Credentials' under the 'APIs & auth' section on the left-hand menu. On the Credentials page under the OAuth section, click the button to create a new Client ID, and select the 'web application' as the application type. On the next screen, all you have to provide is the Product Name (e.g., 'REDCap'), and click the Save button. You may leave the 'Authorized JavaScript Origins' box blank (it is not needed here), but be sure to enter the following URL into the 'Authorized Redirect URIs' text box (ending both with and without a backslash):"
system_config_386 = "3.) Once the Client ID has been created, it will auto-generate a Client ID name and a Client Secret. Copy those values into the text fields below so that REDCap may use them to authenticate with Google."
system_config_387 = "Google OAuth2 setup instructions:"
system_config_388 = "Computer adaptive tests (CATs)<br>and Auto-scoring instruments"
system_config_389 = "If enabled, users will be able to download CATs and Auto-scoring instruments from the REDCap Shared Library, and then use them in their project as a survey that is driven by a third-party service (i.e., another web server). If not enabled, users that navigate to the Shared Library will have all these types of instruments hidden, thus preventing users from downloading them. These include"
system_config_390 = "Neuro-QoL instruments"
system_config_391 = ", among others,"
system_config_392 = "Allow embedding of videos on data entry forms and survey pages?"
system_config_393 = "If enabled, the Online Designer will allow users to supply a video URL for a Descriptive field on a form or survey, in which it will provide a button that, when clicked, will play the embedded video inside a popup dialog. This features allows any video URL to be used from any video hosting website (although it is most compatible with YouTube and Vimeo)."
system_config_394 = "Allow text-to-speech functionality to be enabled for surveys?"
system_config_396 = "(not applicable to Shibboleth authentication)"
system_config_397 = "Allow auto-suggest functionality for searching biomedical ontologies for fields on data entry forms and surveys?"
system_config_398 = "This service utilizes the BioPortal API web service (see documentation at http://bioportal.bioontology.org). For this feature to work, the REDCap web server must be able to make outbound HTTP requests to"
system_config_399 = "If you do not yet have a BioPortal API token, you can"
system_config_400 = "obtain a token here"
system_config_401 = "The service will not function without a valid API token."
system_config_402 = "Alternative REDCap survey base URL (leave blank if same as REDCap base URL above)"
system_config_403 = "This base URL will only be used when constructing survey URLs (e.g., when sending invitations to survey participants). For all other URLs in REDCap, the REDCap base URL will be used. This feature can be useful if you wish to use a different web address for surveys than for the web address where users log in (e.g., when using a reverse-proxy server or separate web server for surveys)."
system_config_404 = "Survey base URL (optional)"
system_config_405 = "(Optional) Enable the Twilio SMS option for two-factor authentication?"
system_config_408 = "(Optional) Enable the Duo for two-factor authentication?"
system_config_409 = "If enabled, the 'SMS' option can be used for two-factor auth, in which an SMS text message containing the 6-digit verification code can be sent to a user's mobile device using the Twilio web service."
system_config_410 = "Before using this feature, you must first set up a Duo account and obtain the required info below."
system_config_411 = "Duo configuration settings"
system_config_412 = "Duo Integration key"
system_config_413 = "Duo Secret key"
system_config_414 = "Duo API hostname"
system_config_415 = "Show secret key"
system_config_416 = "If enabled, the 'Duo' option can be used for two-factor auth, in which the Duo mobile app or website is utilized for completing the login process."
system_config_417 = "The 'Duo' option for two-factor authentication utilizes a third-party web service called Duo. To use this feature, you must have a Duo account. Before you begin the setup steps for Duo on this page, you must <b>1) set up a Duo account</b> at"
system_config_418 = "Once your Duo account has been created, you must <b>2) go to the Duo Admin Panel and create a new Application</b> (see the Applications item on the left-hand menu of that page) if you do not already have an application created, <b>3) set the application type as 'Web SDK'</b>, and 4) <b>give it a name</b> (e.g., 'REDCap production') and save it."
system_config_419 = "Once the application has been created for the account, obtain the Integration key, Secret key, and API hostname for that application. Then enter those values into the 'Duo configuration settings' on this page and save them."
system_config_420 = "Duo"
system_config_421 = "Use Duo Push on the Duo mobile app, or alternatively use the SMS passcode or phone call method."
system_config_423 = "Enforce two-factor authentication only for certain IP addresses?"
system_config_425 = "Enforce on all users"
system_config_426 = "Enforce on all users EXCEPT those whose IP is in a range below"
system_config_427 = "Also include all private network IP addresses in the IP exceptions"
system_config_428 = "IP address exceptions:"
system_config_432 = "Select an option below to complete the second half of REDCap's two-step verification login process. You will not be able to access REDCap until you have completed this verification step."
system_config_433 = "Enter your verification code"
system_config_434 = "Enter the verification code that you obtained from"
system_config_439 = "Sending..."
system_config_440 = "Select option for two-step verification."
system_config_441 = "REDCap two-step login"
system_config_451 = "3) Use the app when you log in to REDCap"
system_config_452 = "Mobile phone number"
system_config_454 = "No phone number"
system_config_455 = "Not available"
system_config_456 = "To complete the REDCap login process, enter the verification code"
system_config_457 = "REDCap 2-step login"
system_config_458 = ", or just REPLY WITH ANY TEXT to this message."
system_config_459 = "(Optional) Enable the email option for two-factor authentication?"
system_config_460 = "If enabled, the email option can be used for two-factor auth, in which the user can obtain the 6-digit verification code via their primary email that is registered in their REDCap account."
system_config_461 = "In most cases, it is good to leave this option enabled as a last resort for users just in case they are not able to use any of the other options for whatever reason."
system_config_462 = "Days, 0 = Disabled"
system_config_464 = "If enabled, a user performing two-factor login will be given the option to have their device/computer be remembered for X days during which they will not have to perform two-factor login but only log in with their username/password."
system_config_466 = "Two-factor settings:"
system_config_467 = "Two-factor login options:"
system_config_474 = "Phone Call"
system_config_475 = "Make a call to the phone number below."
system_config_476 = "Call"
system_config_477 = "This option cannot be used because you do not have a phone number associated with your REDCap account. A phone number can be added to your account on your Profile page in REDCap *after* you log in using one of the other methods on this page."
system_config_478 = "Phone number"
system_config_481 = "Calling your phone"
system_config_483 = "TIP: Instead of using email for 2-step login, you can alternatively have REDCap send you an SMS text message or call your phone. To set this up, *after* logging into REDCap using the code above, go to your Profile page (see link at top right of My Projects page) and add your phone number(s) to your user account."
system_config_484 = "ERROR: The 'SmsUrl' value for your phone number on your Twilio account is not correct and must be corrected to allow users to respond to SMS message's sent to them for Two-Factor Authentication. To fix this, simply go to the Twilio section below on this page, and click the 'Test Twilio credentials' button OR just click the Save button at the bottom of this page."
system_config_485 = "ERROR: The IP addresses listed below are not valid and must be corrected if you wish to use them in the IP ranges for two-factor authentication:"
system_config_486 = "Tip: To enter a number with an extension, place a comma between the number and the extension."
system_config_487 = "TIP: Enter your phone number on the Profile page"
system_config_488 = "It appears that you do not yet have any phone numbers associated with your REDCap user account."
system_config_490 = "Never display this message again"
system_config_491 = "Performing 2-step login in REDCap can be faster and easier when using the SMS or Phone Call options."
system_config_492 = "You may add up to two phone numbers to your user account on the Profile page to begin using the SMS or Phone Call options for 2-step login. Click the button below to go to your Profile page now."
system_config_493 = "NOTE: The email will originate from your administrator account"
system_config_500 = "Don't prompt me with two-step login on this computer for"
system_config_501 = "Two-Factor Authentication Settings:"
system_config_502 = "Exempt the project from 2-step login?"
system_config_503 = "No, enforce 2-step login when applicable (default)"
system_config_504 = "Yes, this project is exempt from 2-step login"
system_config_505 = "If set to 'Yes', then users with access to at least one exempt project will not see the 2-step login page when they initially log in to REDCap, nor will they see it when they enter an exempt project, but they *will* see the 2-step login page if they attempt to enter a regular (non-exempt) project or navigate to their Profile page."
system_config_506 = "Always force 2-step login in this project for EVERY login session?"
system_config_507 = "Can be used to disable 2-step login for projects in which the extra login step might make the project difficult to use or because it is not needed, for example."
system_config_508 = "Yes, make sure users have done 2-step login before entering project"
system_config_509 = "Can be used for projects containing very sensitive data (such as clinical data) in order to enhance the security of the project above the normal REDCap 2-step login security standards."
system_config_510 = "NOTE: This option is only useful if you have set the system's optional 2-step login Authentication Interval to a value other than '0'."
system_config_511 = "If set to 'Yes', then if a user has not had to perform the 2-step login during their current REDCap session (because they had logged in via 2-step login in a previous session), then it will force them to do the 2-step login before entering this project."
system_config_512 = "Exempt from 2-step login"
system_config_514 = "If you're having trouble scanning the QR code, enter the values below into your Google Authenticator app using the Manual Entry method. Also, make sure you set it as 'Time-based'."
system_config_515 = "Account:"
system_config_516 = "Key/secret:"
system_config_517 = "Authentication interval: Trust a device's two-factor login for X days?"
system_config_518 = "(Optional) Secondary authentication interval for specific IP address ranges"
system_config_519 = "If desired, you can set an alternative authentication interval for devices in certain IP ranges. For example, you may want to set the interval to 30 days for users on a semi-secure network but set it to 1 day for users not on a secure network at all. You can set the interval to X days that the user's device will be trusted if within a given IP range."
system_config_520 = "Apply the authentication interval above to these IP ranges only:"
system_config_521 = "(Use decimals for partial days)"
system_config_522 = "Require 2-step verification when users log in to REDCap."
system_config_523 = "Enabling two-factor authentication (also known as 2-step login) can provide greater security with regard to users logging in to the system. While the standard login process consists of entering a username and password, two-factor authentication provides a second step after the initial login, such as entering a 6-digit verification code received via SMS text message, via email, or generated using the Google Authenticator app on their mobile device, or responding to a phone call or a push notification (for Duo app only). Two-factor authentication can be set up and enabled using the settings below, which govern how and when users will be required to go through the 2-step login process."
system_config_524 = "(This code will expire in"
system_config_525 = "minutes.)"
system_config_526 = "(Applies to verification code for SMS, email, and Google Authenticator options)"
system_config_528 = "The API Playground is an interface that allows experimentation with the REDCap API without actually writing any code. You can explore all the different API methods and their various options to customize a given API request. You may even execute a real API request and see the exact response that REDCap returns from the request. If you are interested in creating an API script, the section at the bottom will provide code samples for various programming languages to give you a head start. For details on the capabilities of the REDCap API and how to use it, please see the"
system_config_529 = "Contact person web address/URL (optional)"
system_config_530 = "You may provide a URL that will be linked on the Home page and login page *instead* of the contact email above. This is useful if you have a ticket system at your institution that you would prefer to use rather than an email account. If left blank, then it will display a link on the Home page using the contact email above."
system_config_531 = "Server configuration settings"
system_config_532 = "Other system settings"
system_config_533 = "If using a proxy server that requires username-password authentication, provide the username and password separated by a colon."
system_config_534 = "This features allows users to enable text-to-speech functionality in any given survey, in which text on the survey page can be read out loud audibly by the computer. This service utilizes a service hosted at Vanderbilt University that utilizes the IBM Watson Text-to-Speech API service, and thus will send all displayed survey text (e.g., survey instructions, field labels, choice labels) from the REDCap server to the Vanderbilt-hosted service. This means that the REDCap web server must be able to make outbound HTTP requests to <b>https://redcap.vumc.org</b> in order for this service to work."
system_config_538 = "see custom settings below"
system_config_539 = "Bucket for storing REDCap files:"
system_config_540 = "Bucket for storing temporary files (must be different than bucket above):"
system_config_541 = "The two buckets below cannot have the same name. They must be different."
system_config_542 = "GOOGLE CLOUD STORAGE SETTINGS: If REDCap is hosted on Google Cloud Platform, you must use the Google Cloud Storage option for storing files. Provide the names of two buckets in GCS (one to serve as a temporary file storage, and the other for permanent storage of REDCap files)."
system_config_543 = "Other Security Settings:"
system_config_544 = "Domain allowlist for cross-domain HTTP access control (optional)"
system_config_545 = "By default, for flexibility purposes, AJAX requests (via JavaScript) can be made to REDCap from any domain/URL. If you wish to restrict this so that only certain domains can make cross-domain AJAX requests to REDCap, then you will need to set the domain name of all allowed access control origins (i.e., the domain of the URLs) in the text box to the right. If the text box is left blank (default), then any domain will be able to make cross-domain AJAX requests to REDCap. Restricting access control to specific domains is generally considered to make REDCap more secure to prevent against possible Cross-Site Scripting attacks by malicious users."
system_config_546 = "Leave blank to allow cross-domain access from any domain. Only enter the domain name (not a full URL) with each domain on a separate line."
system_config_547 = "Enable the project XML export functionality (i.e., project backup)?"
system_config_548 = "If enabled (default), users will be able to download a backup of their entire project as a single XML file (CDISC ODM format), which could be used to create a clone of the project (including its data, optionally). This option will be shown on the Other Functionality tab of the 'Project Setup' page and also on the Other Export Options tab of the 'Data Exports, Reports, and Stats' page."
system_config_549 = "Name of REDCap Administrator"
system_config_550 = "Email Address of REDCap Administrator"
system_config_551 = "And also ONLY IF no new fields have labels or variables with matching keywords from the 'Check For Identifiers' page"
system_config_556 = "Local identifier"
system_config_562 = "Mandatory field for AAF authentication"
system_config_564 = "To enable locals to create projects you need a value in the Local Identifier field from aaf edupersonscopedaffiliation to identify locals"
system_config_565 = "Name of grant to be cited (optional) - displayed when users export data"
system_config_566 = "Is this REDCap server a development/test/staging server?"
system_config_568 = "Yes, this a development/test/staging server (non-production)"
system_config_567 = "No, this is a production server"
system_config_569 = "If 'Yes' is selected, then PHP error reporting will be enabled to display all errors to help with debugging purposes on non-production servers."
system_config_570 = "Settings for various modules and services. NOTE: 'Modules' here does *not* refer to External Modules, which you may learn more about by clicking its link on the left-hand menu."
system_config_571 = "Alternate module directories (optional)"
system_config_573 = "Clickjacking prevention"
system_config_574 = "By default, a REDCap page can be embedded in an iframe on a page on any website. In some cases, this is useful, such as embedding surveys into other websites, but there is potential for abuse in which some malicious users may try to trick other users using a technique called clickjacking. If you wish to restrict this so that other websites cannot embed REDCap pages (in order to prevent clickjacking), then you set the option above. If you set it to 'Allow...', then any domain on the web will be able to embed a REDCap page (assuming this REDCap installation is publicly available to the web). Restricting access control from external websites is generally considered to make REDCap more secure to prevent against possible clickjacking attacks by malicious users. Technical note: Setting this to 'Prevent...' will force the HTTP header 'X-Frame-Options: SAMEORIGIN' to be added."
system_config_575 = "Prevent clickjacking / prevent external websites from embedding REDCap pages"
system_config_576 = "Allow external websites to embed REDCap pages"
system_config_577 = "If you are developing external modules and wish to store your modules in another directory (not just in the redcap/modules/ directory), you may set one or more directories here. They do not need to be located under the REDCap web root (e.g., 'redcap' directory), and you must provide the full path of the directory. To define multiple alternative directories, separate them with a pipe |."
system_config_578 = "Allow normal users to modify the 'Repeating Instruments & Events' settings for projects while in production status?"
system_config_580 = "No, only Administrators can modify the repeating instance setup in production"
system_config_581 = "Yes, normal users can modify the repeating instance setup in production"
system_config_582 = "ERROR: Sorry, but only REDCap administrators are allowed to modify the 'Repeating Instruments & Events' settings while a project is in production status. Clicking the Save button below will not do anything."
system_config_584 = "2-step login: Email the user the Google Authenticator setup instructions"
system_config_585 = "Send instructions via email"
system_config_586 = "This email applies only to the REDCap user"
system_config_587 = "NOTICE: Once you have set up Google Authenticator, for security purposes, please DELETE THIS EMAIL."
system_config_588 = "View QR code in separate window"
system_config_589 = "AWS Region / Location Constraint:"
system_config_590 = "If left blank, then <b>us-east-1</b> will be used by default. For the list of AWS regions/location constraints, see the following:"
system_config_591 = "This must be the Region/Location Constraint (e.g., ap-northeast-2) and NOT the Endpoint URL."
system_config_595 = "AZURE BLOB STORAGE SETTINGS: If using 'Microsoft Azure Blob Storage' as your storage option, set the values for your storage account name, storage account key, and the name of the 'container' where all REDCap files should be stored in Azure Blob Storage."
system_config_596 = "Azure storage account name:"
system_config_597 = "Azure storage account key:"
system_config_598 = "Azure storage blob container:"
system_config_599 = "Local Server File Storage"
system_config_600 = "File Storage Methods"
system_config_601 = "Storage Configuration Settings"
system_config_602 = "Configuration Options for Various Types of Stored Files"
system_config_603 = "Setup Instructions: <br>1) Log in to Azure at https://portal.azure.com/ <br>2) Go to 'Storage Accounts' on the left-hand menu, and create a new storage account (this 'name' will be your 'Azure storage account name' in REDCap). <br>3) Under that storage account, click the 'Access keys' option on the menu, and copy the first 'Key' value (this will be your 'Azure storage account key'). <br>4) Under that storage account, click the 'Overview' option on the menu, and then under 'Services' click 'Blobs'. Then click '+Container' to create a new container (this will be your 'Azure storage container')."
system_config_604 = "Setup Instructions"
system_config_605 = "The REDCap server has reached a maximum for the number of POST parameters submitted. Due to this error, if any data was just submitted, it was not saved. Please inform your local REDCap administrator that they should increase the 'max_input_vars' setting to a value of 10000 or higher in the web server's PHP.INI configuration file. The current value for 'max_input_vars' is"
system_config_606 = "Display this announcement text on REDCap's login page too?"
system_config_607 = "Allow users to message admins"
system_config_608 = "Prevent users from messaging admins"
system_config_609 = "Delete a record's logging activity when deleting the record?"
system_config_610 = "If enabled, a user deleting a record in the project will be asked if they also want to delete all the data values and actions that have been logged on the Project Logging page for this record, in which the user will have to type 'DELETE' to confirm that they wish to do this. Users will have to choose whether they want to do this on a per-record basis when deleting the record. Note: For multi-arm longitudinal projects, this feature will delete the record's logging for the given record only in the current arm."
system_config_611 = "Yes, delete the record's logged events when deleting the record"
system_config_612 = "No, preserve the record's logged events when deleting the record"
system_config_613 = "This feature can be used to aid in compliance with GDPR or similar regulations that require 'right to erasure'."
system_config_614 = "Settings relating to Data Privacy (e.g., GDPR)"
system_config_615 = "Auto-delete all Data Export Files in the File Repository that were created more than X days ago? (set value greater than '0' to enable)"
system_config_616 = "To keep disabled, leave value '0' or blank."
system_config_617 = "NOTE: This will only delete files under the Data Export Files tab. No other types of files in the File Repository will be deleted."
system_config_618 = "WARNING: Be careful enabling this because, once enabled, the cron job runs every 12 hours to delete these files. So if this feature is left on, it could begin deleting files within several hours or less."
system_config_619 = "Custom footer text for survey pages"
system_config_620 = "Link text (optional):"
system_config_621 = "If link text is provided, it will be displayed as a link at the bottom of all survey pages in the project, and when clicked, it will display the custom text (initally hidden) in a modal dialog. If the link text is not set (left blank), the custom text will instead be displayed inline at the bottom of all survey pages in the project."
system_config_622 = "Custom survey footer text:"
system_config_623 = "Print text below"
system_config_624 = "The features in the section below can be utilized when dealing with data privacy, such as being in compliance with GDPR or similar regulations, that might require 'right to erasure' and/or the need to display a data privacy statement for participants to view."
system_config_625 = "Custom message for e-Consent Framework settings (optional)"
system_config_627 = "Simplified Chinese (UTF-8)"
system_config_628 = "Traditional Chinese (UTF-8)"
system_config_629 = "Allow file attachments to be uploaded for data queries in the Data Resolution Workflow?"
system_config_630 = "If disabled, this will not appear as an available option for users to utilize for an open data query in DRW."
system_config_631 = "Can REDCap server access the web (make outbound HTTP calls)?"
system_config_632 = "If this REDCap server has no internet connectivity or cannot access the outside World Wide Web, then set to 'No'. If it cannot access the web but is left as 'Yes', it could cause some pages/services to be extremely slow or not load."
system_config_633 = "Yes, REDCap server can make outbound HTTP calls to the web"
system_config_634 = "No, REDCap server does not have access to the World Wide Web"
system_config_635 = "Suppress usage of the Universal FROM Email address for specified email domains"
system_config_636 = "By default, the Universal FROM Email address will be used for all outgoing emails, but if one or more domain names (e.g., vanderbilt.edu) are specified here, then the Universal FROM Email address will NOT be used for any outgoing emails in which the FROM/sender's email address matches one of those domains, but instead the FROM/sender's email address will remain as-is."
system_config_637 = "Configuration for Outgoing Emails"
system_config_638 = "TIP: You probably do not want to use this option unless REDCap is unable to send out some or all outgoing emails successfully (often due to email providers blocking emails whose 'From' address does not match the domain name of the REDCap server (e.g., sending an email from joeuser@gmail.com from the server https://redcap.vumc.org)."
system_config_639 = "An error exists in the field 'Suppress usage of the Universal FROM Email address for specified email domains', in which the items listed below are not valid domain names. Please fix the invalid domain names below and try again. Remember that only one domain should be entered per line."
system_config_641 = "Activate external module"
system_config_642 = "Settings pertaining to the External Module Framework"
system_config_643 = "Enable the built-in process for users to request that an External Module be activated for a project?"
system_config_644 = "Yes, show the 'Request Activation' button for all discoverable modules"
system_config_645 = "No, hide the 'Request Activation' button for all discoverable modules"
system_config_646 = "NOTE: Enabling this setting will only display the button for modules that have been made 'Discoverable' in the system."
system_config_647 = "Utilize the Display Name in all outgoing emails?"
system_config_648 = "Yes, include the sender's display name (preferred)"
system_config_649 = "No, do not include the sender's display name"
system_config_650 = "Display names are used in emails to include a person's name (for example) next to the sender's email address in the recipient's email client in order to provide further context regarding the sender's identity. For example, 'Joe User <joe.user@mysite.edu>'. If the display name is excluded/disabled here, then the recipient will merely see the sender's email address in their email client and not the sender's name, and additionally, all options for adding a Display Name in the user interface will be hidden (e.g., for outgoing survey invitations)."
system_config_651 = "REASON FOR USAGE: The display name feature might need to be disabled if your institution is having a disproportionate amount of emails not being received due to email servers blocking them, sometimes due to the usage of the display name. If you are experiencing this kind of issue, we recommend testing both with and without the display name setting turned on in order to test if the display name might be the cause of emails not being received."
system_config_653 = "Additionally, if set to 'Yes', normal users will be able to designate instruments to events on the 'Designate Instruments For My Events' page that have not yet been designated, but they will not be able to un-designate any instruments that are already designated."
system_config_654 = "Settings related to Project Creation and Project Status Changes"
system_config_660 = "Mandrill Email Configuration"
system_config_661 = "Mandrill API Key"
system_config_662 = "When sending outgoing emails, REDCap can utilize the Mandrill API for sending emails as an alternative to using the REDCap web server's default methods that send emails via PHPMailer. You first need to set up an account on the Mandrill website"
system_config_663 = ", which will give you access to an API key that is connected to your MailChimp account. NOTE: You will need to create an account and generate the API token there in order to use it here in REDCap. Follow all instructions on the Mandrill website for obtaining and using the API token."
system_config_664 = "SendGrid Email Configuration"
system_config_665 = "SendGrid API Key"
system_config_666 = "When sending outgoing emails, REDCap can utilize the SendGrid API for sending emails as an alternative to using the REDCap web server's default methods that send emails via PHPMailer. You first need to set up an account on the SendGrid website"
system_config_667 = ", which will give you access to an Email API key that is connected to your SendGrid account. NOTE: You will need to create an account and generate the API token there in order to use it here in REDCap. Follow all instructions on the SendGrid website for obtaining and using the API token."
system_config_668 = "(optional third-party email configuration)"
system_config_669 = "DATABASE CONFIGURATION RECOMMENDATIONS:"
system_config_670 = "Your database configuration settings do not appear to be optimal. For better database performance and stability, consider making the changes below to your database configuration settings in your <code>my.cnf</code> (Linux/Unix) or <code>my.ini</code> (Windows) configuration file."
system_config_671 = "DISCLAIMER: It is <b>extremely important</b> for you to fully understand each change you make to the database server. If you don't understand the recommendations above, you <b>should consult</b> a knowledgeable DBA or system administrator that you trust. <b>Always</b> test your changes on staging environments, and always keep in mind that improvements in one area can <b>negatively affect</b> the database in other areas."
system_config_672 = "IMPORTANT NOTICE: Since the database Uptime is less than 1 day, the performance tuning suggestions listed below may not be accurate. In fact, the recommendations below will be completely useless on a fresh restarted server. PLEASE WAIT AT LEAST 1 DAY AND THEN REVIEW THIS PAGE AGAIN FOR ACCURATE RECOMMENDATIONS AT THAT TIME."
system_config_673 = "Recommendations for the REDCap database server:"
system_config_674 = "TIP: Remember to restart the"
system_config_675 = "service after making any edits to the configuration, otherwise they won't take effect."
system_config_679 = "Primary Admin"
system_config_680 = "Secondary Admin"
system_config_682 = "The first time this user logs in, they will be given full admin privileges."
system_config_683 = "Same as above, just a backup admin. The first time this user logs in, they will be given full admin privileges."
system_config_684 = "Use default system setting (MOST COMMON)"
system_config_685 = "Manually set the MySQL/MariaDB <code>binlog_format</code> setting for the REDCap database connection"
system_config_686 = "WARNING: Do not change this from the default setting unless you know what you are doing and are intentional about this. Changing this to an incorrect value for your system configuration may cause catastrophic database issues."
system_config_687 = "Sorry, but the 2-step login settings here cannot both be set to YES for the same project. Only one of them can be used at a time. Your change to this setting has been reverted back to its previous value."
system_config_688 = "Mailgun Email Configuration"
system_config_689 = "Mailgun API Key"
system_config_690 = "When sending outgoing emails, REDCap can utilize the Mailgun API for sending emails as an alternative to using the REDCap web server's default methods that send emails via PHPMailer. You first need to set up an account on the Mailgun website"
system_config_691 = ", which will give you access to an Email API key and Domain Name that is connected to your Mailgun account. NOTE: You will need to create an account and generate the API token there in order to use it here in REDCap. Follow all instructions on the Mailgun website for obtaining and using the API token."
system_config_692 = "Mailgun Domain Name"
system_config_693 = "Password Minimum Length"
system_config_694 = "Value entered should be integer (between 6 and 99).<br>If left blank, will default to the value 9."
system_config_695 = "Password Complexity"
system_config_696 = "Requires both letters and numbers"
system_config_697 = "Requires lowercase and uppercase letters and numbers"
system_config_698 = "Requires lowercase and uppercase letters with either numbers or special characters"
system_config_699 = "Requires lowercase and uppercase letters, numbers, and special characters"
system_config_700 = "NOTE: Allowed special characters includes the following:"
system_config_701 = "URL shortening service"
system_config_702 = "When enabled, REDCap provides the option to use the 3rd-party URL shortening services named BIT.LY and IS.GD to shorten or customize public survey links, links for public project dashboards, and public report links. If your server is behind a firewall and cannot make outbound HTTP requests to websites on the web, then you should disable this service."
system_config_703 = "When enabled, REDCap provides the option to use the URL shortening service named REDCAP.LINK to shorten or customize public survey links, links for public project dashboards, and public report links. This service is hosted by Vanderbilt on AWS. If your server is behind a firewall and cannot make outbound HTTP requests to websites on the web, then you should disable this service."
system_config_704 = "Go to Profile"
system_config_706 = "Google Authenticator or Microsoft Authenticator"
system_config_707 = "Open the Google Authenticator or Microsoft Authenticator app on your mobile device to get the verification code associated with your REDCap user account."
system_config_708 = "NOTE: If you have not yet set up REDCap in your Google Authenticator or Microsoft Authenticator app on your mobile device, then you can do so on your Profile page in REDCap after you log in using *another* login method."
system_config_709 = "How do I set up Google Authenticator or Microsoft Authenticator?"
system_config_710 = "(Optional) Enable the Google/Microsoft Authenticator app option for two-factor authentication?"
system_config_711 = "If enabled, the 'Google Authenticator/Microsoft Authenticator' option can be used for two-factor auth, in which the user can obtain the 6-digit verification code from the Google Authenticator or Microsoft Authenticator app on their mobile device."
system_config_712 = "NOTE: Before using the app for two-factor auth, the user must first set up the Google Authenticator app or Microsoft Authenticator using the instructions and QR code on their Profile page."
system_config_713 = "Set up Google Authenticator or Microsoft Authenticator for two-step login"
system_config_714 = "To use two-step verification to log in to REDCap using Google Authenticator or Microsoft Authenticator mobile app, you will need to first download the app onto your mobile device. Use a link below to download the app on your mobile device."
system_config_715 = "Download the app by searching for '<b>Google Authenticator</b>' or '<b>Microsoft Authenticator</b>' in your mobile device's app store (e.g., Apple App Store, Google Play Store)."
system_config_716 = "1) Download the Google Authenticator or Microsoft Authenticator app to your mobile device"
system_config_717 = "After you have scanned the QR code using the Google Authenticator or Microsoft Authenticator app, you can open the app at any time in the future to obtain your verification code for REDCap. The verification code is always changing, so it will be different each time you log in. <b>NOTE: The app does not require an internet connection</b> on your device in order to work."
system_config_718 = "1) Should the Protected Email Mode operate on all alerts, survey invitations, and survey confirmation emails, or only on those whose email body is piping data from Identifier fields?"
system_config_719 = "Only those with data piped from Identifier fields"
system_config_720 = "All alerts, survey invitations, and survey confirmation emails"
system_config_721 = "This setting prevents identifying data (PHI/PII) from being sent in outgoing emails for alerts, survey invitations, and survey confirmation emails. If enabled here at the system-level, users will see an option in the Additional Customizations dialog on the Project Setup page to allow them to enable the Protected Email Mode in their project. If this feature is then enabled in a project, either A) all alerts, survey invitations, and survey confirmation emails or B) those whose email body is attempting to pipe data from Identifier fields will be affected, in which it will not send the full email text to the recipient but will instead send a surrogate email containing a link that leads them to a secure REDCap page to view their original email. The recipient clicking the link allows them to navigate to a secure REDCap page where they may view the original email. If they are accessing an email in the Protected Email Mode for the first time (or in more than a month), it will send a security code to their inbox that will allow the recipient to view any protected emails for up to 30 days on that same device."
system_config_722 = "Prevent identifying data (PHI/PII) from being sent in outgoing emails for alerts, survey invitations, and survey confirmation emails."
system_config_723 = "This setting prevents identifying data (PHI/PII) from being sent in outgoing emails for alerts, survey invitations, and survey confirmation emails. If enabled, either A) all alerts, survey invitations, and survey confirmation emails or B) those whose email body is attempting to pipe data from Identifier fields will be affected, in which <b>it will not send the full email text to the recipient but will instead send a surrogate email containing a link that leads them to a secure REDCap page to view their original email</b>. If they are accessing an email in the Protected Email Mode for the first time (or in more than a month), it will send a security code to their inbox that will allow the recipient to view any protected emails for up to 30 days on that same device."
system_config_724 = "2) Optional custom text to display in the email header and page header seen by the recipient. Default text: <i>REDCap Secure Messaging</i>."
system_config_725 = "HTML may be used to add images, links, or styled text. For example:"
system_config_726 = "Allow normal users to edit their primary email address on their Profile page?"
system_config_727 = "This feature may be used in environments that restrict users in certain ways (e.g., 21 CRF Part 11 environment). Normal users will still be able to (when using Table-based authentication) reset their password, and Administrators will still be able to edit their primary email address regardless."
system_config_728 = "Google Cloud Storage using API Service Account"
system_config_729 = "GOOGLE CLOUD STORAGE API SETTINGS: If using 'Google Cloud Storage' as your storage option, set the values for your account ID, secret key, and the name of the 'bucket' where all REDCap files should be stored."
system_config_730 = "Google Cloud Platform project ID"
system_config_731 = "Bucket name"
system_config_732 = "Secret"
system_config_734 = "Google Cloud Storage (for Google App Engine hosting only)"
system_config_735 = "(only if currently being used as system-level File Storage Method)"
system_config_736 = "Bucket/container name:"
system_config_737 = "Azure/S3-only settings:"
system_config_739 = "SFTP/WebDAV-only settings:"
system_config_741 = "'userPrincipalName' will use the user's fully qualified username as their REDCap username, for example username@domain.com. 'onPremisesSamAccountName' will use the user's legacy domain username if syncing from your on-premises domain, for example 'username'"
system_config_742 = "You can enforce two-factor on all users OR enforce it on all users except for those within a specified IP address range. For example, if you know the IP ranges of computers on your institution's local network or VPN, then you can enforce two-factor only for users accessing REDCap from outside your institution."
system_config_743 = "Authentication type (WebDAV-only):"
system_config_744 = "Digest authentication"
system_config_745 = "NTLM authentication"
system_config_746 = "Basic authentication"
system_config_747 = "Default instrument-level user access set for all project users' Data Viewing Rights and Data Export Rights whenever a new instrument is created while in production status."
system_config_748 = "If a user creates a new instrument while a project is in production, you may choose whether all users in the project will have 'No Access' rights to the new instrument(s) by default or if they will instead have 'View & Edit/Full Data Set' rights to the new instrument(s) by default. NOTE: This applies to ALL projects, and the user access right selected above gets set automatically after the draft mode changes are approved."
system_config_749 = "Additional OpenID Connect Authentication Settings:"
system_config_750 = "Client ID"
system_config_751 = "Client Secret"
system_config_752 = "Provider Base URL"
system_config_753 = "Provider Metadata Document URL"
system_config_754 = "Metadata Document URL typically ends with <code>/.well-known/openid-configuration</code>"
system_config_755 = "The following fields are for configuring the OpenID Connect integration. Please note that the following attributes should be set accordingly on the Identity Provider server:"
system_config_756 = "S3 Custom Endpoint (optional):"
system_config_757 = "If you wish to use the default AWS S3 endpoint, leave this textbox blank."
system_config_758 = "Allow the e-signature feature to be used in a project (displayed below the locking checkbox at bottom of data entry form)."
system_config_759 = "You might wish to disable this feature if you are not using Table-based, LDAP, or LDAP+Table-based authentication since the e-signature feature will not work for certain external authentication methods (e.g., Shibboleth, OAuth2)."
system_config_760 = "Customize and Manage the Record Locking Functionality"
system_config_761 = "Customize & Manage Locking"
system_config_762 = "Locking Management"
system_config_763 = "Enable the Stats & Charts module for ALL projects?"
system_config_766 = "Attribute to use for REDCap username"
system_config_767 = "This OIDC attribute will serve as the authenticated user's REDCap username after logging in. If the selected attribute does not have a value for the user, it will revert to using the user's associated email address to serve as their username."
system_config_768 = "Enforce two-factor authentication ONLY for Table-based users?"
system_config_769 = "Only applicable if using an \"X & Table-based\" authentication method. Otherwise, this is ignored."
system_config_770 = "Yes, enforce only on Table-based users"
system_config_771 = "No, enforce on all users (Table-based and non-Table-based)"
system_config_772 = "Notice: If \"Yes\" is selected, non-Table-based users will be EXEMPT from 2FA and from all 2FA enforcement settings."
system_config_773 = "Image embedding for rich text editor"
system_config_774 = "When enabled, users may embed an inline image into the text of a survey invitation, an alert, field label, or anywhere the rich text editor is used (with one exception: the @RICHTEXT action tag on public surveys) by clicking the image icon in the editor and then uploading an image from their local device."
system_config_775 = "If disabled, the image icon will not appear in the rich text editor, and thus users will not be able to embed images in its text."
system_config_776 = "Alternate URL for \"Contact REDCap Admin\" links on the left-hand menu of each project (optional)"
system_config_777 = "By default (if the text box above is left blank), the \"Contact REDCap Admin\" links will open a pre-formatted email in the user's native email client. But if you enter a URL into the text box, the user's browser will navigate to that URL in a new tab after clicking the \"Contact REDCap Admin\" link. If you are using a ticket system, for example, to collect questions/issues from your users, you may enter the URL of the ticket system's page where new tickets can be submitted."
system_config_778 = "MyCap is a participant-facing mobile application for data collection and the automated administration of active tasks (activities performed by participants using mobile device sensors under semi-controlled conditions). If enabled here at the system-level, users will be able to enable MyCap within their projects on the Project Setup page."
system_config_779 = "Allow normal users to enable MyCap in their projects?"
system_config_780 = "Yes, allow users with Project Setup/Design rights to enable MyCap"
system_config_781 = "No, an administrator must enable MyCap via a user request"
system_config_782 = "File Repository: File storage limit (in MB)"
system_config_783 = "To disable the storage limit, set value as blank or '0'."
system_config_784 = "MB"
system_config_785 = "Set the maximum total file space that can be utilized within each project's File Repository (including only User Files - i.e., excluding Data Export files, eConsent PDFs, etc.).  This setting will be applied to all projects. Note: This value can be overridden for specific projects on a project's 'Edit Project Settings' page."
system_config_786 = "File Repository: File storage limit (in MB) for all projects"
system_config_787 = "Set the maximum total file space that can be utilized within this project's File Repository (including only User Files - i.e., excluding Data Export files, eConsent PDFs, etc.).  This setting will override the system-level setting (if set) on the 'File Upload Settings' page."
system_config_788 = "Response Mode option (<code>response_mode</code>)"
system_config_789 = "If you do not know what it should be, leave it as the default."
system_config_790 = "Notify the REDCap admin via email when a new account is created (excluding Table-based user accounts)?"
system_config_791 = "This setting can be used to notify admins whenever new users enter the system. Table-based users are not included because their accounts are created by an administrator."
system_config_792 = "Yes, send an email to the admin"
system_config_793 = "New user account created:"
system_config_794 = "A new REDCap user account has just been created with the following username, name, and email address:"
system_config_795 = "View the user account"
system_config_796 = "Email Notification Settings"
system_config_797 = "Yes, send the welcome email to the user"
system_config_798 = "Send a \"welcome\" email to new users when they create a REDCap account (excluding Table-based user accounts) - i.e., when they log in the first time using an external authentication method?"
system_config_799 = "The \"welcome\" email will consist of the following stock text:"
system_config_800 = "New REDCap account created:"
system_config_801 = "You have successfully created an account in REDCap at"
system_config_802 = "Your REDCap username is"
system_config_803 = "Please note that REDCap does not manage your password. If you have difficulty logging in, you should contact your local IT department. Welcome to REDCap!"
system_config_804 = "File attachment embedding for rich text editor"
system_config_805 = "When enabled, users may attach a file into the text of a survey invitation, an alert, field label, or anywhere the rich text editor is used (with the exception of the @RICHTEXT action tag and non-project pages, such as Email Users) by clicking the attachment icon in the editor and then uploading a file from their local device. These files may be accessed and/or deleted (if desired) in the \"Miscellaneous File Attachments\" folder in the project's File Repository."
system_config_806 = "If disabled, the attachment icon will not appear in the rich text editor, and thus users will not be able to embed file attachments in its text."
system_config_807 = "Automatically display inline PDF attachments for Descriptive Text fields inside a resulting PDF download of an instrument/survey?"
system_config_808 = "Enabling this feature allows PDF attachments to appear inline in the downloadable PDF as they currently do on the web page, in which they are fully visible."
system_config_809 = "NOTE: This feature requires that the ImageMagick PHP extension be enabled."
system_config_810 = "ImageMagick is currently enabled in PHP."
system_config_811 = "<b>ImageMagick is NOT currently enabled in PHP, so this feature will not work, even if enabled.</b> If you wish to install the extension, visit <a target='_blank' href='https://www.php.net/manual/en/book.imagick.php'>the Imagick extension installation page</a>."
system_config_812 = "NOTICE: These instructions will only be shown once."
system_config_814 = "Default value: common"
system_config_815 = "Provide the GUID value of your tenant if not using 'common'. If left blank, 'common' will be used. Applicable to both Endpoint V1 and V2."
system_config_817 = "Azure Communication Services - Email Configuration"
system_config_818 = "When sending outgoing emails, REDCap can utilize the Azure Communication Services API for sending emails as an alternative to using the REDCap web server's default methods  that send emails. You first need to set up an account on the Microsoft/Azure website"
system_config_819 = ", which will give you access to an Email API key that is connected to your Azure account. NOTE: You will need to create an account and generate the API token there in order  to use it here in REDCap. Follow all instructions on the Microsoft/Azure website for obtaining and using the API token."
system_config_820 = "Azure Communication Services API Key"
system_config_821 = "Azure Communication Services Endpoint"
system_config_822 = "<u>Limitations with Azure Communication Services:</u> Due to limitations in the implementation of this API by Microsoft/Azure,  this email-sending method is not able to display inline images in the body of emails, but any inline images will instead be represented as regular attachments.  Additionally, the true sender’s email address and display name are not able to be displayed to the recipient in their email client,  thus the recipient will only see the REDCap Universal 'From' Address as the sender with no corresponding display name."
system_config_826 = "This setting will override the default setting for new users (see User Settings), which should be set to 'No' if you want to <em>only</em> allow locals to create/copy projects."
system_config_827 = "The following fields are for configuring Australian Access Federation (AAF) authentication. See "
system_config_828 = "the REDCap Community guide on setting up AAF RapidConnect Authentication"
system_config_829 = " for detailed instructions."
system_config_830 = "The URL that AAF provides you when registering a service"
system_config_831 = "The URL that authenticating users are redirected to upon authenticating. This is typically the REDCap base URL"
system_config_832 = "The URL of the federation issuing the authentication token. This should be https://rapid.test.aaf.edu.au for test/development services and https://rapid.aaf.edu.au for production services."
system_config_833 = "Australian Access Federation (AAF) Authentication Settings:"
system_config_834 = "Access URL (required)"
system_config_835 = "Audience URL (required)"
system_config_836 = "Issuer URL (required)"
system_config_837 = "This value in the AAF eduPersonScopedAffiliation attribute identifies a local. Multiple entries, one entry per line, may be used here, in which a user whose eduScopedPersonAffiliation attribute matches any of the supplied identifiers will be treated as a local.<br><strong>Example:</strong><br><code>staff@university1.edu.au<br>student@university2.edu.au</code><br>See the <a href='https://validator.aaf.edu.au/'>AAF Attribute Validator</a> to check your own attributes for reference."
system_config_838 = "Allow locals to create/copy projects?"
system_config_839 = "Display users on 'Email Users' page?"
system_config_840 = "AAF attribute to be used as username"
system_config_841 = "While AAF recommends using eduPersonTargetedID as a user's primary identifier as, unlike mail, it is guaranteed to never change for an individual, the mail attribute is most typically used as a username. eduPersonTargetedID is a long, non-human readable string. Using cn (common name) or displayname are discouraged as they may lead to clashes between individuals with the same name."
system_config_842 = "For AAF authentication you must have an Access URL, Audience URL and Issuer URL configured."
system_config_843 = "None"
system_config_844 = "Locals only"
system_config_845 = "All users"
system_config_846 = "Sorry, but you have exceeded the maximum number of attempts per minute. Please wait a minute and try again."
system_config_847 = "Additional scope (optional)"
system_config_848 = "In certain cases, such as when using OIDC for Azure B2C, the Application (client) ID might need to be provided as the additional scope in order for authentication to work correctly."
system_config_849 = "Mailgun base URL (optional)"
system_config_850 = "If left blank, the base URL <code>https://api.mailgun.net</code> will be used. Other options include the following base URL for the EU region: <code>https://api.eu.mailgun.net</code>."
system_config_851 = "Display the 'variable auto-naming' feature in the Add Field popup in the Online Designer?"
system_config_852 = "No, hide it for all users"
system_config_853 = "Yes, display it for all users"
system_config_854 = "Only display it for administrators"
system_config_855 = "The effort of enabling the Read Replica functionality is very minimal once a replica server has been created and is successfully replicating from the REDCap primary database server.  Most of the work will be simply setting up the replica server. See the instructions below regarding how to enable the Read Replica feature."
system_config_856 = "<b>Set up new database server and enable replication to primary:</b> First, you need to set up a new database server that closely matches the specs of your existing REDCap database server.  <u>Ideally, it should be the same version (or very close version-wise) of MySQL/MariaDB as the primary server, and it is recommended that the replica have the same RAM/CPUs or slightly less than your primary server.</u>  Simply follow the standard procedures for setting up MySQL/MariaDB replication on that server so that  it is successfully replicating in real time from the REDCap primary database server. Once replication is enabled, it might take many hours for the replica to finally catch up to the primary server.  <b>NOTICE:</b> The REDCap development team is purposely not providing specifics on how to set up MySQL/MariaDB replication because they are not experts in this area  and because this should only implemented by an IT specialist, such as a DBA, who has expertise in this area.  <u>If you or your IT folks do not know how to implement database replication, then enabling the Read Replica feature should *not* even be considered.</u>"
system_config_857 = "<b>Add connection variables for the replica to database.php:</b> Create a MySQL/MariaDB 'user' on the replica server so that REDCap may use that user to connect to the replica.  Then open the <code>/redcap/database.php</code> file for editing on your REDCap web server, and add the replica connection variables to the file, as seen below. "
system_config_858 = "If the replica requires an SSL/TLS connection (i.e., MySQL over SSL), you will also need to provide the additional connection variables below."
system_config_859 = "Read Replica functionality is not available for use because the connection variables were not found in database.php."
system_config_860 = "<b>Enable the Read Replica system setting on this page:</b> Once 1 and 2 above have been completed, reload this page (General Configuration),  after which the Read Replica 'enable' drop-down should no longer appear as read-only/disabled. Enable the Read Replica  by selecting 'enable' and saving the page. Then visit the main Control Center page or Configuration Check page, and if they display a warning that the Read Replica might be offline or can't be connected to,  then double check that the correct replica connection variables were added correctly to database.php."
system_config_861 = "Enable a Read Replica database server to improve system performance?"
system_config_862 = "To help offset server load if the REDCap system has been experiencing routine slowness,  REDCap can connect to a read-only, secondary database server that uses MySQL/MariaDB replication to stay in sync with REDCap's primary database server.  <u>The Read Replica server will be utilized only for read-only operations in the following places in REDCap:</u> viewing reports, exporting data (including API exports), viewing record status dashboards, viewing and exporting  the project logging page (including API logging exports), using the data search tool, viewing the scheduling page, executing data quality rules, viewing project dashboards, and viewing the Control Center's  System Statistics and User Activity Log pages."
system_config_863 = "NOTE: The Read Replica is only recommended for use if you have been experiencing performance issues with your REDCap server, such as a routine or off-and-on slowness.  Before enabling the Read Replica feature, it is advised that you explore other ways to improve database performance first, such as adding more RAM and CPUs to your database server to see if that provides some improvement.  If those things do not help, then using the Read Replica might be a good option."
system_config_864 = "How to set up the Read Replica feature"
system_config_865 = "<b>Monitor the Read Replica:</b> If REDCap can connect to the Read Replica successfully, the replica will be utilized (rather than the primary database) on specific pages  throughout REDCap where read-only processes are performed.  <u>The replica can be seen and its activity observed on the Database Activity Monitor page. If the replica's lag time rises higher than {0} seconds, then it will not be used until its lag time from primary  is {1} seconds or less.</u> This is to prevent users from viewing 'stale' data from the replica in case the replica lags too far behind the primary server."
system_config_870 = "Activate this option to improve server performance on slower project pages (e.g., exports, reports, record status dashboard). With Rapid Retrieval enabled, if a requested page is not found in the cache,  the read-through cache system automatically fetches and stores the data from the file system or database, depending on the setting below. This process reduces wait times for data fetches, minimizes direct database queries,  and ensures that the most frequently requested data is stored in the cache for quicker retrieval. In summary, Rapid Retrieval makes some REDCap pages a lot faster to load."
system_config_871 = "Rapid Retrieval (page-level caching feature)"
system_config_872 = "Enable Rapid Retrieval"
system_config_873 = "Page speed was boosted using Rapid Retrieval"
system_config_874 = "The current REDCap webpage was able to load faster because it utilized REDCap's Rapid Retrieval feature. Rapid Retrieval is an automated internal feature that allows REDCap to store  certain pages in a temporary holding cache. When utilizing Rapid Retrieval, if no data or metadata has changed in the project recently, REDCap will output the stored cache of the page from when it was previously loaded.  This means that REDCap does not have to do all the work of normally loading the page but instead can load the page much faster by using the cache. The time that the current page was last cached was"
system_config_875 = "File-based storage (recommended)"
system_config_876 = "Database storage"
system_config_877 = "Alternative directory to store cached files (optional)"
system_config_878 = "If set to 'File-based storage', the Rapid Retrieval feature will store all cached files in REDCap's 'temp' folder by default.  If set to 'Database storage', they will be stored in the <code>redcap_cache</code> database table."
system_config_879 = "NOTE: When using File-based storage, the cached files are completely encrypted (at rest) on the web server, and the files are immediately removed once they have been invalidated and can no longer be utilized."
system_config_880 = "If set to 'File-based storage', the Rapid Retrieval feature will store all cached files in REDCap's 'temp' folder by default. However, you may set an alternate location on your web server for storing the cached files,  whether for security or performance related reasons."
system_config_881 = "Setting an alternative directory can help maximize the efficacy of Rapid Retrieval if you are using load balancing or using cloud-based hosting with multiple nodes if the alternative directory is a centralized place      that all servers/nodes can access, such as a mapped drive to external file storage. If you are not hosting REDCap on a multiple web server/node system, then leaving this setting blank is best."
system_config_882 = "RECOMMENDATION: The File-based storage method is recommended in most cases, such as on very active servers, because the Database storage method can tend to cause the database to be too busy,      in which it may bog down the server and/or cause the MySQL binary log to grow too rapidly. You may try both options to see if one performs better overall. There is no harm in changing this setting      at any time while the system is running."
system_config_883 = "AD attribute to use for REDCap username (Endpoint V1 and V2)"
system_config_884 = "ERROR: Only administrators with 'Admin Rights' privileges, 'Modify system configuration pages' privileges, or 'Access to all projects and data with maximum privileges' privileges are allowed to access this page."
system_config_885 = "The following 4 fields are for configuring the Microsoft Entra ID authentication. Information about the client id and client secret can be found here: (<a href=\"https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-app?tabs=dotnet\" target=\"_blank\">https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-app?tabs=dotnet</a>)."
system_config_886 = "Additional Microsoft Entra ID (formerly Azure AD) Authentication Settings:"
system_config_887 = "API Client ID"
system_config_888 = "API Client Secret"
system_config_889 = "Version 2.0 endpoints allow for multi-tenant authentication into REDCap. To use 2.0 endpoints with REDCap, log into your Azure portal for App registrations, click the Authorization blade, and enable accounts in any organizational directory under the Supported account type field. Differences between the endpoint versions are summarized here: https://devblogs.microsoft.com/premier-developer/azure-ad-endpoint-v1-vs-v2/"
system_config_890 = "Endpoint Version"
system_config_891 = "Tenant"
system_config_892 = "ERROR: The IP addresses listed below are not valid and must be corrected if you wish to use them in the exceptions of IP ranges for rate limiter:"
system_config_893 = "You may enter IPv4 address ranges in either wildcard format with asterisks OR as a range with hyphen. IPv6 subnet masks may also be used. In addition to ranges, individual IP addresses may be used. All IP addresses and ranges must be separated by commas. Example:"
system_config_894 = "Below you may optionally provide IP addresses or ranges to exclude from the Rate Limiter. This will be useful if performing security scans on your server, in which you can add the IP address of the scanning tool so that it does not get banned while performing scans."
system_config_895 = "Enable the e-Consent Framework feature 'Allow e-Consent responses to be edited by users?'"
system_config_896 = "If enabled (default), users enabling e-Consent for a survey can choose whether or not users are allowed to modify survey responses that were completed using the e-Consent Framework.  If disabled, no users will be able to modify survey responses that have been completed using the e-Consent Framework."
system_config_897 = "Store non-e-Consent governed PDF Snapshots on the External Storage server if the snapshot contains a completed e-Consent response."
system_config_898 = "If enabled (default), any PDF Snapshot that is being saved to the File Repository will additionally be stored on the External Storage server if the snapshot contains at least one completed e-Consent response.  If disabled, then only e-Consent governed PDF Snapshots will be stored on the External Storage server for this project."
system_config_899 = "NOTE: This setting will have no effect if the External Storage server (\"The Vault\") is not enabled for the e-Consent Framework on the Modules/Services Configuration page."
system_config_900 = "(optional) URL for Custom Logout Page"
system_config_901 = "Shibboleth User First Name Field"
system_config_902 = "Name of the server variable that contains the user's first (given) name that Shibboleth defines in PHP (e.g., $_SERVER['givenName']). Default value is 'givenName'"
system_config_903 = "Shibboleth User Last Name Field"
system_config_904 = "Name of the server variable that contains the user's last (family) name that Shibboleth defines in PHP (e.g., $_SERVER['sn']). Default value is 'sn'"
system_config_905 = "Shibboleth User Email Field"
system_config_906 = "Name of the server variable that contains the user's email address that Shibboleth defines in PHP (e.g., $_SERVER['mail']). Default value is 'mail'"
system_config_907 = "Shibboleth User Information Settings:"
system_config_908 = "When a user logs in to REDCap for the first time, REDCap can automatically set their name and email address using the information supplied by Shibboleth. These settings determine whether REDCap will do that and which Server fields REDCap will use."
system_config_909 = "Set user information on each login"
system_config_910 = "If set to 'Yes,' then REDCap will override the existing values for user first name, last name, and email address using information from Shibboleth. This is useful if you want changes to users' personal information made in the identity provider's database to be immediately reflected in REDCap. If set to 'No,' then user information will only be set when logging in to REDCap for the first time."
system_config_911 = "Set user information using data from Shibboleth"
system_config_912 = "If Enabled, REDCap will populate user information with values provided by Shibboleth. If Disabled, users will be shown a screen to set their own user information when they log in for the first time."
system_config_913 = "Documentation on How to Configure Shibboleth Options"
system_config_914 = "This setting will not affect existing projects but will be applied in the future to new projects individually at the time of their creation."
system_config_915 = "Organize the stored files into subfolders by REDCap project ID?"
system_config_916 = "NOTE: When enabled, if REDCap is unable (due to a directory permissions issue, etc.) to create a project-level subfolder when a new project is created,  it will instead default to storing all project files in the main Local File Storage directory (specified above) for that project."
system_config_917 = "<b>Cannot create subfolders in main local file storage directory - RECOMMENDED:</b> REDCap is set to organize project-level stored files in individual subfolders by project. However, it appears that REDCap does NOT have the ability to create subfolders in the file storage directory {0}. This is likely due to a folder permissions issue in that main directory. This is not critical, but it means that until this is fixed, any newly created projects will have their files stored in the main file storage directory instead in a project-level subfolder."
system_config_918 = "<b>Subfolders in main local file storage directory are not writable - RECOMMENDED:</b> REDCap is set to organize project-level stored files in individual  subfolders by project. However, while REDCap *can* create subfolders in the file storage directory {0}, it appears that REDCap does NOT have the ability to write and/or delete files in newly created subfolders (e.g., {1}).  This is likely due to a folder permissions issue in that main directory.  This is not critical, but it means that until this is fixed, any newly created projects will have their files stored in the main file storage directory instead in a project-level subfolder."
system_config_919 = "NOTE: This setting also applies when using Google Cloud Storage for Google App Engine hosting below."
system_config_920 = "NOTE: The 'Organize the stored files into subfolders by REDCap project ID?' setting above for Local Storage <u>also applies</u> here to Google Cloud Storage for Google App Engine hosting."
training_res_02 = "REDCap Training Videos"
training_res_03 = "Just Getting Started?"
training_res_05 = "Title"
training_res_07 = "Watch<br>Video"
training_res_09 = "This video provides an overview of basic functions and features within a REDCap project. It will serve as a starting point for learning about the basic concepts of REDCap, what REDCap projects are, how to create them, and how to use them."
training_res_12 = "Online Designer"
training_res_14 = "5 minutes"
training_res_15 = "Data Dictionary"
training_res_17 = "Data Dictionary demonstration file"
training_res_18 = "10 minutes"
training_res_19 = "Scheduling Module"
training_res_22 = "Types of REDCap Projects"
training_res_23 = "There are several flavors of REDCap projects to choose from as you begin thinking about building your own project. Each type of project has its advantages and disadvantages, and may fit the specific needs better of one type of project over another. Please review the different types below, and you may even view a live example of each project type in action or view a short video about it."
training_res_24 = "Project Type"
training_res_26 = "Traditional Project"
training_res_27 = "(classic model with data entry forms)"
training_res_29 = "5 minutes"
training_res_30 = "Longitudinal Project"
training_res_31 = "(multi-use data entry forms,<br>abstract time-points)"
training_res_33 = "3 minutes"
training_res_34 = "Longitudinal Project<br>+ Scheduling"
training_res_35 = "(multi-use data entry forms,<br>defined time points)"
training_res_46 = "Operations"
training_res_47 = "(use case for non-study/non-trial)"
training_res_49 = "Special Features within REDCap Projects"
training_res_50 = "Every REDCap project is capable of utilizing special features, some of which can be enabled by normal users and some by REDCap administrators. Below is a listing of these features."
training_res_51 = "Feature"
training_res_52 = "for multi-site projects"
training_res_56 = "Locking Records"
training_res_60 = "Single Survey Project"
training_res_63 = "VIDEO: How to create and manage a survey"
training_res_69 = "Defining Events in Longitudinal Projects"
training_res_71 = "Types of Projects"
training_res_73 = "This video describes two major decisions that must be made when building a REDCap project. It also briefly illustrates how these decisions affect which type of project is used."
training_res_74 = "The traditional project is used for basic data collection. All data is entered directly in REDCap by users who log in. Multiple data collection instruments are often defined. This project type is suitable for most data collection needs. It can capture longitudinal data, including adverse event reporting or other collection that does not have a pre-defined schedule or end-point."
training_res_75 = "The Survey module allows a REDCap instrument to be completed by survey respondents who do not log in. Data can also still be entered by REDCap users (who do log in). This video explores all the major features of the survey module, including survey distribution. A single survey project has only one data collection instrument, which is used as a survey. "
training_res_76 = "The Longitudinal module allows any data collection instrument(s) to be completed multiple times for each record. The same data may be captured repeatedly. The module uses an event grid to define clear timepoints used for data collection. The longitudinal module is best suited to very structured studies which do NOT last indefinitely. Clinical trials frequently use this project type. "
training_res_77 = "This project type uses two modules. The Longitudinal module allows any data collection instrument(s) to be completed multiple times for each record. The Scheduling module adds record-specific schedules onto a study calendar, using the longitudinal event grid. Schedules can be generated and modified. The longitudinal module is best suited to very structured studies which do NOT last indefinitely. So this project type is useful for large, multi-site clinical trials needing a quick and easy way to schedule patient visits."
training_res_78 = "REDCap can be used for almost any type of data collection. The most common uses are clinical research and trials. However, REDCap is also suitable for administrative and educational data, workflow tracking, quality improvement, biobanking, registries, and non-human research. This example explores a traditional project type being used to capture and track operational bookkeeping information."
training_res_79 = "Designating Instruments for Events in Longitudinal Projects"
training_res_81 = "The Data Access Groups feature assigns users to groups. Any user in a Data Access Group may only access their group's records. Each group is blinded to all other data/records. Users not in a group can access all data across all groups. This feature is especially useful for multi-site projects because each data collection site must usually be restricted from viewing other sites' records."
training_res_82 = "The locking feature freezes data. Users can still view existing data, but they cannot modify it unless they have the needed User Rights permissions. This video illustrates the basics of how instruments are locked. Refer to the built-in help resources and locking applications for more detailed instructions about locking management."
training_res_83 = "Defining events is a requirement of the Longitudinal module. That module allows any data collection instrument(s) to be completed multiple times for each record. The module uses an event grid to define the timepoints used for data collection. This video illustrates how to define the timepoints (also called events)."
training_res_84 = "Designating instruments is an optional step of the Longitudinal module. That module allows any data collection instrument(s) to be completed multiple times for each record. The module uses an event grid to define the timepoints used for data collection. This video illustrates how to designate which instruments are completed at each timepoint."
training_res_85 = "A quick summary of what REDCap is and what it can do."
training_res_86 = "Explore these overviews of fundamental concepts and features."
training_res_87 = "A focused exploration of basic data entry workflow. Suitable for training data entry staff."
training_res_88 = "Building a Project"
training_res_89 = "Learn how to build and modify data collection instruments."
training_res_91 = "An introduction to the Online Designer and Data Dictionary methods of instrument development."
training_res_92 = "This online tool is the quickest and most intuitive method for making instrument modifications."
training_res_93 = "The Data Dictionary is your project structure in a downloadable spreadsheet file. The spreadsheet can be modified and uploaded into REDCap to make instrument modifications. To see an example, download the"
training_res_94 = "An illustration of some popular field types."
training_res_95 = "This advanced tool enables a powerful data query management system."
training_res_96 = "Basic Features & Modules"
training_res_97 = "Applications Overview"
training_res_99 = "This tool organizes your study by tracking upcoming milestones and events."
training_res_100 = "This is an optional feature in longitudinal projects. The tool generates record-specific schedules based on a series of events or timepoints. Used with the calendar module, this tool greatly streamlines longitudinal data entry."
training_res_101 = "Introduction to Instrument Development"
training_res_102 = "A brief exploration of four popular built-in features for project or data management: 1) User Rights, 2) Data Import Tool, 3) Data Exports, Reports, and Stats page, and 4) Alerts & Notifications."
training_res_103 = "An overview of how to use Project Dashboards, with some examples utilizing Smart Charts, Functions, and Tables."
training_res_104 = "Smart Charts, Functions, and Tables"
training_res_105 = "An overview of how to use a new category of Smart Variables called Smart Charts, Smart Functions, and Smart Tables."
training_res_106 = "VIDEO: How to use Project Dashboards"
training_res_107 = "VIDEO: How to use Smart Charts, Functions, and Tables"
training_res_108 = "How to utilize the Multi-Language Management feature that allows users to display data entry forms, surveys, alerts, and several more items in multiple languages."
training_res_109 = "VIDEO: How to use Multi-Language Management"
training_res_110 = "This video provides a detailed overview of building a REDCap project and many of the features that are often involved in that."
training_res_111 = "An overview of how to use the Randomization module for clinical studies and trials."
update_pk_01 = "You have just deleted or moved the location of your first data collection instrument, thus also moving or deleting the location of your record ID field (i.e. the first field on the first form), to which all existing data records are connected."
update_pk_02 = "Changing the record ID field may not have been intentional."
update_pk_03 = "How to fix this issue:"
update_pk_04 = "Now that the first form has been moved, your new record ID field is the field named"
update_pk_05 = "This means that the data for all currently existing records will not be able to be retrieved properly on some pages in the project and may introduce further data errors."
update_pk_06 = "To prevent data errors and eliminate this issue, you may 1) erase all data in the project by using the Control Panel & Settings page, 2) move the form back to its original position as the first form, or 3) move the record identifier field back to the new first form (this can also be done by deleting it from the other form and creating it anew on the new first form or by moving it to the first-field position in your data dictionary)."
update_pk_07 = "You have just deleted or moved the location of your record ID field (i.e. the first field on the first form), to which all existing data records are connected."
update_pk_08 = "Your new record ID field is the field named"
update_pk_09 = "To prevent data errors and eliminate this issue before committing your changes from Draft Mode, you may 1) move the form back to its original position as the first form, or 2) move the record identifier field back to the new first form (this can also be done by deleting it from the other form and creating it anew on the new first form or by moving it to the first-field position in your data dictionary)."
update_pk_10 = "To prevent data errors and eliminate this issue, you may 1) erase all data in the project by using the Control Panel & Settings page, or 2) create the record identifier field anew (if deleted) at the first position on this form or move it back to the first position."
update_pk_11 = "To prevent data errors and eliminate this issue before committing your changes from Draft Mode, you will need to create the record identifier field anew (if deleted) at the first position on this form or move it back to the first position."
user_01 = "Basic User Information Form"
user_02 = "Before accessing REDCap, we first need to obtain some basic information about you. Please enter ALL the fields below and then hit the Submit button. Once this information is saved, you can change it any time by navigating to the Profile page, which you will find the link to at the top right of every page."
user_08 = "Edit Your User Profile"
user_09 = "Your changes have been saved!"
user_10 = "Could not make changes."
user_11 = "If you wish, you may edit your User Profile information below. This information will not be given out to anyone but will be used to help us better keep track of who is using REDCap and also in case you need to be contacted regarding your access to REDCap."
user_12 = "RESET YOUR PASSWORD?"
user_13 = "Do you wish to reset your password for logging in to REDCap? If so, you will be asked to set your new password now."
user_15 = "Re-enter email"
user_16 = "NOTE: The email address entered above will first need to be verified before access to REDCap is granted. After clicking the Submit button, an email will be sent to that email account, after which you will need to click the link inside the email to verify your email account before accessing REDCap."
user_17 = "Please complete all the fields"
user_18 = "The re-entered email address did not match the first. Please re-enter your email address."
user_19 = "Verify your email address"
user_21 = "Click here to confirm your email address"
user_22 = "Awaiting email account verification"
user_23 = "Your REDCap account status is still pending because you have not yet verified the email account that you specified either when setting up your REDCap account or when modifying your account's primary email address. Your verification code was sent to"
user_24 = "Please check that email account to find the account verification email sent by REDCap, and follow its instructions."
user_25 = "Account created / Verification email sent"
user_26 = "Your REDCap account has now been created. But to complete the account setup process, you will need to confirm your email address by checking your email account"
user_27 = "for the account verification email sent by REDCap, and follow its instructions. You will not be able to fully access your REDCap account until the setup process has been completed. Thank you!"
user_28 = "Check your email account"
user_29 = "Email account verified!"
user_30 = "Your email account for REDCap has now been verified. You may now access REDCap by clicking the link below."
user_31 = "Invalid verification code!"
user_32 = "Your email account for REDCap could NOT be verified because the verification code is invalid. Please check your email message from REDCap to make sure the entire URL was copied correctly from the email. If this issue persists, please contact"
user_33 = "Confirm change of email address by entering it again"
user_34 = "If the primary email address is changed, a verification email will be sent to that address so that you may confirm that email account, in which your REDCap account will remain inaccessible until the new email address has been verified."
user_35 = "is already being used as either a secondary or tertiary email address for your REDCap account. You must enter another email if you wish to change your primary email address."
user_38 = "Email address changed / Verification email sent"
user_39 = "Your primary email address has now been changed for your REDCap account, but you will need to confirm it by checking your email account"
user_40 = "for the account verification email sent by REDCap, and follow its instructions. You will not be able to fully access your REDCap account again until this verification process has been completed. Thank you!"
user_41 = "Add new email address to your REDCap account"
user_42 = "Add email"
user_43 = "Up to three email addresses may be associated with your REDCap account. When sending emails in REDCap, you will be able to choose from any of those email addresses to be the 'From' address in the email you are sending. To add a new email to your REDCap account, provide the email address below, and it will send a verification message to that email account, after which it may then be utilized in REDCap."
user_44 = "Enter new email:"
user_45 = "Primary email"
user_46 = "Secondary email"
user_47 = "Before this new email address can be utilized by your REDCap account, you will first need to confirm it by checking your email account"
user_48 = "for the verification email sent by REDCap, and follow its instructions. You will not be able to utilize this new email address in REDCap until this verification process has been completed. Thank you!"
user_50 = "Verification email sent to"
user_51 = "Verification for"
user_52 = "is still pending"
user_53 = "It appears that you have already attempted to add this email address to your REDCap account, and thus you should have received a verfication email for the email address"
user_54 = "Another verification email will not be sent for this address. Please check that email account for the previous verification email that was sent, and follow its instructions. Thank you!"
user_55 = "Tertiary email"
user_56 = "Remove email address?"
user_57 = "Are you sure you wish to remove the email address below from your REDCap account? Once removed, you will no longer be able to utilize that email address as a 'From' address when sending emails via REDCap. However, you may add that email address back to your REDCap account at any time in the future. Do you still wish to remove it?"
user_58 = "Basic Information"
user_59 = "Additional Options"
user_60 = "Save Basic Info"
user_62 = "Re-enter new email"
user_65 = "Does not belong to"
user_66 = "To complete the process of setting up a new primary email for your REDCap account with username"
user_67 = ", you will need to confirm your email address by clicking the link below. You will not be able to fully access your REDCap account until this verification process has been completed. Thank you!"
user_68 = "To complete the process of adding this new email address to your REDCap account with username"
user_69 = ", you will need to confirm your email address by clicking the link below. You will not be able to utilize this new email address in REDCap until this verification process has been completed. Thank you!"
user_70 = "Optional attributes:"
user_71 = "Basic attributes:"
user_72 = "User's sponsor"
user_73 = "(REDCap username of sponsor)"
user_74 = "A user's sponsor is the person to contact regarding this user account and may be the person who requested that this account be created."
user_75 = "(secondary contact person)"
user_76 = "Miscellaneous comments<br>about the user:"
user_80 = "User Preferences"
user_81 = "Set your preferences for how dates, timestamps, and numbers appear to you in REDCap."
user_82 = "Date and time format:"
user_83 = "Number format - decimal character:"
user_84 = "Number format - thousands separator:"
user_85 = "(period / full stop)"
user_86 = "(comma)"
user_87 = "(blank space)"
user_88 = "(apostrophe)"
user_89 = "Save Preferences"
user_90 = "and 24-hour time"
user_91 = "and 12-hour AM/PM time"
user_92 = "[no thousands separator]"
user_93 = "Login-related options:"
user_94 = "None (Email notifications disabled)"
user_96 = "Daily digest"
user_97 = "Everything"
user_98 = "Save Messenger Preferences"
user_99 = "-hour digest"
user_100 = "However, the link you just clicked is intended for the requesting user "
user_101 = "to validate that they are authorized to send REDCap emails on behalf of"
user_102 = "If you are the owner of that email address, and you wish to allow"
user_103 = "to utilize that email address in REDCap, then forward the email link you used to get here to them at"
user_104 = "You are currently logged into REDCap as user"
user_105 = "It is recommended that you set up the Google Authenticator app for 2-step login"
user_107 = "(tab)"
user_109 = "Delimiter for CSV file downloads:"
user_110 = "The email address has now been removed from your REDCap account. The page will now reload to reflect the changes."
user_111 = "Email removed!"
user_112 = "(e.g., 12/31/2004 22:57 or 31/12/2004 10:57pm)"
user_113 = "(e.g., 3.14 or 3,14)"
user_114 = "(e.g., 1,000,000 or 1.000.000 or 1 000 000)"
user_115 = "(e.g., \"record,age,bmi\" or \"record;age;bmi\")"
user_116 = "User Sponsor"
user_117 = "My sponsor:"
user_118 = "Number of users of which user is a sponsor"
user_119 = "view sponsees"
user_120 = "{0}'s List of Sponsees (i.e., users that they sponsor)"
user_121 = "You may add secondary and tertiary email addresses to your account, but please note that they <u>cannot be used for account retrieval purposes</u>  (only your primary email address is used for receiving important email notifications from REDCap). Your secondary and tertiary email addresses can only be used for sending out  survey invitations, alerts, and other similar emails from REDCap, in which they appear as the \"From\" address in the email."
view_equation_02 = "Fields Utilized in Calculation"
view_equation_06 = "Calculation"
identifier_check_01 = "Check For Identifiers"
identifier_check_02 = "Because this project is currently in PRODUCTION, it must be in DRAFT MODE to make changes."
identifier_check_03 = "page and move the project into DRAFT MODE."
identifier_check_04 = "Please go to the"
identifier_check_05 = "page to submit your changes for review."
identifier_check_06 = "This module will help you assess whether or not some fields may be identifiers, and then allows you to easily tag such fields as identifiers for greater data security. While this same process can be accomplished in the Data Dictionary or Online Designer, this page provides a streamlined way of tagging fields as identifiers very quickly. Based off the variable name or field label, the fields listed below may possibly contain identifiers (e.g., name, phone number, address). Please review the entries and select all identifiers, where appropriate. Any fields already tagged as identifiers will already be checked below."
identifier_check_07 = "Update Identifiers"
mobile_app_01 = "App Data Dumps"
mobile_app_02 = "All App Activity"
mobile_app_06 = "Can't get the QR code to work?"
mobile_app_07 = "Alternative method to set up project:"
mobile_app_09 = "NOTE: The initialization code will expire in 10 minutes."
mobile_app_10 = "Initialization code:"
mobile_app_11 = "NOTICE: The initialization code has now expired. If you need to get a new initialization code, close this popup and click the button again to generate a new code."
mobile_app_14 = "Files Sent from Mobile App"
mobile_app_15 = "Uploaded by:"
mobile_app_16 = "File Info"
mobile_app_17 = "File Type"
mobile_app_18 = "App Logging"
mobile_app_19 = "App Data Export (Escape Hatch)"
mobile_app_20 = "Listed below are all the emergency data dump files (data exports) sent from the mobile app for this project. These are often sent when something prevented the app from sending data back to the server normally (i.e., escape hatch). You may click the file icon on the right to download it."
mobile_app_21 = "(Mobile App)"
mobile_app_22 = "Mobile App Dashboard of User Activity"
mobile_app_23 = "No activity has been recorded"
mobile_app_24 = "Displayed below is a log of all mobile app related activity for all devices. For example, setting up a project in the mobile app or downloading data from REDCap to the app."
mobile_app_25 = "Set up project in app"
mobile_app_26 = "Reset project in app"
mobile_app_27 = "Download all data to app"
mobile_app_28 = "Import data from app"
mobile_app_29 = "existing records modified"
mobile_app_30 = "existing record modified"
mobile_app_31 = "new records created"
mobile_app_32 = "new record created"
mobile_app_34 = "Delete API Token & Unlink Mobile App"
mobile_app_35 = "If for security reasons or otherwise you wish to disconnect the REDCap mobile app from this project, you must delete your API token for this project."
mobile_app_36 = "WARNING: Please be aware that if you are using this API token for the REDCap mobile app and you delete or regenerate the API token, then any data collected for this project on the REDCap mobile app that has not been synced back to the server yet will be PERMANENTLY LOST."
mobile_app_37 = "Set Up Project"
mobile_app_39 = "You must have already downloaded the REDCap mobile app on your mobile device or tablet. To set up this project in the REDCap app:"
mobile_app_40 = "NOTICE: In order to set up this project in the REDCap mobile app, you must first request an API token."
mobile_app_41 = "You currently do not have an API token yet for this project. Having a REDCap API token allows other programs, scripts, or apps to communicate with the REDCap server remotely. An API token is required for using the REDCap mobile app so that the app can download and upload your project information and data. To request an API token, simply click the button below, which will send an email request to your local REDCap administrator. Once they have granted you an API token, in which you will be notified via email, then you may return to this page to set up this project on the REDCap mobile app on your device."
mobile_app_42 = "Download the app on your device"
mobile_app_43 = "You must first download the REDCap Mobile App on your iOS, Android, or BlueStacks (Android emulator) device by clicking the appropriate icon below, or alternatively, if you are not currently on a mobile device, you can search the App Store or Google Play Store for 'REDCap' on your mobile device to find the app there to download."
mobile_app_44 = "Set up the mobile project on your device"
mobile_app_45 = "An alternative way to set up this project in your REDCap app on your mobile device or tablet is to use an initialization code. To do this, open the app on your device, click the 'Set Up Mobile Project' button, and near the bottom of that page enter the code that you see displayed below."
mobile_app_46 = "Email me links to download the app"
mobile_app_47 = "Links for downloading REDCap Mobile App"
mobile_app_48 = "Below are the links for downloading the REDCap Mobile App from the Apple App Store or from the Google Play Store (depending on what type of mobile device you have)."
mobile_app_49 = "It has been determined that"
mobile_app_50 = "instruments in your project are either a Computer Adaptive Test (CAT) or an Auto-Scoring instrument, which can only be taken as a survey on the REDCap server. Thus those instruments cannot function in the mobile app. Please note that when you set up this project in the REDCap mobile app, those specific instruments will *not* appear in the app, although all other instruments will."
mobile_app_51 = "The app is available for the following platforms: iOS 6.0 or later (iPhone 4 and up, iPad 2 and up) and Android 4.3 or later (phones and tablets)."
mobile_app_52 = "Mobile App"
mobile_app_53 = "We're sorry, but the alternative method will not work because the REDCap server cannot communicate with the server that generates the initialization code for the alternative method."
mobile_app_54 = "(Administrators: This likely means that your web server is not able to make outbound HTTP requests to https://redcap.vumc.org, which is the server that generates the initialization code.)"
mobile_app_55 = "Open the app on your device."
mobile_app_56 = "Click the 'Set Up Mobile Project' button."
mobile_app_57 = "Click the 'Scan QR Code' button."
mobile_app_58 = "Scan the QR code that you see displayed below."
mobile_app_59 = "The project will automatically begin downloading and processing."
mobile_app_60 = "Dashboard"
mobile_app_61 = "App Logs"
mobile_app_62 = "Last Refresh"
mobile_app_63 = "Last Sync"
mobile_app_64 = "Project Download, but No Data Downloaded"
mobile_app_65 = "Project Download, but Partial Data Download"
mobile_app_66 = "Complete Download, Project and Data"
mobile_app_67 = "Device uninitialized"
mobile_app_68 = "App Event"
mobile_app_69 = "Time"
mobile_app_70 = "Effect"
mobile_app_71 = "Upload with"
mobile_app_72 = "Records."
mobile_app_73 = "Recent Downloads and Uploads (All Devices)"
mobile_app_75 = "No relevant data to display for any devices."
mobile_app_76 = "Import Data from File"
mobile_app_77 = "No associated files"
mobile_app_78 = "Emergency Data Dumps (All Devices)"
mobile_app_79 = "No files uploaded for any devices."
mobile_app_80 = "CSV"
mobile_app_81 = "Included Records"
mobile_app_82 = "Accompanying Files (to Import Manually)"
mobile_app_83 = "No data dump for this device"
mobile_app_84 = "No logs uploaded for this device"
mobile_app_85 = "REDCap User"
mobile_app_86 = "App User"
mobile_app_87 = "Action"
mobile_app_88 = "Data"
mobile_app_89 = "Mobile App Logs (All Devices)"
mobile_app_90 = "Listed below are all the log files sent from the mobile app for this project. Only the most recent one is shown in its totality. You may click the file icon on the right to download it. Reload the page to access the most recent log uploads."
mobile_app_91 = "Displayed below are the devices utilizing the REDCap Mobile App for this project and also a log of important activities - namely, the most recent project download and the five (5) most recent synchronizations. You may provide each device with a nickname to more easily identify the device in the activity below and other Mobile App pages. You may also 'block' an individual device so that it may no longer sync data, download data, or even have the project be accessible within the Mobile App on the device. For instance, you might want to block the device if it were stolen. This helps protect your data from being corrupted or from falling into the wrong hands."
mobile_app_96 = "Devices Used By The Mobile App"
mobile_app_97 = "No Devices Initialized For This Project"
mobile_app_98 = "Device UUID"
mobile_app_99 = "REDCap Nickname for Device"
mobile_app_100 = "Save Nickname"
mobile_app_101 = "Download CSV"
mobile_app_102 = "Add Nickname"
mobile_app_103 = "Edit Nickname"
mobile_app_106 = "Block Device"
mobile_app_107 = "Unblock Device"
mobile_app_108 = "Block Device?"
mobile_app_109 = "Blocked"
mobile_app_110 = "Expand Tables for All Devices"
mobile_app_111 = "Collapse Tables for All Devices"
mobile_app_112 = "Clicking the 'Import' button below will begin the import process to import ALL records contained inside the Data Dump CSV. (Note: Any non-blank values will overwrite any existing values in the project.) You will be given a chance to preview the changes. Please note that if you have modified fields or instruments in the projects after data was collected in the Mobile App, some error messages *may* be shown indicating that you will instead need to download your Data Dump CSV file and make the appropriate changes, after which you may attempt to upload the data file manually in the Data Import Tool."
mobile_app_113 = "Device"
mobile_app_114 = "Unblocked"
mobile_app_115 = "Back to Emergency Data Dumps (Mobile App Dashboard)"
mobile_app_116 = "The data you imported from the file was successfully imported into the project. If you wish to import more data, you may use the box above to select a file on your computer or you may return below to the Mobile App Dashboard."
mobile_app_117 = "All the data from the emergency data dump already exists in the project."
mobile_app_118 = "Record."
mobile_app_119 = "Unblocking a device allows it to communicate freely with the REDCap server. This is the normal mode of operation."
mobile_app_120 = "Blocking a device prohibits that one device from communicating freely with the REDCap server. This step should be taken if the device has been compromised or if someone gains unauthorized access (e.g., device is lost or stolen) in order to prevent possibly compromised data being sent back to the REDCap server. Blocking a device acts similar to revoking a token, except blocking is targeted only at specific device(s), whereas revoking a token would instead affect all devices."
mobile_app_121 = "Project Download with Some or All Data"
mobile_app_122 = "Map location"
mobile_app_124 = "View full list"
mobile_app_125 = "Full list of all included records in data dump"
mobile_app_126 = "Display details for this device"
mobile_app_127 = "[Device name is not known]"
mobile_app_128 = "Download app log"
mobile_app_130 = "<b>NOTICE:</b> You are a REDCap administrator, and since administrators always have maximum privileges, keep in mind that setting up this project on the mobile app under *this* account means that anyone accessing this project in the mobile app will also have maximum user rights in all parts of that project while in the app."
rev_history_01 = "Created project"
rev_history_02 = "Moved to production"
rev_history_03 = "Production revision"
rev_history_04 = "Download data dictionary"
rev_history_05 = "(current)"
rev_history_06 = "Draft Mode (current draft)"
rev_history_07 = "Time since project creation"
rev_history_08 = "Time in development"
rev_history_09 = "Time in production"
rev_history_10 = "Time since last revision"
rev_history_11 = "Average / median time between revisions"
rev_history_12 = "Project Revision Statistics"
rev_history_13 = "The tables below list information about when major changes and revisions were made to the project. The first table below displays when the project was created, and if the project is in production, it lists the time it was moved to production, as well as any revisions made to the project fields while in production. You may also download any of the Data Dictionaries from past revisions. The table at the bottom displays general statistics with regard to the times of project changes and revisions."
rev_history_14 = "Created by"
rev_history_15 = "Requested by"
rev_history_16 = "Approved automatically"
rev_history_17 = "Approved by"
rev_history_18 = "Moved to production by"
rev_history_19 = "Number of fields added"
rev_history_20 = "Number of fields deleted"
rev_history_21 = "Number of fields modified"
rev_history_22 = "Total fields <b>BEFORE</b> changes"
rev_history_23 = "Total fields <b>AFTER</b> changes"
rev_history_24 = "Project Revision Changes Statistics"
rev_history_25 = "Cell background color description:"
rev_history_26 = "No change"
rev_history_27 = "New Project Field Added"
rev_history_28 = "Project Field Deleted"
rev_history_29 = "Project Field Changed"
rev_history_30 = "Download Comparison Changes (CSV):"
rev_history_31 = "You can export all changes listed in below table."
rev_history_32 = "<b>NOTE:</b> There are 3 new columns in the CSV at start:<br>\"Change Status\", \"Changed Fields\" and<br> \"Change Details (field: old values)\""
rev_history_33 = "Preview Change of Field"
rev_history_34 = "New Value of"
rev_history_35 = "Old Value of"
rev_history_36 = "Displayed below is list of all changes made to fields in this project between"
rev_history_37 = "Comparing"
rev_history_38 = "Select Revision to Compare with"
rev_history_39 = "Compare Revision"
rev_history_40 = "Number of instruments added"
rev_history_41 = "Number of instruments deleted"
rev_history_42 = "To perform a comparison of any revision or snapshot, click the icons/buttons on the left-hand side of the table."
invite_participants_01 = "Get a public survey link or build a participant list for inviting respondents"
setup_01 = "Click if finished with this step."
setup_02 = "I'm done!"
setup_03 = "Complete!"
setup_04 = "Not complete?"
setup_05 = "Modify survey settings"
setup_06 = "Set Up My Survey"
setup_08 = "Success!"
setup_09 = "Your changes have been saved."
setup_15 = "The project is now in production."
setup_16 = "Your request to move the project to production status has been sent to a REDCap administrator."
setup_17 = "The secondary record ID field has been set."
setup_18 = "The secondary record ID field has been removed."
setup_24 = "Set up my survey"
setup_29 = "Add or edit fields on your data collection instruments (survey and forms). This may be done by either using the Online Designer (online method) or by uploading a Data Dictionary (offline method)."
setup_30 = "Design your data collection instruments"
setup_31 = "Add or edit fields on your data collection instruments. This may be done by either using the Online Designer (online method) or by uploading a Data Dictionary (offline method)."
setup_33 = "Define your events and designate instruments for them"
setup_34 = "Create events for re-using data collection instruments and/or set up scheduling."
setup_38 = "Additionally, if you wish to limit user access to certain records/responses for this project, you may want to use Data Access Groups, in which only users within a given Data Access Group can access records created by users within that group."
setup_39 = "User Rights and Permissions"
setup_40 = "You may grant other users access to this project or edit the user privileges of current users on this project by navigating to the User Rights page."
setup_41 = "Move your project to production status"
setup_43 = "Move project to production"
setup_44 = "Quick links: "
setup_45 = "Go to"
setup_52 = "You may use the options below to make customizations to the project. When done, click Save to save your changes."
setup_53 = "Reset"
setup_55 = "Email notifications for survey responses"
setup_57 = "Changes saved!"
setup_60 = "because this project contains at least one data collection instrument obtained from the"
setup_61 = "You may not distribute the data collection instruments(s) from the REDCap Shared Library outside your organization."
setup_62 = "View the Terms of Use"
setup_63 = "Please direct any questions to your"
setup_64 = "Survey is currently active"
setup_65 = "Survey is currently offline"
setup_66 = "Bring survey back online"
setup_67 = "Take survey offline"
setup_68 = "Other Functionality"
setup_69 = "Share your instruments with others via the REDCap Shared Library"
setup_70 = "When in production, you may share single data collection instruments from this project with other REDCap users around the world. This is done by uploading your instruments to the REDCap Shared Library. Select the instrument below that you wish to share. Before allowing you to share your instrument, you will be asked to fill out some basic information. (NOTICE: Copyrighted material may not be shared unless you are the owner.)"
setup_71 = "You cannot share instruments to the REDCap Shared Library right now because you are currently in Draft Mode."
setup_72 = "The project is now back in development status."
setup_77 = "API"
setup_78 = "Set up project bookmarks"
setup_79 = "Add or edit bookmarks"
setup_80 = "You may create custom bookmarks to webpages that exist inside or outside of REDCap. These bookmarks will be seen as links on the left-hand project menu and can be accessed at any time by users who are given privileges to do so. Every project bookmark has custom settings that allow one to control its appearance and behavior."
setup_81 = "Set up a randomization model"
setup_82 = "The randomization module will help you implement a defined randomization model within your project, allowing you to randomize your subjects (i.e. records in your project)."
setup_83 = "Set up randomization"
setup_84 = "Enable my survey(s)"
setup_87 = "Active"
setup_89 = "for data collection instrument"
setup_90 = "Design your data collection instruments & enable your surveys"
setup_91 = "You may then enable your instruments to be used as surveys in the Online Designer."
setup_94 = "Auto-numbering for records"
setup_95 = "Enable optional modules and customizations"
setup_96 = "Use surveys in this project?"
setup_97 = "(longitudinal only)"
setup_98 = "Randomization module"
setup_100 = "Modify project title, purpose, etc."
setup_101 = "In progress"
setup_102 = "Not started"
setup_103 = "Optional"
setup_104 = "Additional customizations"
setup_105 = "Main project settings"
setup_106 = "Some options below are disabled because they may not be modified once the project is in production status."
setup_107 = "The option to enable auto-numbering has been disabled because your first data collection instrument has been enabled as a survey. In this case, auto-numbering is mandatory for the project."
setup_108 = "The option to enable the scheduling module has been disabled because you have not enabled longitudinal data collection, which is required in order to use scheduling. If you wish to utilize longitudinal data collection, you may enable it at the top of the page."
setup_109 = "Disable longitudinal data collection?"
setup_110 = "Are you sure you wish to disable longitudinal data collection? If you do so, please note that all your arms and events that you have created thus far will become hidden and will no longer be accessible. If you have collected some data already, only the data collected for your first event (on the first arm) will remain. If you wish to enable longitudinal data collection again, all your events and any data collected on them will return."
setup_111 = "Disable the usage of surveys in this project?"
setup_112 = "Are you sure you wish to disable the usage of surveys in this project? If you do so, please note that all your surveys that you have created thus far will become hidden and will no longer be accessible. Your data collection instruments will remain just as they are, but they will simply not be able to be utilized as surveys. If you wish to enable the use of surveys in this project again, all your surveys that you had previously created will return."
setup_115 = "If the participant's email address has already been captured directly in the Participant List, then that email address will supersede the value of the email field here when survey invitations are sent to the participant."
setup_116 = "Choose an email field to use for invitations to survey participants:"
setup_117 = "You did not select a field from the drop-down list. Please select a field."
setup_118 = "Are you sure you wish to undesignate this email field to use for invitations to survey participants? If you have some survey responses that already utilize it, it may prevent some invitation emails from sending in the future if you have additional surveys that those participants need to complete."
setup_119 = "Undesignate email field"
setup_120 = "Undesignate field"
setup_121 = "Field currently designated:"
setup_122 = "Using the designated email address field can be especially valuable when your first data collection instrument is not enabled as a survey while one or more other instruments have been enabled as surveys. Since email addresses can only be entered into the Participant List directly for the first data collection instrument, the designated email field provides another opportunity to capture the email address of survey participants."
setup_123 = "Test your project thoroughly"
setup_124 = "It is important to test the essential components of your project before moving it into production. Try creating a few test records and entering some data for each to ensure that your data collection instruments look and behave how you expect, especially branching logic and calculations. Then review your test data by creating reports and exporting your data to view in Excel or a statistical analysis package. If you have surveys, complete the surveys as if you were a participant by using the Public Survey Link or Participant List by sending a survey invitation to yourself. If other project modules will be used regularly, test them out a bit too. The best way to test your project is to use it as if you were entering real production data, and it is always helpful to have colleagues (especially team members) take a look at your project to get a fresh set of eyes looking at it."
setup_125 = "No name or emails listed"
setup_126 = "Notifications Enabled"
setup_127 = "Recipient email address"
setup_128 = "not selected"
setup_129 = "If you or other users wish to be notified via email <u>every time</u> a participant completes a survey, select the users to be notified under each survey listed below by selecting their email address in the user's drop-down list, which may contain each user's primary, secondary, or tertiary email address for their REDCap account. To remove a user as a recipient for the survey notifications, change their email drop-down option to 'not selected', after which they will no longer receive notification emails for that survey."
setup_130 = "(Primary)"
setup_131 = "(Secondary)"
setup_132 = "(Tertiary)"
setup_133 = "Please be aware that designating an email field means that survey responses can NEVER BE ANONYMOUS because of the fact that the participant's email address can be viewed on a data entry form, which means it is easy to identify the record/response to which the email address belongs."
setup_135 = "I Agree"
setup_136 = "ERROR: This project is utilizing the randomization module and cannot be moved to production status yet because a randomization allocation table has not been uploaded for use in production status. Someone with appropriate rights must first go to the Randomization page and upload an allocation table."
setup_137 = "DELETE ALL DATA?"
setup_139 = "WARNING: RANDOMIZATION FIELD'S DATA WILL BE DELETED"
setup_140 = "Since you have enabled the randomization module, please be advised that if any records contain a value for your randomization field (i.e. have been randomized), those values will be PERMANENTLY DELETED once the project is moved to production. (Only data for that field will be deleted. Other fields will not be touched.) Is this okay?"
setup_141 = "YES, Move to Production Status"
setup_142 = "Yes, Request Admin to Move to Production Status"
setup_143 = "API Playground"
setup_144 = "Request pending"
setup_145 = "Repeating instruments"
setup_146 = "Repeating instruments and events"
setup_147 = "Are you sure you really want to delete all existing data when the project is moved to production? If not, click Cancel and change the setting inside the yellow box."
setup_148 = "Repeat this instrument?"
setup_149 = "Repeat entire event or selected instruments?"
setup_151 = "Repeat Entire Event (repeat all instruments together)"
setup_152 = "Repeat Instruments (repeat independently of each other)"
setup_153 = "Move the project to production status so that real data may be collected. Once in production, you will not be able to edit the project fields in real time anymore. However, you can make edits in Draft Mode, which will be auto-approved or else might need to be approved by a REDCap administrator before taking effect."
setup_154 = "Custom label for"
setup_155 = "repeating instruments"
setup_156 = "A 'Custom Label for Repeating Instruments' can optionally be added to any instrument that has been set to repeat. Custom Labels are similar to Custom Record Labels, in which they allow you to display data (via piping) from a given instrument on the Record Home Page of a record, in which this piped data will be displayed in a special table containing all repeated instances of this instrument. For example, if an instrument represents a single visit of a person, then if you are collecting the date in a field called 'visit_date' on each repeated instance of the instrument, then you can set the Custom Label as '[visit_date]'. This will provide useful context when viewing a table all repeated instances of the instrument on the Record Home Page. You can also get more advanced with the piping by using multiple fields and even static text. For example, '[visit_date], [weight] kg'."
setup_157 = "Your settings for repeating instruments and/or events have been successfully saved. (The page will now reload.)"
setup_158 = "Below you can specify a data collection instrument to be infinitely repeatable, which means that an instrument can be repeated over and over again (a different number of times for each record) even without enabling REDCap's longitudinal module. Once an instrument is set to repeat, you will see options on the Record Home Page to add another instance of the instrument for the currently selected record. All instances of a repeating instrument will then be displayed as a table near the bottom of the Record Home Page, thus allowing viewing of the instances and easy navigation within them."
setup_159 = "Below you can specify a data collection instrument or a whole event of instruments to be infinitely repeatable, in which each repeating instrument or event can be repeated a different number of times for each record. You may set any event in the project to be repeatable *or* alternatively set selected instruments to be repeatable within an event. <b>The 'Repeat Entire Event' option means that all the event's instruments will repeat together and stay connected, whereas the 'Repeat Instruments' option implies that the instruments will repeat separately and independently from each other on that event.</b> Once an instrument or event is set to repeat, you will see options on the Record Home Page to add another instance of the instrument/event for the currently selected record."
setup_160 = "-- not repeating --"
setup_161 = "ERROR: One or more events have the option 'Repeat Instruments' selected but do not have any instruments selected. Please either select some instruments for that event or change the value of the repeat option drop-down."
setup_162 = "Use longitudinal data collection with defined events?"
setup_163 = "An excellent way to collect repeating data in REDCap is to use repeating instruments and/or repeating events. This is sometimes called one-to-many data collection. Some examples may include but are not limited to the following: data from multiple visits or observations, concomitant medications, adverse events, or repetitive surveys (daily, weekly, etc.)."
setup_164 = "(select instruments to repeat)"
setup_165 = "Survey-specific email invitation field"
setup_166 = "Note: This option will override the project-level email invitation field (if enabled on the Project Setup page) and will also override any email address originally entered into the Participant List. Also, if this field has no value and the project-level email field is enabled, then the project-level email field's value will be used instead."
setup_167 = "Designate an email field for sending survey invitations for <u>this survey only</u>"
setup_168 = "Also, if the email invitation field exists on multiple longitudinal events, on a repeating instrument, or on a repeating event, the field's value will be synchronized across all instances/events so that changing it in one location will change the value across all events/instances where the field appears."
setup_169 = "A survey-specific email invitation field can be enabled for any given survey, in which you can designate any email field in your project to use for sending survey invitations for that particular survey. Thus, you can collect several email addresses (e.g., for a student, a parent, and a teacher) and utilize each email for a different survey in the project. Then you can send each person an invitation to their own survey, after which all the survey responses get stored as one single record in the project."
setup_170 = "The survey-specific email field is similar to the project-level email invitation field except that it is employed only for the survey where it has been enabled. In this way, the survey-level email can override an existing email address originally entered into the Participant List or the project-level email field (if used). This feature allows users to have data entry workflows that require multiple surveys where the participant is different for each survey. (Note: The email field can exist on any instrument in the project, and you may use a different email field on each survey. You may also use the same email field for multiple surveys.)"
setup_171 = "While the email invitation field discussed here is a project-level setting, it is helpful to know that there also exists a survey-level email invitation field option that can be utilized for particular surveys in the project (whereas the project-level field would be applied to ALL surveys)."
setup_172 = "See the 'Survey Settings' page in the Online Designer for this survey-level setting."
setup_173 = "PDF Customizations"
setup_174 = "Downloadable PDFs of data entry forms and surveys can be customized using the options below. Note: The options will be applied to ALL instruments in the project."
setup_176 = "Default text:"
setup_177 = "Display or hide the REDCap logo and website URL at the bottom right of every PDF page?"
setup_178 = "Display REDCap logo and website URL (default)"
setup_179 = "Hide REDCap logo/URL and instead display the following text:"
setup_181 = "Hide it"
setup_183 = "You may designate a text field to serve as a unique constraint whose value cannot be duplicated or shared by any other record in the project. When a value is entered or imported for the secondary unique field, it will be checked in real time to ensure it is not shared by another record, and if so, it will ask the user to enter another value. Additional options exist below that dictate if and how the secondary unique field will be displayed in conjunction to a record name on various pages in the project."
setup_184 = "Display or hide the Secondary Unique Field value at the top right corner of the PDF? (This option is only applicable if the Secondary Unique Field is enabled above and is set to be displayed.)"
setup_185 = "Keep it displayed"
setup_186 = "CODING ERROR: The are issues in the formatting of your missing data codes. Please see the issues listed below. You will need to fix them or remove them in order to save the missing data codes."
setup_188 = "is not in the correct code format. Codes can only have letters, numbers, dots, dashes, and underscores (e.g., '-999, Not asked')."
setup_189 = "Hide Record ID from PDF header? (This will remove the record ID from the header of every PDF page.)"
setup_190 = "It appears that the project-level email invitation field has been enabled already. Please note that <u>it is not required to select a survey-specific email field</u> here if a project-level email field has already been defined. This is an optional setting only."
setup_191 = "Designate an email field for communications (including survey invitations and alerts)"
setup_192 = "By enabling this feature, REDCap can direct specific email communications to the email address provided. This includes sending survey invitations, automated survey invitations, survey confirmation emails, and Alerts & Notifications. If a field is designated for that purpose, then any records in your project that have an email address captured for that particular field will have that email address show up as the participant's email address in the Participant List (unless an email address has already been entered for that participant in the Participant List directly)."
setup_193 = "Use the MyCap mobile app in this project?"
setup_194 = "Disable the usage of MyCap in this project?"
setup_195 = "Are you sure you wish to disable the usage of MyCap in this project? If so, please note that all your MyCap task settings and configuration that you have created thus far will become hidden and will no longer be accessible. Your data collection instruments will remain just as they are, but they will simply not be able to be utilized by MyCap. If you wish to enable the use of MyCap in this project again, all your MyCap tasks settings and configuration that you had previously created will return."
setup_196 = "Use the MyCap participant-facing mobile app?"
setup_197 = "The option to enable the longitudinal data collection has been disabled because you have enabled MyCap for this project, which ONLY supports non-longitudinal projects. If you wish to utilize longitudinal data collection, you may disable MyCap on this page (in the 'optional modules and customizations' section)."
setup_198 = "MyCap ONLY supports classic/non-longitudinal projects. The MyCap option has been disabled in this project because you are currently using longitudinal data collection. If you wish to utilize MyCap for this project, you must disable longitudinal data collection at the top of the page."
setup_199 = "<b>NOTE:</b> One or more instruments are enabled as MyCap and those instruments must be repeatable to work correctly for data collection from MyCap Mobile app. You cannot mark those instruments as non-repeating. If you wish to make instrument non-repeating, you must first delete MyCap task Settings for that instrument from Online Designer."
setup_200 = "The MyCap External Module is already enabled for this project. To enable or manage the MyCap configuration from REDCap,    data from MyCap External Module should be migrated to REDCap First. Only REDCap Administrators are allowed to migrate data from MyCap External Module to REDCap. Please contact your local administrator for help."
setup_201 = "You must agree to the Terms of Use below before you are allowed to perform the desired action"
setup_202 = "<b>NOTE:</b> One or more event's instruments are enabled as MyCap and those instruments must be repeatable to work correctly for data collection from MyCap Mobile app.    You cannot mark those event's instruments as non-repeating. If you wish to make instrument non-repeating, you must first disable event from the MyCap task Settings for that instrument from Online Designer."
setup_206 = "Set custom header text to appear at top left of every PDF page (it may be left blank, if desired). Only static text can be entered; thus piping cannot be utilized here. This text will not be displayed in PDFs emailed to, viewed by, or downloaded by survey participants."
survey_01 = "End the survey?"
survey_02 = "You have selected an option that triggers this survey to end right now."
survey_06 = "Question numbers will not display correctly if using auto numbering if some questions have branching logic employed. Question auto numbering has been automatically disabled because some of your survey questions use branching logic."
survey_07 = "Branching logic in surveys causes question numbers to display incorrectly when using question auto numbering because it hides the entire question."
survey_08 = "Notice for survey named"
survey_09 = "Thus, the question numbering for this survey has now been automatically set to 'custom numbered' to prevent this issue."
survey_10 = "Thus, the question numbering for this survey will be automatically set to 'custom numbered' to prevent this issue."
survey_11 = "It appears that this survey has not been set up yet. You will first need to "
survey_12 = "set up the survey"
survey_13 = "before you can view it."
survey_14 = "Thank you for your interest, but you are not a participant for this survey."
survey_15 = "A respondent"
survey_16 = "completed your survey titled"
survey_17 = "You may"
survey_18 = "view their responses here"
survey_20 = "page, if you have privileges to access that page."
survey_21 = "Survey completed:"
survey_22 = "Returning?"
survey_23 = "Begin where you left off."
survey_24 = "If you have already completed part of the survey, you may continue where you left off. All you need is the return code given to you previously. Click the link below to begin entering your return code and continue the survey."
survey_25 = "Continue the survey"
survey_27 = "Partial"
survey_28 = "Complete"
survey_33 = "belonging to"
survey_34 = "No participants exist"
survey_36 = "Sent?"
survey_37 = "Participant List"
survey_39 = "Check Sent"
survey_40 = "Check Not Sent"
survey_41 = "Check All"
survey_42 = "Uncheck All"
survey_43 = "remove"
survey_44 = "No participants have been added"
survey_45 = "Displaying"
survey_46 = "Invitation Sent?"
survey_47 = "Responded?"
survey_49 = "Survey Title"
survey_50 = "Title to be displayed to participants at the top of the survey page"
survey_51 = "Question Numbering"
survey_52 = "Auto numbered"
survey_53 = "Custom numbered"
survey_57 = "Allow 'Save & Return Later' option for respondents?"
survey_59 = "Logo"
survey_60 = "(Optional: display an image above the survey title)"
survey_61 = "Preview (displaying here at max 500 pixel width):"
survey_62 = "Remove Logo"
survey_63 = "Add new logo:"
survey_65 = "Survey Instructions"
survey_66 = "(Displayed at top of survey after title)"
survey_69 = "Participant Identifier (if exists)"
survey_72 = "To obtain the survey link, copy the URL below"
survey_73 = "and paste it into the body of an email message in your own email client. Your email recipient(s) can then click the link to begin taking your survey."
survey_76 = "The survey link below applies only to"
survey_79 = "Retrieving short survey link..."
survey_83 = "Click here to take the survey"
survey_86 = "More details"
survey_87 = "After receiving an email invitation and then completing the survey, the participant's response status in the list below will be changed to"
survey_88 = "Responded"
survey_89 = "Partial Response"
survey_90 = "No Response"
survey_91 = ", otherwise their status will remain as"
survey_92 = "Once a participant has responded, they will not be able to take the survey again."
survey_93 = "If a participant's email address needs to be changed after it has been added to the Participant List, you may simply click on the email address in the list to begin editing it. In order to be able to identify a specific participant's survey responses, you may provide a <b>Participant Identifier</b> after adding them to the participant list below, which is displayed as a separate field in the exported data results. The identifier may be the participant's name, an ID number, or whatever you desire. <b>NOTE:</b> If a sent email bounces because the email address was entered incorrectly or because the email account is inactive or does not exist, the bounced email will then be redirected back to the sender to notify them that the recipient did not receive the email."
survey_97 = "NOTE: Any participants added here will only be added to"
survey_98 = "Field Order:"
survey_99 = "Email, Participant Identifier (optional)"
survey_101 = "Example"
survey_103 = "Subject:"
survey_105 = "NOTE:"
survey_110 = "Alternatively, if you have forgotten your return code or simply wish to start the survey over from the beginning, you may delete all your existing survey responses and start over."
survey_111 = "Thank you for your interest, but you have already completed this survey."
survey_112 = "Your survey responses were saved!"
survey_118 = "Return Code"
survey_119 = "A return code is <b>*required*</b> in order to continue the survey where you left off. Please write down the value listed below."
survey_120 = "The return code will NOT be included in the email below."
survey_121 = "Survey link for returning"
survey_122 = "You have just been sent an email containing a link for continuing the survey. For security purposes, <b>the email does NOT contain the return code</b>, but the code is still required to continue the survey. If you do not receive the email soon, please check your Junk Email folder."
survey_123 = "You may bookmark this page to return to the survey, OR you can have the survey link emailed to you by providing your email address below. For security purposes, <b>the return code will NOT be included in the email</b>. If you do not receive the email soon afterward, please check your Junk Email folder."
survey_124 = "Send Survey Link"
survey_126 = "Or if you wish, you may continue with this survey again now."
survey_127 = "Continue Survey Now"
survey_132 = "Page"
survey_133 = "of"
survey_134 = "You may open the survey in your web browser by clicking the link below:"
survey_135 = "If the link above does not work, try copying the link below into your web browser:"
survey_136 = "Your survey link for forwarding to participants"
survey_137 = "This link is unique to you and should not be forwarded to others."
survey_138 = "Your emails are being sent"
survey_141 = "[This message was automatically generated.]"
survey_143 = "You may continue your progress on this survey by clicking the link below. You will need your return code that was given to you on the survey webpage."
survey_144 = "Survey partially completed"
survey_151 = "Would you like to enable data collection using a survey?"
survey_152 = "Enable"
survey_153 = "as a Survey"
survey_154 = "Please complete the survey below."
survey_155 = "Thank you for taking the survey."
survey_156 = "Have a nice day!"
survey_157 = "The emails listed below are not valid email addresses. No participants were added. Please correct the invalid emails and submit your list of participants again."
survey_158 = "INVALID"
survey_159 = "An error occurred! The changes were not made. Please try again."
survey_160 = "You may edit the survey's basic information by modifying the fields below and clicking the Save Changes button."
survey_161 = "The return code you entered was incorrect. Please try again."
survey_162 = "You have not completed the entire survey, and your responses are thus considered only partially complete. For security reasons, you will not be allowed to continue taking the survey from the place where you stopped. So you have the option to 1) leave your survey responses unchanged as they are, or 2) you may start the survey over from the beginning so that you may complete it (this will delete all your previously existing responses when you begin again). To start the survey again, click the button below."
survey_163 = "You have partially completed this survey."
survey_165 = "Using a public survey link is the simplest and fastest way to collect responses for your survey. You may obtain the survey link below to email it to your participants. Responses will be collected anonymously (unless the survey contains questions asking for identifying data from the participant). <b>NOTE:</b> Since this method uses a single survey link for all participants, it allows for the possibility of participants taking the survey multiple times, which may be necessary in some cases. "
survey_166 = "Remove all participants"
survey_167 = "View Survey Results"
survey_168 = "Unfortunately, the survey results cannot be viewed at this time because the minimum number of completed responses for this survey has not yet been met. Please return again to this page in the near future to view the survey results. <b>IMPORTANT:</b> Make sure to write down your survey results code before leaving this page."
survey_169 = "Displayed on this page are the aggregate results from this survey with each question listed in the order that it appears on the survey."
survey_171 = "blue"
survey_173 = "orange"
survey_176 = "red"
survey_178 = "Email this page"
survey_179 = "Email address:"
survey_180 = "Send"
survey_181 = "Email successfully sent!"
survey_182 = "You may open the survey results page in your web browser by clicking the link below:"
survey_183 = "Your link for viewing your survey results"
survey_184 = "Allow survey respondents to view aggregate survey results after completing the survey?"
survey_185 = "After completing the survey, participants can view ALL responses in aggregate graphical format and/or as descriptive statistics. Also, the individual respondent's answers will be highlighted in the results."
survey_186 = "Do not show plots for questions lacking diversity in response values?"
survey_187 = "Minimum number of responses required before participants are allowed to view aggregate data (recommended = 10)."
survey_188 = "Additional settings:"
survey_189 = "What does this mean?"
survey_190 = "This option is often used when the survey may be collecting sensitive data. In such situations, enabling this setting helps to ensure that survey participants are not able to learn the responses of other participants. "
survey_193 = "Want to return to this page later?"
survey_194 = "Write down your survey results code:"
survey_195 = "You can ONLY return to this page again if you have your survey results code. Please write it down now."
survey_196 = "<b>ERROR:</b><br>The survey results code you just entered does NOT match the one originally given to you."
survey_197 = "Want to view the aggregate survey responses again?"
survey_198 = "Enter your survey results code:"
survey_199 = "If you enter the survey results code given to you right after you completed this survey, you will be able to view the aggregate survey results. If you do not have the survey results code, you will not be able to view the results."
survey_200 = "Submit"
survey_201 = "<b>NOTE:</b> The email sent to the address above will <u>NOT</u> contain the survey results code, which must be written down and kept."
survey_202 = "Insufficient data exists for this question to be displayed."
survey_203 = "Display Graphical Plots (only)"
survey_204 = "Display Descriptive Statistics (only)"
survey_205 = "Display both Graphical Plots and Descriptive Statistics"
survey_206 = "This field cannot be displayed because no data exists for it."
survey_207 = "For example, if an HIV study has participants taking a survey, in which case one of the questions is 'Do you have HIV?', then if all the participants answer 'Yes', then that participant will know from looking at the graphical bar chart for that question that all other participants have HIV. And knowing such information may thus violate confidentiality agreements regarding who can have knowledge to an individual's medical information."
survey_208 = "Essentially, if a categorical question has had all respondents select the same choice, then the bar chart will not be displayed in the graphical results and will instead display the following message to the participant:"
survey_209 = "Graphs:"
survey_210 = "Statistics:"
survey_211 = "Descriptive statistics will be displayed below for each question. For categorical (multiple choice) questions, it will display a count of all missing and unique values, as well as the frequency of occurrence for each choice selected in the question. For numerical questions, it will display a count of all missing and unique values along with other useful statistics, such as the minimum, maximum, mean, and standard deviation across all responses. Also displayed are percentiles and a listing of the five lowest and highest values for that question."
survey_217 = "Unfortunately, for security reasons this file cannot be re-downloaded until the current web page has first been saved by clicking the button at the bottom of the page. You may close this window or tab in your browser."
survey_219 = "Thank you for your interest, but this survey is not currently active."
survey_220 = "Open survey"
survey_225 = "Your email was successfully sent to"
survey_226 = "SURVEY WARNING:"
survey_228 = "back into the first event position for this arm. Otherwise, all survey responses collected hereafter will be saved under the event named"
survey_229 = "Export list"
survey_230 = "Add participants"
survey_233 = "Public Survey URL:"
survey_234 = "Short Public Survey URL:"
survey_235 = "Embed HTML code"
survey_236 = "Open public survey"
survey_237 = "Send me URL via email"
survey_240 = "Copy the HTML in the text box below to place it within the HTML code of any webpage. It will show up as a link on that webpage so that anyone can easily click the link to begin taking your survey."
survey_243 = "When clicking the 'Responded' icon, you may only view responses that have a Participant Identifier defined. Thus you will <u>not</u> be able to view this participant's response by clicking this icon. This is done in order to preserve this response as anonymous."
survey_244 = "Response cannot be viewed:"
survey_245 = "Click to view the response"
survey_246 = "Click to open survey for this participant"
survey_250 = "Participant Identifier"
survey_251 = "(optional)"
survey_252 = "Are you sure you wish to ENABLE Participant Identifiers?"
survey_253 = "Are you sure you wish to DISABLE Participant Identifiers?"
survey_254 = "Participant identifiers allow you to identify an individual's survey answers. If you attribute an identifying number or designation to any participant in the Participant List, <b><u>the survey can never be considered anonymous</u></b>."
survey_255 = "If you disable participant identifiers, you will <b>no longer be able to add or edit a value in the Participant Identifiers column in the Participant List</b>. Also, disabling identifiers will <u>delete ALL existing identifiers</u> (excluding those for partial or completed responses)."
survey_256 = "Yes, ENABLE Participant Identifiers"
survey_257 = "Yes, DISABLE Participant Identifiers"
survey_258 = "Participant Identifiers have now been DISABLED, and any existing identifiers have been PERMANENTLY ERASED."
survey_259 = "The option to enable or disable the use of identifiers is only available while the project is in development status. Once in production, only a REDCap administrator can reverse this."
survey_260 = "Participant Identifiers have now been ENABLED."
survey_261 = "The Participant List will now reload to reflect the changes."
survey_262 = "Participant Identifiers are currently disabled and cannot be used until you enable them by clicking the 'Enable' button in the Participant List's header."
survey_263 = "Participant Identifiers are disabled and thus cannot be used in this project. Only a REDCap administrator can enable Participant Identifiers once the project is in production status."
survey_264 = "Cannot modify:"
survey_266 = "Compose Survey Invitations"
survey_267 = "Copy and paste your list of participant email addresses, <b>one per line</b>."
survey_268 = "If you are importing Identifiers for any participant, separate them by commas following the guidelines below."
survey_269 = "It appears you are attempting to provide participant identifiers for one or more participants. However, this is not possible because identifiers are not enabled. Please remove the identifiers for the emails listed below, and submit your list of participants again."
survey_270 = "REMOVE IDENTIFIER"
survey_271 = "You may utilize any data collection instrument as a survey by enabling the instrument on this page."
survey_272 = "Data may still be collected on the instrument via normal data entry on the form, but enabling it as a survey allows for the additional option of collecting data via survey by respondents."
survey_273 = "(from Email field)"
survey_274 = "select an existing email address"
survey_275 = "(from Participant List)"
survey_276 = "Or provide another email:"
survey_278 = "Compose survey invitation"
survey_279 = "Public Survey Link"
survey_280 = "-- check/uncheck participants --"
survey_281 = "Actions:"
survey_284 = "[No email listed]"
survey_285 = "Send Emails"
survey_286 = "No participants are selected from the Participant List"
survey_287 = "Loading Participant List..."
survey_288 = "Redirect to a URL"
survey_289 = "Provide a full URL, e.g. http://www.example.com/mypage.html"
survey_290 = "Survey Termination Options:"
survey_291 = "Survey Design Options:"
survey_292 = "(Redirect to a webpage when survey is completed)"
survey_293 = "Survey Access:"
survey_294 = "Survey Expiration (optional)"
survey_295 = "(Time after which the survey will become inactive.)"
survey_296 = "The time must be for the time zone"
survey_297 = ", in which the current time is"
survey_298 = "[could not be determined]"
survey_299 = "The survey expiration allows you to set the time after which the survey will become inactive (i.e. go offline) so that respondents may no longer take the survey. After expiration, the survey can be brought back online again (if needed) on the Project Setup page."
survey_300 = "Option to display the aggregate survey results has been disabled"
survey_301 = "The survey completion redirect option is not compatible with the option to allow survey respondents to view aggregate survey results after completing the survey, which you currently have enabled, because respondents will already be redirected to the other webpage before they can view the aggregrate results. Thus, the aggregate survey results setting has been disabled."
survey_302 = "Cannot enable this feature"
survey_303 = "The option to display the aggregate survey results cannot be enabled right now because the survey completion redirect option is currently enabled for this survey. These two options are not compatible. If you wish to enable the aggregate survey results option, you will first need to change the Survey Termination Options at the bottom of the page so that survey completion redirect setting is no longer enabled."
survey_304 = "(Allow respondents to leave the survey and return later.)"
survey_305 = "Survey is back online, but expiration time was removed"
survey_306 = "Your survey was brought back online successfully. However, the survey's expiration time"
survey_307 = "exists in the past. Because of this, the survey expiration time was automatically removed to prevent any issues. If you wish, you may set a new survey expiration time for this survey on the Modify Survey Settings page."
survey_310 = "Survey title:"
survey_314 = "Survey settings"
survey_315 = "Click to modify survey settings"
survey_316 = "Message Sent"
survey_317 = "Message Not Sent"
survey_318 = "Invitation Scheduled?"
survey_319 = "Check Scheduled"
survey_320 = "Check Not Scheduled"
survey_321 = "Check Not Sent and Not Scheduled"
survey_322 = "When should the emails be sent?"
survey_323 = "Immediately"
survey_324 = "At specified time:"
survey_325 = "Please provide a date/time for when the email(s) should be sent."
survey_326 = "The date/time provided for when the email(s) should be sent is invalid because it exists in the past. Please choose a date/time that resides in the future. The current time is "
survey_327 = "Date/time exists in the past!"
survey_328 = "Your emails have now been successfully sent to the participants you selected. If you sent a large quantity of emails that were scheduled to be sent immediately, it may take a moment for them to show up as 'Sent' in your Participant List."
survey_329 = "Your emails have been successfully sent!"
survey_331 = "Your emails have now been successfully scheduled to be sent for the participants you selected. Their survey invitation will be automatically sent by REDCap on the date/time that you specified."
survey_332 = "Your emails have been successfully scheduled"
survey_333 = "survey invitations were scheduled for"
survey_334 = "Your emails are being scheduled"
survey_337 = "Define Conditions for Automated Survey Invitations (ASI)"
survey_338 = "[All participants who meet the conditions defined]"
survey_340 = "Info"
survey_341 = "Conditions"
survey_342 = "Automated Invitations"
survey_343 = "Reschedule invitations?"
survey_344 = "Among the participants selected, "
survey_345 = "participants have survey invitations that are already scheduled to be sent. These participants will have their survey invitations rescheduled for the new time you specified. If you do not wish to reschedule them but instead wish to keep the current scheduled time, then click the Cancel button below and deselect them in the list."
survey_346 = "Message Sending..."
survey_347 = "When should this email be sent?"
survey_350 = "Survey Invitation Log"
survey_351 = "[Initial survey]"
survey_352 = "Public Survey not set up yet!"
survey_353 = "The public survey has not been set up yet, so a public survey link cannot be displayed here. A public survey is when the first instrument in your project has been enabled as a survey. If you wish to enable a public survey, you may click the button below, after which you will be able to obtain your public survey link and utilize the Participant List for the public survey."
survey_354 = "Enable public survey"
survey_355 = "The Participant List allows you to <b>send a customized email</b> to anyone in your list and <b>track who responds to your survey</b>. It is also possible to identify an individual's survey answers, if desired, by providing an Identifier for each participant (this feature must first be enabled by clicking the 'Enable' button in the table below)."
survey_357 = "You cannot utilize the 'Survey Distribution Tools' page until you have first enabled one or more surveys. You may enable surveys here on the Online Designer by clicking the Enable button for any given data collection instrument. Once you have enabled an instrument as a survey, you may collect data for it by distributing surveys by utilizing the 'Survey Distribution Tools' page on the left-hand menu."
survey_358 = "REMOVE ALL PARTICIPANTS?"
survey_360 = "REMOVE PARTICIPANT?"
survey_361 = "Are you sure you wish to remove the participant from the list? If they have already completed the survey, this will NOT delete their saved responses but will merely destroy the connection between them and their responses."
survey_362 = "PARTICIPANT REMOVED!"
survey_363 = "The participant has now been deleted from the Participant List."
survey_368 = "Remove all"
survey_369 = "ARE YOU SURE?"
survey_371 = "If you no longer wish to receive email confirmations triggered by survey responses, simply uncheck the checkbox for your user name for this survey in the Notifications pop-up on the"
survey_372 = "Display all surveys"
survey_373 = "Option:"
survey_374 = "Survey Status"
survey_375 = "Survey Offline"
survey_376 = "Survey Active"
survey_377 = "If offline, respondents will not be able take the survey."
survey_378 = "(previously entered)"
survey_381 = "Please note that deleting the survey settings will NOT delete any responses collected using the survey. Also, deleting the survey settings will NOT delete the data collection instrument, but instead the instrument will revert back to how it was before it was enabled as a survey, in which data can only be collected by authenticated users on the data entry form."
survey_382 = "If this survey is deleted, all participants will be removed from your Participant Lists associated with this survey, and all survey links and return codes will cease to function for this survey. Any email invitations that have been scheduled to be sent for this survey will be deleted. Additionally, all survey responses will have their 'survey completion' timestamp removed, as seen in a data export file or on the data entry form. If you choose to delete the survey, you may enable the data collection instrument as a survey again, but you will still lose all the survey-related information mentioned thus far."
survey_384 = "Survey successfully deleted!"
survey_385 = "The survey has been successfully deleted. You will now be redirected back to the Online Designer."
survey_386 = "Projects containing surveys"
survey_387 = "Projects not containing surveys"
survey_388 = "Cannot add participants for this survey"
survey_389 = "Survey participants cannot be added here because they can only be added to an 'initial survey', that is, your first data collection instrument. If you have already enabled your first data collection instrument as a survey, you can select it from the drop-down list of surveys in the Participant List, after which the Add Participants button will no longer be disabled, and then you may click it to add more survey participants. If you have not enabled your first data collection instrument as a survey, you may do so on the Online Designer page."
survey_392 = "Participant Email"
survey_393 = "Viewing Survey Invitation"
survey_394 = "Scheduled to be sent at"
survey_395 = "Time sent:"
survey_396 = "(could not be sent)"
survey_397 = "[no subject]"
survey_399 = "Listed below are the survey invitations that have already been sent or have been scheduled to be sent to survey participants in this project. For each invitation it displays the participant email, participant identifier (if exists), survey name, and the date/time in which the invitation was (or will be) sent. You may even view the invitation email itself by clicking the icon in the 'View Email' column. Please note that all times below correspond to the time zone"
survey_401 = "Sent automatically via Automated Invitations from"
survey_402 = "The 'begin time' filter occurs after the 'end time' filter. Please change one or both so that the 'end time' is a later time, otherwise no invitations can be displayed with the current filter settings."
survey_403 = "This field is a Form Status field, whose value cannot be modified for survey responses during a data import. Since this is a survey response, this field's value can only be modified on the survey itself or by marking it as a completed response on the data entry form."
survey_404 = "select a survey"
survey_406 = "When defining the conditions below, you may choose to have survey invitations be triggered by the completion of a survey or when pre-defined logic becomes true (i.e. when the data values of a given record fulfill a requirement). You may use either the logic or survey completion options as triggers, or you may use both together. (Please note that if you set it to be triggered when a specific survey is completed, this also includes if a non-survey user sets the Form Status field as 'Complete' on that survey's corresponding data entry form.) When setting the time after which the invitations will be sent, you may have it send the invitation immediately after the conditions are met or at a relative or fixed time after they are met. Lastly, you will need to activate the automated invitation settings you have defined here, which means that your settings will be initiated immediately and that REDCap will be actively 'listening' in order to send/schedule invitations for your surveys based upon the conditions you defined."
survey_407 = "NOTE: Since this project is longitudinal, if you are using logic as a condition, then you MUST provide the event name in the logic when specifying a field. For example, if you wish your logic to be [age] > 30, then you should also provide the unique event name to precede the variable name: [enrollment_arm1][age] > 30. By doing this, REDCap knows which event to look at when evaluating the logic. If the event name is not provided, the logic may not be evaluated correctly, and thus survey invitations may not get sent when they should."
survey_408 = "Settings for automated invitations were successfully saved!"
survey_409 = "Your settings that you defined for sending automated survey invitations have now been saved for"
survey_412 = "No invites sent yet"
survey_413 = "Invitation status:"
survey_414 = "It is also important to recognize that whenever the conditions below are met, the survey invitation will be immediately scheduled at that moment (whether it gets scheduled to be sent immediately, or after one minute, or after one month). So if an invitation, for example, is scheduled based upon data values using the conditional logic, then the invitation will be scheduled to be sent when that logic evaluates as true, even though the data may be changed again afterward, in which the logic may no longer evaluate as true. So even though the data values might be reverted, the invitation will still remain as having been scheduled."
survey_415 = "Please be informed that since you just moved the first event of this arm into another position (i.e. it is no longer the first event), your public survey link has now changed and points to a different URL (found at the top of the Survey Distribution Tools page). No data has been lost, but if you have already collected survey responses using the public survey link, you may want to consider moving the event named"
survey_416 = "-- select day --"
survey_417 = "(select any project user to be the 'Sender')"
survey_418 = "Specify conditions for sending invitations:"
survey_419 = "When the following survey is completed:"
survey_420 = "When the following logic becomes true:"
survey_421 = "When to send invitations AFTER conditions are met"
survey_422 = "Send immediately"
survey_423 = "Send on next"
survey_424 = "at time"
survey_426 = "days"
survey_427 = "hours"
survey_428 = "minutes"
survey_429 = "Send at exact date/time:"
survey_430 = "Activated?"
survey_432 = "Active"
survey_433 = "Not Active"
survey_434 = "(all events)"
survey_435 = "No invitations to list"
survey_436 = "Invitation send time"
survey_437 = "Survey"
survey_439 = "Begin time:"
survey_440 = "End time:"
survey_441 = "Display"
survey_442 = "Apply filters"
survey_443 = "All invitation types"
survey_444 = "Only sent invitations"
survey_445 = "Only scheduled invitations"
survey_446 = "All response statuses"
survey_447 = "Unresponded"
survey_448 = "Partial responses"
survey_449 = "Completed responses"
survey_450 = "All surveys"
survey_451 = "Please select a survey from the drop-down list as a condition for sending the invitations."
survey_452 = "Please specify a condition for sending the invitations."
survey_453 = "Please specify the conditional logic in the text box, or else uncheck its checkbox."
survey_454 = "Please specify the time when to send invitations after the conditions are met."
survey_455 = "Please specify next day and time to send the survey invitations."
survey_456 = "Please specify the lapse of time after which to send the survey invitations."
survey_457 = "Please specify the exact date/time to send the survey invitations."
survey_458 = "Please set the automatic invitations for this survey as either Active or Not Active."
survey_459 = "Enable auto naming"
survey_460 = "already exists as the name of a matrix group in this project. Please enter another matrix group name."
survey_461 = "The variable names listed below already exist in this project and thus cannot be duplicated. Please replace these variable names with ones that do not exist."
survey_462 = "Variables that already exist:"
survey_463 = "is an illegal variable name. Please enter another variable name."
survey_464 = "already exists in this project and thus cannot be duplicated. Please enter another value."
survey_470 = "The following fields listed in your branching logic do not exist in this project and thus cannot be used. These fields must be removed from the branching logic before you can continue."
survey_471 = "BRANCHING LOGIC ERROR"
survey_472 = "FIELDS:"
survey_473 = "CANNOT USE DRAG-N-DROP LOGIC BUILDER"
survey_474 = "Sorry, but you cannot use the Drag-N-Drop Logic Builder! The advanced branching logic syntax you are using is not compatible with the Drag-N-Drop Logic Builder, and so the logic can only be edited using the advanced method. If you wish to use the Drag-N-Drop Logic Builder again, you must first clear the logic or simplify the logic so that it is then compatible with this method."
survey_475 = "CANNOT MODIFY 'SQL' FIELD"
survey_476 = "For security purposes, 'sql' field types may ONLY be added or modified by REDCap administrators. Please contact them if you require assistance."
survey_477 = "Dynamic Query (SQL)"
survey_478 = "Single Checkbox (advcheckbox)"
survey_479 = "Only invitations that failed to send"
survey_480 = "It appears that Automated Invitations have been set up for other surveys, in which they are triggered by the completion of the first survey instrument. However, you have not designated an email field to use for sending invitations to survey participants (see the Optional Modules section of the Project Setup page). If you do not designate an email-validated text field to be your survey invitation email field, then the Automated Invitations will not work for the Public Survey Link because they will not have an email address to send the survey invitation to when scheduling the invitation for the next survey."
survey_481 = "Email field has not been designated"
survey_482 = "If you do not wish to use the Public Survey Link, then you can safely ignore this message."
survey_483 = "The designated email field does not exist on the first survey."
survey_484 = "It appears that Automated Invitations have been set up for your first survey and that you have also designated an email field to use for sending invitations to survey participants. However, your designated email field does *not* exist on the first survey, so it will be impossible to capture the participant's email address using the Public Survey Link. This means that the Automated Invitations will not work for the Public Survey Link because they will not have an email address to send the survey invitation to when scheduling the invitation for the next survey. In order to resolve this, you should go to the Online Designer and move the following field to your first data collection instrument:"
survey_486 = "Delete the scheduled survey invitation"
survey_487 = "Are you sure you wish to delete this survey invitation, which is scheduled to be sent to"
survey_488 = "The survey invitation has been successfully deleted. The page will now reload to reflect the changes."
survey_489 = "If this invitation is deleted, the participant will NOT receive an email to be invited to take the survey."
survey_490 = "Modify the invitation send time"
survey_491 = "Are you sure you wish to modify the 'send time' for this survey invitation, which is scheduled to be sent to"
survey_492 = "If the send time is modified, the participant will NOT receive the survey invitation at the current time but at the new time specified."
survey_493 = "Specify new date/time to send the invitation:"
survey_494 = "The survey invitation time has been successfully modified. The page will now reload to reflect the changes."
survey_495 = "If you need to retrieve your return code, please contact the survey administrator that originally sent you the survey invitation."
survey_498 = "Cannot add or modify identifier:"
survey_499 = "[undisclosed email address]"
survey_501 = "A participant identifier can only be *added* <u>before</u> the record has been created. It can be *modified* if the identifier existed <u>before</u> the record was created; however, the only place it can be modified is on Participant List for an Initial Survey (i.e. the first instrument)."
survey_502 = "Cannot modify email address here:"
survey_503 = "A participant's email address cannot be modified here but *can* be modified on the Participant List for an Initial Survey (i.e. the first instrument). Alternatively, if you are utilizing a 'designated email field', then you may modify the email address on the data collection instrument where the 'designated email field' is located."
survey_504 = "Begin survey"
survey_505 = "Survey Queue"
survey_506 = "Listed below is your survey queue, which lists any other surveys that you have not yet completed."
survey_507 = "Completed"
survey_508 = "Thank you for your interest, but this Survey Queue link is not valid."
survey_509 = "Close survey queue"
survey_510 = "Get link to my survey queue"
survey_511 = "To begin the next survey, click the 'Begin survey' button next to the title."
survey_512 = "Link to Survey Queue"
survey_513 = "Copy and paste the survey queue link"
survey_514 = "Send the survey queue link in an email"
survey_515 = "Enter email address"
survey_516 = "To obtain your survey queue link, which will allow you to return to your survey queue in the future, you may copy and paste the link displayed in the text box below, or you may have it emailed to you at your email address."
survey_520 = "Please follow this link to your Survey Queue to complete your surveys: "
survey_522 = "Please enter an email address"
survey_523 = "Your survey queue link"
survey_524 = "EMAIL SENT!"
survey_525 = "Set up Survey Queue"
survey_526 = "Display survey in the Survey Queue when..."
survey_527 = "How to use this"
survey_528 = "Your settings that you defined for the Survey Queue have now been saved."
survey_529 = "Auto start?"
survey_531 = "The Survey Queue displays a list of your surveys to a participant all on a single page, in which the queue comprises all surveys that are to be completed (like a 'to-do' list) as well as the surveys that the participant has already completed."
survey_535 = "(view all)"
survey_536 = "All surveys in your queue have been completed!"
survey_537 = "Custom text to display at top of survey queue (optional)"
survey_538 = "If no custom text is provided, then"
survey_539 = "this text"
survey_540 = "will be displayed by default."
survey_541 = "Add custom text to display at top of survey queue"
survey_542 = "Surveys can be set to appear in the Survey Queue based upon 1) if the participant has completed a particular survey, and/or 2) if certain conditions are met (based upon data values). If any surveys have been activated in the Survey Queue, they will be displayed to the participant after completing a survey (displayed below the survey completion text on the page). The participant will only see in their queue the surveys they have already completed and the surveys that they are being requested to take next (based upon the criteria defined below). The setup options below allow you to set the conditions that determine when each survey will be displayed in the queue, and (optionally) you can provide custom text to display at the top of every participant's survey queue, in which you may customize the styling of the text with HTML tags or even utilize Piping to inject data values. Additionally, the 'auto start' feature is optional and can be used to take the participant immediately to the first incomplete survey in the queue if 'auto start' is enabled for that survey, in which it allows for more rapid survey-taking if the participant is completing several surveys in one sitting."
survey_543 = "Not activated"
survey_544 = "Activated"
survey_545 = "The following surveys have been set to be activated, but they have either not had an option selected in their survey drop-down list or conditional logic has not been provided for them. Please set either or both of these attributes for the surveys listed below, or else click the Deactivate button for them to exclude them from the Survey Queue."
survey_546 = "Deactivate"
survey_547 = "Activate"
survey_548 = "Survey Notifications"
survey_549 = "Survey options:"
survey_550 = "ERROR: Survey has not been set up correctly!"
survey_551 = "This survey belongs to a REDCap project that is longitudinal; however, this data collection instrument has not been designated for this event, which means that this survey has not been designated for data collection, thus the survey cannot be displayed. Please log in to the REDCap project and go to the 'Designate Instruments for My Events' page, and enable this instrument for this event, after which you will then be able to complete this survey. If you are not a survey administrator, please notify your survey administrator of this issue."
survey_553 = "Survey Queue Link"
survey_557 = "Adaptive Instrument Settings"
survey_558 = "'No' is default and is recommended"
survey_559 = "You must either 1) select a value for the question displayed, or 2) skip this question by clicking the 'Skip Question' button below."
survey_560 = "Please select a value for the question displayed."
survey_561 = "Skip question"
survey_562 = "WARNING: Value not selected"
survey_563 = "Go back and enter value"
survey_567 = "Public Survey is not accessible!"
survey_568 = "The public survey will always point to the first data collection instrument on the first event in a longitudinal project. It appears that your first instrument has not yet been designated for the first event, so a public survey link cannot be displayed here. To fix this, you may click the button below to navigate to the page Designate Instruments for My Events, after which you will be able to designate your first instrument for the first event."
survey_569 = "Designate first instrument for first event"
survey_570 = "(in ascending order by time sent)"
survey_571 = "View past invitations"
survey_572 = "View future invitations"
survey_573 = "Survey Login"
survey_574 = "Before beginning or continuing this survey, you must first log in by successfully entering the correct values below."
survey_578 = "You must successfully enter a value for ALL the fields below."
survey_581 = "You have chosen to stop the survey for now and return at a later time to complete it. To return to this survey, you will need the survey link to this survey."
survey_582 = "You have just been sent an email containing a link for continuing the survey. If you do not receive the email soon, please check your Junk Email folder."
survey_583 = "You may bookmark this page to return to the survey, OR you can have the survey link emailed to you by providing your email address below. If you do not receive the email soon afterward, please check your Junk Email folder."
survey_584 = "You may continue your progress on this survey by clicking the link below."
survey_587 = "You must successfully enter a value for the field below."
survey_588 = "You must successfully enter a value for all required fields in the login form."
survey_589 = "Unfortunately, it appears that no login fields can be displayed for you because no data has been entered for those login fields for you beforehand, so there is no way to log in. Please contact your survey administrator to have this issue corrected."
survey_590 = "Add another login field"
survey_591 = "Login field"
survey_592 = "You may enable a Survey Login page on one or more surveys that will force your survey respondents to authenticate (log in) on your surveys before they are allowed to view and complete the survey."
survey_593 = "Below, select the fields that you wish to serve as the login fields for the respondent to enter, as well as several other settings that control how the survey login is applied to the surveys in your project. NOTE: Once a respondent has logged in to a survey, they will not be prompted to enter their login credentials again if they return to that survey or begin another survey using the survey login within the following"
survey_594 = "Please note that the login is *not* case sensitive."
survey_595 = "Minimum number of fields above that are required for login"
survey_596 = "Apply the survey login to all surveys in project?"
survey_597 = "All surveys"
survey_598 = "Only selected surveys (set on Survey Settings page)"
survey_599 = "Number of failed login attempts before respondent is locked out for a specified amount of time, which is set below."
survey_600 = "Amount of time respondent will be locked out after having failed login attempts exceeding the limit set above."
survey_601 = "Custom error message: Provide a custom error message that will be displayed on the survey login form for when the user experiences issues, such as not being able to log in successfully, so that they may contact you for help."
survey_602 = "If you have any trouble logging in to the survey, please contact"
survey_603 = "Fields to display on the survey login form"
survey_604 = "Customizations for survey login"
survey_605 = "Successfully saved!"
survey_606 = "Your Survey Login settings have been successfully saved!"
survey_609 = "Security settings for survey login (optional)"
survey_610 = "One or more login fields have not been selected but have been left blank. Please select a field in the drop-down list(s) or alternatively click the red X to remove their row in the table."
survey_611 = "You have not entered a custom error message. Please provide a custom error message that will be displayed on the survey login form for when the user experiences issues."
survey_612 = "It appears that you have only entered one of the two fields in the Security Settings section. Please fix this by removing the value entered or by providing the remaining value not entered yet."
survey_613 = "HTML may be used in order to add links or to add style to text."
survey_614 = "for help."
survey_615 = "The respondent will log in to the survey by entering one or more known values for fields in the project (up to three) - e.g., last name, date of birth. These values must already be saved in the respondent's record in the project. Those values may have been entered or uploaded by a user in the project or may have been entered on a previous survey by the respondents themselves. If Survey Login has been enabled and a record does not exist yet for the respondent (e.g., if they are beginning a Public Survey), then the survey page will be displayed normally and the login page will not be displayed for them. However, once the record exists, the respondent will always be prompted to log in to the survey (with the exception of a Public Survey, which is the only place where Survey Login cannot be used)."
survey_616 = "Enable Survey Login?"
survey_617 = "NOTE: Survey Login will be utilized instead of return codes for this survey since Survey Login has been enabled for all surveys in the project."
survey_618 = "Enforce 'Survey Login'?"
survey_619 = "Please enter your access code to begin the survey."
survey_620 = "Scan the QR Code"
survey_621 = "Survey Access Code or"
survey_623 = "To allow a respondent to begin this survey, have them navigate to the URL below and enter the survey access code. The code is permanent and will never change. (Note: The web address is the same for all projects and surveys, so you may bookmark the address on a computer or device to quickly return to it multiple times.)"
survey_624 = "2.) Then enter this code:"
survey_625 = "1.) Go to this web address:"
survey_626 = "Please follow the instructions below to navigate to the survey page."
survey_627 = "Survey Access Code and<br>QR Code"
survey_628 = "Survey Access Code"
survey_629 = "Get Survey Access Code"
survey_630 = "A Survey Access Code and a QR Code both allow respondents to begin a survey on another computer or device without someone having to email them an invitation."
survey_631 = "A Survey Access Code allows respondents to begin a survey on another computer or device without someone having to email them an invitation."
survey_632 = "The survey link has been converted into a QR code, which can now be scanned by a device that has an app capable of reading QR codes. Once the QR code below is scanned, it should take the respondent directly to the survey in a web browser."
survey_633 = "To start the survey, you may use either of the two choices (the Survey Access Code or the QR code), whichever you find easiest or quickest to use."
survey_634 = "Please enter the survey access code given to you."
survey_635 = "NOTE: Survey Login will be utilized instead of return codes for this survey since Survey Login has been enabled for this particular survey."
survey_636 = "If set to 'Yes', this survey will employ the Survey Login feature according to its settings defined in the Online Designer."
survey_637 = "This option provides respondents with a 'Save & Return Later' button on the survey page, which allows them to save their progress and return where they left off to complete the survey any time in the future. If the 'Survey Login' feature has been enabled for this survey (or for all surveys in the project), then the respondent will be required to enter their login credentials in order to continue the survey. However, if 'Survey Login' is not used, then the respondent will instead be given an auto-generated return code, which they will be required to enter upon returning to the survey in order to continue."
survey_638 = "(All respondents will be required to enter login credentials before beginning the survey and also any time they return to the survey again.)"
survey_639 = "NOTE: The Survey Login feature cannot be used for Public Surveys."
survey_640 = "Allow respondents to return and modify completed responses"
survey_641 = "Please note that the return code is *not* case sensitive."
survey_642 = "Please note that the access code is *not* case sensitive."
survey_643 = "By default, respondents are not allowed to modify their survey responses if the survey has been fully completed. By checking this checkbox, it allows respondents to return to a completed survey response (via the Save & Return Later functionality) and modify any of their answers in the survey. The survey response will remain as a completed response during this process and afterward. The only thing that will change with regard to the actual status of their survey response is that if the respondent gets to the end of the survey again and completes it again, the survey completion time will be updated with the new time of completion. If the survey has the Survey Login feature enabled, then the user will have to log in with their login credentials in order to return to the completed survey response. If that feature is not enabled, then their auto-generated return code will be required to allow them to return."
survey_644 = "Display page numbers at top of survey page"
survey_645 = "One page or multiple pages?"
survey_647 = "Survey Customizations:"
survey_648 = "This is especially useful if the respondent is currently nearby or if you will be sending the survey invitation to a physical mailing address (i.e. 'snail mail'). You may click the Print button at the bottom if you wish to print out the instructions for the respondent."
survey_649 = "Survey options"
survey_650 = "Start the survey by following the steps below."
survey_651 = "Alternatively, if you have a device that has an app capable of reading QR codes, you may scan the QR code below, which should take you directly to the survey in a web browser."
survey_652 = "Enter the Survey Access Code"
survey_653 = "Generate Short Code"
survey_654 = "Alternatively, you may generate a shorter, temporary code that will expire after only one use or after one hour has passed."
survey_655 = "2.) Go to the web address in step 1 above and enter this code:"
survey_656 = "Code will expire at"
survey_657 = "Return Code:"
survey_658 = "'Return Code' needed to return"
survey_659 = "Copy or write down the Return Code below. Without it, you will not be able to return and continue this survey. Once you have the code, click <i>Close</i> and follow the other instructions on this page."
survey_660 = "Sorry, but you must first enable the 'Save & Return Later' option before you can enable the checkbox setting to allow respondents to return and modify completed responses."
survey_661 = "To continue the survey, please enter the RETURN CODE that was auto-generated for you when you left the survey."
survey_662 = "Submit your Return Code"
survey_663 = "NOTE: Be sure that you are *not* entering a Survey Access Code, which is different from a Return Code. Survey Access Codes allow you to navigate to the survey page, but only Return Codes allow you to return when you have already started the survey."
survey_664 = "QR Code"
survey_669 = "Scheduled?"
survey_670 = "Check Not Responded"
survey_671 = "- Check Partial Response"
survey_672 = "- Check Completed Response"
survey_673 = "Check Responded (Partial and Complete)"
survey_674 = "We're sorry, but this survey response cannot be modified because someone has locked the response to prevent any changes to it. It can only be unlocked by a survey administrator who has locking/unlocking privileges. If this seems incorrect, please contact your survey administrator for this survey."
survey_675 = "Survey login session is still active"
survey_681 = "You entered an invalid value. Please try again."
survey_687 = "Invitation type"
survey_688 = "Email invitation"
survey_690 = "SMS invitation (contains phone number to call)"
survey_691 = "- How the participant is invited"
survey_692 = "Compose message"
survey_693 = "[All participants selected from Participant List]"
survey_694 = "Your messages have now been successfully sent to the participants you selected. If you sent a large quantity of messages that were scheduled to be sent immediately, it may take a moment for them to show up as 'Sent' in your Participant List."
survey_695 = "Your messages have been successfully sent!"
survey_696 = "messages were sent"
survey_697 = "message was sent"
survey_698 = "Your messages are being sent"
survey_699 = "Your voice calls are being initiated"
survey_700 = "Your voice calls have now been successfully initiated for the participants you selected. If you initiated a large quantity of voice calls that were scheduled to be made immediately, it may take a moment for them to show up as 'Sent' in your Participant List."
survey_701 = "Your voice calls have been successfully initiated!"
survey_702 = "voice calls were initiated"
survey_703 = "voice call was initiated"
survey_704 = "Your messages have now been successfully scheduled to be sent for the participants you selected. Their survey invitation will be automatically sent by REDCap on the date/time that you specified."
survey_705 = "Your messages have been successfully scheduled"
survey_706 = "Your voice calls have now been successfully scheduled for the participants you selected. The voice calls will be automatically initiated by REDCap on the date/time that you specified."
survey_707 = "Your voice calls have been successfully scheduled"
survey_708 = "Your messages are being scheduled"
survey_709 = "Your voice calls are being scheduled"
survey_711 = "Twilio SMS and Voice Call services"
survey_712 = "Note: In order to use the Twilio service, the REDCap web server must be able to make outbound HTTP/HTTPS requests to the following URL:"
survey_713 = "For more information on Twilio, see"
survey_714 = "Twilio account credentials (obtained from Twilio website)"
survey_715 = "Twilio Account SID"
survey_716 = "Twilio Auth Token"
survey_717 = "Twilio configuration settings"
survey_718 = "Twilio phone number"
survey_720 = "Show auth token"
survey_722 = "Language and gender used for voice calls"
survey_723 = "Female voice"
survey_724 = "Male voice"
survey_728 = "Initiate survey as voice call"
survey_729 = "Initiate survey as SMS conversation"
survey_732 = "[Reminder]"
survey_733 = "Enable reminders"
survey_734 = "Re-send invitation as a reminder if participant has not responded by a specified time?"
survey_735 = "Send every"
survey_736 = "Send only once"
survey_737 = "Send up to"
survey_738 = "times"
survey_739 = "Recurrence:"
survey_740 = "Display invitation reminders?"
survey_741 = "STEP 1:"
survey_742 = "STEP 2:"
survey_743 = "STEP 3:"
survey_744 = "In this pop-up you may define your conditions for automated survey invitations that will be sent out for the survey (and event, if a longitudinal project) listed in the Info box below."
survey_745 = "Automated survey invitations may be understood as a way to have invitations sent to your survey participants, but rather than sending or scheduling them manually via the Participant List, the invitations can be scheduled to be sent automatically (i.e. without a person sending the invitation) based upon specific conditions, such as if the participant completes another survey in your project or if certain data values for a record are fulfilled. Using the settings below, you may compose your survey invitation message, and then specify the conditions that must be met in order to send/schedule the invitation. You will also need to provide the time at which the invitation will be sent."
survey_746 = "OPTIONAL:"
survey_747 = "Survey Completion Text"
survey_748 = "(Displayed after survey is completed as 'thank you' text or as acknowledgement text)"
survey_749 = "(Times below refer to AFTER original invitation time.)"
survey_750 = "Hide the 'Previous Page' button (i.e., Back button) on the survey page"
survey_751 = "(prevents respondents from going back to previous pages)"
survey_752 = "For 'Required' fields, display the red 'must provide value' text on the survey page?"
survey_753 = "If 'No', then it will NOT display the following text beneath all 'Required' fields:"
survey_754 = "Reminder"
survey_755 = "Send confirmation email?"
survey_756 = "(Email the respondent when they complete the survey)"
survey_757 = "Do you wish to delete this logo?"
survey_758 = "Do you wish to delete this email attachment?"
survey_759 = "Remove attachment?"
survey_760 = "Provide email subject, email message, and (optionally) an attachment to be sent to respondent when they complete the survey."
survey_761 = "DISABLE THE SURVEY CONFIRMATION EMAIL? If so, this will remove the email message (and attachment, if any) below?"
survey_762 = "You did not provide an email subject or message for the survey confirmation email setting. You must provide both a subject and message, or else you may disable that option entirely."
survey_763 = "-- associate another email with your account --"
survey_764 = "Enter your email to receive confirmation message?"
survey_765 = "A confirmation email is supposed to be sent to all respondents that have completed the survey, but because your email address is not on file, the confirmation email cannot be sent automatically. If you wish to receive it, enter your email address below."
survey_766 = "Send confirmation email"
survey_767 = "SMS invitation (take survey via SMS conversation)"
survey_768 = "Use participant's preference"
survey_769 = "(those who have *and* have not responded)"
survey_770 = "Add Emails to Participant List"
survey_771 = "Each participant starting on a new line"
survey_772 = "Email (optional), Phone Number (optional), Participant Identifier (optional)"
survey_774 = "Add Emails or Phone Numbers to Participant List"
survey_775 = "Copy and paste your list of participant email addresses or phone numbers, <b>one per line</b>."
survey_776 = "Add participant email addresses"
survey_777 = "and/or phone numbers"
survey_778 = "Specify the default invitation preference for survey invitations for these participants:"
survey_779 = "Invitation preference"
survey_780 = "STEP 4:"
survey_781 = "STEP 5:"
survey_782 = "- PREFERENCE"
survey_783 = "(email address)"
survey_784 = "(phone number)"
survey_785 = "(from Phone field)"
survey_786 = "Or provide another phone number:"
survey_787 = "select an existing phone number"
survey_788 = "Your survey invitation was successfully scheduled to be sent to the recipient below at the listed time:"
survey_789 = "[undisclosed phone number]"
survey_790 = "The phone numbers listed below are not valid phone numbers. No participants were added. Please correct the phone numbers and submit your list of participants again."
survey_791 = "Send a Survey Invitation to Participants"
survey_792 = "Send Invitations"
survey_794 = "You may capture phone numbers for sending invitations to your survey participants by designating a field in your project. This can be done in addition to (or as an alternative to) entering phone numbers directly into the Participant List. So if a participant does not have a phone number that was added to the Participant List, it will use the value of this field when sending survey invitations via SMS or as voice calls."
survey_795 = "Are you sure you wish to remove ALL participants from the list below <b>that have not yet begun the survey?</b> If anyone from the list has already completed the survey (partial or in whole), this will NOT delete them from the participant list. NOTE: Re-adding any existing participants after deleting them will only create a new instance of the participant and will not reconnect the new instance with their old response."
survey_796 = "This process is irreversible. All participants listed will be permanently deleted, excluding those who have already completed the survey (partial or in whole)."
survey_797 = "PARTICIPANTS REMOVED!"
survey_798 = "The participants have now been removed."
survey_799 = "Send survey invitation via SMS to take survey as voice call (respondent makes call)"
survey_800 = "Send survey invitation via SMS to take survey as voice call (respondent receives call when replying via SMS)"
survey_801 = "SMS invitation (reply via SMS to receive voice call)"
survey_802 = "Survey as voice call"
survey_803 = "Survey as SMS conversation"
survey_804 = "Survey as webpage"
survey_805 = "Mixed types"
survey_806 = "Cannot modify phone number here:"
survey_807 = "The participant's phone number cannot be modified here because it originates from the 'designated phone field'. However, you can modify the phone number on the data collection instrument where the 'designated phone field' is located."
survey_808 = "In the text box below, enter the phone numbers of the respondents to which you wish to send survey invitations, either as a voice call or SMS text message."
survey_809 = "Enter phone numbers below with one number per line"
survey_810 = "Choose how these participants will take the survey and be invited:"
survey_811 = "SUCCESS! Your invitations for the public survey have been successfully sent to the following phone numbers:"
survey_812 = "Send more"
survey_813 = "ERROR! Your invitations for the public survey failed to send for the following phone numbers:"
survey_814 = "Enter custom SMS message:"
survey_815 = "Invite participants via Voice Call or SMS"
survey_816 = "You may invite participants to complete the public survey via voice call or SMS. If you wish to invite them directly *right now*, click the button below to open a popup for entering phone numbers to call or send an SMS text message to the participants."
survey_817 = "Call the phone number"
survey_818 = "Send the code"
survey_819 = "as an SMS message to the phone number"
survey_820 = "and enter the code"
survey_821 = "Alternatively, if you instead want the participants to initiate the survey themselves, then you may provide your participants with the instructions for one of the options below."
survey_823 = "Voice Calling and SMS options for the Public Survey"
survey_825 = "Invite participants now:"
survey_826 = "ERROR: Cannot send due to missing emails or phone numbers"
survey_827 = "There are"
survey_828 = "participants that are missing either an email address or phone number, thus making it impossible to send them an invitation using the Invitation Type selected. You can cancel the sending of the invitations, or if you wish, you can have the problematic participants auto-unchecked and send the invitations to the rest of the participants."
survey_829 = "Uncheck and Send Invitations"
survey_835 = "Once your Twilio account has been created, you must <b>2) fund your account with some money</b> (using the Billing page in Twilio) and then <b>3) purchase a phone number</b> to be used for this REDCap project (see the Numbers page in Twilio). Once a phone number has been purchased for the account, obtain the Account SID and Auth Token for your account (see the API Credentials section on the main Account Settings page), and then enter the Account SID, the Auth Token, and the phone number into the 'Twilio account credentials' section below. NOTE: Whenever you set the services as Enabled below and then click the Save button, REDCap will check with your Twilio account to confirm if all the credentials and info are correct. REDCap will not allow you to enable the Twilio SMS and voice call services below until it has verified that the Account SID, Auth Token, and phone number are all valid. "
survey_836 = "Choose survey invitation types to use"
survey_837 = "You may select several different ways for participants to be invited to take surveys and also the medium in which they will take the surveys"
survey_841 = "Please note that 'localhost' CANNOT be used as part of the REDCap Base URL (see General Config page) because Twilio will reject any requests made from a localhost address."
survey_842 = "The Twilio module could NOT be enabled for this project because a phone number has not yet been entered. Once a phone number associated with the Twilio account has been entered, you will be able to enable the Twilio functionality in this project."
survey_843 = "NOTICE: There are no phone numbers associated with the Twilio account."
survey_846 = "How do I set this up?"
survey_847 = "Enable Twilio web service for voice calls and SMS services?"
survey_848 = "This will allow Twilio services to be utilized in REDCap projects, such as for sending survey invitations and taking surveys via SMS or as voice calls."
survey_849 = "Display information about Twilio services to <u>all users</u> on Project Setup page in a project?"
survey_850 = "No, hide all information about Twilio services"
survey_851 = "Yes, display information about Twilio services"
survey_852 = "If 'No' is selected, then Twilio SMS and voice call services will not be advertised to users on the Project Setup page, and all information about Twilio will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make Twilio services known to only a limited number of users without advertising it to all users."
survey_853 = "Additionally, your REDCap server must be publicly available to the web (in the DMZ) so Twilio's web servers can make requests to it. Otherwise, Twilio cannot completely function."
survey_854 = "The participant's email address cannot be modified here because it originates from the 'designated email field'. However, you can modify the email address on the data collection instrument where the 'designated email field' is located."
survey_855 = "Your participants have been added to the Participant List."
survey_856 = "PARTICIPANTS ADDED!"
survey_857 = "Cannot modify phone number here:"
survey_858 = "A participant's phone number cannot be modified here but *can* be modified on the Participant List for an Initial Survey (i.e. the first instrument). Alternatively, if you are utilizing a 'designated phone field', then you may modify the phone number on the data collection instrument where the 'designated phone field' is located."
survey_859 = "The participant's identifier cannot be added <u>after</u> the record has been created if the identifier was originally blank beforehand. This is to prevent users from adding an identifier after the fact and thus incidentally turning an anonymous response into an identifiable response."
survey_860 = "Change participant's invitation preference:"
survey_861 = "When adding participants to the participant list, you can choose the default invitation preference for how they will be sent their invitation. An individual's invitation preference can be changed at any time in the participant list. Then when you are ready to send your survey invitations to participants, you can choose the delivery method used for sending that batch of invitations. The preference does not have to be used when you are sending invitations, but it is provided as a convenience in case you have participants with several different invitation preferences. Listed below are all the invitation types that are available in this project."
survey_863 = "To begin the phone survey, call"
survey_865 = "To begin the survey, reply to this message with any text."
survey_866 = "To begin the phone survey, reply to this message with any text to receive a phone call."
survey_869 = "Analyze surveys for SMS & Voice Calls"
survey_880 = "SMS Survey Issues"
survey_881 = "Participant makes voice call to initiate the survey"
survey_882 = "Participant receives voice call after sending an SMS message to initiate the survey"
survey_883 = "Participant initiates survey as SMS conversation"
survey_884 = "Voice call (participant receives voice call)"
survey_885 = "Voice Call Survey Issues"
survey_886 = "Calculated fields cannot be used in SMS or voice call surveys."
survey_887 = "Field type is unknown"
survey_888 = "File Upload fields cannot be used in SMS or voice call surveys."
survey_889 = "Text fields can only be used in voice call surveys if they have integer or number validation."
survey_890 = "Multiple choice fields (drop-down, radio buttons) can only be used in voice call surveys if *all* their raw coded values are numerical."
survey_891 = "Checkbox fields cannot be used in voice call surveys."
survey_892 = "Notes fields cannot be used in voice call surveys."
survey_893 = "ISSUE:"
survey_894 = "No surveys have been enabled, so there is nothing to show here."
survey_895 = "The table below displays any issues that might be experienced if using a survey as a voice call survey or as an SMS conversation. To see the details of any issue, click the 'view' link next to it, which will display the field with the issue, as well as a description of why this field would be problematic. NOTE: If a survey below is administered as a voice call survey or SMS conversation, then <b>any field having an issue will be skipped</b> in the survey unless the issue described below is remedied by changing or removing the field."
survey_898 = "(Enter a value from 0 to 100.)"
survey_899 = "If you wish to continue to the next survey, press any number."
survey_900 = "If you wish to continue to the next survey, reply to this message with any text."
survey_901 = "View Invite"
survey_902 = "Click to view the invitation"
survey_903 = "[undisclosed phone number]"
survey_904 = "You must choose at least one of the checkboxes for the survey invitation types to use."
survey_905 = "To skip this question, press zero."
survey_906 = "(Reply with 0 to skip question)"
survey_907 = "NOTE: Each line must have either an email address or phone number (or both). If the participant has a phone number but no email address, you may begin the line with the phone number."
survey_908 = "Who can enable Twilio services in a given project?"
survey_909 = "All users (who have Project Design privileges)"
survey_910 = "Only Administrators can view the setting and enable it"
survey_911 = "If 'Only Administrators' is selected, then normal users will not even see the setting on the project's Project Setup page (only Administrators will be able to see it and enable it). If 'All users' is selected, then any user with Project Design/Setup privileges in that project can see the setting and can also enable it on their own to utilize Twilio services in their project."
survey_912 = "NOTE: This setting is only applicable if the 'Only Administrators' option is selected for the setting immediately above."
survey_917 = "[Subject will not be used in SMS and voice call invitations]"
survey_918 = "[Message text above will not be used in voice call invitations]"
survey_919 = "ERROR: Could not connect to Twilio successfully, which likely means that the Account SID or Auth Token was not entered correctly. The Twilio setting cannot be enabled until this is fixed."
survey_920 = "ERROR: The phone number provided does not belong to the Twilio account. Please double check to make sure you entered the correct phone number. If you have not yet purchased a phone number for your Twilio account, then after logging in to Twilio.com, go to the 'Numbers' page and click the 'Buy a number' button, which you can then use for this project. The numbers below are all the phone numbers associated with the account. The Twilio setting cannot be enabled until this is fixed."
survey_921 = "Displayed below is the survey invitation message as it was sent to the survey participant. Included is the time the invitation was sent, the sender, the email address (or phone number) of the survey participant, and the invitation's subject and message."
survey_922 = "Ensure logic is still true before sending invitation?"
survey_923 = "This setting is optional for Automated Survey Invitations. When enabled, REDCap will re-evaluate the logic against the record's data values whenever the record values are changed AFTER the invitation has been scheduled but BEFORE it has been sent to the respondent. And if the logic is no longer true (i.e., if the data values have changed during the time after the survey invitation was scheduled), it will not send the invitation to the respondent but will instead delete it (as if it had never been scheduled). Additionally, if the invitations get deleted due to this setting, then the invitations *may* get scheduled again later if data values are changed such that the logic evaluates as true again. Enabling this setting provides you with greater control over when and how invitations get sent when using conditional logic for Automated Survey Invitations."
survey_925 = "Choose the <u>default invitation preference</u> for new survey participants"
survey_926 = "ERROR: Your default invitation preference has not been checked as a checkbox in the 'Choose survey invitation types to use' section. Please either check its checkbox or change your default invitation preference to another value."
survey_927 = "Has Twilio's 'Request Inspector' been disabled for this account?"
survey_929 = "Has not been checked! You must check it now before Twilio services can be enabled."
survey_930 = "Check it now?"
survey_931 = "Note: Performing this check will cost a small amount of money, in which your Twilio account to be charged with a one-minute phone call."
survey_934 = "Yes, it has been disabled."
survey_935 = "Last checked on"
survey_936 = "Check it again now?"
survey_937 = "NOTE: Only a REDCap administrator can enable the Twilio services in your project, so please contact them to talk to them about how to do this."
survey_938 = "You may enable the Twilio services yourself by clicking the Enable button, after which you will need to follow the instructions provided to fully enable this functionality in your project."
survey_940 = "NOTE: Changing the preference here will change it for ALL surveys in this project for this participant."
survey_941 = "NOTE: Invitations here are sent out in real time, so please be patient if you are sending out many invitations as it may take a couple seconds to send each one at a time."
survey_942 = "You entered"
survey_943 = "Cannot enable SMS conversation option"
survey_945 = "Automatically append response instructions to questions?"
survey_946 = "If this option is set to 'No', then the survey respondent will be given only a question's field label and option choices' text as-is, which means that you will need to modify your question text to say 'For chocolate, press 1. For vanilla, press 2...'. But if you set this option to 'Yes', you may leave your existing question text 'Chocolate, Vanilla, ...', and REDCap will automatically add 'Press 1' to the end of the 'Chocolate' choice text for a voice call, for example. And for an SMS message, it will add '(1)' to the beginning of the choice text in the message."
survey_947 = "No, do not append"
survey_948 = "Yes, auto-append response instructions"
survey_949 = "Suggestion: If you are planning to have all your respondents take the survey using only one medium (via webpage, SMS, or voice call), then it is often best to set this option to 'No' and customize each question's text for that medium. But if you will be utilizing two or more different mediums to collect responses, then setting it to 'Yes' can provide more flexibility because REDCap will display the text appropriately for each medium."
survey_951 = "Press"
survey_952 = "(For FALSE, enter 0. For TRUE, enter 1.)"
survey_953 = "(For NO, enter 0. For YES, enter 1.)"
survey_954 = "Allow participants to skip questions?"
survey_955 = "SMS invitation (contains survey link)"
survey_956 = "To begin the survey, visit"
survey_957 = "Send survey invitation with survey link via SMS"
survey_958 = "NOTICE: The Twilio phone number"
survey_959 = "is currently being used by another REDCap project on this server. The same Twilio phone number cannot be used on multiple REDCap projects. So you will need to buy a new phone number in your Twilio account, and use that new number for this project."
survey_960 = "To begin a survey below, respond with its access code:"
survey_961 = "Please choose one of the following surveys."
survey_963 = "Allow participant to choose which survey to take next"
survey_964 = "Behavior for overlapping SMS invitations"
survey_967 = "PRIVACY & SECURITY INFO: It is important to understand that this feature utilizes the third-party service Twilio.com, which means that all voice calls and SMS messages will be routed through Twilio's servers. However, REDCap goes to great length to ensure that voice call records and SMS transcriptions do not stay in Twilio's logs but are removed shortly after being completed. This is done for security and privacy concerns (e.g., HIPAA), in which your survey participants' phone numbers and their survey responses do not get permanently logged on Twilio's servers but instead remain securely in REDCap."
survey_969 = "SETUP & CONFIGURATION: To use this feature, you must have a Twilio.com user account that is funded with some money (since there is a cost for each phone call made and for each SMS message sent). If you do not have a Twilio account, it is very easy to go to Twilio.com and create one. Once your REDCap project is connected to your Twilio account by entering your Twilio account credentials on your REDCap project's Project Setup page, you can then configure how you want to use Twilio in your project. In general, not much is different between administering a survey normally in REDCap than when using Twilio SMS/voice calls except that you additionally choose how your survey invitations are delivered. The following choices are available: 1) Initiate survey as voice call, 2) Initiate survey as SMS conversation, 3) Send survey invitation with survey link via SMS, 4) Send survey invitation via SMS to take survey as voice call (respondent makes call), 5) Send survey invitation via SMS to take survey as voice call (respondent receives call when replying via SMS). Any or all of these invitation delivery methods can be utilized within a single project. The choice of delivery method completely depends upon your specific use case for how you want to collect data from your participants."
survey_970 = "VOICE CALL SURVEYS: When participants take a survey as a voice call, questions are asked one at a time, in which the Twilio service will use text-to-speech technology to read the questions to the participant audibly on their phone. You may choose the language and/or dialect in which the text should be read. Participants will respond by entering numbers on their phone's keypad, thus only numeric responses can be used because of this limitation (this includes the use of integer/number fields and also multiple choice questions with numeric codings, in which the participant will enter the numeric coded value on their keypad, not the label that is read to them over the phone). For example, the question might be a Yes-No question, which might look like 'Do you like ice cream? Yes, press 1. No, press 0.', or a number question like 'What is your age?'."
survey_971 = "To learn more about using Twilio SMS and voice call services in REDCap, contact your local REDCap administrator."
survey_972 = "SURVEY COMPATIBILITY: Most of REDCap's survey features still function much the same when taking a survey via SMS or as a voice call. This includes the enforcement of required fields, field validation, branching logic, using the Survey Queue for multiple surveys (only works with Auto-Start enabled), survey email notifications and confirmations, the Participant List, Automated Survey Invitations, survey Stop Actions, and computer adaptive tests (CATs) downloaded from the REDCap Shared Library. One of the few survey features that is not compatible is the Survey Login feature."
survey_973 = "SMS SURVEYS: When participants take an SMS survey, questions are asked one at a time as an SMS text message conversation/thread. SMS surveys provide more response possibilities than voice calls. While participants in voice calls can only respond with numbers, they may respond with any kind of alpha-numeric text for an SMS survey. NOTE:"
survey_975 = "COST: In order to use the Twilio SMS and Voice Call services in a REDCap project, you will have to connect your project to your Twilio account by entering your Twilio credentials into REDCap during the setup process. And as REDCap makes calls and/or sends SMS messages using this service, all charges to your Twilio account will be made based upon its usage. This is not done by REDCap but is done internally by Twilio as you use its services. In this way, no monetary transactions are made by REDCap, and thus it is your responsibility to maintain the funds in your Twilio account in order to ensure that the service continues to work for your REDCap project. If your Twilio account runs out of funds, the Twilio services in REDCap will cease to function. For information on the cost of each call or each SMS message, visit your Twilio account to view the rates."
survey_976 = "TWILIO ACCOUNT SETUP INSTRUCTIONS:"
survey_977 = "View text on separate page"
survey_978 = "Take surveys in same order as participant received the invitations"
survey_979 = "Use only most recent invitation (ignore previously sent invitations)"
survey_980 = "If you will be sending SMS invitations for multiple surveys within this project, then you will need to choose the default behavior for when a participant has received SMS invitations to multiple surveys at the same time, in which they will be replying to the same SMS thread for multiple invitations. (This is rare but must still be accounted for.) If the participant has received multiple SMS invites, you can have it behave according to the option selected in the drop-down to the right."
survey_981 = "Only used when sending SMS invites for multiple surveys in this project."
survey_982 = "ERASE YOUR RESPONSES? Are you sure you wish to start the survey over from the beginning? Please note that doing so will erase ALL your responses already entered for this survey."
survey_984 = "Text-To-Speech functionality"
survey_985 = "(Allows text on survey page to be read audibly to participants.)"
survey_986 = "When enabled, icons will be displayed next to all text on the survey page, and when clicked, the text will be read out loud to the participant (must have computer speakers turned on)."
survey_987 = "Administrators, if you wish to disable the Text-To-Speech functionality to prevent the option from displaying here, you may do so on the Modules/Services Configuration page in the Control Center. Once disabled, users will no longer be able to see this option or utilize this feature."
survey_988 = "Language of text to be spoken:"
survey_990 = "Administrators: How to disable this feature"
survey_991 = "* Does not perform translation but only reads text in the language specified here."
survey_995 = "(initially On but can be turned Off by participant)"
survey_996 = "(initially Off but can be turned On by participant)"
survey_997 = "Enable speech"
survey_998 = "Disable speech"
survey_999 = "Automatically start the next survey instrument after finishing this survey"
survey_1000 = "Linking surveys together is only supported inside the same event and must be enabled for each survey you wish to link. This feature allows you to have separate survey instruments strung together to appear as though they were a single survey to the survey participant. This is especially useful for complex longitudinal projects where different combinations of instruments are given in separate events. If enabled and this is the last survey, the selected termination option below will be used. NOTE: If you wish to utilize more advanced conditional logic to control which survey that the participant goes to next, you should use the Survey Queue feature, which can be enabled in the Online Designer."
survey_1001 = "Auto-continue to next survey instrument"
survey_1003 = "Your survey settings were successfully saved!"
survey_1006 = "If new participants are created via data entry form (rather than via survey), then you may select their default survey invitation preference that will get assigned to them when their record is created. This is useful if you are creating records using a data import or on a data entry form, but wish to send survey invitations later for SMS surveys or voice call surveys, in which this setting automatically sets their invitation preferance for you. Without this setting, you would otherwise have to set each participant's preference individually in the Participant List. Also, this value will be used as the pre-selected setting of the delivery preference on the Participant List page when adding new participants to the list."
survey_1007 = "To take the survey, please call back at this phone number."
survey_1008 = "(those who have not responded completely)"
survey_1009 = "NOTICE: All text that is spoken is sent to a service hosted by Vanderbilt University Medical Center that utilizes the IBM Watson Text-to-Speech API service. Be advised that if the survey utilizes piping, for privacy concerns, data piped from Identifier fields will *not* be sent to the service with the rest of the text but will instead be redacted."
survey_1010 = "selected"
survey_1011 = "Basic Survey Options:"
survey_1012 = "Size of survey text"
survey_1013 = "Normal"
survey_1014 = "Large"
survey_1015 = "Very large"
survey_1016 = "Survey theme"
survey_1017 = "Default"
survey_1018 = "Font of survey text"
survey_1020 = "Survey design preview (sample survey):"
survey_1021 = "This is the survey title"
survey_1022 = "Your survey instructions will go here. The instructions can tell your survey participant about the purpose of the survey, as well as what to expect once they have completed the survey. Below is a listing of various question types that might be displayed on your survey."
survey_1023 = "This is a section header to divide the survey page into sections."
survey_1024 = "Thanks for taking the survey!"
survey_1025 = "Survey title and instructions:"
survey_1026 = "Survey questions:"
survey_1027 = "Section headers:"
survey_1028 = "Page Background Color"
survey_1029 = "Button Text Color"
survey_1030 = "General:"
survey_1031 = "Custom survey theme options:"
survey_1032 = "Customize"
survey_1033 = "Exit customization"
survey_1034 = "Save custom theme"
survey_1035 = "Save your custom theme"
survey_1036 = "Enter new theme name"
survey_1037 = "Enter a name for the theme you have customized on this page so that you may use it again later. After saving it, you will be able to choose it in the survey theme drop-down list when creating or editing other surveys."
survey_1038 = "REDCap Survey Themes"
survey_1039 = "My Saved Survey Themes"
survey_1040 = "Other Survey Themes (created by other users)"
survey_1041 = "Manage saved themes"
survey_1042 = "Copy design to other surveys"
survey_1043 = "You may copy any of the current survey's design settings to other surveys in this project. Check off the specific settings you wish to copy, and then choose the surveys to which those settings should be applied."
survey_1044 = "Copy design settings"
survey_1045 = "Copy the following design settings:"
survey_1046 = "Apply to the surveys below:"
survey_1047 = "(Cannot copy logo because it has not been saved yet for this survey.)"
survey_1048 = "You did not select any surveys on the right-hand side. Please select at least one survey checkbox."
survey_1050 = "(including any customizations)"
survey_1051 = "The survey's design settings were successfully copied."
survey_1052 = "NOTE: Please remember that if you have made modifications to any survey design options on this page, their new value will not be saved for this survey until you click the Save button at the bottom of the page."
survey_1053 = "Download log (as seen below)"
survey_1054 = "Reminder number"
survey_1055 = "Participant Phone"
survey_1056 = "Errors<br>(if any)"
survey_1057 = "Listed below are all the saved survey themes that you have created. You can rename or delete any of them by clicking the icons to their right. Note: If you delete any theme that is currently being used by a survey, that survey will revert back to the default survey theme."
survey_1058 = "used by"
survey_1059 = "surveys"
survey_1060 = "survey"
survey_1061 = "not yet used"
survey_1062 = "Delete theme"
survey_1063 = "Are you sure you wish the delete your survey theme named"
survey_1064 = "Latin fonts"
survey_1065 = "Non-Latin fonts"
survey_1066 = "Show value"
survey_1067 = "A Twilio feature named Request Inspector causes all activity to be logged in detail and stored on Twilio's servers. For the highest level of privacy, it MUST BE DISABLED in your Twilio account in order to be able to utilize the Twilio services in REDCap. You will find this setting on the Configure page under 'Programmable Voice'."
survey_1069 = "No, it remains enabled. Please disable it in your Twilio account on the Configure page under 'Programmable Voice'. You will not be allowed to enable the Twilio services in this project until the Request Inspector has been disabled."
survey_1070 = "Delete Survey Settings"
survey_1071 = "Delete this instrument's survey settings?"
survey_1072 = "Use enhanced radio buttons and checkboxes?"
survey_1073 = "Standard radios and checkboxes"
survey_1074 = "Enhanced radios and checkboxes"
survey_1075 = "Show example"
survey_1076 = "Displayed below is a screenshot example of how enhanced radios and checkboxes appear on a survey, rather than being displayed as standard radio and checkbox elements. Their text color and background color are customizable. Also, normally the choices will display as two columns on the survey page, but when the survey is viewed on narrow screens, such as mobile devices, the choices will instead stack into a single column for a better user experience."
survey_1077 = "Includes Yes/No and True/False fields"
survey_1078 = "Standard/enhanced radios and checkboxes"
survey_1079 = "[Erase survey responses and start survey over]"
survey_1081 = "Sample Survey Title"
survey_1082 = "PIPED DATA"
survey_1084 = "Must save instrument first!"
survey_1085 = "NOTICE: Since this page is a repeating instrument or is on a repeating event and does not have any data saved for it yet, the survey options cannot be utilized until this instrument has first been saved. Please click the 'Save & Stay' button to proceed with utilizing the survey options."
survey_1086 = "Note: All survey responses collected are considered anonymous unless you 1) are using Participant Identifiers or 2) have enabled the designated email field for invitations."
survey_1090 = "Take this survey again"
survey_1091 = "Set custom text for the button:"
survey_1094 = "Location of the button on survey:"
survey_1095 = "Before survey is completed, next to Submit button"
survey_1096 = "After survey is completed, below Survey Completion Text"
survey_1097 = "Submit and"
survey_1098 = "Response Limit (optional)"
survey_1099 = "(Maximum number of responses to collect. Prevents respondents from starting the survey after a set number of responses have been collected.)"
survey_1100 = "If left blank, the response limit will not be enforced."
survey_1101 = "Thank you for your interest; however, the survey is closed because the maximum number of responses has been reached."
survey_1102 = "Time Limit for Survey Completion (optional)"
survey_1104 = "If the respondent loads the survey after this time has passed, it will not allow them to begin or continue the survey. (If all are left blank, the time limit will not be enforced.)"
survey_1105 = "Thank you for your interest; however, the time limit for survey completion has been reached, so you will not be able to begin or continue the survey."
survey_1107 = "Will include"
survey_1108 = "partial and completed responses"
survey_1109 = "completed responses only (exclude partials)"
survey_1110 = "An important note about using the Response Limit feature is that if the limit has been reached for a given survey, then the survey will no longer show up in a participant's Survey Queue (if enabled), the Survey Auto-continue option (if enabled on the Survey Settings page) will skip over this survey, and also Automated Survey Invitations (if enabled) will no longer be scheduled for the survey."
survey_1111 = "LONGITUDINAL NOTE: If your project has the longitudinal module enabled, then please keep in mind that the Response Limit will be applied to each event individually where the survey is utilized. For example, if the response limit is set to 50, then even though the survey on Event 1 has reached the limit, the survey on Event 2 and so forth will still be open if the survey on those events have not reached the limit."
survey_1112 = "RECORD DELETION NOTE: If records/responses are deleted from the project after the response limit has been reached, in which the number of responses falls below the limit again, then the survey will begin showing up in the Survey Queue again, the Survey Auto-continue option will begin working normally again, and Automated Survey Invitations will begin to be scheduled again. However, in this case, any invitations that did not get scheduled via Automated Survey Invitations after the limit had been reached will *not* get automatically scheduled again if the response count falls below the limit due to the deletion of records/responses, in which case those invitations would have to be scheduled manually."
survey_1113 = "NOTICE: This survey's response limit has been reached, so it would not make sense to send any more invitations at this time."
survey_1114 = "NOTICE: This survey's response limit has been reached, which means that no more invitations will be scheduled at this time."
survey_1115 = "NOTICE: This survey's response limit has been reached *for this event*, which means that no more invitations will be scheduled at this time."
survey_1116 = "Custom text to display to respondent on survey when limit is reached:"
survey_1117 = "Link Expiration"
survey_1118 = "Survey link will expire on"
survey_1119 = "Survey link expired on"
survey_1120 = "(Click icon to modify)"
survey_1121 = "Modify the participant's link expiration time"
survey_1122 = "To modify the participant's link expiration time, change it in the text box below OR alternatively click the 'Expire it now' button, and then click Save. <b>NOTE: This will permanently override the participant's default link expiration time</b>, which is based on the survey's 'Time Limit For Completion' setting. Additionally, if the survey's Time Limit setting is modified in the future (i.e., for the entire survey), it will *not* affect the overridden time for the participant set here (unless the setting is completely disabled for the survey)."
survey_1123 = "The participant's link expiration time was successfully modified to"
survey_1124 = "NOTE: Please be advised that changing the values above to a new value for Time Limit for Survey Completion will cause all the link expiration times to change on this survey for your participants who have already been sent an invitation (this excludes any participant where you have manually changed/overridden their link expiration time on the Participant List)."
survey_1125 = "New link expiration time:"
survey_1126 = "Participant:"
survey_1127 = "Expire it NOW"
survey_1128 = "(NOTE: Any email address manually entered above will be used only this one time when sending an survey invitation. Any other invitations sent out at other times will instead go to the email address found in the Participant List for this participant.)"
survey_1129 = "Click to increase font size"
survey_1130 = "Click to decrease font size"
survey_1131 = "This field cannot be edited because its value originates from the Participant List."
survey_1132 = "upcoming scheduled invitations"
survey_1133 = "Upcoming Scheduled Survey Invitations"
survey_1134 = "The table below displays this record's upcoming survey invitations that are scheduled to be sent in the next"
survey_1135 = "upcoming scheduled invitation"
survey_1136 = "Allow participants to download a PDF of their responses at end of survey?"
survey_1137 = "Display a button for the participant to download a PDF file of their responses for the survey they just completed."
survey_1138 = "This option will not be available if the Survey Auto-continue or Survey Queue auto-start option is enabled. Also, if a field utilizes the @HIDDEN action tag, it will not be displayed in the PDF."
survey_1139 = "Download your survey response (PDF):"
survey_1140 = "image"
survey_1141 = "Click here to return and continue the survey where you left off."
survey_1142 = "0% means"
survey_1143 = "50% means"
survey_1144 = "100% means"
survey_1145 = "Question required."
survey_1146 = "Click to upload a file in a modal dialog."
survey_1147 = "Signature"
survey_1148 = "Include PDF of completed survey as attachment"
survey_1149 = "WARNING: Since email is not considered a secure form of communication, the PDF attachment option is NOT recommended if the survey contains questions asking for identifying information (e.g., PHI)."
survey_1150 = "Sorry, but you must first enable the 'Save & Return Later' option before you can enable the checkbox setting to allow respondents to return to their survey response without needed a return code."
survey_1151 = "Allow respondents to return without needing a return code"
survey_1153 = "(NOTICE) Please be aware that Action Tags have no effect on SMS surveys or Voice surveys because they only operate on a web page. This field has the following Action Tags:"
survey_1154 = "Please be aware that action tags have no effect on Twilio SMS surveys or Voice surveys because action tags operate on surveys and forms for web pages only. Any action tags will simply be ignored for fields utilized on SMS and Voice surveys."
survey_1155 = "You have not completed the entire survey, and your responses are thus considered only partially complete. However, this survey response has been locked by a survey administrator, so you will not be able to complete the survey until someone has unlocked it. If this seems incorrect, please contact your survey administrator for this survey."
survey_1156 = "You have partially completed this survey, but your response is LOCKED."
survey_1162 = "e-Consent version:"
survey_1163 = "e-Consent type:"
survey_1164 = "First name field:"
survey_1165 = "Last name field:"
survey_1166 = "Date of birth field:"
survey_1169 = "Displayed below is a read-only copy of your survey responses. Please review it and the options at the bottom."
survey_1170 = "If any information above is not correct, you may click the 'Previous Page' button to go back and correct it."
survey_1171 = "I certify that all of my information in the document above is correct. I understand that clicking 'Submit' will electronically sign the form and that signing this form electronically is the equivalent of signing a physical document."
survey_1172 = "Identifier (Name, DOB)"
survey_1173 = "Version"
survey_1174 = "Type"
survey_1175 = "(includes end-of-survey certification & archival of PDF consent form)"
survey_1176 = "Electronic Consent (e-Consent) is a platform for consenting patients or research subjects either on site or at home using a computer-based consent form rather than traditional paper documentation. Consent forms can be implemented in a REDCap survey via computer, mobile phone, or tablet."
survey_1179 = "What is the e-Consent Framework?"
survey_1180 = "Auto-Archiver enabled"
survey_1181 = "Displayed below are PDF files that have been automatically captured and stored by the PDF Auto-Archiver setting, which has been enabled by one or more surveys on their Survey Settings page. Only users with 'Full data set' data export privileges will be able to download the archived files. Note: The PDFs below were archived when a participant completes a survey, which means they might be different from other downloadable PDFs in the project that are generated on demand using the current data."
survey_1183 = "How can the 'signature' process be handled for e-Consent?"
survey_1184 = "Patients/subjects can 'sign' their consents by typing in their name or by utilizing REDCap's 'Signature' field type (i.e., 'wet signature') on the survey. One might also assign PIN numbers to prospective participants to aid in the signature process. <u>Please note that the signature process will NOT be implemented by REDCap automatically,</u> so it is your responsibility as a survey administrator to construct your survey using one of the methods above in order for the signature to get captured appropriately."
survey_1185 = "How the e-Consent Framework works"
survey_1186 = "What is e-Consent?"
survey_1187 = "Why is this called a 'framework'?"
survey_1188 = "The 'e-Consent Framework' is referred to as a 'framework' because enabling this option alone does not provide an e-Consent process but merely provides the general framework or mechanism to allow you to provide e-Consent to patients/subjects. As a survey administrator, you must still create your e-Consent survey and all the questions in it, including name, date of birth, and how you wish to capture the signature. This framework allows you to implement your e-Consent process by providing standardized tools (certification screen + automatic storage of consent form as a 'hard-copy' PDF) while still providing the ability to customize your survey how you wish."
survey_1191 = "Note: If you are using a single field to capture whole name, you may select it for either first/last name above while leaving the other name field unselected."
survey_1192 = "e-Consent Framework: PDF External Storage Settings (for all projects)"
survey_1196 = "Server hostname:"
survey_1197 = "For WebDAV, the hostname must begin with http:// or https:// (e.g., https://ebldav.mc.vanderbilt.edu), but not for SFTP (e.g., sftp.vumc.org). SFTP always assumes port 22, while WebDAV is port 80 or 443."
survey_1198 = "Server username:"
survey_1199 = "Server password:"
survey_1200 = "Server directory to store files:"
survey_1201 = "Path to Private Key file (SFTP only):"
survey_1202 = "Display 'e-Consent Framework' option for ALL surveys?"
survey_1204 = "Show e-Consent Framework option (recommended)"
survey_1205 = "Hide e-Consent Framework option"
survey_1210 = "WARNING: It appears that this survey has the option selected to 'Hide the Previous Page button', which may conflict with the e-Consent Framework because it prevents a participant from returning to a previous page of the survey to fix any incorrect information during the e-Consent process. It is HIGHLY recommended that you uncheck the 'Hide the Previous Page button' option on this page if you wish to use the e-Consent Framework functionality."
survey_1211 = "Most importantly, it is highly recommended that you have a discussion with your local Institutional Review Board (IRB) if you wish to do e-Consent in REDCap."
survey_1212 = "Delete all selected"
survey_1213 = "Delete all selected invitations?"
survey_1214 = "Are you sure you wish to delete all the scheduled survey invitations that have been selected on this page?"
survey_1215 = "No checkboxes were selected. You must first select the checkbox for each invitation on the far right of the table."
survey_1216 = "Deleted scheduled survey invitations"
survey_1217 = "survey invitations were successfully deleted!"
survey_1218 = "Capture the IP address of survey participants that certify the e-Consent process, and store their IP in the File Repository table."
survey_1219 = "Do NOT capture IP address"
survey_1220 = "Capture IP address"
survey_1221 = "IP Address"
survey_1223 = "Note: Because the e-Consent Framework option is enabled on this page, the PDF included here will not be the full-length PDF but will be the 'compact' PDF, which omits unanswered questions and unselected choices."
survey_1224 = "Please take this survey."
survey_1225 = "You may modify or remove any text you wish in the Compose Message text box above. Make sure you include either [survey-link] or [survey-url] in the text or else the participant will not have a way to take the survey."
survey_1226 = "The <b>survey link will NOT be automatically included</b> for invitation types 'Email invitation' and 'SMS invitation (contains survey link)', thus you must make sure to include either [survey-link] or [survey-url] in the text or else the participant will not have a way to take the survey. The other SMS invitation types will automatically provide standard instructional text."
survey_1227 = "WARNING: The public survey link is not available yet because the first instrument of the project has not been designated for the first event. Please see the 'Designate Instruments for My Events' page to designate the first instrument for the first event, after which you may return here to obtain the public survey link."
survey_1228 = "Hard-coded survey links were found in your survey text. It suggested that you NOT place hard-coded survey links into the text but <b>instead use [survey-link] as a placeholder for the survey link</b>. It may be the case that these links originated from previously sent invitations. It is HIGHLY recommended that you remove the hard-coded survey links listed below."
survey_1229 = "The following hard-coded survey links were found:"
survey_1230 = "SUGGESTION: Remove hard-coded survey links from survey text"
survey_1231 = "View all contributors"
survey_1233 = "The following users have contributed to this survey response:"
survey_1234 = "The following users have contributed to this survey response <u>since it was completed</u>:"
survey_1235 = "Select a previously sent email to load it in the Compose box"
survey_1236 = "For this delivery type, the appropriate survey access instructions will automatically be appended to your survey invitation text, so it is not necessary to include the [survey-link] or [survey-url] in the message."
survey_1237 = "[email no longer belongs to a project user]"
survey_1238 = "Sent manually via Participant List (or via Survey Options on data entry form) by"
survey_1239 = "Automated Survey Invitations"
survey_1240 = "Leave ASIs enabled (unless disabled)"
survey_1241 = "You may now close this tab/window"
survey_1242 = "To proceed to the survey, please check off the box and click the button below."
survey_1243 = "Begin survey"
survey_1244 = "Invalid reCAPTCHA response! Please try again."
survey_1245 = "Google reCAPTCHA option for protecting public surveys"
survey_1246 = "Site key:"
survey_1247 = "Secret key:"
survey_1248 = "To enable the option for users to use Google reCAPTCHA on their public surveys, you must first establish a Google reCAPTCHA API site key and secret for your REDCap server. Choose the 'reCAPTCHA v2' and 'Checkbox' options when registering your site, and then enter both keys in the two text boxes here. Once both are set, users on the Public Survey page will be provided with the option to enable reCAPTCHA in that project. Note: Google reCAPTCHA is only employed on public surveys."
survey_1249 = "Create Google reCAPTCHA API key"
survey_1250 = "NOTICE TO ADMINISTRATOR: The Google reCAPTCHA feature for protecting public surveys is currently DISABLED at the system-level for all projects, but if you wish, you may enable the option on the "
survey_1251 = "page in the Control Center. This option will allow users to add protection to their public survey using Google's reCAPTCHA functionality, which can prevent bots from entering trash data into a public survey."
survey_1252 = "Protect the public survey using the Google reCAPTCHA feature"
survey_1253 = "The Google reCAPTCHA feature can be enabled to help protect your public surveys from abuse from 'bots', which are automated software programs that might enter trash data into your survey. A 'captcha' is a turing test to tell humans and bots apart. It is easy for humans to solve, but hard for bots and other malicious software to figure out. By enabling Google reCAPTCHA on your public survey, you can block automated software while helping welcome your survey participants to begin your survey with ease. Below is an example screenshot of what the reCAPTCHA might look like on your survey. Note: A survey participant will never have to pass the reCAPTCHA test more than once per day on a given device/computer."
survey_1254 = "Allow e-Consent responses to be edited by users?"
survey_1255 = "NOTE: The response limit only gets applied when a participant is loading the survey page. This means that if two or more participants load the survey at nearly the same time and then submit the survey, it is possible that the response limit could be exceeded slightly. This is because it will not block a participant's responses from getting saved if the limit is exceeded after a participant has loaded the survey, but it prevents the survey from loading after the limit has been exceeded."
survey_1256 = "Section headers, which begin new sections on the instrument, will serve as the page break in a multi-page survey, in which each page will begin with a section header."
survey_1257 = "For custom numbering, each question's number will be blank by default until manually added via the Online Designer or Data Dictionary."
survey_1258 = "How to use \"stop logic\" to disable an automated invite"
survey_1259 = "If you have Automated Survey Invitations (ASIs) that will not be sent immediately but instead are scheduled to be sent later, it might be a good idea to consider using 'stop logic' (otherwise known as a 'kill switch') in your conditional logic in order to manually stop these scheduled invitations when needed. This might be used if somehow an invitation was scheduled by accident and you need to quickly delete it. NOTE: You must have checked the 'ensure logic is still true' checkbox in order for the 'stop logic' to work. By having the checkbox checked, it means that every time a given record is saved or has data modified, REDCap will see if there is an invitation scheduled for this record/survey, and if so, it will then double check to see if this condition/logic is still true. If condition is no longer true, it will delete the invitation so that it never gets sent. And if the record is modified again later, in which the condition then becomes true again, then the invitation will get re-scheduled. Without the 'ensure logic is still true' checkbox being checkbox, REDCap will leave the scheduled invitation as-is and never delete it."
survey_1260 = "The 'stop logic' could be a complex set of conditional logic, or it could be as simple as a single field in the project (i.e., the kill switch). For example, if you are wanting a survey invitation to be scheduled when a participant is at least 18 years old, your logic might be '[age] >= 18'. And if you want to add the 'stop logic' to be able to manually delete a scheduled invitation, you could have '[age] >= 18 and [remove_alert] <> 1', in which the field 'remove alert' is a Yes/No field. So in this instance, if you wanted to have the scheduled invitation deleted, you could simply go to the data entry form where the 'remove alert' field is located, and set it to 'Yes'. This can be done a variety of different ways. This is merely a simple example to introduce this concept. <b>Remember, the key to using 'stop logic' is that the 'ensure logic is still true' checkbox MUST be checked.</b>"
survey_1261 = "Signature field"
survey_1262 = "Force signature field(s) to be erased if participant clicks Previous Page button while on the certification page?"
survey_1263 = "Select a field below that serves as a signature field in this survey. It could be a <u>free-form text field, a signature field, or a number field</u> (e.g., to collect a PIN), and it must be a <u>Required field</u>. If any fields are selected below, then if the participant gets to the last page of the survey where it asks them to certify their responses, if they then choose to click the Previous Page button, it will erase the value of these signature fields, thus forcing them to 'sign' the field(s) again before completing the survey. If you do not want this behavior, do not select any fields below. You may use up to five signature fields."
survey_1264 = "Erase your signature(s) in this survey?"
survey_1265 = "You have provided your signature on an earlier page in this survey. This may include typing your name, a PIN, and/or signing your signature. You are allowed to return to a previous page in the survey, but if you do so, please be advised that your signature(s) will be automatically removed, after which you will need to provide it again before you can complete the survey. You will also be able to modify any of your existing responses to the questions in this survey. If this is okay, you may proceed to an earlier page in the survey by clicking the button below."
survey_1266 = "Erase my signature(s) and go to earlier page"
survey_1267 = "Select another signature field"
survey_1268 = "There no not exist any valid fields in this survey that are Required and also match the criteria to be used here a signature field."
survey_1269 = "IMPORTANT NOTE: A Twilio feature named the 'Request Inspector' causes all activity to be logged in detail and stored on Twilio's servers. For the highest level of privacy, it is HIGHLY RECOMMENDED that you manually DISABLE THE REQUEST INSPECTOR in your Twilio account if you will be collecting identifying information (e.g., PHI) via Voice Calls and SMS messages in REDCap. You will find this setting on the Settings page under Programmable Voice in your Twilio console. Once there, disable the Request Inspector and click Save."
survey_1270 = "Display name (optional)"
survey_1271 = "Previously used:"
survey_1272 = "The ending of custom URLs may only contain letters, numbers, dots/periods, dashes, and underscores."
survey_1273 = "NOTICE: You may not use the Survey Distribution Tools page until one or more data collection instruments have been enabled as a survey, which can be done on the Online Designer page. However, you do not have access to the Online Designer, so another user in this project will need to do that for you."
survey_1275 = "Choose the language of your survey question text and/or alert message, and select the regional dialect in which you want it to be spoken (used in voice calls only)."
survey_1276 = "REDCap has the capability to make voice calls and send SMS text messages for surveys and for Alerts & Notifications by using a third-party web service named Twilio (www.twilio.com). In this way, you could invite a participant to take a survey by sending them an SMS message or by calling them on their phone, in which the data would be collected in REDCap directly from their phone without having to use a webpage. There are many different options available for how you can invite participants and how they can take your surveys, either as a voice call survey or as an SMS conversation. You may also send Alert & Notifications to recipients via Voice Call or SMS instead of via email."
survey_1277 = "Surveys and survey invitations only (default)"
survey_1278 = "Alerts & Notifications only"
survey_1279 = "ALL: Surveys and survey invitations + Alerts & Notifications"
survey_1281 = "You may enable the Twilio SMS and voice call services in this project for sending Alerts & Notifications, for survey invitations via SMS text messages, and also for having respondents take surveys via a voice call or SMS. Before you begin the setup steps below, you must <b>1) set up your own Twilio account</b> at"
survey_1282 = "ALERTS & NOTIFICATIONS: In addition to sending alerts via email, you may also send them as SMS text messages or as one-way voice calls. When creating a new alert on the Alerts & Notifications page, there will be a choice between Email, SMS, and Voice Call. Choosing SMS or Voice Call will hide all email-specific settings (e.g., email subject, attachments), and it will reveal a phone number text box for entering the phone number(s) of all recipients of the alert. These alerts will still be triggered normally, but instead of sending the notification via email, it will send it as an SMS message or one-way voice call, which uses text-to-speech technology to read the notification to the recipient audibly on their phone."
survey_1283 = "Survey-specific settings:"
survey_1284 = "Twilio SMS and Voice Call services for surveys and alerts"
survey_1285 = "To begin utilizing the Twilio SMS and Voice Call services in this project, click the 'Configure' button below. Once you have the Twilio service enabled, the Configuration popup will allow you to enable Twilio for 1) Alerts & Notifications and/or 2) surveys and survey invitations. If using Twilio for surveys, you will need to first designate an instrument as a survey in this REDCap project, after which you may click the 'analyze surveys' button to run an analysis on all your surveys to determine if they can be used as an SMS survey or as a Voice Call survey."
survey_1286 = "[Auto-Reply: This SMS phone number is not monitored.]"
survey_1288 = "Email sent!"
survey_1289 = "Send the invitation"
survey_1290 = "Sent survey confirmation email"
survey_1291 = "By default, when respondents click the 'Save & Return Later' button on a survey, they will need the return code provided to them in order to return to the survey later to begin where they left off. But this behavior can be modified by checking the checkbox, which will allow anyone with only the survey link to return to the survey and view all previously entered responses WITHOUT needing a return code."
survey_1292 = "NOTE: If you are collecting identifying information (e.g., PII, PHI), for privacy reasons it is HIGHLY recommended that you leave the option unchecked so as to enforce a return code."
survey_1293 = "after time lapse of"
survey_1294 = "(NOTICE: Fields existing on repeating instruments/events will not work as login fields.)"
survey_1296 = "Keep the Survey Queue hidden from participants?"
survey_1297 = "This setting will keep the Survey Queue table hidden from participants, and will force Auto Start to be enabled for all queue-activated surveys (even if unchecked below). This is useful if you wish to use the Survey Queue to automatically guide survey participants to the next survey without displaying the queue of surveys."
survey_1298 = "Please note that the survey-specific email invitation field has been enabled for this survey."
survey_1299 = "NOTICE: The Survey Queue has been enabled in this project. Please note that the Survey Queue can sometimes conflict with the Survey Auto-continue feature."
survey_1300 = "NOTICE: One or more surveys in this project is using the Survey Auto-continue feature (enabled on the Survey Settings page). Please note that the Survey Queue can sometimes conflict with the Survey Auto-continue feature."
survey_1301 = "ERROR: We're sorry, but the data you just submitted on this page cannot be saved. This page has already been saved as an e-Consent survey, in which users are not allowed to modify e-Consent survey responses after they have been completed by the respondent. The e-Consent response was saved at the following time: "
survey_1302 = "Your project is currently in Draft Mode. You are unable to enable an instrument as a survey while in Draft Mode if that instrument did not exist in the project prior to entering Draft Mode. Please review the changes you have made while in draft mode (by clicking the 'View detailed summary of all drafted changes link') and either click the 'Submit Changes for Review' button or click the link 'Remove all drafted changes'. After your changes have been approved (or you remove all drafted changes), the 'enable' button will be available to you and you may enable your instrument as a survey."
survey_1306 = "Current event"
survey_1307 = "Note: If the field selected above exists on a repeating event or repeating instrument, which happens to be the same event or instrument (respectively) as this survey, it will always save the PDF to the current repeating instance of the survey being submitted."
survey_1309 = "(The amount of time that each respondent has to complete the survey based on when they were initially sent the survey invitation. Note: This feature excludes public survey links and is not applicable for survey links sent via Alerts & Notifications.)"
survey_1310 = "Do not display the repeating survey button"
survey_1311 = "End Survey"
survey_1312 = "Return and Edit Response"
survey_1313 = "To save your responses and end the survey, click the 'End Survey' button below. If you have selected the wrong option by accident and/or wish to return to the survey, click the 'Return and Edit Response' button."
survey_1314 = "Control each participant's invitation preference using a multiple choice field"
survey_1315 = "If survey participants require using different methods (e.g., email, SMS w/ link, voice call survey) for receiving survey invitations and/or taking surveys, you can select a multiple choice field (radio and drop-down fields only) whose choices represent each survey invitation delivery method. After mapping the invitation preferences to a field, whenever the value of the field is added or modified, the participant's invitation preference will automatically be changed accordingly. <b>IMPORTANT:</b> The multiple choice codings for the selected field must be defined exactly as delineated on the right, although their corresponding choice labels can be modified to be whatever text you wish."
survey_1316 = "select a phone field"
survey_1317 = "map the invitation preference to a field"
survey_1318 = "Designate a phone number field for survey invitations sent via SMS or voice call (optional)"
survey_1319 = "Listed above are all Text fields having either Integer validation or Phone Number validation."
survey_1320 = "Required choice codes with example choice labels:"
survey_1322 = "NOTE: Not all of the options above need to be set for the field's choices but only the ones needed. Also be aware that if the value of the field selected above is set to blank/null, then the invitation preference for the participant will revert to the project's default invitation preference. Additionally, if a participant's invitation preference is modified via the Participant List, that change will also change the value of the mapping field selected above."
survey_1324 = "Options related to Survey Stop Actions:"
survey_1325 = "Alternate Survey Completion Text (optional)"
survey_1326 = "This completion text is ONLY displayed when a Stop Action triggers the end of the survey. If left blank, the standard Survey Completion Text will be used."
survey_1327 = "Prevent survey responses from being saved if the survey ends via Stop Action?"
survey_1328 = "Save all survey responses regardless of Stop Action being triggered (default)"
survey_1329 = "Do NOT save the survey response when a Stop Action is triggered"
survey_1330 = "If a Stop Action triggers the end of the survey, you may choose to keep the submitted responses or to prevent them from being saved as data in the project."
survey_1331 = "Add offline message"
survey_1332 = "Deleted Response"
survey_1333 = "WARNING: If any data has been saved on the survey instrument prior to the Stop Action being triggered, that data will be deleted. For example, if the survey is a multi-page survey in which data has been entered on previous pages prior to triggering the Stop Action, all data collected thus far in that survey will be deleted as if the survey was never taken. Additionally, if the record does not contain data in any other instruments, the entire record itself will be deleted during this process."
survey_1334 = "NOTE: If the entire record is deleted, all logged data values for this record will be removed from the log as per this project's data privacy setting."
survey_1335 = "TIP: When contacting participants by SMS messages or phone calls, you might consider adding a field that says, '<b>I agree to be contacted by text or phone</b>' and have the participant answer that question. Then you have evidence in your project that the participant is consenting to being contacted by text or phone."
survey_1336 = "You may use Piping in the custom survey queue text above."
survey_1337 = "This file is no longer available for download."
survey_1339 = "Your email address will not be associated with or stored with your survey responses."
survey_1340 = "Enable the external storage device and choose storage method (SFTP, WebDAV, Azure, S3):"
survey_1341 = "Download PDF"
survey_1342 = "<b>NOTICE:<b> The Survey Queue cannot be set up yet because there are no surveys for which it can be utilized. Only follow-up surveys (i.e., surveys other than the first data collection instrument) are available to be utilized in the Survey Queue. If you create more data collection instruments and then enable them as surveys, you will then be able to utilize them in the Survey Queue."
survey_1343 = "<b>ERROR:</b> The login was not successful because the value entered was not correct. Try again."
survey_1344 = "<b>ERROR:</b> The login was not successful because the values entered were not correct. Try again."
survey_1345 = "You must successfully enter at least {0} out of the {1} fields below."
survey_1346 = "You have chosen to stop the survey for now and return at a later time to complete it. To return to this survey, you will need both the <i>survey link</i> and your <i>return code</i>. See the instructions below."
survey_1347 = "Page {0} of {1}"
survey_1348 = "All bar charts will have bars displayed in {0:blue}, and any of the choices that you selected in your survey response will have *asterisks* around that choice's label on the left of the bar chart. You will also see your response appended to the right end of the bar in {1:orange}."
survey_1349 = "For scatter plots, the values of other survey participants will be displayed in {0:blue}, the median value will be displayed in {1:red}, and the value you entered will be displayed in {2:orange}."
survey_1350 = "View all contributors to this response."
survey_1351 = "Your email was successfully sent to {0}."
survey_1352 = "{0} surveys completed!"
survey_1353 = "For security purposes, this survey has been temporarily disabled because it has exceeded the maximum amount of failed login attempts that are allowed within a set period of time (<b>{0} minutes</b>)."
survey_1354 = "You may return to this survey in the future to modify your responses by navigating to the survey URL and entering your Survey Login credentials."
survey_1355 = "You may return to this survey in the future to modify your responses by navigating to the survey URL and entering the code below."
survey_1356 = "{0} instances of this survey have been recorded"
survey_1357 = "{0} instance of this survey has been recorded"
survey_1358 = "The email was successfully sent to:"
survey_1359 = "<b>ERROR:</b> The code entered was not valid! Please try again."
survey_1360 = "Thank you for partially completing the survey '{0}'."
survey_1361 = "Scheduled to send at {0}"
survey_1362 = "Was sent at {0}"
survey_1363 = "Invitation failed to send (originally scheduled for {0})"
survey_1364 = "View PDF"
survey_1365 = "Page {0}"
survey_1366 = "This browser does not support PDFs. Please download the PDF <b>in a new tab</b> to view it:"
survey_1367 = "(Optional) Conditional logic for Survey Auto-Continue:"
survey_1368 = "Auto-continue to the next survey?"
survey_1369 = "Auto-continue to the next survey ONLY if the conditional logic below is <i>TRUE</i> or if the textbox has been left blank."
survey_1370 = "Store the translated version of the PDF"
survey_1371 = "(if using Multi-language Management)"
survey_1372 = "Check Not Responded and Partial Response"
survey_1373 = "Show API Key"
survey_1375 = "Enable SendGrid web service for email services?"
survey_1376 = "This will allow SendGrid services to be utilized in REDCap projects, such as for sending alerts and notifications using SendGrid Templates."
survey_1377 = "Note: In order to use the SendGrid service, the REDCap web server must be able to make outbound HTTP/HTTPS requests to the following URL:"
survey_1378 = "For more information on SendGrid, see"
survey_1379 = "Who can enable SendGrid services in a given project?"
survey_1380 = "If 'Only Administrators' is selected, then normal users will not even see the setting on the project's Project Setup page (only Administrators will be able to see it and enable it). If 'All users' is selected, then any user with Project Design/Setup privileges in that project can see the setting and can also enable it on their own to utilize SendGrid services in their project."
survey_1381 = "Display information about SendGrid services to <u>all users</u> on Project Setup page in a project?"
survey_1382 = "No, hide all information about SendGrid services"
survey_1383 = "Yes, display information about SendGrid services"
survey_1384 = "If 'No' is selected, then SendGrid Template email services will not be advertised to users on the Project Setup page, and all information about SendGrid will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make SendGrid services known to only a limited number of users without advertising it to all users."
survey_1385 = "SETUP & CONFIGURATION: This integration requires that you have an account setup on <a href='https://sendgrid.com' target='_blank'><u>sendgrid.com</u></a>. After creating a SendGrid account, you'll need to configure senders for the account, create the dynamic templates you wish to use for REDCap alerts, and generate an API Key with appropriate permissions for REDCap to use. When configuring senders on your SendGrid account, you may specify individual senders, authenticate an entire domain so that any email address associated with that domain may be a sender, or both. Please refer to SendGrid's documentation on how to set up <a href='https://docs.sendgrid.com/ui/account-and-settings/how-to-set-up-domain-authentication' target='_blank'><u>Domain Authentication</u></a> and how to add individual <a href='https://docs.sendgrid.com/ui/sending-email/senders' target='_blank'><u>Verified Senders</u></a>. To create a dynamic template in your SendGrid account, login to your SendGrid account and use the sidebar to navigate to <b>Email API→Dynamic Templates</b>. Here you can create a dynamic template, give it a name, and associate an email design with it. Please reference SendGrid's documentation on <a href='https://sendgrid.com/solutions/email-api/dynamic-email-templates/' target='_blank'>Dynamic Templates</a> and <a href='https://docs.sendgrid.com/for-developers/sending-email/using-handlebars' target='_blank'><u>Handlebars</u></a> to learn more about creating templates in your SendGrid account. Lastly, to create an API Key for REDCap, login to your SendGrid account and use the sidebar to navigate to <b>Settings→API Keys</b>. Here you can create a new API Key and specify its permissions. It is recommended that you create a <b>Restricted Access</b> API Key and only give the API Key the permissions REDCap needs to function. REDCap will need Full Access to <b>Mail Send</b>, Read Access to <b>Sender Authentication</b>, Read Access to <b>Template Engine</b>, and Read Access to <b>Unsubscribe Groups</b> in the <b>Suppression</b> section. Once you have your API Key, you may use it to configure SendGrid Template email services for alerts & notifications through the REDCap Project Setup page."
survey_1386 = "COST: As REDCap makes API calls to SendGrid's Email API using your account's API Key, your SendGrid account will keep track of REDCap's usage and your SendGrid account will be charged accordingly. This is not done by REDCap but is done internally by SendGrid as you use its services. In this way, no monetary transactions are made by REDCap, and thus it is your responsibility to maintain the funds in your SendGrid account in order to ensure that the service continues to work for your REDCap project. If your SendGrid account runs out of funds, the SendGrid services in REDCap will cease to function. You may reference <a href='https://sendgrid.com/pricing/' target='_blank'><u>SendGrid's pricing page</u></a> to get their latest pricing."
survey_1387 = "SendGrid Template email services for Alerts & Notifications"
survey_1388 = "REDCap has the capability to use <a href='https://sendgrid.com/solutions/email-api/dynamic-email-templates' target='_blank'><u>SendGrid Dynamic Templates</u></a> for sending email-based Alerts & Notifications. SendGrid Templates give you significantly more control over the style and design of your emails when compared to the standard email alert type. Enabling this feature will give you another alert type to choose from on the Alerts & Notifications page called <b>SendGrid Template</b>."
survey_1389 = "SendGrid Template Email Services"
survey_1390 = "ALERTS & NOTIFICATIONS: The SendGrid alert type will allow you to specify a sender email address that's in your SendGrid account's list of <a href='https://docs.sendgrid.com/ui/sending-email/senders' target='_blank'><u>Verified Senders</u></a> or an email address that matches an <a href='https://docs.sendgrid.com/ui/account-and-settings/how-to-set-up-domain-authentication' target='_blank'><u>Authenticated Domain</u></a> associated with your SendGrid account. You'll also have an interface to choose which of your SendGrid account's dynamic templates you'd like to use for the alert as well as an interface to specify key/value pairs that will be used to populate your template with REDCap data. Lastly, choosing recipients for SendGrid alerts works the same way as choosing recipients for email alerts."
survey_1391 = "SendGrid account credentials (obtained from SendGrid website)"
survey_1392 = "SendGrid API Key"
survey_1393 = "How many times to send it"
survey_1394 = "(repeating surveys only)"
survey_1396 = "Leave blank to continue triggering and sending forever."
survey_1473 = "Fixed width (default)"
survey_1474 = "width of page"
survey_1475 = "Width of survey on page"
survey_1476 = "Set a custom width as a percentage of the webpage that the survey will take up."
survey_1477 = "Display the font resize options at the top of the survey page"
survey_1478 = "Single page"
survey_1479 = "Multiple pages (display one section per page)"
survey_1480 = "Show or hide the Submit buttons"
survey_1481 = "Show or hide the Submit buttons displayed at the bottom of every survey page (including the 'Next Page' and 'Previous Page' buttons)."
survey_1482 = "Always display the Submit buttons"
survey_1483 = "Always hide the Submit buttons"
survey_1484 = "Customize the text of the Submit buttons"
survey_1485 = "Provide alternative text for the 'Submit', 'Next Page', and 'Previous Page' buttons displayed at the bottom of every survey page."
survey_1486 = "Any alternative text provided for the submit buttons will override their default text below:"
survey_1487 = "Pagination"
survey_1489 = "Note: This feature cannot be triggered by submitting a data entry form EXCEPT only when a user clicks the 'Save & Mark Survey as Complete' button on the data entry form. Note: If the current survey settings allows participants to return to completed responses, then any existing PDFs that have already been stored in this File Upload field will be overwritten by any new ones if the survey is completed again."
survey_1490 = "Hide survey title on survey page when display logo"
survey_1491 = "Hiding the Submit buttons can be useful if you are not using the survey for data collection but for instructional purposes or other similar use cases."
survey_1492 = "Note: The percentage page width settings are fully dependent on the participant's screen size."
survey_1493 = "Based on the current survey settings, survey responses in this project are considered anonymous. A participant's record is not able to be identified."
survey_1494 = "Based on the current survey settings, some survey responses on this page might not be considered anonymous."
survey_1495 = "Anonymous*"
survey_1496 = "Not Anonymous"
survey_1497 = "Survey Response Status:"
survey_1498 = "*Please note that survey responses in REDCap can never truly be considered 100% anonymous. In some cases it may be possible to identify a participant's record through the process of elimination and deduction and/or by monitoring a record's data values and survey submission times very closely. But when collecting data in a typical manner, it may be said that the survey responses in this project can be casually considered as \"anonymous\" and thus not identifiable."
survey_1499 = "Learn more about anonymous survey responses"
survey_1500 = "Survey responses are considered anonymous <i>unless</i> the participant has a Participant Identifier defined OR if the participant's email address was added via the Designated Email field. Any response on this page that is considered anonymous will have the <i class='far fa-eye-slash'></i> icon displayed in place of its record name in order to prevent users from identifying which record belongs to the participant."
survey_1501 = "This setting will not be applied when viewing the survey on mobile devices."
survey_1502 = "Recurring automated invitation"
survey_1503 = "Delete invitation"
survey_1504 = "Delete recurring invitation"
survey_1505 = "Delete this recurring invitation?"
survey_1506 = "Are you sure you wish to delete ALL recurring invitations for this item? Doing so does not just delete a single invitation, but it deletes ALL future recurring invitations for the ASI/record listed below."
survey_1507 = "The recurring series of survey invitations has been successfully deleted. The page will now reload to reflect the changes."
survey_1508 = "Displayed below is the survey invitation message that will be sent to the survey participant. Included is the scheduled time that the invitation will be sent, the sender, the email address (or phone number) of the survey participant, and the invitation's subject and message."
survey_1509 = "(Optional) Repeat the survey:"
survey_1510 = "Ask participants to take the survey again upon completion"
survey_1511 = "<b>[This option is available since this instrument has been enabled as a repeating instrument.]</b> Once the respondent completes the survey, they will be presented with a button saying 'Take this survey again' (or your custom text) that will start the survey over again from the beginning to capture it as a new repeating instance of the survey for that record. If also using the Survey Queue, a button will be added to the Survey Queue for this survey to allow the respondent to repeat the survey directly from the Survey Queue. If the option is set to 'Do not display the repeating survey button', it will be hidden on the survey page but will still be displayed on the Survey Queue."
survey_1512 = "Survey Notice:"
survey_1513 = "Tip: A monthly recurrence can be approximated as 30.44 days."
survey_1514 = "Thank you for partially completing the survey."
survey_1515 = "ERROR: Sorry, but the survey response could not be saved because the response has been intentionally locked by someone, thus preventing you or others from submitting any responses here."
survey_1516 = "This will allow Mosio SMS services to be utilized in REDCap projects, such as for sending survey invitations and taking surveys via SMS."
survey_1517 = "Note: In order to use the Mosio SMS service, the REDCap web server must be able to make outbound HTTP/HTTPS requests to the following URL:"
survey_1518 = "No, hide all information about Mosio SMS services"
survey_1519 = "Yes, display information about Mosio SMS services"
survey_1520 = "Who can enable Mosio SMS services in a given project?"
survey_1521 = "If 'Only Administrators' is selected, then normal users will not even see the setting on the project's Project Setup page (only Administrators will be able to see it and enable it). If 'All users' is selected, then any user with Project Design/Setup privileges in that project can see the setting and can also enable it on their own to utilize Mosio SMS services in their project."
survey_1522 = "Display information about Mosio SMS services to <u>all users</u> on Project Setup page in a project?"
survey_1523 = "If 'No' is selected, then Mosio SMS services will not be advertised to users on the Project Setup page, and all information about Mosio will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make Mosio SMS services known to only a limited number of users without advertising it to all users."
survey_1524 = "Additionally, your REDCap server must be publicly available to the web (in the DMZ) so Mosio's web servers can make requests to it. Otherwise, Mosio cannot completely function."
survey_1525 = "For more information on Mosio, see"
survey_1526 = "Mosio SMS services for surveys and alerts"
survey_1527 = "Mosio API credentials (obtained from your account on the Mosio website)"
survey_1528 = "Mosio API Key"
survey_1529 = "Configure settings"
survey_1530 = "To begin utilizing the Mosio SMS services in this project, click the 'Configure' button below. Once you have the Mosio SMS service enabled, the Configuration popup will allow you to enable Mosio for 1) Alerts & Notifications and/or 2) surveys and survey invitations. If using Mosio for surveys, you will need to first designate an instrument as a survey in this REDCap project, after which you may click the 'analyze surveys' button to run an analysis on all your surveys to determine if they can be used as an SMS survey."
survey_1531 = "You may now set up your settings by following the directions in this step."
survey_1532 = "Analyze surveys for SMS"
survey_1533 = "The table below displays any issues that might be experienced if using a survey as an SMS conversation. To see the details of any issue, click the 'view' link next to it, which will display the field with the issue, as well as a description of why this field would be problematic. NOTE: If a survey below is administered as an SMS conversation, then <b>any field having an issue will be skipped</b> in the survey unless the issue described below is remedied by changing or removing the field."
survey_1534 = "Only REDCap administrators are allowed to enable the option to initiate a survey as an SMS conversation. Much like email, SMS is not considered a secure form of communication, so you may not want to administer surveys as SMS conversations if the participant will be submitting identifying information (PHI or PII) unless you have been granted special permission from the participant to do so. Given such sensitive privacy issues, only your local REDCap administrator can enable the optional setting to use SMS surveys. Please notify your administrator about this if you wish to have this option enabled."
survey_1535 = "Configuration Settings"
survey_1536 = "SMS Settings"
survey_1537 = "Listed below are all the configuration settings telephony services for this project. These settings control which parts of the telephony services are made available for use throughout the project, and they control how certain parts of the service functions. To set or change any settings, modify them below, and click the Save button."
survey_1538 = "Select the project features for which the telephony services will be enabled (e.g., surveys and/or alerts)"
survey_1539 = "REDCap has the capability to send SMS text messages for surveys and for Alerts & Notifications by using a third-party web service named Mosio (www.mosio.com). In this way, you could invite a participant to take a survey by sending them an SMS message, in which the data would be collected in REDCap directly from their phone without having to use a webpage. There are two ways REDCap currently works with Mosio:<br> 1. SMS Surveys – Sending questions and getting replies via text message.<br> 2. Alerts - Sending REDCap Alerts & Notifications via text message.<br><br> Mosio specializes in research communications automation, helping researchers improve engagement, adherence, and data collection in studies. The service is both HIPAA and 21 CFR Part 11 compliant and willing to sign BAAs."
survey_1540 = "<b>SMS SURVEYS:</b><br>With SMS Surveys, questions are presented individually as part of an SMS conversation thread. Respondents can answer using any type of alphanumeric text.<br><br> Most of REDCap's survey features remain unchanged with SMS Surveys. These include enforcing required fields, validating fields, using branching logic, utilizing the Survey Queue for multiple surveys (only when Auto-Start is enabled), receiving email notifications and confirmations, accessing the Participant List, sending Automated Survey Invitations, implementing Stop Actions and using computer adaptive tests (CATs) downloaded from the REDCap Shared Library. However, the Survey Login feature is not compatible with SMS surveys.<br><br> NOTE: "
survey_1541 = "<b>ALERTS & NOTIFICATIONS:</b><br>With Mosio, you can send Alerts as SMS text messages, located on the Alerts & Notifications page. When creating a new alert, you will have the option to select either Email (via REDCap) or SMS (via Mosio).<br><br> Selecting SMS will remove all settings specific to email (subject line, attachments, etc) and reveal a text box where you can enter the phone number(s) of the recipients. The alerts will still function as usual, but the notification will be sent as an SMS message instead of an email.<br><br> The Mosio team has been helping REDCap users leverage two-way text messaging for many years. Their REDCap Direct offering enables users to use their system in a 'self-service' approach. More features and functionality are being developed."
survey_1542 = "<b>NEXT STEPS:</b><br>For more information and to get a Mosio account, visit <a href='https://www.mosio.com/redcap' target='_blank'><u>https://www.mosio.com/redcap</u></a>.<br> For setup/configuration info, click the 'Enable' button on your REDCap project's Project Setup page.<br> Contact your REDCap Administrator to enable Mosio services in your account."
survey_1545 = "To learn more about using Mosio SMS services in REDCap, contact your local REDCap administrator."
survey_1546 = "NOTE: Only a REDCap administrator can enable the Mosio services in your project, so please contact them to talk to them about how to do this."
survey_1547 = "You may enable the Mosio services yourself by clicking the Enable button, after which you will need to follow the instructions provided to fully enable this functionality in your project."
survey_1548 = "SMS options for the Public Survey"
survey_1549 = "You may invite participants to complete the public survey via SMS. If you wish to invite them directly *right now*, click the button below to open a popup for entering phone numbers to send an SMS text message to the participants."
survey_1550 = "Invite participants via SMS"
survey_1551 = "In the text box below, enter the phone numbers of the respondents to which you wish to send survey invitations via SMS text message."
survey_1552 = "Mosio SMS services have been successfully enabled!"
survey_1553 = "Twilio SMS and Voice Call services have been successfully enabled!"
survey_1554 = "Enable Mosio web service for SMS services?"
survey_1555 = "For more information and to get a Mosio account, visit <a href='https://www.mosio.com/redcap' target='_blank'><u>https://www.mosio.com/redcap</u></a>."
survey_1556 = "REDCap uses a third-party web service named Mosio (<a href='https://www.mosio.com/redcap' target='_blank'><u>https://www.mosio.com/redcap</u></a>) to send/receive text messages for SMS Surveys or Alerts & Notifications. This allows you to invite participants to take a survey by sending them an SMS text message and collect data directly in REDCap from their phone without the need for a webpage. There are several options available for inviting participants and conducting surveys, such as through an SMS conversation. Additionally, you can send Alerts & Notifications via SMS in place of email."
survey_1557 = "Show setup and configuration details"
survey_1558 = "To get started, you’ll need to set up a Mosio account, here: <a href='https://www.mosio.com/redcap' target='_blank'><u>https://www.mosio.com/redcap</u></a>.<br><br> <b>There are two ways REDCap currently works with Mosio:</b><br> 1. SMS Surveys – Sending questions and getting replies via text message.<br> 2. Alerts - Sending REDCap Survey links via text message.<br><br> More two-way text messaging capabilities (Interactive “TextChat,” SMS Appointment Reminders, etc) are being developed. The information below will help you with Setup and Configuration. For more assistance, visit the REDCap Help & FAQ page or on Mosio’s website: <a href='https://www.mosio.com/redcap-guide' target='_blank'><u>https://www.mosio.com/redcap-guide</u></a>.<br><br> <b>SETUP & CONFIGURATION:</b><br> After you’ve obtained a Mosio Account, enter your Mosio API Key on your REDCap project’s Project Setup page.<br><br> Everything is quite like administering a survey in REDCap, except you choose how your surveys are delivered, either as an SMS Survey or with Alerts & Notifications (sending the REDCap survey link via text message). Any or both delivery methods can be used in a single project. If your surveys are collecting PHI, using Alerts & Notifications to deliver a REDCap survey link is recommended.<br><br> <b>ALERTS & NOTIFICATIONS:</b><br> When creating a new alert on the Alerts & Notifications page, there will be a choice between Email and SMS. Choosing SMS will hide all email-specific settings (e.g., email subject, attachments), and it will reveal a phone number text box for entering the phone number(s) of all recipients of the alert. These alerts will still be triggered normally, but instead of sending the notification via email, it will send it as an SMS text message.<br><br> <b>SMS SURVEYS:</b><br> When participants take an SMS survey, questions are asked one at a time as an SMS text message conversation/thread. Participants can respond with any kind of alpha-numeric text for an SMS survey.<br><br> <b>NOTE ABOUT SMS SURVEYS:</b> Only REDCap Administrators are allowed to enable the option to initiate a SMS Survey. Like email, SMS is not considered a secure form of communication, so you may not want to administer SMS Surveys if the participant will be submitting identifying information (PHI or PII) unless you have been granted special permission from the participant to do so. Given such sensitive privacy issues, only your local REDCap administrator can enable the optional setting to use SMS surveys. Please notify your administrator about this if you wish to have this option enabled.<br><br> <b>SURVEY COMPATIBILITY:</b><br> Most of REDCap's survey features remain unchanged with SMS Surveys. These include enforcing required fields, validating fields, using branching logic, utilizing the Survey Queue for multiple surveys (only when Auto-Start is enabled), receiving email notifications and confirmations, accessing the Participant List, sending Automated Survey Invitations, implementing Stop Actions and using computer adaptive tests (CATs) downloaded from the REDCap Shared Library. However, the Survey Login feature is not compatible with SMS surveys.<br><br> <b>PRIVACY & DATA SECURITY INFO:</b><br> It is important to understand that this feature utilizes the third-party service Mosio.com, which means that all SMS messages will be routed through Mosio's servers. However, REDCap goes to great length to ensure that SMS transcriptions do not stay in Mosio's logs but are removed shortly after being completed. This is done for security and privacy concerns (e.g., HIPAA), in which your survey participants' phone numbers and their survey responses do not get permanently logged on Mosio's servers but instead remain securely in REDCap. Mosio is HIPAA and 21 CFR Part 11 compliant. For more information about how Mosio handles privacy and data security, you can request their privacy statement."
survey_1559 = "View survey instructions"
survey_1560 = "Download QR Code in SVG format"
survey_1561 = "The Mosio API key entered is already in use by another REDCap project on this server. Mosio API keys can only be used by one project at a time. Please enter another Mosio API key and try again."
survey_1562 = "Brazilian Portuguese (Female)"
survey_1563 = "English - United Kingdom (Female)"
survey_1564 = "English - United Kingdom (Male)"
survey_1565 = "English - United States (Female)"
survey_1566 = "English - United States (Male)"
survey_1567 = "French - France (Male)"
survey_1568 = "French - France (Female)"
survey_1569 = "German (Female)"
survey_1570 = "German (Male)"
survey_1571 = "Italian (Female)"
survey_1572 = "Japanese (Female)"
survey_1573 = "Spanish - Castilian (Male)"
survey_1574 = "Spanish - Castilian (Female)"
survey_1575 = "Spanish - Latin American (Female)"
survey_1576 = "Spanish - North American (Female)"
survey_1577 = "French - Canadian (Female)"
survey_1578 = "Netherlander (Female)"
survey_1579 = "Korean (Female)"
survey_1580 = "ERROR: We're sorry, but the data you just submitted on this page cannot be saved. This page has already been saved as a partially or fully completed survey response,  and since you do not have user privileges to edit survey responses, you may not modify the data on this data entry form."
survey_1581 = "Edit Survey Queue"
survey_1582 = "When defining the conditions below, you may choose to have survey invitations be triggered by the completion of a survey or when pre-defined logic becomes true (i.e. when the data values of a given record fulfill a requirement). You may use either the logic or survey completion options as triggers, or you may use both together. (Please note that if you set it to be triggered when a specific survey is completed, this also includes if a non-survey user sets the Form Status field as 'Complete' on that survey's corresponding data entry form.) When setting the time after which the invitations will be sent, you may have it send the invitation immediately after the conditions are met or at a relative or fixed time after they are met. Lastly, you will need to activate the automated invitation settings you have defined here, which means that your settings will be initiated immediately and that REDCap will be actively 'listening' in order to send/schedule invitations for your surveys based upon the conditions you defined."
survey_1583 = "To begin the phone survey, call {0:PhoneNumber}"
survey_1584 = "To begin the survey, visit {0:SurveyLink}"
survey_1585 = "File Storage Time"
survey_1586 = "Survey Completed"
survey_1587 = "If the 'e-Consent Framework' is enabled on any survey, the e-Consent PDF Snapshot files that are archived in the File Repository can additionally be stored on an external file server  using the settings below. This might be desirable for certain regulatory compliance requirements, such as 21 CFR Part 11 studies where the PDFs must be stored in a Part 11 compliant environment.  Note: If enabled, then *all* surveys in this entire REDCap installation that have the 'e-Consent Framework' option enabled will automatically have those PDF Snapshots stored on the  external server whose credentials/settings are defined below."
survey_1588 = "Thus, regardless of the participant's local time, the survey will expire at the time entered above for the {0} time zone."
survey_1589 = "NOTE: Since the e-Consent Framework is enabled for this survey, respondents will not be allowed to return and modify their completed e-Consent response in order to maintain the fidelity of  the participant's consent."
survey_1590 = "NOTICE: While in Analysis/Cleanup project status, any already-scheduled survey invitations will NOT be sent unless the project is moved back to Production status."
survey_1591 = "NOTICE: While in Analysis/Cleanup project status, any already-scheduled alerts will NOT be sent unless the project is moved back to Production status."
survey_1592 = "If you do not have an access code, please contact the person(s) administrating this survey."
survey_1593 = "from event"
asi_000 = "Upload or download Auto Invitations"
asi_001 = "Upload Automated Survey Invitations settings (CSV)"
asi_002 = "Download all Automated Survey Invitations settings (CSV)"
asi_004 = "Using the checkboxes below, select the surveys to which you want to apply the Automated Invitation settings you just saved, then click the Copy button."
asi_005 = "You may import the Automated Survey Invitation (ASI) settings for *all* surveys/events in a single CSV file, which must contain all the required columns, each with a valid value (see below). Uploading many ASI settings at once can often be less time-consuming than entering them one at a time. If you need a quick template for an ASI import file, you might manually create an ASI for a single survey, and then perform an ASI export as the basis for your own ASI import file (e.g., using copy-and-paste in a spreadsheet program to create ASIs for other surveys/events)."
asi_006 = "Choose and upload CSV file"
asi_007 = "View the complete list of *required* columns in the CSV import/export files"
asi_008 = "Condition if this survey instrument is completed"
asi_009 = "Condition if this survey instrument is completed on this event"
asi_010 = "Email Sender"
asi_011 = "0 for Disabled, 1 for Enabled"
asi_012 = "Conditional logic"
asi_013 = "0 for No, 1 for Yes"
asi_014 = "Save & Copy to..."
asi_015 = "Automated Invitation settings were successfully copied!"
asi_016 = "Copy Automated Invitation settings to other surveys"
asi_017 = "Copy"
asi_018 = "Copy the Automated Invitation settings to the following surveys:"
asi_019 = "Survey to copy from:"
asi_020 = "The Automated Invitation settings were successfully added or modified for the following surveys:"
asi_021 = "Automated Invitation settings were successfully uploaded!"
asi_022 = "ERROR: There were errors in your uploaded CSV file. Your changes were not saved. The fields listed below in your file had either a missing value or an invalid value. Please correct these errors, and re-upload your CSV file."
asi_023 = "Re-evaluate conditions for Auto Invitations"
asi_024 = "Re-evaluate selected surveys"
asi_025 = "It may sometimes be necessary to re-evaluate some or all Automated Survey Invitations (ASIs) for all records in the project. <b>This is especially useful if an ASI's conditions (in Step 2 of the ASI setup process) has been modified after data has already been entered for some records.</b> Thus, re-evaluating an ASI for all records can bring them all up to speed to where they should be based on the current conditions of the ASI. Thus, re-evaluating them might cause some invitations to be sent and/or scheduled."
asi_026 = "If you select the surveys below and click the 'Re-evaluate' button, it will begin the process of re-evaluating each ASI for *every* record in the project. NOTE: If your project contains thousands of records or more, the process may take a few minutes, so please let it finish, and do not leave the page until it completes. Additionally, if an ASI has conditional logic and has the option 'Ensure logic is still true before sending invitation?' checked, please be aware that any scheduled (i.e. unsent) invitations *may* get unscheduled/removed during the process of re-evaluation if the conditional logic no longer evaluates as TRUE for a given record."
asi_027 = "Select surveys below to re-evaluate their ASI conditions:"
asi_028 = "Prevent this invitation from ever being sent in the future, even if conditions are met for Automated Survey Invitations? If left unchecked, this invitation will still be deleted, but it could possibly get triggered again in the future if ASI conditions are met."
asi_029 = "Prevent these invitations from ever being sent in the future, even if conditions are met for Automated Survey Invitations (if any of these invitations where originally triggered via ASI)? If left unchecked, these invitations will still be deleted, but they could possibly get triggered again in the future if ASI conditions are met if they were originally triggered via ASI."
asi_030 = "Only deleted invitations (i.e., permanently cancelled)"
asi_031 = "(excluding deleted invitations)"
asi_032 = "(permanently cancelled)"
asi_033 = "Nothing changed! It appears that no survey invitations needed to be scheduled or removed for any records in the project."
asi_034 = "invitations were scheduled (and"
asi_035 = "already-scheduled invitations were unscheduled) across a total of"
asi_036 = "Completed!"
asi_038 = "Permanently cancel this invitation? (optional)"
asi_039 = "Permanently cancel these invitations? (optional)"
asi_043 = "Please keep in mind that ASI invitations will be sent shortly after clicking the button below if set to send 'Immediately', and if any are set to send after a certain delay, the delay will be based on when you re-evaluated the ASI."
asi_044 = "NOTE: <u>Re-evaluating an ASI will schedule invitations that haven't been scheduled that should be scheduled</u>, and conversely, it will remove any invitations that are currently scheduled that should not be scheduled (because the ASI condition no longer evaluates as TRUE). <u>Re-evaluating an ASI will *NOT* modify already-scheduled invitations</u> - i.e., it will not modify their invitation text, recipient/sender addresses, or the date/time that the invitation is scheduled to be sent *if* the invitation has already been scheduled. When re-evaluating an ASI, only changes to Step 2 of the ASI setup process will be considered (and not changes to Step 3) when determining if an invitation should be scheduled or if an already-scheduled invitation should be removed/unscheduled."
asi_045 = "Integer - Recurring interval for repeating surveys only"
asi_046 = "Integer - Times to repeat (leave blank to repeat forever)"
asi_047 = "- Units of the recurring interval"
asi_048 = "Activate automated invitations for this survey?"
asi_049 = "\"Active\" must be selected in order for automated survey invitations to be triggered and sent using the conditions specified in this popup. You may make it Not Active (and vice versa) at any point in the future."
asi_050 = "NOTICE: Setting the ASI to 'Not Active' will not prevent any invitations from sending if they have already been scheduled, in which case they must instead be deleted manually via the Survey Invitation Log. Additionally, even if the 'Ensure logic is still true' setting is enabled, any already-scheduled invitations will not be re-evaluated while the ASI is set to 'Not Active'."
asi_051 = "Auto Invitation options"
asi_052 = "Re-evaluate Automated Survey Invitations"
asi_053 = "Run Re-eval Now"
asi_054 = "Reset before saving?"
asi_055 = "Change(s) made in {0} require that the queue and/or recurrence table(s) be reset for this record in order for the change(s) to take effect. We recommend you perform a reset before proceeding."
asi_056 = "Yes, Reset & Save Changes"
asi_057 = "No, Ignore & Save Changes"
asi_058 = "<b>Test Run mode is enabled</b>: Selected surveys will be re-evaluated in a sandbox-like environment, which will allow you to view which records *would be* affected by the re-evaluation  <b>without actually sending or scheduling any invitations</b>. With the test run enabled, no records will be affected during the re-evaluation."
asi_060 = "Any new value set in this Automated Survey Invitation will NOT automatically be applied for any existing records in the project UNLESS the record has  some data added/updated (via survey, data entry form, or data import). <b>As best practice, it is advised that you click the 'Re-evaluate ASIs' option in the 'Auto Invitation options' drop-down</b>  to run the re-evaluation process, which will double-check if any existing records should be triggered (and thus need to have some survey invitations to be scheduled) due to any recent change made to the ASI."
fdl_000 = "Edit Form Display Logic"
fdl_001 = "Download Form Display Logic Setup (CSV)"
fdl_002 = "Upload Form Display Logic Setup (CSV)"
fdl_003 = "You may import the Form Display Logic (FDL) settings for *all* forms/events in a single CSV file, which must contain all the required columns, each with a valid value (see below). If you need a quick template for an FDL import file, you might perform an FDL export as the basis for your own FDL import file (e.g., using copy-and-paste in a spreadsheet program to create logic for other forms/events)."
fdl_004 = "View the complete list of *required* columns in the CSV import/export files"
fdl_005 = "Form Display Logic settings were successfully added or modified for the following forms:"
fdl_006 = "Form Display Logic Setup settings successfully uploaded!"
sqs_001 = "Upload Survey Queue Setup (CSV)"
sqs_002 = "You may import the Survey Queue Setup (SQS) settings for *all* surveys/events in a single CSV file, which must contain all the required columns, each with a valid value (see below). SQS Settings for surveys not represented in the import file will retain their preexisting settings. If you need a quick template for an SQS import file, you might enable the survey queue feature on a single survey in the project, and then perform an SQS export as the basis for your own SQS import file (e.g., using copy-and-paste in a spreadsheet program to create SQSs for other surveys/events)."
sqs_003 = "The Survey Queue Setup settings were successfully added or modified for the following surveys:"
sqs_004 = "Survey Queue Setup settings were successfully uploaded!"
sqs_005 = "View the complete list of *required* columns in the CSV import/export files"
sqs_006 = "File is empty - Delete <b>ALL</b> existing Survey Queue settings?"
sqs_007 = "Download Survey Queue Setup (CSV)"
extres_01 = "Append record info to URL"
extres_02 = "Please note that selecting this option will append the record name (and if a longitudinal project, the unique event name also) to the URL of the target link. If the record names for this project are an identifier (i.e. PHI), such as social security number or medical record number, you should probably not utilize this feature, especially if you are not involved in the management or development of the website to which you are sending this record information. This is merely a warning to ensure that you are protecting any private information that might exist in the record names in your project so that you are not sending them to a third-party website unknowingly. If this is okay, then press the Save button below."
extres_03 = "Name not listed"
extres_05 = "Summary"
extres_07 = "Exactly what information is appended to the URL?"
extres_08 = "When viewing a record on a data collection instrument, one or two pieces of information will be appended to the URL: the name of the record being viewed and (if a longitudinal project) the unique event name of the current event. The following will be added to the query string of the URL: "
extres_09 = ", in which RECORDNAME and UNIQUEEVENTNAME will be replaced with the current record and event being viewed at that time. For classic, non-longitudinal projects, it would only include the record name. The unique event name for longitudinal projects is the same as can be found on the Define My Events page."
extres_10 = "Examples (assumes the user is viewing a data collection form):"
extres_11 = "If the URL defined is"
extres_12 = "and the current record name is"
extres_13 = "and the unique event name for the current event is"
extres_14 = "(classic project):"
extres_15 = "(longitudinal project):"
extres_16 = "This module will allow you to set up project bookmarks (i.e. custom links) that point to webpages that exist inside REDCap (i.e. other REDCap projects) or outside REDCap (i.e. webpages on a different server on the web). You can create simple web links for navigating to those webpages, and the links will be displayed on the left-hand project menu. You may set various settings for each link, such as defining the label for how it appears on the left-hand menu, whether or not the link opens a new window/tab in your web browser, and which individual users (or Data Access Groups) within your project will be able to utilize these bookmarks."
extres_17 = "You may"
extres_19 = "at the bottom of this page. You simply need to provide a label and a web address (URL). If you want to merely take the user to the target website, using the Simple Link option should be enough. You can create links to other REDCap projects that you have access to by selecting the REDCap Project link type. It will bring up a list of your projects, after which you will be able to choose one to create the link to it. Linking to other REDCap projects can be useful if several projects are related and require users to navigate back and forth between them often."
extres_20 = "Tell me more about the Advanced Link option"
extres_21 = "Advanced Link option"
extres_22 = "The Advanced Link option provides more capabilities than the Simple Link option. The Simple Link merely takes the user to the target website in an anonymous fashion, so the site cannot discern who is visiting it. Not only does the Advanced Link take the user to the target website, but it sends information to that website that can then be used for verifying the identity of the user. NOTE: Some technical knowledge (e.g., web development/programming skills) is required in order to utilize the Advanced Link option, and it requires that you (or your team/associates/colleagues) be the managers or developers of that external site in order to properly utilize this service. Details are listed below."
extres_23 = "Choose users who can view this link:"
extres_24 = "Project title:"
extres_25 = "Simple Link"
extres_26 = "Advanced Link"
extres_27 = "REDCap Project"
extres_28 = "Selected users"
extres_29 = "Enter the label for the link as it is seen on the left-hand menu"
extres_30 = "Enter the web address (URL) for the link"
extres_31 = "Link"
extres_32 = "Link Label"
extres_33 = "Link URL / Destination"
extres_34 = "Link Type"
extres_35 = "User Access"
extres_36 = "Opens new window"
extres_37 = "Listed below are all the REDCap projects in either production or development status to which you currently have access. Select a project to which you wish to create a link."
extres_38 = "Your REDCap projects:"
extres_39 = "select project"
extres_40 = "How to verify the identity of the REDCap user via an Advanced Link"
extres_41 = "When a user clicks on an Advanced Link, it is not a typical HTML web link, but it is actually an HTML web form that uses the POST method to send an HTTP POST request to the target external website. When the link is clicked, the POST request submits a single field named 'authkey' to the external website. The authkey is an undecipherable, encrypted string of text that will then be used by the external website for identifying the user using the steps below."
extres_42 = "Steps required for programmers/developers:"
extres_43 = "The external site will then need to send the authkey back to REDCap via a POST request to the REDCap API at the URL provided below. This will then allow REDCap to evaluate who the user is and if their session in REDCap is still active. In the API request to REDCap, only two POST parameters need to be sent: <b>'authkey'</b> and <b>'format'</b>. The 'authkey' parameter will be the value of the authkey originally received from REDCap. The 'format' parameter allows you specify the format of the response data that is returned from the API request: 'csv' (default), 'json', or 'xml'. This API request must be sent to this exact URL: "
extres_44 = "The authkey from REDCap is received by the external website via an HTTP POST request immediately after the user clicks the external link on the left-hand project menu."
extres_45 = "After sending the API request to REDCap, REDCap will return the following information in the format that was specified: <b>'username'</b> (the username of the user who clicked the link), <b>'project_id'</b> (the id number of the REDCap project that the user is coming from), <b>'data_access_group_name'</b> (the name of the data access group that the user is in, if in a group), <b>'data_access_group_id'</b> (the id number of the data access group that the user is in, if in a group), and <b>'callback_url'</b> (URL of the REDCap project from which the user came). If the API request is not formatted correctly or if the user's session is no longer active in REDCap, then REDCap will return a failed response of '0'."
extres_46 = "The values returned from the API response (e.g., username) can then by used by the external website for a variety of different purposes, such as verifying the user's identify in order to implement certain user permissions on the external site. This will all need to be handled dynamically by the external site and thus assumes that the developer of the website has designed the site to follow the appropriate course of action that the developer's script dictates based upon the values received from the API response. Once the site successfully receives the API response with all the user info and project info, the site can then do what it will with that information for whatever purpose it sees fit."
extres_47 = "Additional information for programmers/developers:"
extres_48 = "The REDCap API is language agnostic, so it does not matter in which programming language that the external website has been written when making the API request. All that is required is that the POST request to the API be formatted properly."
extres_49 = "If any of the steps listed above seems daunting or makes little sense to you, then utilizing the Advanced Link option may not be a viable option for you. If you still wish to go forward with implementing it, you may need to consider hiring a web developer who can write the script for the external site in order to accomplish the steps above for utilizing the Advanced Link option."
extres_50 = "(NOTE: This API request does NOT require the use of an API token, which is typically required for most API requests.)"
extres_51 = "You may also utilize more advanced capabilities if you use the Advanced Link option, which additionally sends extra information (e.g., user and project info) from REDCap to the target website as a means of verifying the identify of the REDCap user on that external site."
extres_52 = "Selected DAGs"
extres_53 = "Choose data access groups who can view this link:"
extres_54 = "Custom Application Links for Projects"
extres_55 = "Custom Application Links"
extres_56 = "This module will allow you to set up custom links (similar to project bookmarks) that <b>appear at the bottom of the Applications list of EVERY project's left-hand menu</b> (see example screenshot to the right). These links point to websites outside of REDCap (i.e. reside on a different server on the web), as well as to other REDCap projects. You may set various settings for each link, such as defining the label for how it appears on the left-hand menu, whether or not the link opens a new window/tab in your web browser. <b>By default, these Custom Application Links will appear for ALL users in ALL projects.</b> However, you may set them to only display for particular users, and you may also exclude it from some projects so that it will not appear for those projects."
extres_58 = "at the bottom of this page. You simply need to provide a label and a web address (URL). If you want to merely take the user to the target website, using the Simple Link option should be enough. You can create links to existing REDCap projects by selecting the REDCap Project link type. It will bring up a list of all projects, after which you will be able to choose one to create the link to it."
extres_59 = "All REDCap projects:"
extres_60 = "Listed below are all the REDCap projects in either production or development status for ALL users. Select one or more projects that you do NOT wish to have this external link displayed for them. ANY projects left unchecked below will have this external link appear on their Applications list on their project's left-hand menu."
extres_61 = "Excluded projects"
extres_62 = "Exclude projects from using for this external link"
extres_63 = "For the projects selected below, do NOT display the external link "
extres_64 = "on the project's Applications menu."
extres_65 = "Append project ID to URL"
extres_66 = "The option to append a REDCap project's project ID automatically onto the link's URL can be useful in certain cases. The project ID can be found in the URL's query string as the 'pid' numerical value for any given REDCap project while accessing that project. The project ID is how REDCap recognizes one project from another. Thus it could be used by any external webpages in the same way to differentiate the project from which a user is coming in order to cater to multiple REDCap projects individually using the same webpage for all such projects. The following will be added to the query string of the URL:"
extres_67 = "For example, if the URL defined is"
extres_68 = ", then the resulting URL after the value is appended would be the following:"
extres_69 = "add a new bookmark"
extres_70 = "This option is useful to advanced users who want to pass on extra information to the bookmarks's destination website (most likely because they manage/develop that particular website and want to use the information passed in some particular way). When this option is checked off for a given bookmark link, it will append certain information onto the link URL already specified if the link is clicked on the left-hand menu while the user is currently viewing a record on a data collection instrument. The information appended is specific to the record being viewed at that moment, and thus allows one to pass that record info onto the target website. If the user clicks the bookmark link and is NOT on a data collection form, then nothing will get appended to the URL. A good example use case for this functionality is if someone has developed a website that is able to display reports for records and thus can display the report for a single record if that record name is explicitly provided (i.e. via the URL query string)."
extres_71 = "EXAMPLE: Below displays how the Custom Application Links would appear on a project's menu."
extres_72 = "The REDCap projects of *all* users in this project:"
extres_73 = "Note: Since you are an Administrator, you are able to select a project belonging to any of the users in this project, whereas normally users can only view their own projects."
extres_74 = "Field variables and Smart Variables can be piped inside the URL of a Project Bookmark below. While many Smart Variables can be piped successfully outside of a record context (e.g., [redcap-base-url]), all field variables and some Smart Variables (e.g., [record-name], [previous-event-name]) can only be piped into the URL while the user is inside a record context, such as viewing the Record Home Page or data entry form."
dataqueries_01 = "comment"
dataqueries_02 = "comments"
dataqueries_04 = "Communication Log"
dataqueries_06 = "Date/Time"
dataqueries_08 = "Add New Comment"
dataqueries_09 = "Enter a new comment below and click the Add button."
dataqueries_12 = "exclusion not displayed"
dataqueries_13 = "exclusions not displayed"
dataqueries_14 = "Rule"
dataqueries_15 = "Rule Name"
dataqueries_16 = "Rule Logic"
dataqueries_17 = "(Show discrepancy only if...)"
dataqueries_18 = "Total Discrepancies"
dataqueries_19 = "Since you have been assigned to a Data Access Group, you are only able to view discrepancies for records assigned to your group."
dataqueries_20 = "This module will allow you to execute data quality rules upon your project data to check for discrepancies in your data. Listed below are some pre-defined data rules that you may utilize and run. You may also create your own rules or edit, delete, or reorder the rules you have already created. To find discrepancies for a given rule, simply click the Execute button next to it, or click the Execute All Rules button to fire all the rules at once. It will provide you with a total number of discrepancies found for each rule and will allow you to view the details of those discrepancies by clicking the View link next to each."
dataqueries_21 = "The pre-defined rules listed in red text cannot be modified, reordered, or removed. They are there if you wish to use them. You may also build and execute your own rules at the bottom of the table below. Rules can be set up using a literal logic format (e.g., [age] > 65) that will be evaluated as a boolean value (true or false) after an existing record's value for that field is substituted (e.g., assuming a record's value is 23 for 'age', 23 > 65 evaluates as false). The logic will be applied to all existing records in the project, and for any record for which the logic evaluates as true, it will return it as a discrepancy for that rule. Similar to branching logic and calculated fields, REDCap variable/field names may be utilized in the rule logic by placing the variable name inside square brackets [ ]. Also, for longitudinal projects, you may reference a field on one specific event by prepending the variable name in the logic with the unique event name in square brackets."
dataqueries_22 = "page. If Data Access Groups exist for this project, then discrepancies will also be stratified according to their group (assuming the user viewing this page is not in a group). Any user within a Data Access Group will only be able to see the discrepancies for their own group. Also, if users do not have user privileges to view or edit data on specific data entry forms, then they will not be able to view data from those forms if displayed in any results on this page as a data quality discrepancy."
dataqueries_23 = "Status"
dataqueries_25 = "Discrepant fields with their values"
dataqueries_26 = "(Sorted by DAG)"
dataqueries_27 = "The term 'hidden fields' refers to any fields on a survey or data entry form that are not being displayed because branching logic is hiding them, which assumes that the field's value should be blank/null."
dataqueries_28 = "Delete rule?"
dataqueries_29 = "Exclude"
dataqueries_30 = "What is 'exclusion'?"
dataqueries_31 = "You may hide certain results from displaying again and again by excluding them. Simply click the 'exclude' link for a result in the table of discrepancies for a rule, and that result will not be counted next time in the number of discrepancies for that rule, nor will it be displayed in the table of results. Results that have been excluded can be viewed again by clicking the 'view' link at the top of the results table for that rule, in which it will display the number of excluded results if any should exist. Results may have their exclusion status removed by clicking the 'remove exclusion' link in the results table for an excluded result."
dataqueries_32 = "Could not process"
dataqueries_33 = "due to an unknown error."
dataqueries_34 = "Please check this rule's logic for any possible errors in syntax."
dataqueries_35 = "Read more detailed instructions."
dataqueries_36 = "Special functions may also be used within the logic as well (similar to functions in calculated fields), all of which are listed on the"
dataqueries_37 = "If a discrepancy has been found for a given rule, any individual discrepancy in the list of results may be excluded from those results in the future. Excluding a result merely prevents it from being included in the count of discrepancies if the rule is executed again in the future. Excluded results can be accessed again by clicking the 'view' link at the top of the results table for that rule, after which they can be un-excluded, if desired."
dataqueries_38 = "Data Quality (create/edit rules)"
dataqueries_39 = "Data Quality (execute rules)"
dataqueries_40 = "Create & edit rules"
dataqueries_41 = "Execute rules"
dataqueries_44 = "You do not have access rights to some of the fields used in the logic because you do not have user privileges to view the data entry forms on which those fields exist. Thus, you will not be able to view the results for this rule."
dataqueries_45 = "The following fields listed in your logic do not exist in this project and thus cannot be used. These fields must be removed from the logic before you can continue."
dataqueries_46 = "FIELDS:"
dataqueries_47 = "SYNTAX ERROR IN LOGIC"
dataqueries_48 = "UNRECOGNIZED FUNCTIONS:"
dataqueries_50 = "This rule cannot be properly executed because the logic contains syntax errors, which may include incorrectly defined variable names in the logic or the use of illegal/unrecognized functions. Try editing and saving the logic again, and it should report back what the exact issues are so that you may fix them."
dataqueries_51 = "Issue exists"
dataqueries_52 = "Resolved"
dataqueries_53 = "Missing value"
dataqueries_54 = "Validation error"
dataqueries_55 = "Outlier"
dataqueries_56 = "Deferred"
dataqueries_57 = "Invalid value"
dataqueries_58 = "Out of range"
dataqueries_59 = "Leave as-is / Ignore"
dataqueries_60 = "Not an issue"
dataqueries_61 = "Cannot be resolved"
dataqueries_62 = "Blank values"
dataqueries_63 = "(required fields only)"
dataqueries_64 = "Field validation errors"
dataqueries_65 = "(incorrect data type)"
dataqueries_66 = "(out of range)"
dataqueries_67 = "Outliers for numerical fields"
dataqueries_68 = "(numbers, integers, sliders, calc fields)"
dataqueries_69 = "Hidden fields that contain values"
dataqueries_70 = "Multiple choice fields with invalid values"
dataqueries_71 = "[no data]"
dataqueries_72 = "[cannot display data]"
dataqueries_73 = "(Reason: Lack of user privileges)"
dataqueries_75 = ", stdev:"
dataqueries_76 = "Enter descriptive name for new rule"
dataqueries_77 = "(e.g., Participants below age 18)"
dataqueries_78 = "Enter logic for new rule"
dataqueries_79 = "How do I use special functions?"
dataqueries_80 = "Execute"
dataqueries_81 = "Data Quality Rules"
dataqueries_82 = "Processing rule"
dataqueries_83 = "of"
dataqueries_84 = "Processing Complete!"
dataqueries_86 = "Clear"
dataqueries_87 = "exclude"
dataqueries_88 = "remove exclusion"
dataqueries_89 = "(excluded)"
dataqueries_90 = "Reloading table..."
dataqueries_91 = "Discrepancies found:"
dataqueries_92 = "view"
dataqueries_93 = "Record:"
dataqueries_96 = "The error may occurred because too many discrepancies were found or too much data exists in the project, thus causing an overload during processing."
dataqueries_97 = "(NOTE: All results cannot be shown because there are too many. Only the first"
dataqueries_98 = "can be displayed.)"
dataqueries_99 = "ERROR! Syntax errors exist in the logic. Please check the logic to ensure that illegal characters or illegal functions are not used and that any parentheses, quotes, or brackets have not been accidentally omitted from the logic."
dataqueries_100 = "What is Data Quality?"
dataqueries_101 = "The Data Quality module is a page that can help you easily find any data discrepancies or errors in your project data by allowing you to create and execute data quality 'rules'. If a user has 'create & edits rules' rights for Data Quality, then they will be able to access the Data Quality module and will be able to create, edit, reorder, and delete any of the custom rules in that module. If this user setting is not checked, they will not be able to do so. If they have 'execute rules' rights for Data Quality, then they will be able to access the Data Quality module and will see the 'Execute' buttons on that page and thus be able to execute any of the rules that have been created (including the pre-defined rules), which will display a detailed list of all data discrepancies. If this user setting is not checked, they will not be given the option to execute any rules. If a user does not have either checkbox set for Data Quality rights, then they will not see the Data Quality module listed on the project's left-hand menu, nor will they be able to access the module."
dataqueries_108 = "TIMEOUT"
dataqueries_109 = "The following terms listed in your logic appear to be either illegal or unrecognized functions, and thus they will not be allowed in your logic. They must be removed from the logic before you can continue. To see a list of allowed functions, click the 'How do I use special functions?' link on this page."
dataqueries_110 = "One or more fields are not referenced by event. Since this is a longitudinal project, you must specify the unique event name when referencing a field in the logic. For example, instead of using [age], you must use [enrollment_arm1][age], assuming that enrollment_arm1 is a valid unique event name in your project. You can find a list of all your project's unique event names on the Define My Events page."
dataqueries_111 = "One or more of the unique event names referenced in the logic is invalid. Please replace the invalid event names below with a valid unique event name. You can find a list of all your project's unique event names on the Define My Events page."
dataqueries_112 = "Invalid unique event names:"
dataqueries_113 = "Data Quality rules were violated!"
dataqueries_115 = "Execute rules:"
dataqueries_116 = "All except A&B"
dataqueries_117 = "All custom"
dataqueries_118 = "The Data Quality rules listed below were found to have discrepancies for this record. Review the table below to see which rules were violated so that the data values for the fields involved can be corrected, if necessary. You may exclude a result in the table by clicking the 'exclude' link on the right side, after which that rule will no longer be displayed for this record whenever the record is saved."
dataqueries_119 = "Rule(s) violated"
dataqueries_120 = "Fields involved"
dataqueries_121 = "You may hide the violations of Data Quality rules for a given record by excluding them, which prevents them from being displayed again and again in the future. Simply click the 'exclude' link for a rule, and that rule will no longer be displayed in the table of rules violated. If a rule was excluded accidentally, you may remove its exclusion status while the pop-up is still open by clicking the 'remove exclusion' link in the table."
dataqueries_122 = "[cannot display data due to user privilege restrictions]"
dataqueries_123 = "Real-time execution"
dataqueries_124 = "Execute in real time on data entry forms"
dataqueries_125 = "Enabling the 'real-time execution' functionality for a custom rule is a great way to add more data validation on a data entry form to ensure that data are getting entered correctly *at the moment* they are entered, as opposed to checking the quality of the data retroactively by executing the rules here on this page. Using the 'real-time execution' feature is an excellent way to be proactive about maintaining the quality and integrity of your data."
dataqueries_126 = "Checking the 'real-time execution' checkbox for any custom data quality rule will enable the rule to be executed invisibly on data entry forms whenever a user clicks the Save button to create or modify a record. After clicking Save, it will execute all relevant data quality rules invisibly (i.e. behind the scenes) and will display a warning pop-up message if any of the rules have been violated, in which it will display a list of the data quality rules that were violated and also display the fields involved with their data values. If no rules were violated, then it will save the record as usual and not display a pop-up message. Just like the results that are returned when executing rules on the Data Quality page itself, results displayed on data entry forms for 'real-time execution' can be excluded (if desired) so that they will not be displayed again if they are still in violation in the future."
dataqueries_127 = "NOTE: The pre-defined rules cannot have 'real-time execution' enabled, but only the custom rules can. Also, the 'real-time execution' functionality does not work on survey pages, nor does it get executed when performing data imports (either via the Data Import Tool or via the API). Thus, it only works on data entry forms."
dataqueries_128 = "After changing the value, click the button here to save it."
dataqueries_129 = "This pop-up displays the Data Resolution Workflow for the specified record for a given field and/or Data Quality rule. Users with appropriate user privileges may open data queries to begin a documented process of resolving an issue with the data. Opened data queries may thus be responded to by users with appropriate privileges, and then they may be closed once the issue has been resolved. All data queries can also be viewed on the Resolve Issues page in this project."
dataqueries_130 = "Resolve issue"
dataqueries_131 = "What is the Data Resolution Workflow?"
dataqueries_132 = "Data issues found with the Data Quality module can be resolved using the Data Resolution Workflow. After executing any given data quality rule and viewing the results in the pop-up window, you will see a button in the 'Resolve issue' column that allows you and other users in the project to leave comments and/or complete a formal data resolution process for documenting details of the data issue, including the origin the issue, who resolved the issue, and how it was resolved (if applicable). Once the data resolution process has been opened for an item, it will then appear in the 'Resolve Issues', which allows you to view all open items that need to be resolved."
dataqueries_133 = "Enable the Field Comment Log or Data Resolution Workflow (Data Queries)?"
dataqueries_134 = "For this project, you may enable either the Field Comment Log or Data Resolution Workflow (also known as the Data Queries module). The Field Comment Log (enabled by default) allows users to leave comments for any given field on a data entry form by clicking the balloon icon next to the field. All comments can also be viewed, searched, and downloaded on the Field Comment Log page. Alternatively, if the Data Resolution Workflow is enabled, users will be allowed to open a workflow for documenting the process of resolving issues with data in the project (i.e. opening, responding to, and closing data queries)."
dataqueries_135 = "All data access groups"
dataqueries_136 = "All events"
dataqueries_137 = "Data Resolution Workflow"
dataqueries_138 = "Respond only to opened queries"
dataqueries_139 = "Open, close, and respond to queries"
dataqueries_140 = "View data resolution workflow"
dataqueries_141 = "Field Comment Log"
dataqueries_142 = "Enable:"
dataqueries_143 = "View only"
dataqueries_144 = "This data resolution workflow, often called 'data queries' in clinical trials and studies, can be utilized either on a data entry form (clicking the balloon icon next to the field) or on the Data Quality page when finding data discrepancies. The Data Quality module will then display a new 'Resolve Issues' tab, which will allow users to view all resolved and unresolved data queries and thus resolve any queries that are still open. Different user privileges may be given to users that control whether or not users can view, open/close, or respond to data queries."
dataqueries_145 = "View comment log"
dataqueries_146 = "Comments"
dataqueries_147 = "Comments and Details"
dataqueries_148 = "Resolve Issues"
dataqueries_149 = "Incorrect values for calculated fields"
dataqueries_150 = "Incorrect value"
dataqueries_151 = "Close the query"
dataqueries_152 = "Respond to query"
dataqueries_153 = "Send back for further attention"
dataqueries_154 = "This pop-up displays all the field comments for the record and field specified below. Users with access to data entry forms may leave one or more comments on any field on a data collection instrument, after which the balloon icon will stay lit up to signify that comments exist for that field for this record. All field comments for all records/fields can also be viewed, keyword searched, and filtered on the"
dataqueries_155 = "What is Data Resolution Workflow?"
dataqueries_156 = "If the Data Resolution Workflow is enabled, users will be allowed to open a workflow for documenting the process of resolving issues with data in the project."
dataqueries_157 = "Some users may have their privileges restricted so that they have no access to the Data Resolution Workflow, thus they cannot view or edit any data queries. Those with 'view only' privileges will be able to view all opened queries but not modify them or contribute. Users with 'respond only' privileges can respond to an opened query (especially if they have been assigned to it), but can neither open nor close a data query. And users with the highest privileges can perform all of the above actions (open, respond to, and close queries)."
dataqueries_158 = "User assigned (all users) or not assigned"
dataqueries_159 = "User not assigned"
dataqueries_160 = "There was an error during file upload!"
dataqueries_161 = "Corrected - Data missing"
dataqueries_162 = "Corrected - Typographical error"
dataqueries_163 = "Corrected - Wrong source used"
dataqueries_164 = "Verified - Confirmed correct (no error)"
dataqueries_165 = "The Data Resolution Workflow cannot be opened because the record does not exist yet. It must first been saved. You may click the Save button below, which will save all the values on the current form and then automatically open the Data Resolution Workflow pop-up."
dataqueries_166 = "The Field Comment Log cannot be opened because the record does not exist yet. It must first be saved. You may click the Save button below, which will save all the values on the current form and then automatically open the Field Comment Log pop-up."
dataqueries_167 = "Must save record before opening Data Resolution Workflow"
dataqueries_168 = "Must save record before opening Field Comment Log"
dataqueries_169 = "Data Quality Rule:"
dataqueries_170 = "This page displays various statistics and metrics regarding all data queries that are currently unresolved or have already been resolved via the Data Resolution Workflow in this project. The 'average time for query response' refers to the time lapse between when a query was opened and the time it was first responded to by a user (includes both open and closed queries). The 'average time to query resolution' refers to the time lapse between when a query was opened and the time it was closed (includes only closed queries)."
dataqueries_171 = "This page displays all data queries that are currently unresolved or have already been resolved using the Data Resolution Workflow. Some issues may have been initiated by users on data collection instruments, and others may have been initiated after executing Data Quality rules on the Find Issues tab. The table lists the name of the record and the specific field or Data Quality rule to which the data query belongs, as well as the user assigned to the query (if applicable), the number of days the data query has been open, and a brief snippet of the query's first and last comment. The results in the table can be filtered by the query status type (e.g., open, closed), by certain fields or Data Quality rules, and also by users assigned to it. Each data query may be viewed by clicking the button to its left."
dataqueries_172 = "This page displays the Field Comment Log for all records/events/fields in this project. You may use the controls below to perform keyword searches in the comments as well as filter the comments by record, event, field, or data access group. Keep in mind that if you do not have user privileges to view some data collection instruments, then comments for any fields on those instruments will not be displayed in the table. Also, if you belong to a data access group, then you will only see results for records that belong to your group. The entire Field Comment Log is downloadable as a file in Excel/CSV format."
dataqueries_173 = "Click button to<br>view data query"
dataqueries_174 = "Data Quality rule<br>and/or Field"
dataqueries_175 = "Days Open"
dataqueries_176 = "User Assigned"
dataqueries_177 = "First Update"
dataqueries_178 = "Last Update"
dataqueries_179 = "Filters:"
dataqueries_180 = "Data Resolution Dashboard"
dataqueries_181 = "[Users assigned]"
dataqueries_182 = "[Fields]"
dataqueries_183 = "All fields"
dataqueries_184 = "All rules"
dataqueries_185 = "All fields and rules"
dataqueries_186 = "Open / unresolved issues"
dataqueries_187 = "Open unresponded"
dataqueries_188 = "Open responded"
dataqueries_189 = "Closed / resolved issues"
dataqueries_190 = "No results to display"
dataqueries_191 = "[Rules]"
dataqueries_192 = "[same as first update]"
dataqueries_193 = "Find Issues"
dataqueries_194 = "Resolution Metrics"
dataqueries_195 = "Comment"
dataqueries_196 = "Reopen query"
dataqueries_197 = "Open query"
dataqueries_198 = "Upload file (optional):"
dataqueries_199 = "-- choose response --"
dataqueries_200 = "Reply with response:"
dataqueries_201 = "Assign query to a user (optional):"
dataqueries_202 = "Reopen the closed query"
dataqueries_203 = "Response comment:"
dataqueries_204 = "New comment:"
dataqueries_205 = "Assigned to user:"
dataqueries_206 = "Reopened query"
dataqueries_207 = "Action:"
dataqueries_208 = "Closed query"
dataqueries_209 = "Sent back for further attention"
dataqueries_210 = "Opened query"
dataqueries_211 = "Uploaded file:"
dataqueries_212 = "Response:"
dataqueries_213 = "Awaiting action by user with sufficient user privileges."
dataqueries_214 = "Status:"
dataqueries_215 = "Closed / Resolved"
dataqueries_216 = "Open / Unresolved"
dataqueries_217 = "Not Opened"
dataqueries_218 = "(responded)"
dataqueries_219 = "(unresponded)"
dataqueries_220 = "Data Verified"
dataqueries_221 = "Verified data value"
dataqueries_222 = "Data De-verified"
dataqueries_223 = "De-verified data value"
dataqueries_224 = "De-verify data value"
dataqueries_225 = "(automatically via data change)"
dataqueries_226 = "Click button to view comment log"
dataqueries_227 = "more comment not displayed"
dataqueries_228 = "more comments not displayed"
dataqueries_229 = "Keyword search"
dataqueries_230 = "Keywords must contain at least 2 characters when performing a keyword search. Please change it and try again."
dataqueries_231 = "Search tips"
dataqueries_232 = "When performing a keyword search for the Field Comment Log, you may use as many keywords as you wish. By default, it will return all results that contain ANY of the keywords provided. To search for an exact phrase, surround your phrase with double quotes and it will return all results that contain that exact phrase (plus any other keywords/phrases you provide in that search). Also, please note that the following keywords will be ignored:"
dataqueries_233 = "[Returned no results]"
dataqueries_234 = "Results returned:"
dataqueries_235 = "Display maximum"
dataqueries_236 = "Use filters to limit results further."
dataqueries_237 = "results"
dataqueries_238 = "Export entire log"
dataqueries_239 = "Top 5 queried fields"
dataqueries_240 = "Top 5 queried data quality rules"
dataqueries_241 = "Top 5 queried records"
dataqueries_242 = "General statistics"
dataqueries_243 = "Average time to query resolution:"
dataqueries_244 = "Number of open / unresolved queries:"
dataqueries_245 = "responded:"
dataqueries_246 = "unresponded:"
dataqueries_247 = "Number of closed / resolved queries:"
dataqueries_248 = "Number of open queries (by data access group)"
dataqueries_249 = "Average time to query resolution (by data access group in days)"
dataqueries_250 = "Insufficient data exists for this chart to be displayed."
dataqueries_251 = "Be advised that when using the user filter in conjunction with the keyword search, the searching/filtering for each will always be performed independently on the thread-level (rather than at the comment-level). This means, for example, that if you search by keyword and also filter by a user at the same time, it will return results (i.e. threads) where that user contributed at least one comment to the entire thread while the keyword was also found in at least one comment in that same thread. Thus, it will not return only threads where that user added a comment containing that keyword."
dataqueries_252 = "Number of closed queries (by data access group)"
dataqueries_253 = "Average time for query response (by user in days)"
dataqueries_254 = "Average time for query response (by data access group in days)"
dataqueries_255 = "Average time for query response:"
dataqueries_256 = "Since Data Access Groups exist and since you do not belong to a group, it will also display several charts for comparing the resolution metrics of all groups."
dataqueries_257 = "NOTE: Since you belong to a Data Access Group, you will not be able to view the charts for comparing the resolution metrics of all groups. Only users that do not belong to a group will be able to view such charts."
dataqueries_258 = "page in this project."
dataqueries_259 = "None"
dataqueries_260 = "The Data Resolution Workflow has now been enabled!"
dataqueries_261 = "Please read the instructions below regarding your next steps or view the video."
dataqueries_262 = "Set user privileges"
dataqueries_263 = "Before the users in your project can begin utilizing the Data Resolution Workflow, they must first be given user privileges to do so. These user privileges dictate the things which they are allowed to do within the Data Resolution Workflow. Navigate to the User Rights page where you will see a new section of privileges specifically for the Data Resolution Workflow. You may give any user one of the following privileges: no access, view only, respond only, and open/close/respond to queries. All users will initially have 'no access' privileges."
dataqueries_264 = "Opening data queries"
dataqueries_265 = "Using the Resolve Issues page"
dataqueries_266 = "An open data query implies that there is an issue with a data value that needs to be resolved. Opening the query initiates the process of investigating the issue and resolving it (i.e. closing the query). The most typical place to open a data query is for a field on a data entry form. On the form, click the gray balloon next to the field, which will open up the Data Resolution Workflow pop-up. This will allow you to open a new query if you have appropriate user privileges to do so in which you can leave a descriptive comment along with the ability to assign that particular data query to another user (optional). Instead of opening a query, alternatively you may verify the field's data value, which will denote that the data value has been certified as correct. NOTE: If a verified data value is ever changed, it will become automatically de-verified, after which it may be verified again (if desired)."
dataqueries_267 = "Responding to and closing data queries"
dataqueries_268 = "Any user with 'respond' privileges will be able to respond to an open query (even if it is assigned to a specific user). The responder may select a response type (e.g., typographical error) and provide a descriptive comment with the ability to also attach a file (optional). Once a query has been responded to, a user with 'close' privileges may close the query, after which it will be considered resolved."
dataqueries_269 = "While data queries will be opened either on a data entry form or via the results of a Data Quality rule, users will most likely respond to and close queries on the 'Resolve Issues' page (seen on left-hand menu). This page will serve as a dashboard that will neatly organize all queries (both open and closed) so that they may be reviewed and so that any open queries may be easily responded to and closed. That page can serve as a nice to-do list for addressing all open queries."
dataqueries_270 = "Viewing resolution metrics"
dataqueries_271 = "It can sometimes be useful to view metrics with regard to your data queries, such as a count of how many queries are open or closed, the average time that users respond to an open query, or the average time to query resolution. The 'Resolution Metrics' page will provide some useful statistics and some helpful bar charts for viewing progress and activity. If your project utilizes Data Access Groups, it provides even more useful charts to compare the progress of the different groups and to stratify their activity."
dataqueries_272 = "Data queries may also be opened on the Data Quality page when viewing the results of an executed Data Quality rule in which a button to open the Data Resolution Workflow will appear next to each result in the pop-up. If a data query's status is either 'Closed' or 'Data Verified', it will not be initially displayed as visible in Data Quality discrepancy results anymore but will be considered as excluded (since it is considered resolved). Any excluded results can always be made visible by clicking the 'view' link in the Data Quality results pop-up."
dataqueries_273 = "For a brief overview, view the Data Resolution Workflow video."
dataqueries_274 = "Read introduction to Data Resolution Workflow"
dataqueries_275 = "Introduction to Data Resolution Workflow"
dataqueries_276 = "The data history results are sorted from earliest to most recent."
dataqueries_277 = "(most recent data change)"
dataqueries_278 = "Close survey"
dataqueries_279 = "Average time queries remain unresolved:"
dataqueries_280 = "(open queries only)"
dataqueries_281 = "(closed queries only)"
dataqueries_282 = "(includes open and closed queries)"
dataqueries_284 = "Delete this Field Comment?"
dataqueries_285 = "Are you sure you wish to delete this Field Comment for this field for this record? This process is irreversible."
dataqueries_286 = "* Edited"
dataqueries_287 = "NOTE: If you wish to prevent all users in this project from editing or deleting field comments below, see the Additional Customizations popup on the Project Setup page."
dataqueries_288 = "Allow users to edit or delete Field Comments (excludes Data Resolution Workflow comments)?"
dataqueries_289 = "Open queries only"
dataqueries_290 = "Open and respond to queries"
dataqueries_291 = "Calculated value should be"
dataqueries_292 = "Fix ALL incorrect calculated values?"
dataqueries_293 = "Fix calcs now"
dataqueries_294 = "Calculated values fixed!"
dataqueries_295 = "calculated values were successfully fixed."
dataqueries_296 = "(The data quality rule is now automatically re-running to ensure that all calculated field values were updated correctly.)"
dataqueries_297 = "Apply to:"
dataqueries_298 = "for record"
dataqueries_299 = "Number of comments"
dataqueries_300 = "All status types"
dataqueries_301 = "The term 'outlier' refers to a value that is more than two standard deviations from the mean."
dataqueries_302 = "[User deleted from system]"
dataqueries_304 = "[Data cannot be viewed because you do not have view access to the data collection instrument.]"
dataqueries_305 = "Fields containing \"missing data codes\""
dataqueries_306 = "Note: This rule will not return any fields that are blank but also have Missing Data Codes. If you wish to find fields with Missing Data Codes, it is recommended to execute Rule I instead."
dataqueries_307 = "Codes for Missing Data"
dataqueries_308 = "Code / Value"
dataqueries_309 = "The Data Quality rules listed below were found to have discrepancies for this record. Review the table below to see which rules were violated so that the data values for the fields involved can be corrected, if necessary. If you have some data query privileges, you may click the button in the 'Resolve issue' column to open the Data Resolution Workflow popup for a given rule. After that data query is set to 'closed', that rule will no longer be displayed for this record whenever the record is saved."
dataqueries_310 = "Current Query Status"
dataqueries_311 = "Data Quality Rule"
dataqueries_312 = "Time Raised"
dataqueries_313 = "Time Resolved"
dataqueries_317 = "Notify this user of their assignment using:"
dataqueries_318 = "You were assigned to a data query"
dataqueries_319 = "You have been assigned to a data query that was just opened in the REDCap project"
dataqueries_320 = "Open the data query assigned to you"
dataqueries_321 = "Assigned to a data query"
dataqueries_322 = "Assign to other user"
dataqueries_323 = "Reassign query to selected user:"
dataqueries_324 = "Reassign"
dataqueries_325 = "Assign query to a user"
dataqueries_326 = "ERROR: Only REDCap administrators may delete uploaded files from data queries. You will need ask an admin to return here to delete this file."
dataqueries_327 = "SUCCESS! The attachment was successfully deleted from the data query."
dataqueries_328 = "Are you sure you wish to delete this file from the data query?"
dataqueries_329 = "Upload or download Data Quality Rules"
dataqueries_330 = "Upload Data Quality Rule (CSV)"
dataqueries_331 = "Download Data Quality Rule (CSV)"
dataqueries_332 = "You can <b>only add new Data Quality Rules</b> to the project by uploading a CSV file with a new Data Quality Rules configuration. The format for the CSV upload file can be acquired by exporting the CSV file of your existing Data Quality Rules."
dataqueries_333 = "Select your CSV file of Data Quality Rules to be added:"
dataqueries_334 = "The rule name"
dataqueries_335 = "The rule logic"
dataqueries_336 = "is not valid."
dataqueries_337 = "Real-time execution"
dataqueries_338 = "Please specify 'n' for Disabled, 'y' for Enabled"
dataqueries_339 = "Displayed below is a preview of all new data quality rules you are about to commit. Please look over the additions, and then approve them by clicking the Upload button."
dataqueries_340 = "data quality rules were added."
dataqueries_341 = "<b>Note:</b> You <b>cannot edit or delete</b> existing Data Quality Rules using the CSV file but can only do that by clicking the edit/delete icon next to a given Rule."
dataqueries_342 = "<b>Note: </b> These new data quality rules will be added to the existing set of data quality rules."
dataqueries_343 = "Row #"
dataqueries_345 = "Both Rule Name and Rule Logic are missing."
dataqueries_346 = "Export results (CSV)"
dataqueries_347 = "Downloading data quality results..."
dataqueries_348 = "SUCCESS! The data quality results were successfully downloaded."
dataqueries_349 = "Fields that contain values that should be hidden"
dataqueries_350 = "This refers to any fields on a survey or data entry form that are being displayed because they have a value in which their branching logic dictates that they should otherwise be hidden."
dataqueries_351 = "<b>ERROR:</b> You are running too many Data Quality rules simultaneously. To protect the performance of the REDCap server, only {0:MaxConcurrentQueries} Data Quality rules may be running at the same time. The oldest Data Quality rule requests will be forced to end prematurely, thus resulting in this error. However, you may always run them again."
dataqueries_352 = "<b>REDCap ERROR:</b> An unknown error has caused the REDCap page to halt. This may have occurred if you have opened multiple browser tabs of the same REDCap page. If that is not the case, then please try to reload this page."
dataqueries_353 = "REDCap Database Error:"
dataqueries_354 = "<b>TIMEOUT ERROR:</b> The task could not finish because it exceeded the processing time limit, which is {0:TimeoutValueSeconds} seconds. You may try again to see if this task completes, but the task may simply take too long to ever complete successfully."
dataqueries_355 = "mean:"
dataqueries_356 = "The Blank Values rules above automatically exclude fields hidden by branching logic when searching for blank values. If a field is hidden by branching logic on a data entry form or survey, then it is expected that such a field would not have a value. Thus for these cases, the values for those hidden fields will not be classified as missing."
dataqueries_357 = "Hide closed/verified data queries from Data Quality results (for Data Resolution Workflow only)"
dataqueries_358 = "Are you sure you wish to delete data quality rule"
dataqueries_359 = "<b>WARNING:</b> Since you are using the Data Resolution Workflow, please be advised that deleting this data quality rule will additionally DELETE ALL DATA QUERIES (open or closed) that are currently associated with this rule. This is a permanent and irreversible process."
random_01 = "Randomization is a process that assigns participants/subjects by chance (rather than by choice) into specific groups, typically for clinical research and clinical trials. The randomization module in REDCap will help you implement a defined randomization model within your project, allowing you to randomize your subjects (i.e. records in your project). In this module, you first define the randomization model with various parameters. Based on the defined parameters, the module creates a template allocation table, which you can use to structure the randomization table you will import. The module also monitors the overall allocation progress and assignment of randomized subjects."
random_02 = "select a field"
random_03 = "Add another stratum"
random_04 = "C) Choose your randomization field"
random_05 = "Example #1 (basic)"
random_06 = "Choose strata"
random_07 = "STEP 2: Download template allocation tables (as Excel/CSV files)"
random_08 = "Upload allocation table (CSV file)"
random_09 = "Upload File"
random_10 = "ERROR: This field has already been used. Please choose another field."
random_11 = "ERROR: An error occurred during the download. Please go back and try again."
random_12 = "Only CSV files can be uploaded"
random_13 = "ERROR: An error occurred during the upload."
random_14 = "Uploaded file was empty."
random_15 = "The header variables in the first row of your CSV file are not correct. The first row should be the following:"
random_16 = "User privileges"
random_17 = "The following errors occurred. Please address them and try again."
random_18 = "There does not exist any values in your CSV file other than the headers (first row)."
random_19 = "Excel/CSV"
random_20 = "is not a valid categorical option for the field"
random_21 = "The randomization allocation table was created!"
random_22 = "How it works"
random_23 = "Sorry, but the maximum number of fields that can be used as randomization criteria is"
random_24 = "Randomization in REDCap works by allowing you to create your custom allocation list, which will serve as a lookup table for deciding how to randomize subjects. In step 1 below, you will set up your randomization model and all its parameters, after which step 2 will provide some examples of how to set up your allocation table before you will finally upload it in step 3. <b>NOTE:</b> The randomization module does not create the randomization table for you. This table must be generated outside of REDCap using other software (e.g., SAS, Stata, R), most likely by the statistician/data analyst involved in your project. The randomization table you upload will be used as a lookup table for randomizing subjects. By letting you create your own allocation table outside of REDCap, it lets you and your team choose exactly how you wish to structure your allocations and assignments (e.g., block sizes, permutations, stratification balancing). It does not necessarily matter how you create or set up your allocation table so long as you structure it correctly, as prescribed in the steps listed below in this module."
random_25 = "When randomization occurs"
random_26 = "Dashboard (all allocations)"
random_27 = "Please choose at least one criteria field"
random_28 = "Randomization of subjects will occur on the data collection form where your randomization field (from step 2) is located. Before a subject is randomized, a 'Randomize' button will appear next to that field. When a user (who has been given appropriate 'Randomize' user privileges) clicks that button, a pop-up box will appear that will allow the user to randomize the subject. If any grouping or stratification is being used, the user must provide the group or strata values if any are missing before they can randomize the subject. After a subject has been randomized, the grouping and/or strata fields (if any of these are used) will become permanently locked and unmodifiable. The randomization field will always be locked and unmodifiable both before and after randomization has occurred for a subject. When the user randomizes the subject, REDCap will check the allocation table and assign that subject's randomization field value, which will be derived from the next match in the table based upon the criteria (e.g., strata field values, group). If not using stratified randomization and not randomizing by group/site, then it will simply provide the subject with the very next value in the allocation table."
random_29 = "STEP 1: Define your randomization model"
random_30 = "STEP 3: Upload your allocation table (CSV file)"
random_31 = "This step will allow you to define the randomization model you will be implementing and all its parameters, which includes defining strata (if applicable) and optionally randomizing subjects per group/site (if a multi-site study)."
random_32 = "Once you have created your custom allocation table as a CSV file and made sure that you kept the format prescribed in the template files from Step 2 above, you may now upload the file below. It will be checked for any possible errors first before it is accepted and stored in REDCap. Please note that you will need to create two different allocation tables: one to be used for testing while your project is in development status and the other for use when in production status. Below are some important reminders before you begin uploading your allocation tables."
random_33 = "Below are some example files that you may download to get a general idea for how you may structure your own randomization table. You do not have to use any of these. In fact, <b>we recommend that you NOT use these exact templates</b> but instead recommend that you merely use them as an example or baseline to start from in order to create your own custom allocation file. After uploading your allocation table in Step 3 below, it will then be used as a lookup table to perform assignments when subjects are being randomized. <b>NOTE:</b> Record names (e.g., study ID) should NOT be included as a column in your allocation table, but only the fields listed in the example files below."
random_34 = "Example #2 (all possible combos)"
random_35 = "for use in DEVELOPMENT status"
random_36 = "for use in PRODUCTION status"
random_39 = "Not uploaded yet"
random_40 = "New assignments were appended to your existing randomization allocation table!"
random_41 = "All assignments are listed in their proper order. Records that have been already randomized will have a checkmark icon in its row with the name of the record listed."
random_42 = "There already exists an allocation table"
random_43 = "All assignments are grouped to show in aggregate the count of records that have been randomized for each row (i.e. combinations). Assignments that have been used will get counted in the 'Used' column while those that are still unallocated will get counted in the 'Not Used' column. Once all assignments have been used for a given row/combination, it will display a checkmark icon in its row."
random_44 = "Already uploaded"
random_45 = "The table below displays the allocation dashboard"
random_46 = "Used"
random_47 = "Not Used"
random_48 = "Setup"
random_49 = "Dashboard (grouped)"
random_50 = "There is nothing to display yet. You must first set up your allocation table(s) on the Setup tab."
random_51 = "Randomize"
random_52 = "Below you may perform randomization for"
random_53 = "on the field"
random_54 = "Provide any missing values below for"
random_55 = ", then click the Randomize button below."
random_56 = "Already randomized"
random_57 = "was randomized for the field"
random_58 = "and assigned the value"
random_60 = "RANDOMIZATION ERROR:"
random_61 = "cannot be randomized because there are no allocations available for assignment based upon the values you just submitted. If this is a problem, please speak to the person(s) in charge of randomization for this project (e.g., your project manager, data analyst, statistician) in order to resolve this."
random_62 = "Please note that the fields below will become permanently locked and uneditable on the data entry form once this record has been randomized."
random_63 = "Download table"
random_64 = "Delete allocation table?"
random_65 = "Are you sure you wish to delete this allocation table? It will be permanently erased along with all randomizations that have been allocated thus far. (NOTE: The ability to delete the allocation table is ONLY available while the project is still in Development status.)"
random_66 = "The allocation table has been deleted."
random_67 = "Also, for ALL records that have already been randomized, the randomization field's value will be deleted for each record."
random_68 = "Do you still wish to delete the table?"
random_69 = "Not yet randomized"
random_70 = "This record cannot be randomized right now because a randomization allocation table has not yet been uploaded for this project. Someone with appropriate user privileges should go to the Randomization module (found on this project's left-hand menu) and upload an allocation table. Only then can records be randomized."
random_71 = "This record cannot be randomized right now because a randomization allocation table was never uploaded for this project. Since your project is now in Production status, no one is allowed to upload an allocation table EXCEPT a REDCap admin. <b>Please notify your REDCap admin</b> if you wish them to upload your allocation table for you OR if you wish them to move your project back to Development status so that you can upload it on your own."
random_72 = "The allocation dashboard cannot be displayed here because an allocation table has not yet been uploaded for this project"
random_73 = "Please go to the Setup page and upload a randomization allocation table"
random_74 = "<b>NOTE:</b> This section is currently locked and uneditable because the randomization setup process has already been completed. "
random_75 = "If you wish to modify the randomization setup below, you will need to click the Erase Randomization Model button below."
random_76 = "Because this project is in Production status, the randomization setup values below CANNOT be modified."
random_77 = "Because this project is already in Production status, no one is allowed to upload an allocation table (except REDCap admins)."
random_78 = "A) Use stratified randomization?"
random_79 = "The exact balance within the subgroups will be whatever proportion you prescribe, as dictated by the allocation table you create. Increased number of stratification variables or increased number of levels within strata leads to fewer subjects per stratum."
random_80 = "The headers in the table may be clicked to sort the table by that column either in ascending or descending order."
random_81 = "B) Randomize by group/site?"
random_82 = "Use an existing field to designate each group/site"
random_83 = "Use Data Access Groups to designate each group/site ("
random_84 = "groups currently exist)"
random_85 = "WARNING: You have not yet created any Data Access Groups. You cannot choose this option until some have been created. You may go create your groups, which requires certain user privileges) and then return here later to select this option again."
random_87 = "Please select a field as your randomization field"
random_88 = "- Do NOT modify the first row, although you may modify, add, or delete any other row in this file."
random_89 = "- You do not have to delete this 'notes' column when uploading your allocation table (it will be ignored)."
random_90 = "Values/labels for"
random_91 = "NOTES:"
random_92 = "If this is a multi-center/multi-site project (or something similar), you may want to stratify the randomization by each group/site. You can select an existing multiple choice field that represents the groups/sites, OR you can use Data Access Groups to stratify by group/site."
random_93 = "Save randomization model"
random_94 = "Erase randomization model"
random_95 = "Are you sure you wish to erase your randomization setup? This will also delete any allocation tables you have uploaded. (Note: This action may only be performed while still in Development status.)"
random_96 = "Your randomization setup and all allocations have now been erased."
random_97 = "Please choose one of the grouping options OR uncheck the Randomize By Group checkbox."
random_98 = "Please select a field from the drop-down in the Randomize By Group section."
random_99 = "The randomization model has been saved!"
random_100 = "The template allocation tables will contain all the raw coded values for the fields used in your randomization model. When downloading and opening any of the template allocation tables, you will find some helpful notes in the last column of each file. It will list each multiple choice option's label corresponding to each raw coded value for all the fields utilized (e.g., it will specify 0=Female and 1=Male for the field 'gender'). If you are using Data Access Groups to randomize by group, then it will additionally list each group name with its corresponding group ID number, which can be used in your allocation table in the same fashion as the raw coded values for your randomization field and strata. The last column with the notes will be ignored when you finally upload your custom allocation table in Step 3."
random_101 = "There are several different user privileges that can be utilized for randomization, all of which correspond to different roles during the randomization process and can be set on the User Rights page. These specific randomization privileges are named 'Setup', 'Dashboard', and 'Randomize'. If you have been given 'Setup' privileges, you will see the Setup tab on the Randomization page, which will allow you to define the randomization model and all its parameters, as well as upload your custom allocation table. If you have 'Dashboard' privileges, you will see the Allocation Dashboard tab on the Randomization page, in which you may view the overall allocation progress and assignments for subjects that have been randomized. If you have 'Randomize' privileges, you will be able to view the Randomize button on the data collection form that contains the randomization field, thus allowing you to perform the randomization on the subject/record you are viewing. If someone is given 'Randomize' privileges, they will be able to view and modify any existing data already collected for the randomization strata fields (if stratification is used) when they are performing the randomization, even if they do not specifically have form-level rights to view the form on which a strata field exists. Thus 'Randomize' rights trumps form-level user privileges in this way, but only for the randomization strata fields. All three user rights for randomization ideally belong to three different types of people in your project (although it is possible that you may have some users with overlapping roles). It makes most sense for a normal data entry person to have 'Randomize' privileges but not other randomization privileges. 'Setup' and 'Dashboard' privileges should be given only to the highest ranking people in your project, such as a PI or statistician/data analyst, most likely someone having past experience with randomization or data quality."
random_102 = "Restrictions"
random_103 = "The Setup phase for randomization is ONLY available while the project is in development status, and thus the entire setup process should be completed before the project is moved to production status. Once the project is in production, the Setup tab will become permanently locked and no settings can be modified, nor can any assignments be undone."
random_104 = "Example #3 (5x all possible combos)"
random_105 = "(Data Access Group)"
random_106 = "- Below is a list of all raw coded values and their corresponding option labels for each strata field and/or Data Access Groups."
random_107 = "Assign this record to a Data Access Group"
random_108 = "The current record will be saved as"
random_109 = "because"
random_110 = "was recently saved by another user and thus already exists. Even though the current page here may still be showing the other record name, please be advised that the record will be saved with this new record name instead of the other one currently seen on the page."
random_111 = "The allocation table you just uploaded was not accepted or saved because it matches the other allocation table that has already been previously uploaded. Please be aware that the allocation table used in Development status cannot be exactly the same as the allocation table used in Production status. Please modify your allocation table and upload it again."
random_112 = "ERROR: Duplicate allocation table!"
random_113 = "Once your project is in production status, the allocation tables will become locked and unmodifiable."
random_114 = "Be sure to include more assignments in your allocation table than you think you will need (to accommodate possible drop-out and drop-in of subjects)."
random_115 = "Record names (e.g., study ID) should NOT be included as a column in your allocation table, but only the fields listed in the example files from Step 2 above."
random_116 = "Reminders:"
random_117 = "Randomize Record"
random_118 = "NOTICE: It appears that"
random_119 = "records already contain data for the randomization field you have chosen. No data can exist for your randomization field prior to setting up your randomization model, so ALL those values will automatically be ERASED for those records (no other data will be erased except for that one field). Are you sure you want to do this?"
random_121 = "- Remember that this file is ONLY a template and should NOT be used as-is as your allocation table."
random_122 = "This record cannot be randomized right now because it appears that one or more fields that are utilized during randomization have somehow been deleted. The following fields must be re-added if randomization is to commence:"
random_123 = "<b>REMINDER:</b> This project is still in development status, so you should NOT be randomizing real subjects yet. You should only be randomizing real subjects after moving the project into in production status."
random_124 = "Upload more allocations? (Administrators only)"
random_125 = "<b>NOTE:</b> If necessary, a REDCap Administrator may upload more allocations while the project is in production. When they access this page, they will see a form below to upload another allocation table. The uploaded table will NOT replace the existing allocation table but instead will ONLY APPEND to it, thus adding more allocations."
random_126 = "(only REDCap admins may download the allocation table while in production)"
random_127 = "Allocated records"
random_128 = "could not be randomized because the data belonging to one or more strata fields violates a Data Quality rule (see table below). The only way to randomize this record is to either exclude the violation below by clicking the 'exclude' link next to the rule violated or by modifying the value(s) of your strata field(s) so that they no longer violate a Data Quality rule. If you still wish to randomize this record and choose to exclude all the rules below, you will need to close this pop-up and then click the Randomize button again in order to randomize this record. (NOTE: The data values for all strata fields have been saved, if they had not already been saved beforehand.)"
random_129 = "Note: It is recommended that only people with experience in randomization set up the Randomization module."
random_130 = "It is often necessary to ensure equal treatment among a number of factors. Stratified randomization is the solution to achieve balance within one or more subgroups, such as gender, race, diabetics/non-diabetics, etc. By choosing strata (multiple choice criteria fields), you may then be able to ensure balance within those subgroups."
random_131 = "(criteria fields used for stratification; may specify up to 14 multiple choice fields)"
random_132 = "NOTICE: Because the randomization field somehow has a value saved prior to this record being randomized, you will not be able to randomize this record, and this field will remain disabled/read-only."
random_133 = "The event has not been selected for this field! You must erase this randomization model and reset the event."
random_134 = "Because Randomization is enabled, the project cannot be moved back to Development status."
random_135 = "Single-select multiple choice fields for Open Allocation"
random_136 = "Text fields for Blinded Allocation (unvalidated fields only)"
random_137 = "Allocation will be <strong>open</strong> with <strong>randomization group</strong> assigned to this <strong>single-select</strong> choice field."
random_138 = "Allocation will be <strong>concealed (blinded)</strong> with <strong>randomization number</strong> assigned to this <strong>text</strong> field."
random_139 = "Randomization Field"
random_140 = "Your randomization field is"
random_141 = "a single-select field (for open allocation)"
random_142 = "a text field (for concealed allocation)"
random_143 = "Values in the redcap_randomization_number column are REQUIRED"
random_144 = "Values in the redcap_randomization_group column are optional"
random_145 = "Values in the redcap_randomization_number column are optional"
random_146 = "Values in the redcap_randomization_group column are REQUIRED and must match the values for your randomization field"
random_147 = "Empty values detected in column"
random_148 = "Using your randomization field name (\"%s\") instead of \"%s\" is supported."
random_149 = "Validation type not permitted for randomization target fields."
random_150 = "The randomization number assigned to the record. For randomization in a text field (blinded allocation), this is equivalent to piping the randomization field. For randomization in a categorical field (open allocation), this will be the randomization number associated with the randomization group allocation, if one has been uploaded (this is optional).<br> Use <code>:n</code> to refer to a specific randomization where a project has more than one (default=1)."
random_151 = "The <strong>server</strong> date and time at which a record was randomized. In a piping context, such as in a field label, survey invitation, or inside the @DEFAULT action tag, the format of the date and time will be displayed based on the current user's date/time display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD HH:MM:SS' format and would be more appropriate for conditional logic or calculated fields, simply append <code>:value</code>.<br>Use <code>:n</code> to refer to a specific randomization where a project has more than one (default=1)."
random_152 = "The <strong>UTC</strong> date and time at which a record was randomized. In a piping context, such as in a field label, survey invitation, or inside the @DEFAULT action tag, the format of the date and time will be displayed based on the current user's date/time display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD HH:MM:SS' format and would be more appropriate for conditional logic or calculated fields, simply append <code>:value</code>.<br>Use <code>:n</code> to refer to a specific randomization where a project has more than one (default=1)."
random_153 = "Add new randomization model"
random_154 = "Summary"
random_155 = "ERROR: Invalid randomization ID."
random_156 = "Target"
random_157 = "Stratification"
random_158 = "Total Allocations (Development)"
random_159 = "Total Allocations (Production)"
random_160 = "Allocation Type"
random_161 = "Open group allocation"
random_162 = "Concealed allocation"
random_163 = "Target field already selected for randomization in this project."
random_164 = "Target field and event already selected for randomization in this project."
random_165 = "Admin Only"
random_166 = "View Allocation Table"
random_167 = "Error: can't decode stratum"
random_168 = "Error: invalid stratum value"
random_169 = "Stratum"
random_170 = "Target Event"
random_171 = "Target Field"
random_172 = "Stratum Allocation Table"
random_173 = "Sequence"
random_174 = "Alternate"
random_175 = "Rows"
random_176 = "Remove Randomization"
random_177 = "Confirm removal of this randomized allocation. The record will be removed from the allocation table and the value will be removed from the randomization field for the record."
random_178 = "Manual Randomization"
random_179 = "Manually assign an existing record to this allocation table entry."
random_180 = "Make Sequence Unavailable"
random_181 = "Make this allocation unavailable to future randomizations."
random_182 = "Edit Target Field"
random_183 = "Specify a new value for the target field for this allocation table entry."
random_184 = "Edit Target Alternate"
random_185 = "Specify a new value for the alternate field for this allocation table entry."
random_186 = "Existing record to assign"
random_187 = "Enter new value"
random_188 = "Type \"CONFIRM\""
random_189 = "Specify Reason"
random_190 = "Enter the required information"
random_191 = "Current value"
random_192 = "Restore Availablity"
random_193 = "Restore availabilty of this allocation."
random_194 = " is not a valid category for target field "
random_195 = "Specified new value matches existing value"
random_196 = "Record does not exist"
random_197 = "Randomization ID"
random_198 = "Return alternate"
random_199 = "STEP 4: Automatic Triggering Option"
random_201 = "Trigger option"
random_202 = "Manual only, using Randomize button (default)"
random_203 = "Trigger logic, for users with Randomize permission only"
random_204 = "Trigger logic, for all users (including survey respondents)"
random_205 = "Trigger logic"
random_206 = "Tip: you may utilise the smart variables <code>[is-survey]</code> or <code>[is-form]</code> to provide different behaviour in survey view or on the data entry form."
random_207 = "Save"
random_208 = "Randomization settings"
random_209 = "This is the field where the \"Randomize\" button will appear on your data collection form. The type of field you choose (text field vs. single-select multiple choice field) dictates the  Allocation Type for this randomization model.<br><strong>For open randomization:</strong><ul class='mb-0'><li>Select a single-select (dropdown or radio) field. The randomized <strong>group allocation</strong>  will be saved to this field.</li></ul><strong>For concealed (blinded) randomization:</strong><ul class='mb-0'><li>Select a text field that <u>does not have field validation</u>. The assigned <strong>randomization number</strong> will be saved to this field.</li></ul>  <p>Note that the randomization number is available through the smart variable <code>[rand-number]</code>.</p>"
random_210 = "The table below displays all sequences (i.e., rows in the allocation table) for the specific combination of strata listed above. As a REDCap administrator, you may use any of the actions  in the Edit column to perform manual randomization, remove the randomization from an already-randomized record, remove a specific sequence/row from being used in randomization, or modify the strata values  and/or randomization/target value for a given sequence. Note: Performing these actions is typically rare and only done when things have not gone as planned in the project.  All actions performed below will be appropriately logged."
random_211 = "(randomization number)"
random_212 = "(randomization group)"
random_213 = "ERROR: No allocations exist!"
random_214 = "Randomization can be automated to occur in real time when a data entry form or survey page is saved when the logic expression entered below becomes true (i.e., without someone clicking the Randomize button).  If strata are being utilized in the randomization model, all required strata fields must have saved values before the automatic triggering can take place.  Using the options below, please provide 1) the trigger option, 2) the instrument (and event, if longitudinal) where the automatic randomization will occur, and 3) the trigger logic that must become  true in order to trigger the automatic randomization. Note: For multi-page surveys, the logic expression will be checked when each survey page is submitted; however, if you prefer the randomization to be triggered  when a multi-page survey is completed, consider appending <code>[form_complete]='2'</code> to the trigger logic, in which 'form' in the variable name should be substituted with the unique instrument name of the survey."
pub_001 = "Access denied!"
pub_002 = "Alias"
pub_003 = "All of these"
pub_004 = "and then click"
pub_005 = "Cancel All Changes"
pub_006 = "Decide later"
pub_007 = "download it here."
pub_008 = "Dr."
pub_009 = "copy"
pub_010 = "copy PI"
pub_011 = "Once downloaded, place the cron.php file in the following directory on your web server:"
pub_012 = "Your file called by the cron job should have the following contents:"
pub_013 = "Setting up a cron job for this service:"
pub_014 = "Email"
pub_015 = "Export to Excel/CSV"
pub_016 = "A file is missing that is required, but you can"
pub_017 = "Loading..."
pub_018 = "Manage Projects"
pub_019 = "(matched to projects)"
pub_021 = "missing data"
pub_022 = "missing names"
pub_023 = "First name"
pub_024 = "Last name"
pub_025 = "MI"
pub_026 = "???"
pub_027 = "None of these"
pub_028 = "Other"
pub_029 = "P.I."
pub_031 = "PIs that will be emailed by REDCap"
pub_032 = "Projects"
pub_033 = "Provide any"
pub_034 = "Additional institution names associated with this project to be used for publication searches. List one per line."
pub_035 = "Do you really want to cancel all publication matching settings you have made on this page?"
pub_036 = "Copy complete and selected items have been marked Ready. Please remember to save your data when done."
pub_037 = "Check which ToDo items you would like to copy into"
pub_038 = "Copy this data to other rows?"
pub_039 = "This module is not enabled. To enable it, execute the query below in your MySQL database:"
pub_040 = "Congratulations on your publication(s)! Please contact your REDCap administrator if you have any questions."
pub_041 = "EXAMPLE EMAIL TO P.I."
pub_042 = "REDCap will email Principal Investigators according to the settings you have specified in the Setup tab. Below is an example of the email a P.I. will receive when REDCap finds matching publications. Also, at the very bottom of this page is a table that lists the PIs to be emailed, which includes a button for each that navigate to the page that the PI will be taken to when they click the link in their email in order to perform the matching."
pub_043 = "You are receiving this message because we have identified one or more recently published manuscripts that may have been supported by the REDCap Data Management Platform. REDCap is supported by several NIH grants and other local infrastructure funding sources. Continued support for the program relies on impact assessment and evaluation, so we hope you will take 1-2 minutes to provide input on whether REDCap was used in supporting your new manuscript(s)."
pub_044 = "Please use the following link to match your publications:"
pub_045 = "This P.I. will NOT be emailed because the email limit has been reached for these publications. They will not receive emails until new matches are found."
pub_046 = "Publications to match:"
pub_047 = "Related services/programs:"
pub_048 = "(the email text may be modified on the Setup tab)"
pub_049 = "[REDCap] Action Requested - Confirm REDCap Supported Publication"
pub_050 = "You can only copy to rows with ToDo status, but no such rows exist!"
pub_051 = "All missing data must be entered before you can click Ready."
pub_052 = "In order to protect your data, copying is disabled for rows with Ready status."
pub_053 = "The following articles have been matched to projects tracked by REDCap. They are displayed in descending order by publication date."
pub_054 = "No publications have been matched to any REDCap projects yet."
pub_055 = "Publication Matching is currently DISABLED! This means that REDCap will NOT search for publications related to your principal investigators. This functionality can be enabled on the Setup tab."
pub_056 = "P.I. Emailing"
pub_057 = "Publication Matching emails are currently DISABLED! This means that REDCap will NOT email your principal investigators about publications that might be related to their projects. This functionality can be enabled on the Setup tab."
pub_058 = "Enabling PI emailing will allow REDCap to email project PIs when new matching publications are found. Use the 'P.I. Emails' tab to preview emails and view more information."
pub_059 = "Days between emails"
pub_060 = "Wait this many days before sending the PI another email about new matching publications."
pub_061 = "Email Limit"
pub_062 = "Only send a maximum of this many emails about a particular publication to a PI."
pub_063 = "Email Subject"
pub_064 = "The subject line in emails to the PI."
pub_065 = "Email Text"
pub_066 = "The text to display in emails to the PI."
pub_067 = "Enabling Publication Matching will allow REDCap to periodically search for publications related to the PIs of projects that you can specify in the 'ToDo List' tab."
pub_068 = "Use a search method below to retrieve project-specific Publication Matching settings"
pub_069 = "Allows you to select which ToDo rows to populate with this PI name, email, alias, and status data."
pub_070 = "PI view"
pub_071 = "A search of publication databases (e.g., PubMed) has discovered the following publications which contain your name in the author list. Please indicate whether these are your publications by selecting 'yes' or 'no' next to each one. If you select 'yes', then you will be prompted to indicate which projects are associated with the publication."
pub_072 = "Is this your publication?"
pub_073 = "Copy PI name, email, and alias to this row"
pub_074 = "Match Publications to Projects"
pub_075 = "Remaining publications to review:"
pub_076 = "Which projects are related to this publication?"
pub_077 = "pubs"
pub_078 = "Pending Pubs"
pub_079 = "In the table below are settings for customizing how the publication matching service works, such as modifying the institution name used when querying authors affiliated with your institution, as well as controlling frequency and content of emails sent to Principal Investigators. All the values listed below are required in order for this module to function correctly."
pub_080 = "Suggestions (click to copy):"
pub_081 = "To allow REDCap to obtain the best possible publication search results, please provide the Principal Investigator information requested in the To-Do list. Sometimes this PI info is missing, which is why it must be back-filled here manually. (Please note that by adding the PI information below, you are adding it to the project itself, after which it can be seen in the Modify Project Settings pop-up for the given project.) For your convenience, REDCap will group PIs by name and present them one group at a time. Use the dropdown below to select a different group (i.e. PI)."
pub_082 = "Exclude from use"
pub_083 = "Ready for use"
pub_084 = "Reload this page when complete."
pub_085 = "Save"
pub_086 = "Save All"
pub_087 = "Please don't close me yet - I'm still saving your data!"
pub_088 = "Save FAILED, retrying..."
pub_089 = "Saving..."
pub_090 = "Search by PI name"
pub_091 = "Want to copy from an existing PI? Start typing their name..."
pub_092 = "Type to search for PI name..."
pub_093 = "Start typing a PI name and then press ENTER to search."
pub_094 = "Search by project"
pub_095 = "Select a project to view its Publication Matching settings."
pub_096 = "Setup"
pub_097 = "Stats"
pub_098 = "SUBJECT:"
pub_099 = "ToDo"
pub_100 = "All done - nothing more To Do!"
pub_101 = "To-Do List"
pub_102 = "toggle all"
pub_103 = "Currently working on:"
pub_105 = "REDCap base URL"
pub_106 = "The REDCap URL you specified does not appear to be valid!"
pub_107 = "The list of PIs below represents those PIs that have been matched to publications and will subsequently be emailed so that they may perform the publication matching. The list may include PIs that have already been emailed and also those that will be emailed in the next batch. Once the PI has performed their matching of all their publications, they will no longer appear in the list below. To view the 'matching' page that the PI will see, click the 'PI view' button."
pub_108 = "FINISHED? Once you have finished selecting your publications above, you may close this tab/window in your web browser. THANKS SO MUCH for taking the time to complete this process!"
pub_109 = "NOTICE: Once this module is enabled, all matched publication ID numbers (e.g., PubMed IDs) will be sent along with your REDCap stats every week so that they may be aggregated in order to measure impact across the entire consortium. Only the publication ID numbers themselves will be sent."
pub_110 = "The base web address of your REDCap installation (e.g., https://redcap.vumc.org/, https://YOURSITE.edu/redcap/). This will be used to construct the URL when users navigate throughout REDCap as well as for contructing survey URLs included in email invitations."
pub_111 = "P.I.-Pub Matches"
pub_112 = "Project-Pub Matches"
pub_113 = "NOTE: Only projects that have purpose 'Research' that are in production status can be used in the Publication Matching module. Also, the REDCap project's creation time will be used as the lower date limit for the publications when REDCap searches for matches in online publication databases, so it assumes that the project is created prior to the publication being published."
pub_114 = "No P.I.'s to email yet"
ws_02 = "Fetching data for"
ws_03 = "Fetch data"
ws_08 = "Invalid source value!"
ws_13 = "The first step in setting up the Dynamic Data Pull (DDP) from an external source system is to map the fields in your project to fields from the source system. Once the fields have been mapped, REDCap will then know what data to import from the source system and where to store it in the REDCap project."
ws_14 = "Existing value"
ws_15 = "Lowest numerical value"
ws_16 = "Highest numerical value"
ws_17 = "Earliest value (based on timestamp)"
ws_18 = "Latest value (based on timestamp)"
ws_19 = "Setup / Mapping"
ws_20 = "Adjudicate Data"
ws_21 = "ERROR: User does not have access to"
ws_22 = "explain"
ws_23 = "You will not be able to view data or adjudicate data that originates from the external source system. Despite the fact that you have been given user privileges in this project to adjudicate data from the source system, it has been determined that you do not have (or no longer have) access to the source system itself. REDCap has determined this using a user access web service call to the source system, which noted that you do not have access. If you believe this to be in error, please contact your"
ws_24 = "Excluding a source value"
ws_25 = "If you click the 'exclude' link next to a source value when adjudicating data from the external source system, it will hide that source data value in the future when retrieving data for that field for the given record. Thus, excluding a value is a way of temporarily or permanently hiding a particular source value for whatever reason (e.g., incorrect or bad/malformatted data). Any excluded source value may be viewed again by clicking the 'View all' button next to 'Items not displayed' in the popup, and if you wish to un-exclude the value after exluding it, you may click the 'remove exclusion' link when viewing it."
ws_26 = "Set up Dynamic Data Pull (DDP) from"
ws_27 = "Adjudicate data from"
ws_28 = "Dynamic Data Pull (DDP) from External System"
ws_29 = "Set up mapping for Dynamic Data Pull (DDP)"
ws_30 = "DDP"
ws_31 = "When the Dynamic Data Pull (DDP) is enabled for a project, two distinct user privileges may be set for any given user for utilizing different aspects of the DDP. Users may be given privileges to perform the setup/mapping process and/or to adjudicate the data to import it from the source system into the REDCap project. If given Setup/Mapping privileges, they will see a new step on the Project Setup page to navigate to the Mapping page where they can begin mapping fields from the external source system to REDCap project fields, as well as defining other settings used when pulling data from the source system. If the user has Adjudicate Data privileges, it means that they will be able to view, adjudicate, and import data coming in from the source system, which can be seen on the Record Status Dashboard and also at the top of data entry forms."
ws_35 = "select all"
ws_36 = "Explain DDP rights"
ws_37 = "The Dynamic Data Pull (DDP) is a special feature for importing data into REDCap from an external source system. It provides an adjudication process whereby REDCap users can approve all incoming data from the source system before it is officially saved in their REDCap project."
ws_38 = "What is the DDP?"
ws_39 = "How the DDP works"
ws_40 = "The DDP has the ability to fetch data from the external source system both manually in real time and automatically at a regular interval. The DDP can only import external data for records that already exist in the REDCap project, in which it assumes that a record identifier (e.g. medical record number) is stored within each REDCap record so that the DDP can connect the REDCap record to a record from the source system. Once REDCap has a record identifier value for a given record, it will then go and immediately retrieve the data from the source system in real time, and later it will also check the source system at regular intervals for any additional data."
ws_41 = "VIDEO: Dynamic Data Pull (DDP)"
ws_42 = "Enabling the feature"
ws_43 = "After being granted access to the DDP, the user will then see the DDP step on the Project Setup page where they can navigate to the DDP mapping/setup page, which allows the user to map fields already created in their REDCap project to fields from the external source system. This mapping allows REDCap to know how where to put the data when importing it from the external system."
ws_44 = "The field mapping process"
ws_45 = "A user on the mapping/setup page can choose any available fields from the external source system to map to one of their REDCap project fields. (Note: This assumes that the user has already created their data collection instruments and fields in their project.) There are two types of fields that may be mapped: 1) one-time data fields, and 2) temporal data fields. One-time data fields are those where data will only be stored one time in the source system, such as demography data. Conversely, temporal data fields are those where data may be collected many times over a period of time (e.g., labs, vitals, any kind of longitudinal data). When mapping temporal fields, you must also specify a REDCap date/datetime field that will be used for determining the window of time in which it should look when fetching data from the source system. It will determine the window of time in conjunction with the day offset value defined on the mapping page. For example, if the value of the mapped REDCap date/datetime field is 2001-11-29 and the day offset is 1 day, it will query the source system and return only data saved for the field from 2001-11-28 until 2001-11-30. Any source data outside of that range will be ignored during the adjudication process. It is important to note that the source data for a temporal field will NOT be fetched from the external source system UNLESS its associated REDCap date/datetime field has a value. Once a value is entered for the associated date/datetime field, source data will then be fetched for that temporal field."
ws_46 = "Preview fields (optional)"
ws_47 = "On the mapping/setup page, you may choose up to 5 source fields to be used as 'preview fields'. Preview fields are optional and are typically used to confirm that the record identifier (e.g. medical record number) that was entered is correct by displaying other contextual data from the source system. For example, if you have 'last name' and 'date of birth' as source fields, you may choose them to be preview fields in your project, and thus when a value is entered in REDCap as the record identifier, if will then fetch and display the last name and date of birth of the person to validate their identity. If preview fields are not utilized, it is possible that incorrect source data is imported. Thus preview fields are not required but are recommended for data quality purposes."
ws_48 = "The adjudication process"
ws_49 = "After the mapping process has been completed, data from the external source system will not be imported automatically into the REDCap project, but instead it requires that a person view and adjudicate each data item from the source system before being imported into the project."
ws_50 = "To utilize the Dynamic Data Pull (DDP) for a REDCap project, please contact your REDCap administrator regarding the process entailed and procedures required in order to have the DDP enabled for the project and also for an individual to be given authorization to use the DDP."
ws_51 = "Dynamic Data Pull (DDP) from"
ws_52 = "External Source System"
ws_54 = "The mapping process consists of two steps: 1) choosing source fields from the external source system whose data you wish to import into your REDCap project, and 2) map those source fields to REDCap fields in your project. Once the source fields are mapped, REDCap will then be able to import source data as soon as a record is given a value for its Source Identifier Field (e.g., medical record number). Data from the source system will be fetched immediately in real-time on a data entry form or on the Record Status Dashboard, and later it will also check the source system at regular intervals for any additional data."
ws_55 = "deselect all"
ws_56 = "After a REDCap administrator has enabled the DDP for your REDCap project, the adminstrator can then give any user in the project access to the DDP (assuming the user has been authorized to access source system data), in which the user can be given user privileges to perform the mapping/setup process and/or to adjudicate/import data from the source system. Only an administrator can grant individuals access to begin utilizing the DDP."
ws_57 = "After a REDCap administrator has enabled the DDP for your REDCap project, someone with access to the User Rights page may then give you and any user in the project user privileges to access the DDP, in which the user can be given user privileges to perform the mapping/setup process and/or to adjudicate/import data from the source system."
ws_58 = "See the User Rights page to enable privileges for a given user."
ws_59 = "The adjudication screen can be accessed from either of two places: 1) on the Record Status Dashboard, and 2) on the data entry form when viewing a record. The Record Status Dashboard will display a new table column with a count of any new items from the source system for each record displayed. Clicking on the count will open the adjudication screen for that record. Alternatively, when viewing a record on a data entry form, the count of new items from the source system will be displayed at the top of the page in red box, in which clicking the View button will open the adjudication screen. On the adjudication screen, it will display all data from the source system that has not been adjudicated yet."
ws_60 = "If only a single source value has been returned for a REDCap field, it will automatically pre-select that item for you. If the field is a temporal data field that has multiple values returned, it will automatically pre-select the data value *ONLY IF* that value is the only value returned that occurs on the exact same calendar date as the REDCap date/datetime value (that is, unless a pre-selection option - e.g., Minimum value, Latest value - has already been set for that field on the mapping page)."
ws_61 = "The user must view all the items on the adjudication screen and select the radio button next to each to denote the source value they wish to import. Once all values have been selected, clicking the Save button will import the value into the project. If some items were left and were not adjudicated, the user can return at any time to adjudicate them in the future."
ws_62 = "The DDP can only be enabled by a REDCap Administrator, so you should contact them if you wish to utilize the DDP for this project."
ws_63 = "Dynamic Data Pull (DDP)"
ws_64 = "Before the DDP can be used by REDCap users, it must first be set up and enabled on this page. The DDP operates by communicating with two web services (with an optional third web service) via HTTP/HTTPS, by which REDCap will make requests to those web services, and the services will respond back with an appropriate response for the specific action made by REDCap. The technical specifications of these web services are described in the PDF that is available for download below. Also below is a link to a page that describes how to use the DDP once it has been set up and enabled, in which the link to the page can sent to end-users who are interested in using the DDP."
ws_65 = "Technical specifications for DDP web services (PDF)"
ws_66 = "Enable Dynamic Data Pull (DDP)"
ws_67 = "Custom name for the external source system"
ws_68 = "This will be the name of the source system as it is displayed for the user. If left blank, it will simply say 'source system' in its place."
ws_69 = "Custom text specific to your institution to display to users"
ws_70 = "This text will be displayed at the top of DDP's informational popup window. Your text should describe your institution's process and/or procedures that are required in order for DDP to be enabled for a project or user. It may include a link to a survey or request form for collecting requests from users who wish to use DDP."
ws_71 = "If left blank, then it will display the following text to the user:"
ws_72 = "URL for Metadata Web Service"
ws_73 = "URL for Data Web Service"
ws_74 = "URL for User Access Web Service (optional)"
ws_75 = "Display information about DDP on Project Setup page in a project?"
ws_76 = "Yes, display information about DDP"
ws_77 = "No, hide all information about DDP"
ws_78 = "If 'No' is selected, then DDP will not be advertised to users on the Project Setup page, and all information about DDP will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make DDP known to only a limited number of users without advertising it to all users."
ws_79 = "A valid web address (URL) that is reachable by the REDCap web server."
ws_80 = "Allow normal users to grant DDP user privileges to other users in a project?"
ws_81 = "Yes, normal users can grant DDP rights to other users"
ws_82 = "No, only Administrators can grant DDP rights to users"
ws_83 = "Setting it to 'No' will allow only Administrators to grant users DDP privileges on the User Rights page in a project. Typically, 'Yes' will be selected if you are utilizing the User Access Web Service, which will automatically restrict users from accessing data from the external source system from within REDCap if the web service notes that they should not have access."
ws_84 = "Time interval that REDCap will check the source system for new data for individual records"
ws_85 = "Time of inactivity after which REDCap will stop checking for new data from the source system"
ws_86 = "If a DDP-enabled project has not had any logged activity in this amount of time, then no records in the project will be automatically checked in the source system at the regular interval above. Also, if a specific record within an active DDP-enabled project has not had its data modified in this amount of time, then it will not be automatically checked in the source system at the regular interval above."
ws_87 = "(for projects and individual records)"
ws_88 = "(min: 1, max: 999)"
ws_89 = "(min: 1, max: 100)"
ws_90 = "Records in DDP-enabled projects will be checked for new data from the external source system at this regular interval of time, in which the exact time of the data fetch is determined from the time of the last data fetch for a given record. This automatic data fetching will be performed by a cron job running in the background."
ws_91 = "Every"
ws_92 = "REDCap will make requests to this web address when users are mapping fields from the source system. This web service provides a list of all fields (and their attributes) that are available from the source system."
ws_93 = "REDCap will make requests to this web address when pulling data from the source system for an individual record. When REDCap calls this web service, in which REDCap will provide details on the data requested, the web service will return the data available for the record in the specified format prescribed in the technical documentation PDF above."
ws_94 = "REDCap will make requests to this web address when validating if the current user has proper authorization for adjudicating data and/or accessing data from the source system. This web service will only be called once per project per session. If the user is determined by the service not to have access, then they will be given an error message if they attempt to adjudicate any data from the source system. Note: This service is only optional for extra security."
ws_95 = "Once DDP is enabled for the system, it can then be enabled for a given project by an Administrator on the project's Project Setup page (in the 'optional modules and customizations' section)."
ws_96 = "NOTE: If either the 'metadata web service' or 'data web service' are not defined below or if the services are not set up correctly, then the DDP will not function. It is recommended that both of those mandatory services be created and set up prior to enabling DDP."
ws_97 = "* See the technical documentation PDF for details on this web service"
ws_98 = "Informational page on how to use DDP (for providing to users)"
ws_99 = "NOTE: If the 'User Access Web Service' is not defined above, then it is HIGHLY recommended that this option be set to 'No' for security purposes if the data from the source system is considered sensitive or confidential in nature."
ws_112 = "Map the source field again"
ws_115 = "Remove source mapping"
ws_116 = "Source Identifier Field"
ws_117 = "SETTINGS"
ws_118 = "Preview Fields (optional):"
ws_119 = "Source system fields can be selected that will provide a quick preview of data from the source system when a user initially enters the value of the source ID field."
ws_121 = "Select preview fields from"
ws_122 = "(up to 5)"
ws_124 = "Default day offset (for temporal fields):"
ws_125 = "When pulling temporal data (i.e. fields with an associated timestamp) from the source system, the day offset will be used in conjunction with the value of a mapped REDCap date/time field to create a window of time for searching for data in the source system. Only data within that window of time will be displayed during the adjudication process. This helps to provide a buffer of time in the instance that the date/time value from REDCap and/or the timestamp from the source system lack some amount of precision."
ws_126 = "Default day offset:"
ws_130 = "MAP SOURCE FIELDS TO REDCAP FIELDS"
ws_134 = "Find more source fields to map"
ws_135 = "does not contain a value for the REDCap field"
ws_136 = "That field needs to have a value before REDCap can search for its data in the source system!"
ws_137 = "ERROR: An error occurred with the data web service."
ws_138 = "It appears that the response returned from the web service was not in a proper JSON-encoded format. The returned content is listed below:"
ws_139 = "The web service could not be reached at the URL"
ws_140 = "No data returned for this record!"
ws_141 = "Time of last data fetch:"
ws_142 = "Display all items"
ws_143 = "Display only this form's items"
ws_144 = "Hide"
ws_145 = "hidden items (existing values)"
ws_146 = "items (existing values)"
ws_147 = "exclusions"
ws_148 = "REDCap Event"
ws_149 = "REDCap Field"
ws_150 = "REDCap Date/Time"
ws_151 = "Source Date/Time"
ws_152 = "Current Value"
ws_153 = "Source Value"
ws_154 = "Import?"
ws_155 = "(all forms/events)"
ws_156 = "(all forms)"
ws_157 = "Successfully imported!"
ws_158 = "Data was successfully imported from the source system and saved for"
ws_166 = "Displayed below is the data fetched from the external source system. It will display all the mapped REDCap fields that have source data returned. To import the source data values into REDCap, select the source value by clicking the radio button for the desired value in the row. Some fields may have multiple values returned, so you must choose the best or most correct value. Once you made all your selections, press the Save button below to save the source values into REDCap."
ws_168 = "Fetching data..."
ws_169 = "Fetching preview data from"
ws_170 = "REDCap is currently fetching preview data for this record."
ws_171 = "Once it has completed, review the preview data below to ensure that the values match the record you wish to pull from the external source system. If they are correct, click the Save button to save this value and automatically begin fetching data from the source system. If the data displayed below is not correct for the value you entered, click Cancel to change the value."
ws_172 = "Save record and fetch data"
ws_173 = "Saving and fetching..."
ws_174 = "No new items from source system"
ws_175 = "new items from source system"
ws_176 = "just now"
ws_177 = "less than a minute ago"
ws_178 = "{0} minute ago"
ws_179 = "{0} minutes ago"
ws_180 = "{0} hour ago"
ws_181 = "{0} hours ago"
ws_182 = "{0} day ago"
ws_183 = "{0} days ago"
ws_184 = "[no value]"
ws_185 = "Are the values below correct for"
ws_186 = "DDP demo files - mock web service for testing and evaluation (ZIP)"
ws_189 = "days from date AND time"
ws_190 = "using"
ws_191 = "min {{min_days}} days ({{min_minutes}} minutes), max: {{max_days}} days"
ws_192 = "min:"
ws_193 = "Now that you have entered a value for the Source Identifier Field, click the Save button below to save the value and automatically begin fetching data from the source system."
ws_194 = "Nearest value (based on timestamp)"
ws_197 = "Records with data values adjudicated by users via DDP"
ws_198 = "Data values pulled from source system via DDP"
ws_199 = "Data values adjudicated by users via DDP"
ws_200 = "Projects with data values adjudicated by users via DDP"
ws_203 = ", or perhaps the user has not been added to the FHIR user allowlist or has never launched REDCap from inside of"
ws_204 = "You will not be able to view data or adjudicate data that originates from the EHR system. Despite the fact that you have been given user privileges in this project to adjudicate data from the EHR, it has been determined that either 1) you have not been added to the FHIR user allowlist, or 2) you have never launched REDCap from inside of the EHR system. Once one of those two has been done, you should be able to adjudicate CDP data from the EHR. If you believe this to be in error, please contact your"
ws_205 = "View DDP adjudication instructions"
ws_207 = "REDCap can communicate with any EHR (electronic health record system) that has implemented 'SMART on FHIR' web services that allow for interoperability and data extraction from the EHR. In this way, REDCap can be embedded inside and launched within an EHR user interface (e.g., Cerner, Epic Hyperspace), which allows REDCap users to easily add patients to their projects and/or to access patient data inside a REDCap project. In addition to launching REDCap inside the EHR, REDCap can also extract data from the EHR to import clinical data into a REDCap project by using a feature called 'Clinical Data Pull' (CDP). CDP provides an adjudication process whereby REDCap users can approve all incoming data from the EHR before the data is officially saved in their REDCap project."
ws_210 = "Clinical Data Pull from"
ws_211 = "What is 'Clinical Data Pull' (CDP)?"
ws_212 = "Clinical Data Pull is a special feature for importing data into REDCap from an EHR (electronic health record system), such as Epic, Cerner, etc. It provides an adjudication process whereby REDCap users can approve all incoming data from the EHR before it is officially saved in their REDCap project. Clinical Data Pull can only be enabled by a REDCap Administrator, so you should contact them if you wish to utilize Clinical Data Pull for this project."
ws_213 = "Set up Clinical Data Pull from"
ws_214 = "Custom name for the EHR system"
ws_216 = "Once Clinical Data Pull is enabled for the system, it can then be enabled for a given project by an Administrator on the project's Project Setup page (in the 'optional modules and customizations' section). Also, users that launch REDCap from inside the EHR system will be able to access their Clinical Data Pull projects from the EHR interface."
ws_217 = "EHR's patient identifier string for medical record numbers (optional)"
ws_218 = "Most EHRs will not use medical record number as the back-end naming convention of patients, so in that case, you must provide a system identifier that REDCap will use to retrieve each patient's MRN from a FHIR data bundle."
ws_219 = "Client ID and Client Secret for the FHIR app/client created for REDCap in the EHR"
ws_220 = "These are essentially a username and API key that REDCap will use to communicate with your EHR using the SMART on FHIR services. These client values will likely need to be generated for you by your EHR's technical team."
ws_221 = "Client ID:"
ws_222 = "Client Secret:"
ws_223 = "Show secret"
ws_224 = "FHIR web service URLs"
ws_225 = "The base URL endpoint should have been provided to you by your EHR's technical team."
ws_226 = "FHIR Token URL:"
ws_227 = "FHIR Authorize URL:"
ws_228 = "FHIR Base URL:"
ws_229 = "The token and authorize URLs can often be found using the base URL you have provided above and then by clicking the 'Auto-find' button below. If the Auto-find method is not successful, then the Token URL and Authorize URL below will need to be provided to you by your EHR's technical team."
ws_230 = "NOTE: This is *not* a FHIR web service but an independent web service created by your institution for the purpose of validating if REDCap users have access to your EHR system."
ws_231 = "Auto-find token URL and authorize URL"
ws_232 = "(Make sure that the Client Secret is the secret value itself and not the stored hashed value of the secret.)"
ws_233 = "Other settings"
ws_234 = "EHR-specific and FHIR-specific settings"
ws_235 = "This will be the name of the EHR system as it is displayed for the user. If left blank, it will simply say 'EHR' in its place."
ws_236 = "Setup instructions and technical specifications (ZIP)"
ws_237 = "Redirect URL (to add to your FHIR app/client for REDCap)"
ws_238 = "Copy and paste the Redirect URL and provide it to your EHR technical team to be added to your FHIR app/client."
ws_239 = "Redirect URL (read-only):"
ws_240 = "Custom"
ws_243 = "NOTE: Before users can utilize the Data Mart feature, <b>a REDCap administrator must go into their user account on the Browse Users page and enable it on their account</b>. Additionally, a user will not be able to utilize this feature until the user has first logged into REDCap from inside the EHR user interface, which is required before using any Clinical Data Pull functionality."
ws_245 = "WARNING: Multiple values were found for this field; however, since this is a neither a temporal field nor a checkbox field, it can only take one data value. So the other data values must be disregarded."
ws_246 = "The errors listed below ocurred when pulling data from the EHR. You might want to talk to your local EHR contact about this issue to resolve it."
ws_247 = "RECOMMENDATION: This field should probably be converted to a Checkbox field so that all its data values can be imported for it."
ws_248 = "How 'Clinical Data Pull' works"
ws_249 = "Clinical Data Pull has the ability to fetch data from the EHR system both manually in real time and automatically at a regular interval. From the EHR interface, Clinical Data Pull can create new records in a CDP-enabled REDCap project. Additionally, if a user knows the patient identifier (e.g. medical record number), then they could optionally enter the MRN for a record in a CDP-enabled REDCap project, after which it will then go and immediately retrieve the patient data from the EHR in real time."
ws_251 = "DDP Custom"
ws_252 = "Convert source system timestamps from GMT to local server time?"
ws_253 = "Yes, convert timestamps to local time from GMT"
ws_254 = "No, leave timestamps as they are"
ws_255 = "If the source system has temporal data with dates/datetimes of service that are being output in Greenwich Mean Time (GMT), setting this to 'Yes' will automatically correct all associated timestamps so that they appear in local time in the adjudication popup."
ws_256 = "Note: You should only set this to 'Yes' if you can absolutely verify that the timestamps associated with incoming data values are in GMT time instead of in local time. Also, if this is turned on after some data is pulled into a project from the external system, it will not retroactively fix any of their timestamps but will instead only have an effect on new data imported after the fact."
ws_257 = "Learn more about this module: "
ws_258 = "There are a few demography fields (race, sex, and ethnicity) that, if used in a project, are required to have their choices coded a very specific way. Listed below are the codings that should be used for these fields."
ws_260 = "NOTE: The URL will not end with /metadata but typically similar to /FHIR/DSTU2/."
ws_262 = "Clinical Data Interoperability Services"
ws_265 = "Clinical Data Pull"
ws_266 = "Informational page on how to use Clinical Data Pull (for providing to users)"
ws_267 = "Services To Enable:"
ws_268 = "To utilize the Clinical Data Pull (CDP) for a REDCap project, please contact your REDCap administrator regarding the process entailed and procedures required in order to have the CDP enabled for the project and also for an individual to be given authorization to use the CDP."
ws_269 = "This text will be displayed at the top of CDP's informational popup window. Your text should describe your institution's process and/or procedures that are required in order for CDP to be enabled for a project or user. It may include a link to a survey or request form for collecting requests from users who wish to use CDP."
ws_270 = "Display information about CDP on Project Setup page in a project?"
ws_271 = "Yes, display information about CDP"
ws_272 = "No, hide all information about CDP"
ws_273 = "If 'No' is selected, then CDP will not be advertised to users on the Project Setup page, and all information about CDP will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make CDP known to only a limited number of users without advertising it to all users."
ws_274 = "A valid web address (URL) that is reachable by the REDCap web server."
ws_275 = "Allow normal users to grant CDP user privileges to other users in a project?"
ws_276 = "Yes, normal users can grant CDP rights to other users"
ws_277 = "No, only Administrators can grant CDP rights to users"
ws_278 = "Setting it to 'No' will allow only Administrators to grant users CDP privileges on the User Rights page in a project. Typically, 'Yes' will be selected if you are utilizing the User Access Web Service, which will automatically restrict users from accessing data from the external source system from within REDCap if the web service notes that they should not have access."
ws_279 = "Records in CDP-enabled projects will be checked for new data from the external source system at this regular interval of time, in which the exact time of the data fetch is determined from the time of the last data fetch for a given record. This automatic data fetching will be performed by a cron job running in the background."
ws_280 = "If a CDP-enabled project has not had any logged activity in this amount of time, then no records in the project will be automatically checked in the source system at the regular interval above. Also, if a specific record within an active CDP-enabled project has not had its data modified in this amount of time, then it will not be automatically checked in the source system at the regular interval above."
ws_281 = "After a REDCap administrator has enabled the CDP for your REDCap project, the adminstrator can then give any user in the project access to the CDP (assuming the user has been authorized to access source system data), in which the user can be given user privileges to perform the mapping/setup process and/or to adjudicate/import data from the source system. Only an administrator can grant individuals access to begin utilizing the CDP."
ws_282 = "After a REDCap administrator has enabled the CDP for your REDCap project, someone with access to the User Rights page may then give you and any user in the project user privileges to access the CDP, in which the user can be given user privileges to perform the mapping/setup process and/or to adjudicate/import data from the source system."
ws_283 = "After being granted access to the CDP, the user will then see the CDP step on the Project Setup page where they can navigate to the CDP mapping/setup page, which allows the user to map fields already created in their REDCap project to fields from the external source system. This mapping allows REDCap to know how where to put the data when importing it from the external system."
ws_284 = "VIDEO: Clinical Data Pull (CDP)"
ws_285 = "Clinical Data Pull (CDP) - NOTE: This video references the 'Dynamic Data Pull' (DDP), which was renamed to CDP. While somewhat outdated, 90% of this video is still representative of CDP's current functionality."
ws_286 = "The first step in setting up the Clinical Data Pull (CDP) is to map the fields in your project to fields from the EHR. Once the fields have been mapped, REDCap will then know what data to import from the EHR and where to store it in the REDCap project."
ws_287 = "Set up mapping for Clinical Data Pull (CDP)"
ws_288 = "The Clinical Data Pull (CDP) is a feature for importing data into REDCap from an EHR. It provides an adjudication process whereby REDCap users can approve all incoming data from the source system before it is officially saved in their REDCap project."
ws_289 = "The first step in setting up the Clinical Data Pull (CDP) is to map the fields in your project to fields from the EHR. Once the fields have been mapped, REDCap will then know what data to import from the EHR and where to store it in the REDCap project."
ws_290 = "Explain Clinical Data Pull rights"
ws_291 = "When the Clinical Data Pull (CDP) is enabled for a project, two distinct user privileges may be set for any given user for utilizing different aspects of the CDP. Users may be given privileges to perform the setup/mapping process and/or to adjudicate the data to import it from the EHR into the REDCap project. If given Setup/Mapping privileges, they will see a new step on the Project Setup page to navigate to the Mapping page where they can begin mapping fields from the EHR to REDCap project fields, as well as defining other settings used when pulling data from the EHR. If the user has Adjudicate Data privileges, it means that they will be able to view, adjudicate, and import data coming in from the EHR, which can be seen on the Record Status Dashboard and also at the top of data entry forms."
ws_292 = "CDP"
ws_293 = "Update Record(s)"
ws_294 = "Key differences between Clinical Data Pull (CDP) and Clinical Data Mart (CDM)"
ws_295 = "Once the Clinical Data Interoperability Services have been enabled for the system via the setup below, the Clinical Data Mart feature can be enabled so that privileged users may create projects with pre-defined instruments to allow for the fetching of clinial data for many medical records at once from the EHR. When enabled, this will appear as an option on the Create New Project page and then afterward as a page on the project's left-hand menu."
ws_296 = "Overview of Clinical Data Pull and Clinical Data Mart"
ws_297 = "Another feature is called 'Clinical Data Mart' and works differently than CDP in that Data Mart can pull patient information in bulk while CDP pulls patient information from the EHR just one patient at a time. To learn their differences and strengths, see the sections below for documentation."
ws_299 = "Allow the patient's email address to be imported from the EHR?"
ws_300 = "Yes, display 'email address' option in EHR source field list"
ws_301 = "No, do not display 'email address' option in EHR source field list"
ws_303 = "Records with data values adjudicated by users via CDP"
ws_305 = "Data values adjudicated by users via CDP"
ws_306 = "Projects with data values adjudicated by users via CDP"
ws_307 = "Records with data values imported via Data Mart"
ws_308 = "Projects with data values imported via Data Mart"
ws_311 = "Authorization type for obtaining FHIR access tokens"
ws_315 = "By default, REDCap users can establish a REDCap connection to the EHR using an 'EHR Launch' via the embedded REDCap page inside the EHR interface. Additionally, other options can be enabled to allow REDCap users to log in to the EHR from inside REDCap to establish connection to the EHR. Once the connection has been established to the EHR, users may begin to import clinical data into REDCap."
ws_316 = "Only use EHR launch for peforming authorization and fetching FHIR tokens (not common)"
ws_317 = "Before 'Clinical Data Interoperability Services' can be used by REDCap users, it must first be set up and enabled on this page. To get started, download the ZIP file linked below, and follow the instructions contained therein. There may be instructions for your particular EHR, but if not, then you may use the 'Instructions - General' file. After you have followed the setup procedures, the REDCap user may begin using the Clinical Data Mart and Clinical Data Pull in REDCap. While the Data Mart can only be used on the REDCap side, CDP can optionally be used either inside the EHR user interface or from the REDCap side (without being inside the EHR)."
ws_319 = "Online status check"
ws_320 = "You are being redirected to the EHR login page..."
ws_321 = "Allow EHR user-level login from inside REDCap using Standard Authorization Flow (recommended for Epic & Cerner)"
ws_322 = "Allow system-level connection to EHR using Client Credentials Authorization flow"
ws_323 = "The Client Credentials Authorization flow uses system-level access credentials to interface with the EHR when peforming authorization and fetching FHIR tokens. However, the Standard Authorization Flow requires a user-level EHR login to establish connection to the EHR. If using Epic or Cerner, the Standard Authorization Flow is recommended."
ws_324 = "Find patient identifier string"
ws_325 = "Helper for finding the Patient Identifier String"
ws_326 = "As a quick way to determine the specific Patient Identifier String for medical record numbers in your EHR system, you can enter the Social Security Number (SSN) of *any* patient in the EHR. (NOTE: The SSN entered will not be logged or saved anywhere.) It can be the SSN of literally any patient in the system, and it may be entered with or without dashes. If the Patient Identifier String cannot be determined here, you will instead need to obtain it from your local EHR or Health IT folks."
ws_327 = "Lookup"
ws_328 = "The patient identifier strings listed below were found in your EHR system. Displayed first in bold is the patient identifier (e.g., MRN) then followed by a colon and the patient identifier string for that identifier. Choose the one identifier that corresponds to the MRN (medical record number) of your EHR system, and then copy/paste that identifier string into the EHR Patient Identifier String text box on this page. Then save the page."
ws_329 = "REQUIREMENTS: Please note that in order to use this feature, the Client ID, Client Secret, and FHIR Base URL must already be entered and saved on this page. Additionally, you (the current user) must have proper privileges in the EHR in order to pull patient information."
ws_330 = "(excludes flushed DDP data in Analysis/Cleanup projects)"
ws_332 = "Data values imported via Data Mart"
ws_333 = "New items from {0}"
ws_334 = "Mappable FHIR data"
ws_335 = "Resources"
ws_336 = "Request additional mappings (survey)"
ws_337 = "Setup custom mappings"
ws_338 = "Allow individual projects to decide"
ws_339 = "For privacy reasons, you might wish to exclude the 'email address' field so that REDCap users cannot import a patient's email address from the EHR. If 'No' is selected, the email option will not appear in the EHR source field list for any project, preventing the import of email addresses from the EHR across the entire system. Selecting 'Yes' will make the email option visible and available in the EHR source field list for all projects across all CDIS services (Clinical Data Pull, Clinical Data Mart) without the need for additional enabling at the project level. Choosing 'Allow individual projects to decide' gives each project the autonomy to determine whether the email option will be displayed in their EHR source field list. This setting respects the decision made at the project level under the 'Edit project settings' page."
ws_340 = "DocumentReference - Clinical Notes"
ws_341 = "A DocumentReference resource in FHIR is used to index clinical notes and other documents, making them available to healthcare systems. In REDCap, the DocumentReference resource is utilized specifically to extract clinical notes from the FHIR system. A document is a sequence of bytes that is identifiable, establishes its own context (e.g., subject, author, etc.), and has defined update management. The DocumentReference resource can be used with any document format that has a recognized MIME type and conforms to this definition."
ws_342 = "To integrate clinical notes efficiently into CDP projects, follow the guidelines below:"
ws_343 = "Field Configuration: Utilize the \"Notes Box\" as the receiving field to handle the extensive text typical of clinical notes."
ws_344 = "Enhanced Formatting: Implement the \"@RICHTEXT\" action tag to activate rich text capabilities, allowing HTML formatting to preserve the original presentation of the notes."
ws_345 = "Optimal Alignment: Set the alignment to \"Left / Horizontal (LH)\" to facilitate consistent and professional document appearance."
ws_346 = "Please note that CDP projects will store clinical notes only if they are in HTML format, even though the FHIR system might offer them in different formats. For those needing to work with clinical notes in any format, we suggest using Clinical Data Mart (CDM) projects. CDM projects accept various data formats, ensuring you have access to all clinical notes regardless of their format."
cc_cdp_auto_adjudication_title = "Clinical Data Pull \"Instant Adjudication\" option"
cc_cdp_auto_adjudication_description = "This option allows users to enable the Instant Adjudication feature for all CDP-enabled projects. Once enabled here for the whole system, this setting can be enabled on the CDP project's field mapping page, after which it will allow users to bypass the normal data adjudication process and will let them import and save all data into the project that has already been cached from the EHR system. This can save a great deal of time when importing lots of patient records. After Instant Adjudication is enabled in a CDP project, users with CDP-adjudication privileges will see the button to initiate this process on the Record Status Dashboard. After the button is clicked, it will begin adjudicating the EHR data for all records in real time."
cc_cdp_auto_adjudication_label = "Enable Instant Adjudication for all CDP projects?"
cron_02 = "Dear REDCap user,"
cron_03 = "This email is to inform you that your REDCap account with username"
cron_04 = "has expired. This means that your account is now suspended, and thus you will no longer be able to log in to REDCap at"
cron_06 = "will expire on"
cron_08 = "Reminder to visit the User Access Dashboard"
cron_09 = "has been automatically suspended due to the fact that you have not logged into REDCap in the past"
cron_10 = "days. This means that you will no longer be able to log in to REDCap at"
cron_11 = "You may reply to this email if you would like to inquire about this matter. Thank you!"
cron_12 = "This email is your monthly reminder to visit your User Access Dashboard in REDCap. The User Access Dashboard is a reporting tool designed to assist you in the management of users that have been granted access to your REDCap projects. You have received this email because you have rights to the User Rights application for at least one REDCap project. It is recommended that you regularly visit the User Access Dashboard to ensure that all users in your projects still require access. If they do not, the User Access Dashboard makes it easy to delete users from your projects or to quickly expire their access. This is only a reminder. Thank you!"
cron_13 = "This email is to inform you that the REDCap account with username"
cron_15 = ", who is CC'd on this email so that they are also aware. At the time of expiration, the user's account will be suspended, after which the user will no longer be able to log in to REDCap at"
cron_16 = "'s account will expire in"
cron_17 = "has expired."
cron_18 = ", who is CC'd on this email so that they are also aware. The user's account is now suspended, so they will no longer be able to log in to REDCap at"
cron_19 = "'s account has expired"
cron_20 = "has been automatically suspended due to the fact that the user has not logged into REDCap in the past"
cron_21 = "Visit the REDCap User Access Dashboard"
cron_22 = "'s account has been suspended due to inactivity"
cron_24 = "At the time of expiration, your account will be suspended, after which you will no longer be able to log in to REDCap at"
cron_25 = "There are"
cron_26 = "To view your message(s),"
cron_27 = "new messages"
cron_29 = "unread messages waiting for you, REDCap user"
cron_30 = "log in to REDCap"
cron_31 = "new message in conversation"
cron_32 = "new messages in conversation"
cron_33 = "new message"
cron_34 = "unread message waiting for you, REDCap user"
cron_35 = "There is"
cron_37 = "Your account has been set to expire because it meets the criteria set forth by your organizational policy."
cron_38 = "The sponsor (i.e., secondary contact - such as the principal investigator, mentor, or supervisor) for this REDCap user account is"
cron_39 = "using that user account until the access is restored at the request of the Sponsor. Your projects or data will not be lost. Please reply to this email and request the account extension, and our team will contact you shortly to verify additional details. Thank you!"
cron_40 = "<b>For the sponsor only:</b> Please note that as a user sponsor, you can make requests on behalf of your sponsored users on the"
cron_41 = "using that user account. Your projects or data will not be lost. If you need an account extension, please reply to this email, and our team will contact you shortly. Thank you!"
messaging_01 = "Create new conversation"
messaging_02 = "<b>NOTICE:</b> In REDCap Messenger, this user belongs to conversations that are linked to this project. Thus for security purposes, this user will automatically be removed from ALL conversations below when you remove them from this project."
messaging_03 = "User will be removed from these conversations associated with this project:"
messaging_04 = "General Notifications"
messaging_05 = "NO ACCESS:"
messaging_06 = "System Notifications"
messaging_07 = "REDCap Administrator"
messaging_08 = "Messenger"
messaging_09 = "REDCap Messenger"
messaging_10 = "Notification Preferences for REDCap Messenger"
messaging_11 = "If you receive a message while you are not logged in to REDCap, Messenger will send an email informing you of any unread messages (note: the email will *not* contain the message text itself). Below you may adjust your preferences for how often you want to receive email notifications from REDCap Messenger."
messaging_12 = "Frequency of email notifications for any new messages received:"
messaging_13 = "Enable instant email notifications for 'Important' messages and messages where you are tagged (@username)? This overrides the frequency setting above."
messaging_14 = "(If checked, always send an email when tagged or when receiving an 'Important' message.)"
messaging_15 = "If you wish to modify your email notification preferences for REDCap Messenger, visit the"
messaging_16 = "[REDCap Messenger]"
messaging_17 = "was removed from the conversation"
messaging_18 = "were removed from the conversation"
messaging_19 = "while being removed from the linked project"
messaging_20 = "Your user privileges have expired for the project to which this conversation is linked. You will not be able to view any messages in this conversation until another user in the project un-expires you."
messaging_21 = "REDCap Messenger is a communication platform built directly into REDCap. It allows REDCap users to communicate easily and efficiently with each other in a secure manner. At its core, REDCap Messenger is a chat application that enables REDCap users to send one-on-one direct messages or to organize group conversations with other REDCap users."
messaging_22 = "REDCap Messenger is also the best and easiest way to share documents with other REDCap users, in which you can upload documents and embed pictures inside any given conversation."
messaging_23 = "Messages sent (total)"
messaging_24 = "Conversations"
messaging_25 = "Conversations linked to a project"
messaging_26 = "Messages sent (past 7 days)"
messaging_27 = "Messages sent (past 30 days)"
messaging_28 = "How to use REDCap Messenger"
messaging_29 = "Type a message to ALL users..."
messaging_30 = "Mark as important"
messaging_31 = "Add file"
messaging_32 = "Type a message..."
messaging_33 = "(click to go to message)"
messaging_34 = "(edited)"
messaging_35 = "This message has been deleted by"
messaging_36 = "If you are a REDCap Administrator, you can click here to see the message."
messaging_37 = "Members:"
messaging_38 = "Everyone"
messaging_39 = "no messages..."
messaging_40 = "Notifications"
messaging_41 = "Open my archived conversations"
messaging_42 = "Search my conversations"
messaging_44 = "Add users"
messaging_45 = "Remove users"
messaging_46 = "Remove self from conversation"
messaging_47 = "Rename conversation"
messaging_48 = "Conversation permissions"
messaging_49 = "Pin/unpin to top"
messaging_50 = "Download as Excel/CSV"
messaging_51 = "Archive conversation"
messaging_52 = "Delete conversation"
messaging_53 = "Introducing REDCap Messenger"
messaging_54 = "Why use REDCap Messenger?"
messaging_55 = "There are lots of chat products out there, but not all of them are good choices for secure, private communication, especially if you deal with PHI (Protected Health Information) and other types of sensitive information. REDCap Messenger is fully secure, is hosted by your local institution, and meets HIPAA compliance standards. It is also possible for it to be implemented (as part of REDCap) in other compliance environments, including GCP, 21 CFR Part 11, and FISMA environments. Just as your data in REDCap is secure, so are your conversations. There's no need to use email or third-party chat apps for all your communication in your projects. You can just use REDCap Messenger as the central hub for all your team communication and file sharing. And the best part is that it's a built-in part of REDCap. So if you're already using REDCap for data collection, it just makes sense to use REDCap Messenger for all the communication that is a natural part of your data collection and your projects."
messaging_56 = "Where do I find REDCap Messenger?"
messaging_57 = "If you log into REDCap you will find 'Messenger' on the top navigation bar of the My Projects page. And when inside a project, you will see it near the top of the project's left-hand menu. Clicking on it will open the REDCap Messenger panel on the left side of the webpage where you can view any unread messages sent to you or create new conversations of your own. When done reading or sending your messages, just click the X at the top right of the Messenger panel to close it. REDCap Messenger will always let you know if you receive any new messages, so there's no need to keep the Messenger panel open all the time except when you need it."
messaging_58 = "User tagging and marking messages as 'important'"
messaging_59 = "You can target specific REDCap users in a group conversation by referencing them as @username in your message - e.g., 'Thanks for letting me know, @harrisjt'. Just add an @ sign before their REDCap username in a message to tag them. You can also mark any message inside your conversations as important or urgent by checking the 'mark as important' checkbox below the textbox where you type your message. The 'important' option and tagging feature can serve as a way to draw a user's attention quickly to a specific message, and they will be prioritized when notifying the user via email if the user is not currently logged in to REDCap."
messaging_60 = "User permissions within conversations"
messaging_61 = "You have full control over your conversations, and you can create as many as you wish. When you create a new conversation, you automatically have maximum privileges in the conversation. You can then add others to your conversation and (if you wish) also grant them 'conversation administrator' privileges, which means that they will be able to add (or remove) other users to the conversation, rename the conversation, or eventually archive/delete it. In a conversation, there are only two categories of users: 1) a conversation administrator (management privileges within the conversation), and 2) a conversation member (limited privileges with only the ability to view and post messages and attachments)."
messaging_62 = "Email notifications for unread messages"
messaging_63 = "If you receive a message while you're not currently logged in to REDCap, Messenger will send you an email notification a short time afterward letting you know that you have some unread messages waiting for you. And don't worry, the email will *not* contain the actual text of your messages. You will have to log in to REDCap to securely view your unread messages. If you wish to change your email notification settings for REDCap Messenger, navigate to the Profile page (found at the top right of the My Projects page), and you will find the options at the bottom of that page."
messaging_64 = "Does REDCap Messenger have a mobile app?"
messaging_65 = "It does not, but Messenger works on mobile devices. You can just log into REDCap as usual on your smartphone or tablet, and use REDCap Messenger just the same as on your desktop or laptop computer. That means you can use REDCap Messenger to communicate from any device. "
messaging_66 = "Can I send messages to survey participants using REDCap Messenger?"
messaging_67 = "REDCap Messenger is not intended for survey participants but only for REDCap users to communicate with each other."
messaging_68 = "Other notifications"
messaging_69 = "You will probably see other notifications appear in the Messenger panel from time to time. Some of these might be from REDCap itself, such as informative notices about new features, and some might be direct communication from your REDCap Administrators, such as announcing server downtime, help sessions, etc. Note: Notifications will not trigger any email notifications like conversation messages do; they are only meant to be viewed in the context of using REDCap."
messaging_70 = "Tag user in message:"
messaging_71 = "Add to conversation"
messaging_72 = "entered this conversation"
messaging_73 = "Conversation has been deleted."
messaging_74 = "Conversation has been archived."
messaging_75 = "Status changed to 'inactive'"
messaging_76 = "Message from"
messaging_77 = "posted at"
messaging_78 = "has been deleted."
messaging_79 = "has been edited."
messaging_80 = "Are you sure you want to delete this conversation? Once deleted, you and all other members will not be able to access the conversation anymore."
messaging_82 = "Delete Conversation?"
messaging_83 = "Are you sure you want to archive this conversation? Archiving a conversation means that it is *not* deleted but is simply removed from the list of REDCap Messenger conversations for all the users in this conversation. Members of the conversation will not be able to post new messages in it again unless it is restored to active status, which can be done at any time by a Conversation Administrator."
messaging_84 = "Archive"
messaging_85 = "Archive Conversation?"
messaging_86 = "Conversation Members"
messaging_87 = "(click for a more detailed view)"
messaging_88 = "Messages in this channel will be visible to all users"
messaging_89 = "Action forbidden! Cannot revoke Conversation Admin status for REDCap Administrators."
messaging_90 = "Action forbidden! There must be at least one Conversation Admin per conversation."
messaging_91 = "Are you sure you want to change your own status? If so, you will not be able to edit user permissions for this conversation anymore."
messaging_92 = "Change your status?"
messaging_93 = "Action forbidden! Can't access members panel on archived conversations."
messaging_94 = "Conversation Members and Admins"
messaging_95 = "Two categories of users exist in a conversation: 1) Conversation Administrators, and 2) Conversation Members. Conversation Administrators may add or remove members from the conversation, archive or delete the conversation, and make other members a Conversation Administrator. Conversation Members may only view and post messages to the conversation and also download the conversation as an Excel/CSV file."
messaging_96 = "Users in this conversation"
messaging_97 = "Conversation Admin?"
messaging_98 = "Edit the message in the text box below, and then click 'Confirm' to submit your changes."
messaging_100 = "Message will still be visible for REDCap Administrators only."
messaging_101 = "this message"
messaging_102 = "Message options"
messaging_103 = "Author:"
messaging_104 = "Posted at:"
messaging_105 = "Message:"
messaging_106 = "Action forbidden. This message has been deleted."
messaging_107 = "Sorry, but you do not have permission to edit this message. Permission is granted only to the message original author or to REDCap Administrators."
messaging_108 = "Attached file:"
messaging_109 = "Time of change"
messaging_110 = "Message"
messaging_111 = "Below is a history of all the changes to this message."
messaging_112 = "Message history"
messaging_113 = "Action forbidden! Only REDCap Administrators can access deleted messages."
messaging_114 = "Message (edited):"
messaging_115 = "Message: This message has been deleted by"
messaging_116 = "If you are a REDCap Administrator, you can click here to see the message."
messaging_117 = "New Messages"
messaging_118 = "(click to go to project)"
messaging_119 = "(current project)"
messaging_120 = "Title edited!"
messaging_121 = "Please fill both title and description fields before submitting"
messaging_122 = "ERROR: You do not have permissions to perform this action."
messaging_123 = "joined the conversation"
messaging_124 = "Conversation"
messaging_125 = "was created"
messaging_126 = "Are you sure you want to add those users to this conversation? They will have full access to all previous messages in this conversation."
messaging_127 = "Users:"
messaging_128 = "Please select at least one user to add to the conversation."
messaging_129 = "Are you sure you want to remove those users from this conversation?"
messaging_130 = "Please leave at least one user in the conversation."
messaging_131 = "Please select at least one user to remove from the conversation."
messaging_132 = "Link Conversation to Project"
messaging_133 = "You may associate a conversation with a REDCap project if the conversation will be centered around a single project and its data collection. Linking a project is a good way of specifying a central communication channel for the project. Also, linking the project gives you the extra benefit of reminding you to remove users from a conversation if a user is being removed from the project to which it is linked. This prevents users from seeing sensitive data inside conversations once they are no longer associated with your project."
messaging_134 = "(select all)"
messaging_135 = "(unselect all)"
messaging_136 = "Users in this project:"
messaging_137 = "Users across all my projects:"
messaging_138 = "All Users in this conversation:"
messaging_139 = "Add users to Conversation"
messaging_140 = "All Users not in this conversation:"
messaging_141 = "Users in this project not in this conversation:"
messaging_142 = "Remove users from Conversation"
messaging_143 = "Search for user by username, name, or email"
messaging_144 = "Type a title..."
messaging_145 = "Conversation Title"
messaging_146 = "(required)"
messaging_147 = "Users List"
messaging_148 = "Initial Message"
messaging_149 = "There are no users within any projects"
messaging_150 = "No project selected"
messaging_151 = "No projects available"
messaging_152 = "Messages:"
messaging_153 = "from:"
messaging_154 = ", on:"
messaging_155 = ", Conversation:"
messaging_156 = "(inactive)"
messaging_157 = "Results..."
messaging_158 = "Type a keyword..."
messaging_159 = "Type a username..."
messaging_160 = "Search Conversations"
messaging_161 = "Search by keyword"
messaging_162 = "Search by person"
messaging_163 = "Are you sure you wish to restore the conversation titled"
messaging_164 = "back to the active status? If so, all members of the conversations will then be able to view it and use it again."
messaging_165 = "Restore Conversation?"
messaging_166 = "Restore"
messaging_167 = "No archived conversations"
messaging_168 = "Archived Conversations"
messaging_169 = "Below is a list of all your archived conversations. To view a read-only copy of the conversation, click the conversation title. You may also download the conversation or restore it back to active status again."
messaging_170 = "Your permission to access the conversation"
messaging_171 = "has been revoked."
messaging_172 = "This conversation has been deleted."
messaging_173 = "This conversation has been archived."
messaging_174 = "You have been removed from this conversation."
messaging_175 = "Open"
messaging_176 = "Do you want to open the archived conversation?"
messaging_177 = "NOTICE: It appears that you may have multiple browser windows/tabs open, which may prevent some things from working on this page until this page is refreshed. It is advised that you complete what you are doing, and then refresh this page."
messaging_179 = "Browser compatiblity issue"
messaging_180 = "Please choose a file to upload first."
messaging_181 = "File chosen is too big."
messaging_182 = "Download file preview"
messaging_183 = "(Type the word"
messaging_184 = "in the text box below to proceed with deleting the conversation.)"
messaging_185 = "in the text box below to proceed)."
messaging_186 = "While it is typically okay to place PHI or other identifying information into a message in a conversation (unless your institution states otherwise), entering such into a conversation's title is <i>highly discouraged</i>. This is because conversation titles are much more visible than conversation text."
messaging_187 = "Enable email notifications for General Notifications (sent by REDCap administrators) and System Notifications (updates about new features)?"
rep_forms_events_01 = "Repeating Instruments and Events"
rep_forms_events_02 = "Export Repeating Instruments and Events"
rep_forms_events_03 = "This method allows you to export a list of the repeated instruments and repeating events for a project. This includes their unique instrument name as seen in the second column of the Data Dictionary, as well as each repeating instrument's corresponding custom repeating instrument label. For longitudinal projects, the unique event name is also returned for each repeating instrument. Additionally, repeating events are returned as separate items, in which the instrument name will be blank/null to indicate that it is a repeating event (rather than a repeating instrument)."
rep_forms_events_04 = "Repeated instruments and events for the project in the format specified and will be ordered according to their order in the project."
rep_forms_events_05 = "Import Repeating Instruments and Events"
rep_forms_events_06 = "Import Repeating Instruments and Events"
rep_forms_events_07 = "This method allows you to import a list of the repeated instruments and repeating events for a project. This includes their unique instrument name as seen in the second column of the Data Dictionary, as well as each repeating instrument's corresponding custom repeating instrument label. For longitudinal projects, the unique event name is also needed for each repeating instrument. Additionally, repeating events must be submitted as separate items, in which the instrument name will be blank/null to indicate that it is a repeating event (rather than a repeating instrument)."
rep_forms_events_08 = "Number of repeated isntruments or repeated events that have been imported"
calendar_widget_done = "Done"
calendar_widget_prev = "Prev"
calendar_widget_next = "Next"
calendar_widget_month_jan = "Jan"
calendar_widget_month_feb = "Feb"
calendar_widget_month_mar = "Mar"
calendar_widget_month_apr = "Apr"
calendar_widget_month_may = "May"
calendar_widget_month_jun = "Jun"
calendar_widget_month_jul = "Jul"
calendar_widget_month_aug = "Aug"
calendar_widget_month_sep = "Sep"
calendar_widget_month_oct = "Oct"
calendar_widget_month_nov = "Nov"
calendar_widget_month_dec = "Dec"
calendar_widget_month_day_short_sun = "Su"
calendar_widget_month_day_short_mon = "Mo"
calendar_widget_month_day_short_tues = "Tu"
calendar_widget_month_day_short_wed = "We"
calendar_widget_month_day_short_thurs = "Th"
calendar_widget_month_day_short_fri = "Fr"
calendar_widget_month_day_short_sat = "Sa"
calendar_widget_month_day_long_sun = "Sunday"
calendar_widget_month_day_long_mon = "Monday"
calendar_widget_month_day_long_tues = "Tuesday"
calendar_widget_month_day_long_wed = "Wednesday"
calendar_widget_month_day_long_thurs = "Thursday"
calendar_widget_month_day_long_fri = "Friday"
calendar_widget_month_day_long_sat = "Saturday"
calendar_widget_hour = "Hour"
calendar_widget_min = "Minute"
calendar_widget_sec = "Second"
calendar_widget_choosetime = "Choose Time"
calendar_widget_choosetimehint = "Click to select a time"
calendar_widget_choosedatehint = "Click to select a date"
calendar_widget_choosedatetimehint = "Click to select a date/time"
piping_01 = "The current user's REDCap username."
piping_02 = "The Data Access Group (the unique group name) to which the current user belongs (blank if not in a DAG)."
piping_03 = "The group ID number of the Data Access Group to which the current user belongs (blank if not in a DAG)."
piping_04 = "The record name of the current record."
piping_05 = "The Data Access Group (the unique group name) to which the current record belongs (blank if not in a DAG)."
piping_06 = "The group ID number of the Data Access Group to which the current record belongs (blank if not in a DAG)."
piping_07 = "(longitudinal only) The current event (unique event name)."
piping_08 = "(longitudinal only) The event (unique event name) that occurs immediately before the current event (blank if current event is the first event)."
piping_09 = "(longitudinal only) The event (unique event name) that occurs immediately after the current event (blank if current event is the last event)."
piping_10 = "The web address (URL) of the specified data entry form for the current record/event/instance. The format must be [form-url:instrument], in which 'instrument' is the unique form name of the desired instrument."
piping_11 = "The HTML web link that, when clicked, will navigate to the specified data entry form for the current record/event/instance. The format must be [form-link:instrument] or [form-link:instrument:Custom Text], in which 'instrument' is the unique form name of the desired instrument. 'Custom Text' is an optional parameter whereby you can specify the visible link text, and if it is not provided, it defaults to the form label of the data entry form. The format [form-link:Custom Text] can also be used if the instrument is assumed, such as when viewing a form or in a survey invitation. Also, it can be used simply as [form-link] inside the content of a survey invitation, in which 'instrument' is assumed to be the current survey instrument."
piping_12 = "The web address (URL) of the specified survey for the current record/event/instance. The format must be [survey-url] or [survey-url:instrument], in which 'instrument' is the unique form name of the desired instrument. This can be used simply as [survey-url] inside the content of a survey invitation, in which 'instrument' is assumed to be the current survey instrument."
piping_13 = "The HTML web link that, when clicked, will navigate to the specified survey for the current record/event/instance. The format must be [survey-link], [survey-link:instrument], or [survey-link:instrument:Custom Text], in which 'instrument' is the unique form name of the desired instrument. 'Custom Text' is an optional parameter whereby you can specify the visible link text, and if it is not provided, it defaults to the survey title of the survey. The format [survey-link:Custom Text] can also be used if the instrument is assumed, such as when viewing a form or in a survey invitation. Also, it can be used simply as [survey-link] inside the content of a survey invitation, in which 'instrument' is assumed to be the current survey instrument."
piping_14 = "The web address (URL) of the survey queue for the current record."
piping_15 = "The HTML web link that, when clicked, will navigate to the survey queue for the current record. The format must be [survey-queue-link] or [survey-queue-link:Custom Text], in which 'Custom Text' is an optional parameter whereby you can specify the visible link text. And if it is not provided, it defaults to 'Survey Queue Link'."
piping_16 = "Survey Queue Link"
piping_17 = "(longitudinal only) The current event (the event label, not the unique event name)."
piping_18 = "(longitudinal only) The event (the event label, not the unique event name) that occurs immediately before the current event (blank if current event is the first event)."
piping_19 = "(longitudinal only) The event (the event label, not the unique event name) that occurs immediately after the current event (blank if current event is the last event)."
piping_20 = "(longitudinal only) The current arm number."
piping_22 = "Detects if the current instrument is being administered as a survey (returns 1 for True, 0 for False), as opposed to a form."
piping_23 = "Detects if the current instrument is being viewed as a data entry form (returns 1 for True, 0 for False), as opposed to a survey."
piping_24 = "(repeating instruments/events only)"
piping_25 = "Name of Smart Variable"
piping_26 = "Example of Usage"
piping_27 = "Example input"
piping_28 = "Example output"
piping_29 = "(longitudinal only) The arm label text of the current arm."
piping_31 = "The repeating instance number that occurs immediately before the current instance (e.g., current instance minus 1). 'Instance' refers to the instance of either a repeating instrument or a repeating event."
piping_32 = "The repeating instance number that occurs immediately after the current instance (e.g., current instance plus 1). 'Instance' refers to the instance of either a repeating instrument or a repeating event."
piping_33 = "The repeating instance number of a repeating instrument or a repeating event in the current context."
piping_34 = "The first (lowest numbered) repeating instance number for the current record/event context."
piping_35 = "The last (highest numbered) repeating instance number for the current record/event context."
piping_36 = "Note: This can be used as stand-alone or can be appended to a field variable."
piping_37 = "Note: This can be used as stand-alone or can be prepended to a field variable."
piping_38 = "Event & Arm"
piping_39 = "Smart Variable List"
piping_40 = "Listed below are all available Smart Variables, in which the description is given for each, along with an example of how it might be used. Please keep in mind that while Smart Variables can be used in calc fields, conditional logic, and piping, it does not mean that every Smart Variable should be used all of those places. For instance, you will likely only use [survey-link] and [form-url] for piping purposes. Also, [is-survey] and [next-event-name] will likely never make sense to be utilized in piping but instead in conditional logic (branching logic most likely). So remember that just because you *can* use Smart Variables in certain places does not necessarily mean that you *should*."
piping_41 = "The date and time on which the specified survey instrument was completed for the current record/event. The format must be [survey-time-completed:instrument], in which 'instrument' is the unique form name of the desired instrument. In a piping context, such as in a field label, survey invitation, or inside the @DEFAULT action tag, the format of the date and time will be displayed based on the current user's date/time display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD HH:MM:SS' format and would be more appropriate for conditional logic or calculated fields, simply append ':value'. If the survey has not been completed, it returns a blank value."
piping_43 = "Inside the @DEFAULT action tag"
piping_44 = "Important: When using this as a stand-alone variable, it will always return the event that occurs *immediately* before the current event, whereas if it is prepended to another variable, it will instead return the closest previous event for which the field's instrument has been designated, which might be different than the event that occurs directly before the current event. This behavior is due to the fact that the field's instrument might not always be designated for the event that occurs directly before the current event."
piping_45 = "Important: When using this as a stand-alone variable, it will always return the event that occurs *immediately* after the current event, whereas if it is prepended to another variable, it will instead return the closest following event for which the field's instrument has been designated, which might be different than the event that occurs directly after the current event. This behavior is due to the fact that the field's instrument might not always be designated for the event that occurs directly after the current event."
piping_46 = "The name/label of the Data Access Group to which the current user belongs (blank if not in a DAG)."
piping_47 = "The name/label of the Data Access Group to which the current record belongs (blank if not in a DAG)."
piping_48 = "Your survey invitation text appears to be missing the survey link, which should be inserted into the invitation text as either [survey-link] or [survey-url]. Without a link to the survey in your invitation, participants will not be able to navigate to the survey in order to take it. It is highly recommended that you add the [survey-link] variable to your invitation text, unless you truly do not want the survey link to appear in the email to the participant. Would you like to auto-add the survey link to the invitation text or just leave it as is?"
piping_50 = "Leave as is with no survey link"
piping_51 = "Add [survey-link] to text"
piping_52 = "Important: When using this as a stand-alone variable, it will always return the first event for the current arm, whereas if it is prepended to another variable, it will instead return the first event (for the current arm) for which the field's instrument has been designated, which might be different than the very first event. This behavior is due to the fact that the field's instrument might not always be designated for the very first event."
piping_53 = "Important: When using this as a stand-alone variable, it will always return the last event for the current arm, whereas if it is prepended to another variable, it will instead return the last event (for the current arm) for which the field's instrument has been designated, which might be different than the very last event. This behavior is due to the fact that the field's instrument might not always be designated for the very last event."
piping_54 = "(longitudinal only) The first event (unique event name) for the current arm."
piping_55 = "(longitudinal only) The last event (unique event name) for the current arm."
piping_56 = "(longitudinal only) The first event (the event label, not the unique event name) for the current arm."
piping_57 = "(longitudinal only) The last event (the event label, not the unique event name) for the current arm."
piping_58 = "The Project ID (i.e., PID) of the current REDCap project."
piping_59 = "The base web address for this REDCap installation."
piping_60 = "The current REDCap version number of this REDCap installation."
piping_61 = "The base web address of the current REDCap version directory for this REDCap installation."
piping_62 = "The base web address for surveys for this REDCap installation."
piping_63 = "The current user's first and last name (as listed on their Profile page)."
piping_64 = "The current user's primary email address (as listed on their Profile page)."
piping_65 = "The unique instrument name of the current survey or data entry form. It will return a blank value if not in an instrument context."
piping_66 = "The instrument label of the current survey or data entry form. It will return a blank value if not in an instrument context."
piping_67 = "The survey title of the instrument specified by the 'instrument' parameter (if provided). If the 'instrument' parameter is not provided, the current survey instrument will be used, else it will return a blank value if not in an instrument/survey context."
piping_68 = "The Role ID of the user role to which the current user is assigned (blank if not assigned to any user role). This value is auto-generated for each user role. NOTE: This value is not just unique for all roles within the project but is also unique across all REDCap projects. Thus, if the project and its user roles are copied, the Role IDs of the user roles in the resulting copy will be different from the ones in the original project."
piping_69 = "The unique role name of the user role to which the current user is assigned (blank if not assigned to any user role). This value is auto-generated for each user role. NOTE: This value is only unique for roles within the project. Thus, if the project and its roles are copied, the new project will retain the same unique role names, which allows you to utilize the unique role names in conditional logic, calculations, branching logic, etc. that will not break when the project is copied."
piping_70 = "The name/label of the user role to which the current user is assigned (blank if not assigned to any user role). This value is defined by the user that creates the user role."
piping_71 = "(longitudinal only) The event id number of the current event."
piping_72 = "The Survey Access Code of the specified survey for a given record/event/instance. The format must be [survey-access-code] or [survey-access-code:instrument], in which 'instrument' is the unique form name of the desired instrument. This can be used simply as [survey-access-code] inside the content of a survey invitation, in which 'instrument' is assumed to be the current survey instrument."
piping_73 = "The Survey Return Code of the specified survey for a given record/event/instance in order to allow a participant to return to a completed or partially completed survey response when using the 'Save & Return Later' survey feature. The format must be [survey-return-code] or [survey-return-code:instrument], in which 'instrument' is the unique form name of the desired instrument. This can be used simply as [survey-return-code] inside the content of a survey invitation, in which 'instrument' is assumed to be the current survey instrument."
piping_74 = "NOTICE: Invitation text is missing [survey-link] variable"
piping_75 = "(longitudinal only) The current event's ordinal number as listed on the Define My Events page that denotes the order of the event within a given arm."
piping_76 = "The date and time on which the specified survey instrument was started for the current record/event (i.e., the initial time the survey page is opened). The format must be [survey-time-started:instrument], in which 'instrument' is the unique form name of the desired instrument. In a piping context, such as in a field label, survey invitation, or inside the @DEFAULT action tag, the format of the date and time will be displayed based on the current user's date/time display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD HH:MM:SS' format and would be more appropriate for conditional logic or calculated fields, simply append ':value'. NOTE: If the start time is a blank value, it implies that the response began while on an earlier version of REDCap when start times were not yet collected."
piping_78 = "The amount of time that has elapsed since the survey was started (returned in the time units specified, defaults to 's'), and represents the difference between the survey's start time and either its 1) completion time (if completed) or 2) the current time (if not completed). Options for 'units': 'y' (years, 1 year = 365.2425 days), 'M' (months, 1 month = 30.44 days), 'd' (days), 'h' (hours), 'm' (minutes), 's' (seconds). Tip: The units value should not be wrapped in apostrophes or quotes. NOTE: If using [survey-duration] inside a calculated field or @CALCTEXT field, the value for partially completed surveys will always be changing until the survey is completed, and thus the value might not be accurate on reports or data exports unless you run Data Quality rule H immediately beforehand."
piping_79 = "The total time it took to complete the survey (returned in the time units specified, defaults to 's'), and represents the difference between the survey's start time and completion time. NOTE: A blank value will be returned if the survey has not been completed. Options for 'units': 'y' (years, 1 year = 365.2425 days), 'M' (months, 1 month = 30.44 days), 'd' (days), 'h' (hours), 'm' (minutes), 's' (seconds). Tip: The units value should not be wrapped in apostrophes or quotes."
piping_80 = "A new, not-yet-created repeating instance for the current record/event context, in which [new-instance] is essentially [last-instance]+1. Note: This can be used as stand-alone or alternatively can be used by being appended to only the following Smart Variables: [survey-link], [survey-url], [survey-access-code], [form-link], and [form-url]."
piping_81 = "The MyCap project code of the current REDCap project."
piping_82 = "The participant code of the current record."
piping_83 = "The web address (URL) for the current record that can be used by the participant to join the project on the MyCap mobile app."
piping_84 = "The HTML web link belonging to the current record that, when clicked, will allow the participant to join the project on the MyCap mobile app. 'Custom Text' is an optional parameter whereby you can specify the visible link text, and if it is not provided, it defaults to simply displaying the URL as the link text."
piping_85 = "visit_data_form"
piping_86 = "Visit Data Form"
piping_87 = "Click here to view Demographics"
piping_88 = "Download your calendar events (ICS file)"
piping_89 = "demographics"
piping_90 = "Demographics"
piping_91 = "prescreening_survey"
piping_92 = "Pre-Screening Survey"
piping_93 = "followup_survey"
piping_94 = "Follow-up Survey"
piping_95 = "Take the pre-screening survey"
piping_96 = "View your survey progress"
piping_97 = "Enter to Win a New Car"
piping_98 = "Cardiology Study"
piping_99 = "Event 2"
piping_100 = "Third Timepoint"
piping_101 = "Minor"
piping_102 = "Week 22"
piping_103 = "Drug B"
piping_104 = "Repeating Survey"
piping_105 = "Click this MyCap link"
piping_106 = "The name of the specific redcap_data* database table (located on the back-end REDCap database server) used by the current REDCap project.  If a PID (project ID) is provided as a parameter (e.g., [data-table:435]), then the name of the redcap_data* table will be returned for that specific project/PID."
piping_107 = "The date on which the specified survey instrument was completed for the current record/event (includes date component only, unlike [survey-time-completed]). The format must be [survey-date-completed:instrument], in which 'instrument' is the unique form name of the desired instrument. In a piping context, such as in a field label, survey invitation, or inside the @DEFAULT action tag, the format of the date will be displayed based on the current user's date display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD' format and would be more appropriate for conditional logic or calculated fields, simply append ':value'. If the survey has not been completed, it returns a blank value."
piping_108 = "The date on which the specified survey instrument was started for the current record/event (includes date component only, unlike [survey-time-completed]). The format must be [survey-date-started:instrument], in which 'instrument' is the unique form name of the desired instrument. In a piping context, such as in a field label, survey invitation, or inside the @DEFAULT action tag, the format of the date will be displayed based on the current user's date display preferences. If you wish to have it return the raw value, which will instead be in 'YYYY-MM-DD' format and would be more appropriate for conditional logic or calculated fields, simply append ':value'. NOTE: If the start time is a blank value, it implies that the response began while on an earlier version of REDCap when start times were not yet collected."
data_mart_refresh_009 = "Clinical Data Mart settings for this project (Administrators only)"
data_mart_refresh_010 = "By default, users using the Data Mart can only pull EHR data one time, and they cannot modify their initial Data Mart configuration. As an administrator, by clicking the buttons below you may grant project users the privilege to fetch EHR data multiple times and also the privilege to submit changes (i.e., as new revisions) to their existing Data Mart configuration, in which each revision of the configuration must be approved by an administrator in the To-Do List."
data_mart_refresh_011 = "Users can fetch EHR data multiple times (after the initial fetch)"
data_mart_refresh_012 = "Users can request changes to their Data Mart configuration"
data_mart_refresh_013 = "Using the Clinical Data Mart page"
data_mart_refresh_014 = "In order to pull data from the EHR using the Data Mart or to change your Data Mart configuration, please visit the Clinical Data Mart page using this link on the left-hand menu."
data_mart_refresh_016 = "Auto-fetch all clinical data once a day (based on Data Mart configuration)"
project_setup_modal_title = "Disable this option?"
project_setup_modal_body = "Are you sure you want to disable this option?"
alerts_01 = "The settings below can be used to restrict the ability for users to send alerts to certain email addresses on the Alerts & Notifications page in all projects. This allows some institutions to be more restrictive if they have concerns about users using this functionality (intentionally or maliciously) in a way that might threaten regulatory compliance or privacy laws/regulations, such as piping sensitive data into an alert's email message and sending it to a non-project user."
alerts_02 = "Allow normal users to manually enter email addresses as <u>freeform text</u> for an alert's To, CC, or BCC?"
alerts_03 = "Allow normal users to use project variables for <u>email fields</u> in the project for an alert's To, CC, or BCC?"
alerts_05 = "Yes, allow normal users to use this"
alerts_06 = "No, only allow administrators to use this"
alerts_07 = "If set to 'Yes', then users will be able to choose email-validated text fields in the multi-select when setting an alert's To, CC, or BCC. Administrators will always be able to do this in a project regardless of this setting."
alerts_08 = "If set to 'Yes', then users will be able to <u>manually type *any* email address</u> for an alert's To, CC, or BCC. Administrators will always be able to do this in a project regardless of this setting."
alerts_09 = "Optional: <u>Domain allowlist for email addresses</u> that are manually entered as freeform text (via option above)"
alerts_10 = "If the option immediately above is set to 'Yes', you may optionally limit the kinds of email addresses that can be entered as an alert's To, CC, or BCC by specifying one or more domain names (e.g., vanderbilt.edu) that will serve as an allowlist of the only acceptable domains that email addresses may have for an alert. If an email with another domain is entered by a user, it will display an error and will not accept it."
alerts_12 = "Prevent piping of data for Identifier fields"
alerts_13 = "If this checkbox is checked, any field variables (e.g., [date_of_birth]) that exist in the alert's subject or message will not have their value piped if the field has been tagged as an 'Identifier' field. In this case, it will simply replace the field variable with [*DATA REMOVED*] rather than piping the actual data into the message."
alerts_14 = "Allow piping of data for Identifier fields?"
alerts_15 = "Fields are often marked as Identifiers because they contain sensitive or identifying information, such as Personally identifiable information (PII) or Protected Health Information (PHI). To uphold the highest level of privacy to prevent potentially-sensitive data from being sent out of your project as an alert, it is recommended to keep this checkbox checked."
alerts_16 = "Are you sure you still wish to allow piping of data for Identifier fields?"
alerts_17 = "Sent alert"
alerts_18 = "View past notifications"
alerts_19 = "View future notifications"
alerts_20 = "Notification Log"
alerts_21 = "Notification send time"
alerts_22 = "View Notification"
alerts_23 = "Subject"
alerts_24 = "Alert"
alerts_25 = "No notifications to list"
alerts_26 = "Recipient"
alerts_27 = "All alerts"
alerts_28 = "Click to view notification"
alerts_29 = "Delete this scheduled recurring notification"
alerts_30 = "Ensure logic is still true before sending notification?"
alerts_31 = "This setting is optional for Alerts & Notifications. When enabled, REDCap will re-evaluate the conditional logic against the record's data values whenever the record values are changed AFTER the notification has been scheduled but BEFORE it has been sent to the recipient. And if the logic is no longer true (i.e., if the data values have changed during the time after the notification was scheduled), it will not send the notification to the recipient but will instead delete it (as if it had never been scheduled). Additionally, if the notifications get deleted due to this setting, then the notifications *may* get scheduled again later if data values are changed such that the logic evaluates as true again. Enabling this setting provides you with greater control over when and how notifications get sent when using conditional logic for Alerts & Notifications."
alerts_32 = "Learn more"
alerts_33 = "How to use 'stop logic' to disable a scheduled alert"
alerts_34 = "If you have alerts that will not be sent immediately but instead are scheduled to be sent later, it might be a good idea to consider using 'stop logic' (otherwise known as a 'kill switch') in your conditional logic in order to manually stop these scheduled alerts when needed. This might be used if somehow an alert was scheduled by accident and you need to quickly delete it. NOTE: You must have checked the 'ensure logic is still true' checkbox in order for the 'stop logic' to work. By having the checkbox checked, it means that every time a given record is saved or has data modified, REDCap will see if there is an alert scheduled for this record, and if so, it will then double check to see if this condition/logic is still true. If condition is no longer true, it will delete the notification so that it never gets sent. And if the record is modified again later, in which the condition then becomes true again, then the notification will get re-scheduled. Without the 'ensure logic is still true' checkbox being checkbox, REDCap will leave the scheduled alert as-is and never delete it."
alerts_35 = "The 'stop logic' could be a complex set of conditional logic, or it could be as simple as a single field in the project (i.e., the kill switch). For example, if you are wanting to schedule an alert when a participant is at least 18 years old, your logic might be '[age] >= 18'. And if you want to add the 'stop logic' to be able to manually delete a scheduled alert, you could have '[age] >= 18 and [remove_alert] <i> 1', in which the field 'remove alert' is a Yes/No field. So in this instance, if you wanted to have the scheduled alert deleted, you could simply go to the data entry form where the 'remove alert' field is located, and set it to 'Yes'. This can be done a variety of different ways. This is merely a simple example to introduce this concept. <b>Remember, the key to using 'stop logic' is that the 'ensure logic is still true' checkbox MUST be checked.</b>"
alerts_36 = "Create new alert"
alerts_37 = "Edit Alert"
alerts_38 = "Add another attachment"
alerts_39 = "Please add some text for this alert's message."
alerts_40 = "One or more of the files could not be saved."
alerts_41 = "The file was not able to be deleted."
alerts_42 = "Click to select a date/time"
alerts_43 = "Select recipients"
alerts_44 = "Select file upload fields"
alerts_45 = "ERROR: Must provide instrument name for survey link/URL"
alerts_46 = "Your message text contains [survey-url], [survey-link], [form-url], [form-link], which is incorrect. An instrument name parameter must be provided for theses Smart Variable in alerts - e.g., [survey-link:prescreening_survey] or [form-url:demographics]. This is required because alerts do not have a default instrument context, thus the unique instrument name must be provided. This must be corrected before the alert can be saved."
alerts_47 = "Yes, I understand"
alerts_48 = "No, cancel"
alerts_49 = "The following are not valid email addresses:"
alerts_50 = "Please either correct or remove any invalid emails."
alerts_51 = "The domain of the email(s) entered is not allowed. (The domain name is the part of the email address after the @ sign.) The only acceptable domain names for email addresses are the ones listed below. You may only enter emails that end in one of these domain names. Please try again."
alerts_52 = "Acceptable domains:"
alerts_53 = "Email addresses with disallowed domain:"
alerts_54 = "Disallowed domain names for email addresses"
alerts_55 = "Alert recipient is incorrect"
alerts_56 = "Alert sender is empty"
alerts_57 = "The email address listed for the alert is not a valid email"
alerts_58 = "The email address listed for the alert is missing"
alerts_59 = "Attachment is too large"
alerts_60 = "One or more alert attachments in the following project are too large to be sent via email because they exceed the max size of"
alerts_61 = "Just once"
alerts_65 = "(available for Admins only)"
alerts_66 = "-- Project Users --"
alerts_67 = "Survey Participant"
alerts_68 = "-- and/or Project Users --"
alerts_69 = "and/or Email Field Variables"
alerts_70 = "[Any Event]"
alerts_71 = "New alert created."
alerts_72 = "The alert was updated."
alerts_73 = "The alert was copied."
alerts_74 = "The alert was deactivated."
alerts_75 = "The alert was permanently deleted."
alerts_76 = "The alert was re-enabled."
alerts_78 = "While similar in many respects to Automated Survey Invitations, Alerts & Notifications allow for greater complexity and have more capabilities. For example, alerts apply to both data entry forms and surveys, and they also allow for more options regarding who can be the recipient of a notification (project users, survey participants, etc.)."
alerts_79 = "To get started with creating alerts, click the 'Add New Alert' button to view all the settings that must be defined for a given alert. Once an alert has been created, it immediately becomes active and may be triggered at any time thereafter. If you would like to remove or stop using an alert, see the Options->Deactivate Alert setting, which will prevent the alert from being triggered anymore. It may also be re-enabled at any time, in which case it becomes immediately active again. To view all notifications that have already been sent or will be sent in the future, you may view the Notification Log tab."
alerts_80 = "NOTICE: Because you are using an older version of Internet Explorer, this page cannot function as expected. You may view the page below, but you will not be able to create or modify any alerts. We recommend upgrading to the latest version of Internet Explorer or instead using another browser, such as Firefox or Google Chrome."
alerts_81 = "My Alerts"
alerts_82 = "Preview Message"
alerts_83 = "View Notification"
alerts_84 = "Delete this recurring notification?"
alerts_85 = "Are you sure you wish to delete ALL recurring notifications for this item? Doing so does not just delete a single notification, but it deletes ALL future recurring notifications for the alert/record listed below."
alerts_86 = "Alert:"
alerts_87 = "Delete recurrence series"
alerts_88 = "Add New Alert"
alerts_90 = "Alert Triggers & Settings"
alerts_91 = "Deactivate alert"
alerts_92 = "DEACTIVATED: Alert was deactivated"
alerts_93 = "Permanently delete"
alerts_94 = "Re-enable alert"
alerts_95 = "record had an alert scheduled"
alerts_96 = "records had alerts scheduled"
alerts_97 = "records scheduled for Alert"
alerts_98 = "view list"
alerts_99 = "No alerts scheduled yet"
alerts_100 = "alerts sent for Alert"
alerts_101 = "Last sent:"
alerts_102 = "No alerts sent yet"
alerts_103 = "Activity:"
alerts_104 = "Record names:"
alerts_105 = "View scheduled alerts in Notification Log"
alerts_106 = "View sent alerts in Notification Log"
alerts_107 = "Schedule to send on"
alerts_108 = "Schedule to send later on next"
alerts_109 = "Show {0} deactivated alert(s)"
alerts_110 = "Leave Alerts enabled (unless disabled)"
global_1540 = "Send immediately"
global_1541 = "Send one time"
global_1542 = "Repeat every"
global_1543 = "minute"
global_1544 = "hour"
global_1545 = "day"
global_1546 = "Repeated sending (when triggered)"
global_1547 = "Alert expires on"
global_1548 = "Copy alert"
global_1549 = "Options"
global_1550 = "Institutional login"
global_1551 = "Non institutional login"
global_1552 = "If your institution (for example an Australian University, Health or research institution) is a member of the Australian Access Federation click on the AAF graphic below."
global_1553 = "If your institution is not a member of the Australian Access Federation, fill in your login details below."
global_1554 = "<strong>Note:</strong> You must first be granted an account by an administrator at "
global_1555 = " before you can log in to REDCap using this method."
alerts_120 = "the instrument"
alerts_121 = "is saved and has any form status"
alerts_122 = "is saved and has a Complete status"
alerts_123 = "If the following logic is TRUE every time"
alerts_124 = "If the following logic is TRUE when"
alerts_125 = "Every time"
alerts_126 = "When"
alerts_127 = "the following logic becomes TRUE during data import or data entry:"
alerts_128 = "Attachments"
alerts_129 = "Preview message by record"
alerts_130 = "You may define the settings for your alert in Steps 1-3 below. After clicking the Save button at the bottom, your alert will immediately become active and may be triggered at any time thereafter. If you would like to remove or stop using an alert, it may be deactivated at any time. You may modify an existing alert at any time, even after some notifications have already been sent or scheduled."
alerts_131 = "Title of this alert:"
alerts_132 = "STEP 1: Triggering the Alert"
alerts_133 = "How will this alert be triggered?"
alerts_134 = "When a record is saved on a specific form/survey"
alerts_137 = "Trigger the alert..."
alerts_138 = "is saved with any form status"
alerts_139 = "is saved with Complete status only"
alerts_140 = "when"
alerts_141 = "(excludes data imports)"
alerts_142 = "while the following logic is true:"
alerts_143 = "when the following logic becomes true:"
alerts_145 = "STEP 2: Set the Alert Schedule"
alerts_146 = "When to send the alert?"
alerts_148 = "Send it how many times?"
alerts_150 = "Warning: Using the every time option with the instrument selected in Step 1 will cause the alert to be sent when *every* page is saved if taken as a survey (since it is a multi-page survey)."
alerts_152 = "after initially being sent"
alerts_153 = "STEP 3: Message Settings"
alerts_154 = "Email From:"
alerts_155 = "Email To:"
alerts_156 = "Show more options"
alerts_157 = "Or manually enter emails"
alerts_158 = "Email CC:"
alerts_159 = "Email BCC:"
alerts_160 = "Email to send email-failure errors:"
alerts_162 = "In the subject or message, you may use"
alerts_164 = "Add attachments"
alerts_165 = "Message Attachments"
alerts_166 = "File Upload fields:"
alerts_167 = "You may utilize files attached to records that have been uploaded into File Upload or Signature fields."
alerts_168 = "-- and/or --"
alerts_169 = "Attachment"
alerts_170 = "Alert expiration:"
alerts_171 = "This alert will be auto-deactivated at the specified date/time above. Note: This will cause any already-scheduled notifications not to be sent after the expiration time."
alerts_176 = "Deactivate Alert"
alerts_177 = "Are you sure you want to deactivate this Alert? It can be re-enabled later, if needed."
alerts_178 = "Deactivate"
alerts_179 = ">Delete Alert"
alerts_180 = "Are you sure you want to delete this Alert?"
alerts_181 = "*This will permanently delete the Alert."
alerts_182 = "Choose a record in order to preview how the message for this alert would appear for that record."
alerts_183 = "Preview Message by Record"
alerts_184 = "The uploaded file is"
alerts_185 = "in size, thus exceeding the maximum file size limit of"
alerts_186 = "or the typical maximum attachment size for most email clients"
alerts_187 = "The uploaded file could not be saved!"
alerts_188 = "Could not detect an uploaded file!"
alerts_189 = "Add Instances"
alerts_190 = "*If none is typed, only the first instance added"
alerts_191 = "CC:"
alerts_192 = "BCC:"
alerts_193 = "-- select a record --"
alerts_194 = "record was alerted"
alerts_195 = "records were alerted"
alerts_196 = "-- choose an instrument/survey --"
alerts_197 = "Please set a recipient for this alert."
alerts_198 = "Please select an instrument and/or add some conditional logic."
alerts_199 = "Alert Type:"
alerts_201 = "SMS Text Message"
alerts_202 = "Voice Call"
alerts_203 = "Recipient phone number(s):"
alerts_204 = "Or enter numbers in any format separated by semicolons. Include area code and (if needed) country code."
alerts_205 = "Type a record name"
alerts_206 = "and/or Phone/Integer Field Variables"
alerts_207 = "Email-related options:"
alerts_208 = "Phone-related options (only used if Twilio telephony services are enabled in the project):"
alerts_209 = "Allow normal users to use project variables for <u>phone fields and integer fields</u> in the project for an alert's recipient phone numbers?"
alerts_211 = "If set to 'Yes', then users will be able to choose phone-validated and integer-validated text fields in the multi-select when setting an alert's recipient phone numbers. Administrators will always be able to do this in a project regardless of this setting."
alerts_212 = "If set to 'Yes', then users will be able to <u>manually type *any* phone number</u> for an alert's recipient phone numbers. Administrators will always be able to do this in a project regardless of this setting."
alerts_214 = "Please set an email subject."
alerts_215 = "Trigger Limit: Trigger the alert..."
alerts_216 = "only once per record"
alerts_217 = "and also on every instance of a repeating instrument"
alerts_218 = "only once per event in a record"
alerts_219 = "A)"
alerts_220 = "B)"
alerts_221 = "C)"
alerts_222 = "only once per instrument regardless of the event in a record"
alerts_223 = "and also on every instance of a repeating instrument/event"
alerts_224 = "only once per instrument per event (i.e., will not re-trigger on each repeating instance)"
alerts_225 = "Every time the form/survey in Step 1B is"
alerts_226 = "Repeated sending (when triggered by saving new or modified data)"
alerts_227 = "saved"
alerts_228 = "i.e., never re-trigger"
alerts_229 = "(The trigger limit determines where and to what extent within a record that the alert will be triggered.)"
alerts_230 = "saved with new or modified data"
alerts_231 = "(ignoring calc fields)"
alerts_232 = "Multiple times on a recurring basis:"
alerts_233 = "times total (including the first time sent)."
alerts_234 = "Leave blank to continue sending forever."
alerts_235 = "times total"
alerts_237 = "(All Events)"
alerts_238 = "after"
alerts_239 = "Send the alert"
alerts_243 = "Or based on the time value of a field from"
alerts_245 = "before"
alerts_246 = "Schedule to send later:"
alerts_250 = "Do not show this message again."
alerts_251 = "Re-evaluate selected alerts"
alerts_252 = "Re-evaluate conditions for Alerts & Notifications"
alerts_253 = "Re-evaluate Alerts"
alerts_254 = "Nothing changed! It appears that no notifications needed to be scheduled or removed for any records in the project."
alerts_255 = "notifications were scheduled (and"
alerts_256 = "already-scheduled notifications were unscheduled) across a total of"
alerts_257 = "0 records were affected."
alerts_258 = "It may sometimes be necessary to re-evaluate some or all Alerts & Notifications for all records in the project. <b>This is especially useful if an alert's conditions (in Step 1 of the alert setup process) has been modified after data has already been entered for some records.</b> Thus, re-evaluating an alert for all records can bring them all up to speed to where they should be based on the current conditions of the alert. Thus, re-evaluating them might cause some notifications to be sent and/or scheduled."
alerts_259 = "If you select the alerts below and click the 'Re-evaluate' button, it will begin the process of re-evaluating each alert for *every* record in the project. NOTE: If your project contains thousands of records or more, the process may take a few minutes, so please let it finish, and do not leave the page until it completes. Additionally, if an alert has conditional logic and has the option 'Ensure logic is still true before sending notification?' checked, please be aware that any scheduled (i.e. unsent) notifications *may* get unscheduled/removed during the process of re-evaluation if the conditional logic no longer evaluates as TRUE for a given record."
alerts_260 = "Select alerts below to re-evaluate their conditions:"
alerts_261 = "<u>NOTE: Re-evaluating alerts will *NOT* modify anything for already-scheduled notifications</u>, such as email text, recipient or sender addresses, and the date/time that the notification is scheduled to be sent. <u>Re-evaluating an alert only schedules notifications that haven't been scheduled that should be scheduled</u>, and conversely, it will remove any notifications that are currently scheduled that should not be scheduled (because the alert condition no longer evaluates as TRUE)."
alerts_262 = "Please keep in mind that notifications will be sent shortly after clicking the button below if set to send 'Immediately', and if any are set to send after a certain delay, the delay will be based on when you re-evaluated the alert."
alerts_263 = "The alert will not be re-triggered if the form/survey is saved again, unless it is set to send Every time in Step 2 below."
alerts_264 = "WARNING: It is generally not recommended to use 'Using conditional logic...' in Step 1A together with the option '...on every instance of a repeating instrument' in Step 1C. If these are used together, that means that this alert will be trigger by EVERY repeating instance that is saved for ANY repeating instrument in the project."
alerts_265 = "The Alerts & Notifications feature allows you to construct alerts and send customized notifications. These notifications may be sent to one or more recipients and can be triggered or scheduled when a form/survey is saved and/or based on conditional logic whenever data is saved or imported. When adding/editing an alert, you will need to 1) set how the alert gets triggered, 2) define when the notification should be sent (including how many times), and 3) specify the recipient, sender, message text, and other settings for the notification. For the message, you may utilize customized options such as rich text, the piping of field variables (including Smart Variables), and uploading multiple file attachments."
alerts_266 = "Allow normal users to manually enter phone numbers as <u>freeform text</u> for an alert's recipient phone numbers?"
alerts_267 = "Move alert"
alerts_268 = "Move alert to another location"
alerts_269 = "select an alert"
alerts_270 = "You may move the alert listed below to any location on the current alerts listing. Choose from the drop-down below the location to which you wish to move this alert."
alerts_271 = "Alert to be moved:"
alerts_272 = "Move an alert to another location"
alerts_273 = "Move the alert above so that it will be located immediately *AFTER* the following alert:"
alerts_274 = "Reschedule existing notifications for below highlighted alert?"
alerts_275 = "[ALERT IS CURRENTLY LOCATED HERE]"
alerts_276 = "Upload or download Alerts"
alerts_277 = "Upload Alerts (CSV)"
alerts_278 = "Download Alerts (CSV)"
alerts_279 = "The alert was successfully moved to a new location!"
alerts_280 = "(Note: Your alert settings have NOT been saved yet.) Because it appears that you are modifying when notifications will be sent/scheduled when below <b><i>highlighted</i></b> alerts are triggered, it is *recommended* that you reschedule all notifications that have already been scheduled. (If you do not reschedule them, any currently scheduled notifications might never be sent.)"
alerts_281 = "Please select an alert"
alerts_282 = "You can add new Alerts to the project or update the Alert details of any existing Alert by uploading a CSV file with a new Alerts configuration. The format for the CSV upload file can be acquired by downloading the CSV file of your existing Alerts."
alerts_283 = "Select your CSV file of Alerts to be added:"
alerts_284 = "alerts were added or updated."
alerts_285 = "Invalid Unique Alert ID."
alerts_286 = "Unique Alert ID does not exists."
alerts_287 = "Invalid Unique Form Name."
alerts_288 = "Deactivated"
alerts_289 = "You can export a list of all alerts for this project. <br><br><b>Attributes returned:</b>"
alerts_290 = "View Message"
alerts_291 = "Preview Change"
alerts_292 = "Previous Message"
alerts_293 = "Updated Message"
alerts_294 = "You can upload a CSV file to add new alerts to this project and to modify existing alerts."
alerts_295 = "Please note that the format of the uploaded CSV file must be in the exact format specific above, which can be most easily seen when viewing the downloaded CSV file of the alerts. Also, if the value of field alert-unique-id is blank in the export CSV, it will add new alert in project during the import. If you wish to modify the any attributes of an alert, you should set a valid alert-unique-id for specific alert row."
alerts_296 = "Set to this when value entered in CSV does not match one of Possible Values"
alerts_297 = "Below is list of Possible Values and Default Value for specific fields in CSV. <br><b>NOTE: These values are *case insensitive*.</b> E.g. You may enter \"Submit\" or \"submit\" for value \"SUBMIT\"."
alerts_298 = "Unit at which to repeat cron while sending multiple times on a recurring basis"
alerts_299 = "Possible Values"
alerts_300 = "Default Value"
alerts_301 = "Please either correct or remove any invalid phone numbers."
alerts_302 = "Please either correct or remove invalid date time field value for \"send-on-field\"."
alerts_303 = "Date must be in the M/D/Y H:M format."
alerts_304 = "Alert sender is invalid."
alerts_305 = "Email entered to send email-failure errors is invalid."
alerts_306 = "Value entered should be integer (between 0 and 9999)."
alerts_307 = "Value entered should be integer (between 0 and 999)."
alerts_308 = "Invalid Event Unique Name."
alerts_309 = "-- Previously Saved --"
alerts_310 = "Invalid File Upload Field."
alerts_311 = "Unique Alert ID:"
alerts_312 = "<b>NOTE:</b> Alerts can be updated by simply changing the Alert details in the CSV file. Alerts <b><i>cannot be deleted or moved</i></b> using the CSV file. If you wish to delete or move an alert, please do so using the specified links for each Alert on this page. New alerts will always get added at the end, no matter where it is added in CSV file."
alerts_313 = "PLEASE NOTE that moving this alert may have caused some or all of the alerts to be re-numbered automatically. They will still retain their same alert title and unique alert ID, but their alert number (#) may have changed because alert numbers are generated on the fly based on the order of the alerts."
alerts_314 = "repeat-for should be 0 or blank if alert-send-how-many='ONCE'"
alerts_315 = "Entire log"
alerts_316 = "If conditional logic is <i>TRUE</i> when a record is saved on a specific form/survey"
alerts_317 = "When conditional logic is <i>TRUE</i> during a data import, data entry, or as the result of time-based logic"
alerts_318 = "Time-based logic"
alerts_319 = "In this description, 'time-based logic' refers to the conditional logic containing the datediff() function with 'today' or 'now' as a parameter in the function."
alerts_320 = "If a date field is selected here (as opposed to a datetime field), the time of 00:00 (midnight) will be used when determining the send time. For example, if a date field is used and the time lapse is set to be 9 hours, that means that it will be sent at 9:00AM that day. Also, please note that <b>modifying the value of this field will have no effect on invitations/alerts that have already been scheduled</b>."
alerts_321 = "If you wish to send email alerts using SendGrid Templates, read about enabling the SendGrid Template Email Services on the Project Setup page or ask your local REDCap administrator."
alerts_322 = "SendGrid Template:"
alerts_323 = "Email From:"
alerts_325 = "Please set a from email."
alerts_326 = "Please set a to email."
alerts_327 = "Please set a template ID."
alerts_328 = "SendGrid Template"
alerts_329 = "SendGrid Template Data:"
alerts_330 = "Template Data Key"
alerts_331 = "Template Data Value"
alerts_332 = "Add Template Data"
alerts_333 = "Key"
alerts_334 = "Template ID:"
alerts_335 = "Template Data:"
alerts_336 = "Invalid JSON detected in sendgrid-template-data field."
alerts_337 = "SendGrid Template Email"
alerts_338 = "Invalid API Key"
alerts_339 = "API Key does not have the required SendGrid API Scopes:"
alerts_340 = "Modify Template Data"
alerts_341 = "The Template Data Keys that you may configure above correspond to the Handlebars expressions configured in your SendGrid Template. For example, if you use the Handlebars expression <code>{{name}}</code> in your SendGrid Template, then you should configure <code>name</code> as the Template Data Key with the Template Data Value being either static text or a piped variable name (including Smart Variables) - e.g., <code>[first_name]</code>. To insert a survey link into the alert, for instance, set the Handlebars expression as <code>{{surveylink}}</code> in your SendGrid Template, and then set the Data Key and Value as <code>surveylink</code> and <code>[survey-url:instrument]</code>, respectively, in which \"instrument\" would represent whatever the unique instrument name is for your survey. Reference SendGrid's documentation on <a href='https://docs.sendgrid.com/for-developers/sending-email/using-handlebars' target='_blank'><u>Handlebars</u></a> to learn more."
alerts_342 = "Invalid From Email Format"
alerts_343 = "Invalid SendGrid From Email"
alerts_344 = "Select sender"
alerts_345 = "Missing Template ID"
alerts_346 = "Invalid Template ID"
alerts_347 = "No SendGrid Templates Found"
alerts_348 = "Sender Authentication Not Configured on SendGrid Account"
alerts_349 = "Click to learn about this option"
alerts_350 = "If you wish to send alerts as SMS Messages or Voice Calls, read about enabling the Twilio Telephony Services on the Project Setup page or ask your local REDCap administrator."
alerts_351 = "has a Template ID that is no longer valid"
alerts_352 = "In the Template Data Value field, you may use"
alerts_353 = "the exact time that the automated invitation was triggered"
alerts_354 = "the same day (beginning at midnight) that the automated invitation was triggered"
alerts_355 = "Send it based on..."
alerts_356 = "<b>Example of a repeating survey using recurring alerts:</b><br>Please complete your daily survey: [survey-link:daily_repeating_survey][new-instance]"
alerts_357 = "<b>Example:</b><br>Hi [first_name]! Please complete this survey: [survey-link:followup_survey]"
alerts_358 = "Bypass List Management"
alerts_359 = "Bypass Spam Management"
alerts_360 = "Bypass Bounce Management"
alerts_361 = "Bypass Global Unsubscribe Management"
alerts_362 = "Sandbox Mode"
alerts_363 = "SendGrid Tracking Settings:"
alerts_364 = "Click Tracking"
alerts_365 = "Open Tracking"
alerts_366 = "Subscription Tracking"
alerts_367 = "There is a maximum of 10 unique categories and each category name may not exceed 255 characters"
alerts_368 = "Bypass List Management is mutually exclusive with the other bypass options"
alerts_369 = "SendGrid Unsubscribe Groups:"
alerts_370 = "No SendGrid Unsubscribe Groups Found"
alerts_371 = "SendGrid Categories:"
alerts_372 = "ex: category_1;category_2;category_3 (Maximum of 10 Categories)"
alerts_373 = "SendGrid Mail Settings:"
alerts_374 = "Invalid JSON detected in sendgrid-mail-send-configuration field."
alerts_375 = "Invalid Unsubscribe Group ID"
alerts_376 = "Invalid SendGrid Mail Send Configuration Detected"
alerts_377 = "Invalid Categories in SendGrid Mail Send Configuration"
alerts_378 = "Invalid Bypass Settings in SendGrid Mail Send Configuration"
alerts_379 = "Invalid Value for Bypass List Management Setting"
alerts_380 = "Invalid Value for Bypass Spam Management Setting"
alerts_381 = "Invalid Value for Bypass Bounce Management Setting"
alerts_382 = "Invalid Value for Bypass Global Unsubscribe Management Setting"
alerts_383 = "Invalid Value for Sandbox Mode Setting"
alerts_384 = "Invalid Value for Click Tracking Setting"
alerts_385 = "Invalid Value for Open Tracking Setting"
alerts_386 = "Invalid Value for Subscription Tracking Setting"
alerts_387 = "Allows you to bypass all unsubscribe groups and suppressions to ensure that the email is delivered to every single recipient"
alerts_388 = "Allows you to bypass the spam report list to ensure that the email is delivered to recipients"
alerts_389 = "Allows you to bypass the bounce list to ensure that the email is delivered to recipients"
alerts_390 = "Allows you to bypass the global unsubscribe list to ensure that the email is delivered to recipients"
alerts_391 = "Sandbox Mode allows you to send a test email to ensure that your request body is valid and formatted correctly"
alerts_392 = "Allows you to track if a recipient clicked a link in your email"
alerts_393 = "Allows you to track if the email was opened by including a single pixel image in the body of the content"
alerts_394 = "Allows you to insert a subscription management link at the bottom of the text and HTML bodies of your email"
alerts_395 = "(Optional) STEP 4: Advanced SendGrid Settings"
alerts_396 = "In this section you can associate your SendGrid Template Alert with a SendGrid Unsubscribe Group defined in your SendGrid account as well as up to 10 categories. You may also configure bypass settings, tracking settings, and sandbox mode for your SendGrid Template Alert."
alerts_397 = "+ Show Advanced SendGrid Settings"
alerts_398 = "- Hide Advanced SendGrid Settings"
alerts_399 = "the exact time that the alert was triggered"
alerts_400 = "the day (beginning at midnight) that the alert was triggered"
alerts_401 = "If you wish to send alerts as SMS Messages, read about enabling the Mosio SMS services on the Project Setup page or ask your local REDCap administrator."
alerts_402 = "Enable Test Run?"
alerts_403 = "<b>Test Run mode is enabled</b>: Selected alerts will be re-evaluated in a sandbox-like environment, which will allow you to view which records *would be* affected by the re-evaluation <b>without actually sending or scheduling any alerts</b>. With the test run enabled, no records will be affected during the re-evaluation."
alerts_404 = "Re-eval Results (Test Run)"
alerts_405 = "Reset alert before saving changes?"
alerts_406 = "(Note: Your alert settings have NOT been saved yet.) Because it appears that you are modifying when notifications will be sent/scheduled when this alert is triggered, it is *recommended* that you reset/invalidate existing scheduled notifications for this alert. (If you do not invalidate them, any currently scheduled notifications might never be sent.) <br> <b>NOTE: You must still Re-evaluate Alerts after this step in order for your saved changes to take effect.</b>"
alerts_407 = "Yes, Reset Alert & Save"
alerts_408 = "No, Just Save Alert"
alerts_409 = "Download list of affected records"
alerts_410 = "No records were actually affected."
alerts_411 = "[Current Event]"
missing_data_01 = "Mark field as:"
missing_data_02 = "[Clear value]"
missing_data_03 = "Mark field as missing"
missing_data_04 = "Missing Data Codes"
missing_data_05 = "Remove missing data codes from export"
missing_data_08 = "Missing Data Codes: Set up your missing data codes for this project"
missing_data_09 = "Fields that have a blank/missing value may be marked with a custom 'Missing Data Code' to note why the value is blank. These missing codes may be used to aid in data analysis by specifying why a field lacks a value. To enable this feature below, enter both the codes AND their labels for all the categories of missing data that you wish to use in this project. The missing codes should be coded just like the choices of a multiple choice field with <i>code + comma + label</i>, in which the codes can only have letters, numbers, dots, dashes, and underscores (e.g., '-999, Not asked' or 'UNK, Unknown'). If no codes are entered, this feature will remain disabled."
missing_data_10 = "Add code from standardized list of missing data codes (optional suggestions):"
missing_data_11 = "USAGE: After your missing data codes have been set up, you will see an 'M' icon next to each field when viewing a data entry form. Click the icon to open your list of missing data codes, and select one. Once selected, it will save the missing code as the literal data value for the field. Missing data codes can be used for any field type (e.g., date, slider, file upload fields). Since a missing data code is saved as the field value, this means that the field's missing data code can then be optionally exported in a data export or viewed in a report (if you so choose - this is an option when creating a report). Entering a missing data code must be done manually by a user via the user interface or through a data import (API or Data Import Tool), in which you may import the missing data codes as the fields' values in your data import file."
missing_data_12 = "Missing Data Code entered:"
missing_data_13 = "Note: Values listed as 'Missing' may include records with a Missing Data Code (if Missing Data Codes are defined)."
missing_data_14 = "Display any Missing Data Codes in place of blank values (where applicable)"
missing_data_15 = "Additional instructions and notes:"
missing_data_16 = "TIP: When defining your missing data codes, please keep in mind to make sure that your missing code will never clash/overlap with a real value on a field in your project. For example, it you have an integer field where '-999' is a possible value, then you should not use -999 as a missing data code. This is because REDCap will not be able to know if this is a real value or if it is a missing code used to denote that the field is blank. Below to the right are some optional suggestions for missing data codes that you might consider using, but feel free to use whatever missing data codes that you wish."
missing_data_17 = "NOTE: Behavior with branching logic - If a field should be hidden by branching logic, REDCap will typically ask the user (except on surveys) if they wish to delete the value of the field being hidden. But if the field has a missing data code saved for it, it will still hide the field but will not remove the missing data code as the field’s value. This allows a field to still be 'blank' and have a missing code while being hidden by branching logic."
missing_data_18 = "LOGIC: Because missing data codes are stored as the literal field values, they may be used and referenced in logic throughout REDCap (i.e., logic for report filters, Data Quality rules, Survey Queue, Automated Survey Invitations, branching logic). For example, if you want to display a field on a form only if the previous field is blank and is marked with the missing data code 'NASK', your branching logic might be the folowing: [field] = 'NASK'. Additionally, a special function 'isblankormissingcode()' may be used in logic as a catch-all for determining if a field's value is truly blank or if it contains a missing data code. E.g. isblankormissingcode([age]), in which if age has a value of UNK (which might be a missing data code in a project), then it will return TRUE. And if the field has any non-blank/non-null value that is also not a missing data code, it will return FALSE."
missing_data_19 = "ACTION TAG: By default, the missing data code functionality is enabled for ALL fields in the project, but it can be disabled on a field-by-field basis by adding the action tag @NOMISSING for an individual field, in which this will hide the 'M' icon for the field on the data entry form and thus prevent usage of the missing data codes for the field."
missing_data_20 = "Modify missing data codes"
missing_data_21 = "Please note that re-labeling or removing any Missing Data Codes that are in use in a production project where data collection has already begun could result in data issues. It is recommended that you only add new Missing Data Codes and not remove or re-label any existing ones if some data has already been collected in the project."
missing_data_mdc_ni = "No information"
missing_data_mdc_inv = "Invalid"
missing_data_mdc_unk = "Unknown"
missing_data_mdc_nask = "Not asked"
missing_data_mdc_asku = "Asked but unknown"
missing_data_mdc_nav = "Temporarily unavailable"
missing_data_mdc_msk = "Masked"
missing_data_mdc_na = "Not applicable"
missing_data_mdc_navu = "Not available"
missing_data_mdc_np = "Not present"
missing_data_mdc_qs = "Sufficient quantity"
missing_data_mdc_qi = "Insufficient quantity"
missing_data_mdc_trc = "Trace"
missing_data_mdc_unc = "Unencoded"
missing_data_mdc_der = "Derived"
missing_data_mdc_pinf = "Positive infinity"
missing_data_mdc_ninf = "Negative infinity"
missing_data_mdc_oth = "Other"
auth_01 = "Shibboleth & Table Splash Page Customization:"
auth_02 = "Default login method"
auth_03 = "Table login selection title"
auth_04 = "Clickable text to use table-based login"
auth_05 = "Shibboleth Login Options"
auth_06 = "Shibboleth login selection title"
auth_07 = "Clickable text to use Shibboleth login"
auth_08 = "Shibboleth login descriptive text"
auth_09 = "Descriptive text displayed with Shibboleth login"
auth_10 = "Shibboleth Link Image URL"
auth_11 = "URL for image to be displayed to link to server's Shibboleth login"
auth_12 = "URL for Shibboleth SP Session Initiator"
auth_13 = "Additional IdP Controls"
auth_14 = "Add IdP"
auth_15 = "Delete This IdP"
auth_16 = "If left blank, will default to the value stored in $_SERVER['Shib-Handler']"
mapping_helper_01 = "EHR Mapping Helper"
mapping_helper_02 = "The Mapping Helper utility will assist you in finding the fields in your EHR (electronic health record system) that you would like to utilize in your Clinical Data Pull project or Clinical Data Mart project. If you already have appropriate privileges for pulling data into REDCap from your EHR, you may enter a valid MRN (medical record number) into any of the tabs in the Mapping Helper to pull all the data for that patient for those data categories. Once the data is pulled, it will be displayed on the page for you to view. The EHR field names and LOINC codes will be displayed, thus allowing you to find the specific fields you need to use during the field mapping process of your CDP or Data Mart project."
break_the_glass_settings_01 = "Break-the-Glass"
break_the_glass_disabled = "Disabled"
break_the_glass_enabled = "Enabled"
break_glass_description = "Once Break-the-Glass is enabled for the system, the user will not be required to login into Hyperspace to break the glass for a patient. All Break-the-Glass requests are logged both in REDCap and in Epic."
break_glass_ehr = "The type of the EHR user that REDCap has mapped to the current user in the EHR launch process"
break_glass_usertype_ehr = "The type of user used in Epic - typically \"External\""
break_glass_003 = "\"Break-the-Glass\" feature (for Epic only)"
break_glass_004 = "Break-the-Glass (which draws its name from breaking the glass to pull a fire alarm) refers to a quick means for a person who does not have access privileges to certain information to gain access when necessary.<br/><br/>In Epic, the Break-the-Glass procedure is used to control and monitor access to sensitive data. "
break_glass_007 = "EHR User type"
break_glass_project_setup_enable_header = "Break-the-Glass settings for this project (Administrators only)"
break_glass_project_setup_enable_text = "By default, users cannot perform a \"Break-the-Glass\" when REDCap detects a protected patient. As an administrator, by clicking the buttons below you may grant project users the privilege to use the \"Break-the-Glass\" feature."
break_glass_project_setup_enable_button_info = "Users are able to \"Break-the-Glass\""
dash_01 = "Create New Dashboard"
dash_02 = "Dashboard name"
dash_03 = "View"
dash_04 = "Dashboard options"
dash_05 = "Project Dashboards are pages with dynamic content that can be added to a project. They can utilize special Smart Variables called <b>Smart Functions, Smart Tables, and Smart Charts</b> that can perform aggregate mathematical functions, display tables of descriptive statistics, and render various types of charts, respectively. Project dashboards have two basic attributes: a title and a body. User access privileges are customizable for each dashboard, and anyone with Project Design privileges can create and edit them. A wizard is provided on the Project Dashboard creation page to help you easily construct the syntax to add Smart Functions, Smart Tables, or Smart Charts to your dashboards, and a list of helpful examples is also included."
dash_06 = "My Project Dashboards"
dash_07 = "The table below lists all the users in this project who will have access to this dashboard based upon your selections in the Custom User Access section."
dash_08 = "Dashboard title:"
dash_09 = "Dashboard content:"
dash_10 = "Add any static or dynamic text to be displayed, including Smart Functions, Smart Tables, and Smart Charts."
dash_11 = "(Note: Users with Setup/Design privileges can still access all dashboards via the Project Dashboards page.)"
dash_12 = "Choose who sees this dashboard on their left-hand project menu"
dash_13 = "View a list of users who will have access to this dashboard based on the selections above:"
dash_14 = "<b>Set as \"public\":</b> Project dashboards may also be optionally set as \"public\", which means that they can be viewed outside of the REDCap project <u>by anyone with the unique link to the public dashboard</u> (i.e., without logging in). To help protect potentially sensitive data being displayed on public dashboards, any Smart Function, Smart Table, or Smart Chart displayed on the public version of the dashboard will not be rendered unless they are utilizing/displaying at least"
dash_15 = "You have not provided a title for the dashboard. Please enter a title and try again."
dash_16 = "No users have been given access to this dashboard. Please select some users in the User Access section and try again."
dash_17 = "You have not provided any content for the body for the dashboard. Please add some content and try again."
dash_18 = "The dashboard named"
dash_19 = "Your dashboard has been saved!"
dash_20 = "Continue editing dashboard"
dash_21 = "Return to My Dashboards"
dash_22 = "View dashboard"
dash_23 = "COPY DASHBOARD?"
dash_24 = "Are you sure you wish to COPY the dashboard named"
dash_25 = "DELETE DASHBOARD?"
dash_26 = "Are you sure you wish to DELETE the dashboard named"
dash_27 = "Drag report up or down to move it"
dash_28 = "Add<span style='margin:0 1px;'>/</span>Edit"
dash_29 = "Save Dashboard"
dash_30 = "Edit existing dashboard"
dash_31 = "Export as PDF"
dash_32 = "Set as \"public\":"
dash_33 = "Enabling this feature below will auto-generate a public link for viewing the dashboard without needing to log in to REDCap."
dash_34 = "Dashboard is publicly viewable by anyone with the public link"
dash_35 = "Public"
dash_36 = "ERROR: This is not a valid project dashboard in REDCap."
dash_37 = "User access:"
dash_38 = "Public link:"
dash_39 = "[Note: The dashboard must be saved first before its public link can be generated.]"
dash_40 = "Create Custom Dashboard Link"
dash_41 = "You may create a short and easy to remember custom URL that redirects to your public dashboard. <b>Enter the your desired custom URL</b> that you wish to redirect to your public dashboard. When submitted, it will check if the URL has already been taken. If not, it will save the custom URL here in your project so that you may continue to use it."
dash_42 = "Create custom link"
dash_43 = "Custom link:"
dash_44 = "Are you sure you want to remove the custom dashboard link?"
dash_45 = "SUCCESS! The custom dashboard link was successfully removed."
dash_46 = "SUCCESS! The following custom dashboard link was successfully created:"
dash_47 = "NOTE: Please be advised that even though it has been removed and is no longer associated with this dashboard, if anyone still possesses that custom link and attempts to use it, it will still function and will redirect to this dashboard. However, you can generate another more preferable custom link for this project dashboard, if you wish."
dash_48 = "Use the Wizard"
dash_49 = "Dashboard help:"
dash_50 = "This dashboard is no longer publicly available."
dash_52 = "Public link"
dash_53 = "Displaying information generated"
dash_54 = "minutes ago"
dash_55 = "Export table (CSV)"
dash_56 = "minute ago"
dash_57 = "Displaying recently generated information"
dash_60 = "Yes, allow users to make dashboards public on their own"
dash_61 = "No, do not allow public dashboards"
dash_62 = "Yes, but an administrator must approve the request"
dash_63 = "Allow project dashboards to be made 'public'?"
dash_64 = "If set to allow public dashboards after approval by an admin, the admin will receive the request from the user via the To-Do List page (or via email, if setting is enabled), and after the admin approves/disapproves the request, the user will receive an email regarding the response to their request."
dash_65 = "If a project dashboard is made public, it can be accessed at a unique URL that does not require any authentication."
dash_67 = "This setting represents the system-level value applied to all projects. However, you may override this setting for an individual project on the 'Edit Project Settings' page."
dash_68 = "[INSUFFICIENT AMOUNT OF DATA FOR DISPLAY]"
dash_69 = "The data cannot be displayed on this public dashboard because there exist fewer than"
dash_70 = "data points. Once that minimum requirement has been met, the data can be displayed here."
dash_71 = "INSUFFICIENT AMOUNT OF DATA"
dash_72 = "Enable color-blind accessibility"
dash_73 = "Disable color-blind accessibility"
dash_74 = "NOTE: Setting this dashboard as \"public\" requires approval from an administrator."
dash_75 = "You may set this dashboard as \"public\" because you are an administrator."
dash_76 = "Set the project dashboard below to be \"public\", which means it will be publicly viewable by anyone with a link to the dashboard?"
dash_77 = "Make project dashboard public?"
dash_78 = "Set as public"
dash_79 = "Project dashboard:"
dash_80 = "SUCCESS! The project dashboard was successfully set as \"public\"."
dash_81 = "Click chart to view as fullscreen"
dash_82 = "Request to enable public dashboard"
dash_83 = "A user has requested that a project dashboard be made \"public\", which means that the dashboard would be publicly viewable by anyone with a link to the dashboard (i.e., with no authentication required to view it). As an administrator, you may click the link below to approve their request, which will make their dashboard public and then will notify the requester of the approval."
dash_84 = "APPROVE REQUEST to make the project dashboard public"
dash_85 = "Your public dashboard request was successfully sent to a REDCap administrator. You will receive an email notification when they have approved your request. Thank you!"
dash_86 = "NOTICE: This project dashboard has already been made public, so there is nothing to do here."
dash_87 = "Project dashboard has been made public"
dash_88 = "As requested, your project dashboard below has been made PUBLIC for the project"
dash_89 = "You may access your dashboard using the link below."
dash_91 = "Examples of Smart Functions, Smart Tables, and Smart Charts:"
dash_92 = "Wizard for creating Smart Functions, Smart Tables, and Smart Charts"
dash_93 = "Step 4) Copy the generated Smart Variable syntax and paste it in your project dashboard:"
dash_94 = "Step 1) Choose a Smart Variable to create:"
dash_95 = "Step 2) Choose a field to utilize:"
dash_96 = "Add another field"
dash_97 = "Step 3) Optional data filtering and other settings:"
dash_98 = "Filter the data using a report:"
dash_99 = "Table columns to display:"
dash_100 = "All columns (default)"
dash_101 = "-- no filtering by report -- "
dash_102 = "-- no filtering by data access group -- "
dash_103 = "Filter the data using DAGs:"
dash_104 = "-- no filtering by event -- "
dash_105 = "Filter the data using events:"
dash_106 = "Remove field"
dash_107 = "This wizard can help you create a new Smart Function, Smart Table, or Smart Chart that you can then use in a Project Dashboard. Simply make selections using the drop-down lists below regarding which Smart Variable you wish to use, which fields to be utilized in it, and other optional features available. Once your selections have been made, you may click the 'Copy to clipboard' button at the bottom, after which you may paste that generated text into the body of your Project Dashboard."
dash_108 = "Current user's DAG"
dash_109 = "data points."
dash_110 = "<b>Data filtering:</b> By default, Smart Functions, Smart Tables, and Smart Charts will utilize all the data from *all records* in the project. However, you may utilize a subset of the data in the project by limiting them to a specific report's data (using a unique report name), to records belonging to one or more DAGs, and/or to data in specific events (if the project is longitudinal). Unique report names can be found for each report listed on the \"My Reports & Exports\" page. You can append the unique report names, unique DAG names, and unique events names to any Smart Function, Smart Table, or Smart Chart using the syntax described in the"
dash_111 = "Smart Variables documentation"
dash_112 = "By default, Smart Functions, Smart Tables, and Smart Charts will utilize all the data from *all records* in the project. However, you may utilize a subset of the data in the project by limiting them to a specific report's data (using a unique report name), to records belonging to one or more DAGs, and/or to data in specific events (if the project is longitudinal)."
dash_114 = "For privacy reasons, you may adjust the minimum amount of data points required when viewing a public project dashboard, public report, or survey page that contains Smart Charts, Smart Tables, or Smart Functions. Thus if any given Smart Chart, Smart Table, or Smart Function on a public project dashboard, public report, or survey page does not meet the minimum requirements, it will not output the chart, table, or value, respectively, but will instead output the text '[INSUFFICIENT AMOUNT OF DATA FOR DISPLAY]'. Note: This privacy setting does not apply to dashboards or reports being viewed from inside a REDCap project but only when viewing them via their public link."
dash_115 = "Public Reports, Project Dashboards, Smart Charts, Smart Tables, and Smart Functions"
dash_116 = "Allow reports to be made 'public'?"
dash_117 = "If a report is made public, it can be accessed at a unique URL that does not require any authentication. Users must have 'User Rights' privileges in the project in order to make a report public or to request an admin to do so. Once a report has been made public, the public link to the report will only be accessible to users in the project with 'User Rights' privileges. Note: <u>administrators will always have the ability to make a report public</u> regardless of the setting here."
dash_118 = "Before a user or admin (depending on the selection above) makes a report public, they must do and agree to ALL of the following:"
dash_119 = "No, do not allow reports to be made public"
dash_120 = "Yes, allow users to make reports public on their own"
dash_121 = "Must view the report being made public beforehand."
dash_122 = "Must acknowledge that they understand that making the report public means that all data in the report will be fully accessible to anyone with the public link to the report."
dash_123 = "Must acknowledge that they are responsible if any private, sensitive, or identifying data in the report is exposed to persons who should not have access to such data."
dash_124 = "Minimum number of data points required to display Smart Charts, Smart Tables, or Smart Functions on a *public* Project Dashboard, *public* report instructions, survey queue custom text, or any place on a survey page."
dash_125 = "NOTE: You cannot reference a report with DAGs or events together in a single Smart Charts, Smart Tables, or Smart Functions. If you wish to filter the data via a report and DAGs/events, it is recommended that you simply add the DAG/event filtering to the report filter itself by editing the report."
dash_126 = "You may optionally provide custom email text in the two editors below for any emails sent to users regarding the upcoming expiration of their REDCap account.  You may specify this for users that do not have a sponsor and also for users that do have a sponsor. These emails serve as reminders 2 days before and also 14 days before a user's account will expire.  <b>NOTICE: If no custom text is provided below, REDCap will simply use stock email text for the account expiration emails to users.</b>"
dash_127 = "Custom Account Expiration Email (Users without a Sponsor)"
dash_128 = "Enter the custom email text below for users who do not have a sponsor. You may utilize the Dynamic Variable menu to personalize the email content, if you wish. These variables will be automatically replaced with corresponding user's information when the email is sent."
dash_129 = "Custom Account Expiration Email (Users with a Sponsor)"
dash_130 = "Enter the custom email text below for users who have a sponsor. You may utilize the Dynamic Variable menu to personalize the email content, if you wish. These variables will be automatically replaced with corresponding user's information when the email is sent."
dash_131 = "Account Expiration: Email Templates (optional)"
dash_132 = "Search by title"
dash_133 = "Project Dashboard Folders"
dash_134 = "Project Dashboard Folders are a way to organize your dashboards by putting them into groups. You may create new folders below and then assign dashboards to them on the right. A project dashboard can be assigned to multiple folders at the same time. To reorder your folders, you can drag and drop them in the left-hand table. Note: All users in this project will be able to see the folders as long as they have 'View Access' to at least one dashboard in the folder."
dash_135 = "My Dashboard Folders"
dash_136 = "STEP 2: Assign Your Dashboards To Folders"
dash_137 = "Hide dashboards already assigned"
dash_138 = "Select dashboards below to add to this folder"
queue_system_monitor_menu = "Queue Monitor"
queue_system_monitor_page_title = "Queue Monitor"
queue_system_monitor_page_description = "Queues allow REDCap to defer the processing of a time consuming task, such as sending an email, until a later time. Deferring these time consuming tasks drastically speeds up web requests. REDCap uses a cron job to check the <em>queue</em> every minute and creates a <em>worker</em> if any <em>message</em> 'waiting' to be processed is found. The <em>worker</em> translates each <em>message</em> into a <em>task</em> and starts processing it (FIFO). If after a minute the <em>worker</em> has not processed all the <em>messages</em> in the <em>queue</em>, another <em>worker</em> will be created to help. If a <em>worker</em> has been working for more than 10 minutes it will not process any further <em>message</em>; this helps avoiding 'Maximum execution time' errors. A maximum of 5 <em>workers</em> can run at the same time by default, but this number can be increased."
cdp_auto_adjudication_settings_title = "Instant adjudication"
cdp_auto_adjudication_settings_label = "Instant adjudication"
cdp_auto_adjudication_settings_description = "Temporal fields may have multiple values returned from the external source system; once you set a \"preselect\" value for ALL your mappings, you can enable 'instant adjudication' and REDCap will skip the 'adjudication' table preview and save the best or most correct value."
ws_119_02 = "Up to 5 source EHR fields can be configured to display a preview of the matched patient record. When entering an MRN in REDCap, these selected fields will display the corresponding EHR data, allowing users to verify they have identified the correct patient record."
cdp_auto_adjudication_settings_title_02 = "Adjudication method"
cdp_auto_adjudication_settings_label_02 = "Adjudication method"
cdp_adjudication_metod_manual_title = "Manual"
cdp_adjudication_metod_manual_description = "The data pulled for each record is manually reviewed and “accepted”."
cdp_adjudication_metod_instant_title = "Instant"
cdp_adjudication_metod_instant_description = "Rather than reviewing every record individually, the user can apply all pending pulled EHR data in one step."
cdp_adjudication_metod_automatic_title = "Automatic"
cdp_adjudication_metod_automatic_description = "This option automatically applies (saves) all data pulled from the EHR to the REDCap records without user intervention"
cdp_auto_adjudication_settings_description_02 = "Temporal fields may have multiple values returned from the external source system; once you set a \"preselect\" value for ALL your mappings, you can enable 'instant adjudication' and REDCap will skip the 'adjudication' table preview and save the best or most correct value."
cdp_auto_adjudication_settings_description1 = "Adjudication refers to the process of reviewing and determining which values to accept when multiple values are returned from an external source system for temporal fields. REDCap offers different methods for adjudication: <code>Manual</code>, <code>Instant</code> and <code>Auto</code>."
cdp_auto_adjudication_settings_note = "Note: The <code>Instant</code> and <code>Auto</code> methods can only be used if a 'preselect' strategy has been assigned to all temporal fields, ensuring the most appropriate value is chosen without manual review."
cdp_total_selected_fields = "{{fields}} temporal fields out of {{total_fields}} are set"
cdp_setup_table_header_external_source = "External Source Field"
cdp_setup_table_header_event = "Event"
cdp_setup_table_header_field = "Field"
cdp_setup_table_header_date = "Date/Time Field"
cdp_setup_table_header_preselect_strategy = "Preselect Strategy"
cdp_setup_table_header_actions = "Actions"
cdp_instant_adjudication_enabled = "Enabled"
cdp_instant_adjudication_disabled = "Disabled"
cdp_instant_adjudication_disabled_description = "Instant adjudication can only be enabled when all temporal fields have been set"
cdp_instant_adjudication_enabled_text = "Enable instant adjudication"
cdp_instant_adjudication_disabled_text = "Disable instant adjudication"
cdp_preview_add_another_field = "Add another preview field"
cdp_mapping_form_label_fhir_field = "FHIR field"
cdp_mapping_form_label_redcap_event = "REDCap Event"
cdp_mapping_form_label_redcap_field = "REDCap Field"
cdp_mapping_form_label_date_time = "Date/Time"
cdp_mapping_form_label_preselect_strategy = "Preselect Strategy"
cdp_unsaved_changes_warning_title = "You have unsaved changes"
cdp_unsaved_changes_warning_description = "Do you want to save before leaving?"
cdp_unsaved_changes_warning_save_button = "Save Changes"
cdp_unsaved_changes_warning_discard_button = "Discard Changes"
cdp_unsaved_changes_warning_cancel_button = "Stay on Page"
cdp_record_identifier_section_title = "Record Identifier Field (Required)"
cdp_record_identifier_description = "Select a field that will act as the unique identifier, such as a medical record number (MRN). This field must accurately match the patient's MRN in the EHR to enable data retrieval."
cdp_record_identifier_mrn_label = "EHR MRN/ID"
cdp_record_identifier_redcap_event_label = "REDCap Event"
cdp_record_identifier_redcap_field_label = "REDCap Field"
cdp_record_identifier_note = "Configuring the correct MRN field is essential for accurate data linkage. Verify that this field is properly formatted and consistent with EHR data standards to ensure smooth data retrieval."
cdp_mappings_export_title = "Mappings Export"
cdp_mappings_export_description = "Your data is ready to be downloaded!"
cdp_mappings_export_note = "Note: Exported data includes the record identifier along with other mapped fields."
cdp_mappings_export_download_link = "click here to download"
cdp_incorrect_adjudication_strategy_warning_title = "Warning"
cdp_incorrect_adjudication_strategy_warning_message = "The selected adjudication method requires a preselect strategy for all temporal fields. Since not all preselect strategies are set, the adjudication method will automatically switch to <code>Manual</code> if you continue."
cdp_setup_intro = "To set up this feature, follow these steps:"
cdp_setup_settings_title = "Set Up Settings"
cdp_setup_settings_description = "Begin by configuring optional preview fields, setting the default day offset for temporal data, and selecting an adjudication method. These settings will customize how data from the EHR is processed and displayed."
cdp_record_identifier_title = "Choose the Mandatory Record Identifier"
cdp_create_mappings_title = "Create Mappings"
cdp_create_mappings_description = "Map fields from the external source system to corresponding fields in your REDCap project. This allows REDCap to know which data to import from the EHR and where to store it."
cdp_data_import_info = "Once mappings are created, REDCap will be able to import data from the source system as soon as a record is given a value for its Source Identifier Field. Data from the EHR will be fetched immediately on a data entry form or on the Record Status Dashboard, and additional data checks will occur at regular intervals."
multilang_01 = "Multi-Language Management"
multilang_02 = "Change language"
multilang_03 = "Allows you to capture the currently used language in projects where multilingual data is enabled on data entry forms. The @LANGUAGE-CURRENT-FORM action tag can be used on fields of type 'Text Box' (no validation), and 'Drop-down List', or 'Radio Buttons' (these need to have choices whose codes correspond to the IDs of the defined languages - e.g., 'en'). This action tag is only active on data entry forms and will always, when possible, set the field's value to the currently active language. However, it has no effect when viewing survey responses."
multilang_04 = "Exclude"
multilang_05 = "<span class='badge badge-secondary shortcut fs11' title='On Mac, use CMD-G'>CTRL-G</span> – Go to field:"
multilang_06 = "– <i>Empty</i> –"
multilang_07 = "Add a new language"
multilang_08 = "System languages can be defined below, after which they will become available to import into any project for the User Interface translations only. Modifying any languages on this page will not affect existing projects but only project created hereafter. The default language is the language that is shown when no user language preference is found."
multilang_09 = "Currently, there are no languages set up in this project."
multilang_10 = "Currently, there are no system languages configured."
multilang_11 = "<b>Disable</b> (i.e. turn off) multi-language support for this project"
multilang_12 = "<b>Disable</b> (i.e. turn off) multi-language support for <b>all</b> projects"
multilang_13 = "WARNING: THIS WILL AFFECT ALL PROJECTS!"
multilang_15 = "Highlight untranslated text on <b>Data Entry</b> pages that should be translated"
multilang_16 = "Highlight untranslated text on <b>Survey</b> pages that should be translated"
multilang_17 = "<b>Debug mode</b> (status messages will be output to the browser console)"
multilang_18 = "Admin-only settings"
multilang_19 = "Add New Language"
multilang_20 = "Edit Language"
multilang_21 = "Language ID"
multilang_22 = "Enter a unique ID for this language"
multilang_23 = "The language ID is invalid or, when adding a new language, may already exist."
multilang_24 = "A unique identifier (case-insensitive) for this language. It is recommended to use the ISO code, such as '<b>en</b>' or '<b>en-US</b>' for English, or '<b>es</b>' for Spanish. <b>Use only letters and hyphen.</b>"
multilang_25 = "Display Name"
multilang_26 = "Enter a display name"
multilang_27 = "You must provide a value."
multilang_28 = "This is the name of the language as shown in the language selectors. This should be entered in its language, such as '<b>English</b>' or '<b>Deutsch</b>' (for German)."
multilang_29 = "Sort Override (optional)"
multilang_30 = "Provide alternate name for sorting purposes"
multilang_31 = "If set, this will be used instead of the display name for determining the sort order of languages in language selectors."
multilang_33 = "from a file (JSON, CSV, or INI)"
multilang_35 = "This is not a valid language file."
multilang_36 = "from available system languages"
multilang_37 = "There are no system languages available."
multilang_38 = "Import options:"
multilang_39 = "When merging,"
multilang_40 = "keep local values"
multilang_41 = "use imported values"
multilang_42 = "Import empty values <i>(clears local values)</i>"
multilang_43 = "Add Language"
multilang_44 = "Apply Changes"
multilang_45 = "Delete Language?"
multilang_46 = "When a language is deleted, all associated instrument/survey and user interface translations will be deleted from this project permanently. <b>This cannot be undone.</b><br><br>Are you sure you want to delete this language?"
multilang_47 = "When a language is deleted, all associated user interface translations will be deleted permanently. <b>This cannot be undone.</b> Projects currently using this language are not affected.<br><br>Are you sure you want to delete this language?"
multilang_48 = "Delete Language"
multilang_49 = "Filter items on this page:"
multilang_50 = "Search for anything…"
multilang_51 = "Hide translated items"
multilang_52 = "Initializing ..."
multilang_53 = "Show less."
multilang_54 = "Learn more."
multilang_55 = "On this page you can create and configure multiple display languages for your project (for surveys, data entry forms, alerts, survey invitations, etc.) or alternatively export and import translations using a file. Do not forget to <b>save your changes</b> (keyboard shortcut: <span class='badge badge-secondary shortcut fs11' data-bs-toggle='tooltip' title='On Mac, use CMD-S'>CTRL-S</span>) at any time on this page when you are done editing. NOTE: <u>This page will not auto-translate your text for you</u>, but provides tools so that you may easily translate them yourself."
multilang_56 = "On this page you can create and configure multiple display languages available on this REDCap installation that are available for projects to use for their User Interface translations. When used in a project, user interface translations defined here will be copied to the project and can be freely customized there. Do not forget to <b>save your changes</b> (keyboard shortcut: <span class='badge badge-secondary shortcut fs11' data-bs-toggle='tooltip' title='On Mac, use CMD-S'>CTRL-S</span>) at any time on this page when you are done editing. NOTE: This page <u>will not auto-translate</u> your text for you, but provides tools so that you may easily translate them yourself."
multilang_57 = "<b>This is the default language.</b> Thus, items cannot be edited here, but they can be modified in the <i>Online Designer</i> (or via <i>Data Dictionary</i> upload) and the <i>Survey Settings</i> page. However, fields and individual survey settings can be set to be excluded from translation here. <b>If you wish to begin/continue translating the default language text, click a language button above.</b>"
multilang_58 = "Custom Survey Queue Text"
multilang_59 = "Custom Survey Login Error Message"
multilang_61 = "There are no translatable fields on this form. They may have been excluded from translation."
multilang_63 = "Survey Settings"
multilang_65 = "Multi-Langauage Management is currently <b>turned off</b> system-wide. In all projects, surveys and data entry forms are currently <b>not</b> translated and the Multi-Language Mangagement menu is not visible."
multilang_66 = "Changes have been saved."
multilang_67 = "Languages"
multilang_68 = "Forms/Surveys"
multilang_69 = "Alerts"
multilang_70 = "Misc"
multilang_71 = "User Interface"
multilang_72 = "Settings"
multilang_73 = "ID"
multilang_75 = "Default"
multilang_76 = "Fallback"
multilang_77 = "RTL"
multilang_78 = "Visible"
multilang_79 = "ASIs"
multilang_80 = "Translate the instrument's name"
multilang_83 = "Translate"
multilang_84 = "Excluded"
multilang_85 = "Check to exclude this field from being translated"
multilang_86 = "Check to mark this field as translated"
multilang_87 = "Check to mark this matrix as translated"
multilang_89 = "Enter translation"
multilang_90 = "Rich Text Editor"
multilang_91 = "Translation"
multilang_92 = "Setting"
multilang_93 = "Check to exclude this setting from being translated"
multilang_94 = "Default text:"
multilang_95 = "Mark this translation as adequate for the changed default text"
multilang_96 = "Copy the default text to the clipboard"
multilang_97 = "Export Language"
multilang_98 = "Please choose what to include in the export file, and set export options."
multilang_100 = "Success"
multilang_101 = "Import language data ..."
multilang_102 = "The language '{0}' is not available."
multilang_103 = "There are no items matching the current filter criteria."
multilang_104 = "<b>ATTENTION:</b> The underlying project data has changed since this page was loaded. It is suggested that you save any unsaved changes and then reload this page before you make any further changes."
multilang_105 = "-- Select an option --"
multilang_106 = "Paste the default text"
multilang_107 = "Translation of the instrument name:"
multilang_108 = "H:M"
multilang_109 = "Y-M-D"
multilang_110 = "M-D-Y"
multilang_111 = "D-M-Y"
multilang_112 = "Y-M-D H:M"
multilang_113 = "M-D-Y H:M"
multilang_114 = "D-M-Y H:M"
multilang_115 = "Y-M-D H:M:S"
multilang_116 = "M-D-Y H:M:S"
multilang_117 = "D-M-Y H:M:S"
multilang_120 = "Use this feature to set a source for a participant's language preference (their initial language setting). This must be a radio or dropdown field with choices matching the language <code>ID</code> you have defined for each language above, or a text box field with no field validation. The value of this field can be set manually through data entry/data import or with the <code>@LANGUAGE-CURRENT-FORM/SURVEY</code> action tags. The value of this setting will dictate the language used for rendering Automated Survey Invitations, Alerts, and PDFs."
multilang_121 = "Language preference field:"
multilang_122 = "-- Select a field --"
multilang_123 = "<b>NOTE:</b> Similar to a designated email field, when this field exists on multiple events in longitudinal projects, on a repeating instrument, or on a repeating event, the field's value will be synchronized across all instances/events so that changing it in one location will change the value across all events/instances where the field appears."
multilang_124 = "<b>Warning:</b> The field's options do not include all active languages!"
multilang_125 = "When used on a field, the data entry form or survey on which the field is located will be rendered in the specified language (which must have been set up using the Multi-Language Management feature). The format must follow the pattern @LANGUAGE-FORCE=\"???\", in which the ID of the desired language should be inside single or double quotes - e.g., @LANGUAGE-FORCE=\"de\". Piping is supported - e.g., @LANGUAGE-FORCE=\"[field_name]\" (if the source field is a radio field, make sure to add the <i>:value</i> qualifier). When the language is forced successfully (i.e., it exists and is active), the language selector is hidden. This action tag is evaluated when the form or survey loads. Using this together with @LANGUAGE-CURRENT-FORM/SURVEY on the source field for @LANGUAGE-FORCE may be used to 'lock in' a user to their selected language."
multilang_126 = "Same as @LANGUAGE-FORCE, but the effect is limited to data entry forms (i.e., this does not affect surveys)."
multilang_127 = "Same as @LANGUAGE-FORCE, but the effect is limited to surveys (i.e., this does not affect data entry forms)."
multilang_128 = "Include translation prompts"
multilang_129 = "Include default values"
multilang_130 = "This will export the user interface translations for this language. Optionally, the translation prompts and the default values (from the currently active language file) can be included (e.g., when the file is not purely intended for transfer or backup purposes)."
multilang_131 = "<i>Export Options:</i>"
multilang_132 = "<i>NOTE:</i> The export will reflect the currently <b>SAVED</b> state only. Thus, any unsaved changes will <b>NOT</b> be contained in the export file."
multilang_133 = "<i>Include the following:</i>"
multilang_134 = "Translations of user interface items"
multilang_135 = "Translations of field items"
multilang_138 = "Thus, a cross-project import of field translations would only work for fields of the same name."
multilang_140 = "Use this page to manage which instruments will be translated, separately in data entry and survey modes. Furthermore, use it to navigate to the various sub-pages, such as field exclusions (default language only), or translations of field items (labels, etc.), survey settings (title, instructions, etc.) and ASI emails."
multilang_141 = "Defaults"
multilang_142 = "Processing file ..."
multilang_143 = "Failed to parse .ini file."
multilang_144 = "When used on a Drop-down or Radio Button field only, this action tag will allow the field's value to control the currently shown language (in the same way as switching the language via the buttons at the top of the page). Tip: When used in a survey, this field could be prepopulated (and thus auto-selected) by embedding a participant's language ID in the survey URL itself (for details, see the FAQ's \"How to pre-fill survey questions\" section)."
multilang_145 = "Highlight translation fallbacks on non-project pages"
multilang_146 = "The default text has changed since this item was translated."
multilang_147 = "There are no options to be set for the default language. Please choose another language."
multilang_148 = "Multi-language support in REDCap works by providing translations for each display item, i.e. field labels, choice labels, and user interface elements, but also for items such as email subjects and body texts of alerts and automated survey invitations. Translations for each supported item can be set on this page. In case an item is not translated, the item will be shown in the language defined as fallback, or, if not set there either, the default text will be used."
multilang_149 = "The default language is defined as the one that has been used to set up the project's data dictionary (i.e. what is shown in the Online Designer). A default language must always be defined, although it is possible to not expose it to the user (by setting its <i>Active</i> state to off). Furthermore, note that by default, a language is turned off for instruments in data entry and survey modes unless explicitly turned on."
multilang_150 = "Translate instrument name"
multilang_151 = "Failed to save changes. Please check the browser console (F12) for details."
multilang_152 = "<b>This is the default/reference language.</b> Thus, items cannot be edited here, but they can be modified on the <i>Alerts & Notifications</i> page. However, individual alerts can be set to be excluded from translation here. <b>If you wish to begin/continue translating the default language text, click a language button above.</b>"
multilang_153 = "Use this page to manage which alerts should be translated. Alerts that are turned off will not show up for (nor be translated into) other languages. Note that since alerts can be set up for various purposes and triggered in different contexts, it is not possible to automatically determine the language that should be used to render an alert. Therefore, for each alert, the source for the language information needs to be set. This can either be the <b>'Language preference field'</b> (as set on the 'Languages' tab; this is the default), or the <b>'User's or survey respondent's active language'</b> (as set in their profile/browser cookie)."
multilang_155 = "Check to exclude this alert from being translated"
multilang_156 = "There are no alerts that can be translated."
multilang_157 = "Collapse all"
multilang_158 = "Expand all"
multilang_159 = "Translation Snapshots"
multilang_160 = "Create Snapshot"
multilang_161 = "Show/Hide Snapshots"
multilang_162 = "A snapshot of your current translation settings (all translations and settings for all languages) can be saved and stored by clicking the 'Create Snapshot' button on this page. All snapshots can be accessed and downloaded at any time from the table below (click the 'Show/Hide Snapshots' link to toggle display of the table). There is no limit to how many snapshots can be created. Creating a snapshot can be useful to allow you to revert your translations back to a specific point in time, if desired, by downloading the snapshot (a ZIP file) and re-importing the individual files (one per language) contained in it. Note that restoring this way will be based on a <i>best effort</i> scheme, as the underlying project structure may have changed since the snapshot was created."
multilang_163 = "Failed to load the snapshots table. Please try again after reloading this page."
multilang_164 = "There are no snapshots yet."
multilang_165 = "The snapshot has been created."
multilang_166 = "Failed to create the snapshot. Please check the browser console (F12) for details."
multilang_167 = "The snapshot has been deleted."
multilang_168 = "Failed to delete the snapshot. Please check the browser console (F12) for details."
multilang_169 = "Show deleted snapshots"
multilang_170 = "There are no snapshots to be shown."
multilang_171 = "Delete Snapshot?"
multilang_172 = "Are you sure you want to delete this snapshot?<br><br><b>This action cannot be undone!</b>"
multilang_173 = "Delete Snapshot"
multilang_174 = "There are no alerts in this project."
multilang_175 = "How to use this file: This file can be used to restore (or update) settings on a project's Multi-Language Management page. To do so, import this file using the 'Import General Settings' mechanism on the 'Languages' tab. Note that first, however, at least one language must exist in the project. This file can be edited manually before importing. When doing so, make sure to keep the structure of the file intact (it must be valid JSON). Only language IDs, true/false, and field/user (alertSources) are valid options. During the import operation, a best-effort approach is taken - any setting that is not applicable at the time of import will be silently ignored."
multilang_176 = "Failed to download the snapshot. Please check the browser console (F12) for details."
multilang_178 = "Missing Data Code Translations"
multilang_179 = "Code"
multilang_180 = "Translations of automated survey invitations"
multilang_181 = "Translations of alerts"
multilang_182 = "Translations of instruments names"
multilang_183 = "Translations of event names"
multilang_184 = "Translations of missing data code labels"
multilang_185 = "Failed to create the export. Please check the browser console (F12) for details."
multilang_186 = "Missing Data Code label translation:"
multilang_187 = "Translations of project-specific items"
multilang_188 = "These include: fields, survey settings, ASIs, alerts, missing data code labels, ..."
multilang_189 = "Protected Email"
multilang_190 = "reCAPTCHA"
multilang_191 = "Field Types"
multilang_192 = "Common"
multilang_193 = "Validation"
multilang_194 = "eConsent"
multilang_195 = "Secondary Unique Field"
multilang_196 = "Protected Email Message"
multilang_197 = "Protected Email Code Message"
multilang_198 = "Protected Email Code Check"
multilang_199 = "Protected Email Display"
multilang_200 = "Same as @LANUGAGE-CURRENT-FORM, but works only on survey pages. For multi-page surveys, @LANGUAGE-CURRENT-SURVEY needs to be used on a field of each page where capture of the language is relevant (e.g. for performing branching)."
multilang_201 = "Text box fields are denoted with [T] while radio and dropdown fields are denoted with [R] and, in case they include all language keys, are highlighted with a green background."
multilang_202 = "RTL refers to <u>right-to-left</u> with regard to the direction of the text. Some languages, such as Arabic, are read right-to-left. You can enable the RTL setting if the language should be read in right-to-left direction."
multilang_204 = "The language that will be used as a fallback in case the current context has not been translated."
multilang_205 = "View list of ISO 639-1 language codes."
multilang_206 = "Language Display Name"
multilang_207 = "HINT: You may check the checkbox next to each field to mark it as \"done\" if its text does not require translation."
multilang_208 = "Language Source"
multilang_209 = "Language preference field"
multilang_210 = "User's or survey respondent's active language"
multilang_212 = "How to use this file: Any information above the column title row is purely informational and will be ignored during import. The column title row must remain intact, i.e. the row 'section,type,name,index,kind,text' (the delimiter can be either comma, as shown, or semicolon or tab) and be the first non-empty line that is not staring with # (denoting comments). The essential lines are those with 'translation' or 'value' in the 'kind' column. In these lines, the translation (or value) in the 'text' column can be edited. All other lines (except the 'hash' kind. see below) are ignored when the file is imported. Do not change the contents of the 'section', 'type', 'name', 'index', and 'kind' columns at all. Furthermore, subsets of this file can be created and used at will, as long as the rules layed out above are observed. The 'hash'-kind rows are not essential, but assist in tracking if a default value has changed since the file was created, and thus a translation may be out of date. During an import operation, a best-effort approach is taken. Any items that cannot be matched during import will be silently ignored."
multilang_213 = "Note that some tabs on this page, such as Missing Data Codes or Protected Email Mode, will only be shown when the corresponding features are enabled in this project. If nothing is displayed below, then there is nothing to translate here."
multilang_214 = "Translations of PDF customizations"
multilang_215 = "Translations of Protected Email settings"
multilang_216 = "Instrument name translation:"
multilang_217 = "Event name translation:"
multilang_218 = "Custom event label translation:"
multilang_219 = "Parsing of CSV file produced errors:"
multilang_220 = "You may translate any of the REDCap's stock user interface elements seen on forms/surveys, such as field validation error messages, survey submit buttons, and other things that typically cannot be defined in a project. Please keep in mind that <b>you probably do not need to translate all user interface items</b> since it is likely that many of them might not be used on your forms/surveys. Tip: Use the 'highlight' feature on the Settings tab above to highlight all untranslated text on the page as a quick way of determining which specific elements need to be translated."
multilang_221 = "Because the project is currently in production status, this page can only be modified if you enable Draft Mode. So if you wish to make edits or additions to your translations, <b>first enable Draft Mode in the project via the Online Designer</b>, and then return here to make translation changes while in Draft Mode. When your drafted changes are approved, your translation changes made here will automatically be approved together with them."
multilang_222 = "Your project is currently in Draft Mode, thus all translations and changes made here will NOT be made in real time but will only go live once your draft changes have been approved and committed via the Online Designer through the typical approval process. NOTE: Any changes made to translations here <i>will be lost if you revert your drafted changes via the Online Designer</i>. If you are finished with your translations and wish to commit them, go to the Online Designer and click the 'Submit Changes for Review' button."
multilang_223 = "<b>Multi-language Notice:</b> If you have made any modifications to your translations on the Multi-Language Management page while in Draft Mode, those changes will go live once they are approved and committed with all drafted changes here."
multilang_224 = "<b>Multi-language Notice:</b> If you have made any modifications to your translations on the Multi-Language Management page while in Draft Mode, those changes WILL BE LOST if you choose to remove all drafted changes here."
multilang_225 = "(default)"
multilang_226 = "Use the Languages table to control which languages are shown in the Codebook by clicking the corresponding checkboxes. The default language will always be shown. Tip: Toggle all languages on or off with the checkbox in the header row of the Langauges table. '{0}' denotes a missing translation."
multilang_227 = "Active languages: {0}"
multilang_228 = "Active languages - Data Entry: {0} | Survey: {1}"
multilang_229 = "Were changes made to translations in Multi-Language Management?"
multilang_230 = "No, no language translations have been modified."
multilang_231 = "Yes, some language translations have been modified."
multilang_232 = "Import from file or system"
multilang_233 = "Import from file"
multilang_234 = "<b>Multi-language Notice:</b> Because some modifications to translations on the Multi-Language Management page been made while in Draft Mode, those changes WILL BE LOST if you choose to remove all drafted changes here."
multilang_236 = "Manage the available languages in this project using the table and options below by following these steps:"
multilang_240 = "Learn how to implement some language-related action tags, such as <code>@LANGUAGE-SET</code>, if desired. Learn about them here:"
multilang_241 = "Test your translations by switching back and forth between languages on your data entry forms and/or surveys. Note that only active languages will be available for selection on those places."
multilang_242 = "Translation for the custom text to display at top of Survey Queue:"
multilang_243 = "Language-specific redirect url after when survey is completed:"
multilang_244 = "Redirect URL"
multilang_245 = "Translation of the 'Take this survey again' button label:"
multilang_246 = "Repeat Survey Button Text"
multilang_247 = "Language-specific text-to-speech voice:"
multilang_248 = "Text-to-Speech Language/Voice"
multilang_249 = "Text-to-Speech Options"
multilang_250 = "Language-specific text-to-speech option:"
multilang_251 = "Text-to-Speech"
multilang_252 = "Confirmation Email Content"
multilang_253 = "Confirmation Email Subject"
multilang_254 = "Confirmation Email"
multilang_255 = "Language-specific email from display name:"
multilang_256 = "Confirmation Email From Display"
multilang_257 = "Translation of the custom response limit text:"
multilang_258 = "Response Limit Text"
multilang_259 = "Translation of the stop-action alternative survey completion text:"
multilang_260 = "Stop Action Completion Text"
multilang_263 = "Translation of the custom text to display when the survey is offline:"
multilang_264 = "Offline Instructions"
multilang_265 = "Text for the 'alt' attribute of the custom survey logo:"
multilang_266 = "Translation of the survey completion text:"
multilang_267 = "Translation of the survey instructions:"
multilang_268 = "Survey Title and Prompts"
multilang_269 = "Translation of the survey title:"
multilang_270 = "Form name translation:"
multilang_271 = "Translation of the @Action Tag value(s):"
multilang_272 = "Action Tag"
multilang_273 = "Matrix header translation:"
multilang_274 = "Choices translation:"
multilang_275 = "Section header translation:"
multilang_276 = "Field label translation:"
multilang_277 = "Field note translation:"
multilang_278 = "Slider labels translation:"
multilang_279 = "Slider Label"
multilang_280 = "Language-specific URL of the embedded video:"
multilang_281 = "Form status label translation:"
multilang_282 = "Form Status"
multilang_283 = "Page Navigation"
multilang_284 = "Controls & Display Elements"
multilang_285 = "Dialog Elements"
multilang_286 = "Miscellaneous Elements"
multilang_287 = "Survey Completion"
multilang_288 = "Survey Start / Continuation"
multilang_289 = "Survey Stop"
multilang_290 = "Survey Save & Return Later"
multilang_291 = "Survey Email"
multilang_292 = "Survey Results"
multilang_293 = "Printing"
multilang_294 = "Error Messages"
multilang_295 = "Checkbox Field"
multilang_296 = "Yes/No Field"
multilang_297 = "True/False Field"
multilang_298 = "Dropdown Field"
multilang_299 = "Slider Field"
multilang_300 = "Date & Time Fields"
multilang_301 = "File Upload & Signature Fields"
multilang_302 = "Descriptive Field"
multilang_303 = "PROMIS"
multilang_304 = "Data Collection Menu"
multilang_305 = "Actions Menu"
multilang_306 = "Record Actions Menu"
multilang_307 = "Save Buttons"
multilang_308 = "Deletion Notices & Confirmation"
multilang_309 = "Action Messages"
multilang_310 = "Default Missing Data Code Labels"
multilang_311 = "Validation Messages"
multilang_312 = "The '{0}' tooltip text:"
multilang_313 = "The '{0}' prompt:"
multilang_314 = "The @NONEOFTHEABOVE alert message (use {0} as placeholder for the choice label):"
multilang_315 = "The '{0}' placeholder text:"
multilang_316 = "Label for the '{0}' option:"
multilang_317 = "Page number (use {0} and {1} as placeholders for the current page and the total number of pages, respectively):"
multilang_318 = "Use {0} and {1} symbols for previous/next buttons?"
multilang_319 = "Dropdown arrow alt text:"
multilang_320 = "Message displayed for unset sliders (desktop):"
multilang_321 = "Use the {0} symbol for the submit button instead of a text label?"
multilang_322 = "Message displayed for unset sliders (mobile):"
multilang_323 = "The '{0}' link label:"
multilang_324 = "The '{0}' slider voice explanation:"
multilang_325 = "The '{0}' label"
multilang_326 = "The '{0}' full day name:"
multilang_327 = "The '{0}' abbreviated day name:"
multilang_329 = "The '{0}' popup window title:"
multilang_330 = "The '{0}' date format indicator:"
multilang_331 = "The '{0}' link label and popup title:"
multilang_332 = "Text for non-specific errors:"
multilang_333 = "The '{0}' hint:"
multilang_334 = "The alternatives separator '- {0} -' (dashes may be added automatically):"
multilang_335 = "The '{0}' button label:"
multilang_336 = "The '{0}' indicator:"
multilang_337 = "The '{0}' notification:"
multilang_339 = "Generic image alt attribute:"
multilang_340 = "The '{0}' error message:"
multilang_341 = "The '{0}' dialog message:"
multilang_342 = "The maximum file size notice (use {0} as placeholder for the number of megabytes):"
multilang_343 = "The '{0}' message:"
multilang_344 = "The '{0}' notice:"
multilang_345 = "Text of the iOS limitation notification:"
multilang_346 = "The file deletion confirmation message (the placeholder {0} will contain the file name):"
multilang_347 = "The file version deletion confirmation message (use {0} as placeholder for the version number):"
multilang_348 = "The '{0}' title (used in PDFs):"
multilang_349 = "Alt attribute of the signature image"
multilang_350 = "The reCAPTCHA prompt:"
multilang_351 = "Translation of the REDCap Secure Messaging text:"
multilang_352 = "Translation of the PDF custom header text:"
multilang_353 = "Translation of the message body:"
multilang_354 = "Translation of the email subject:"
multilang_355 = "Language-specific sender display name:"
multilang_356 = "Translation for the Survey Login ustom error message:"
multilang_357 = "The '{0}' default banner text:"
multilang_358 = "The sender information text (use {0} as placeholder for display name and email address of the sender):"
multilang_359 = "The subject of the Protected Email verification email:"
multilang_360 = "The Protected Email code notice (use {0} as placeholder for the code):"
multilang_361 = "The Protected Email code expiration notice (use {0} as placeholder for the time in minutes):"
multilang_362 = "Security check page title:"
multilang_363 = "Security check informational text:"
multilang_364 = "Security check informational text (multiple recipients):"
multilang_365 = "The dialog text confirming that the email has been sent (use {0} as placeholder for the email address):"
multilang_366 = "The number of files indicator (plural; use {0} as placeholder for the number of files):"
multilang_367 = "The number of files indicator (singular; use {0} as placeholder for the number of files):"
multilang_368 = "Email sent time label - '{0}':"
multilang_369 = "Email sent time - '{0} minute ago' (singular; use {0} as placeholder for the number of minutes):"
multilang_370 = "Email sent time - '{0} minutes ago' (plural; use {0} as placeholder for the number of minutes):"
multilang_371 = "Email sent time - '{0} hour ago' (singular; use {0} as placeholder for the number of hours):"
multilang_372 = "Email sent time - '{0} hours ago' (plural; use {0} as placeholder for the number of hours):"
multilang_373 = "Email sent time - '{0} day ago' (singular; use {0} as placeholder for the number of days):"
multilang_374 = "Email sent time - '{0} days ago' (plural; use {0} as placeholder for the number of days):"
multilang_375 = "The survey already completed notification message:"
multilang_376 = "The response limit reached notification message:"
multilang_377 = "The time limit reached notification message:"
multilang_378 = "The repeat instance recorded confirmation message (singular; use {0} as placeholder for the number of instances):"
multilang_379 = "The repeat instances recorded confirmation message (plural; use {0} as placeholder for the number of instances):"
multilang_380 = "Introduction to the survey login instructions:"
multilang_381 = "Instructions stating that a value must be entered:"
multilang_382 = "Instructions regarding the minimum nubmer of required fields (use {0} and {1} as placeholders):"
multilang_383 = "Instructions stating that all fields are required:"
multilang_384 = "Note that login is not case sensitive:"
multilang_385 = "The error message displayed when the login fails (note singular):"
multilang_386 = "The error message displayed when the login fails (note plural):"
multilang_387 = "The message displayed when there is no data for the login fields:"
multilang_388 = "The access denied informational text (use {0} as placeholder for the number of minutes):"
multilang_389 = "Password disclaimer text:"
multilang_390 = "The page number label (use {0} as placeholder for the page number):"
multilang_391 = "The response added statement (use {0} as placeholder for the timestamp):"
multilang_392 = "The partial completion notice:"
multilang_393 = "The intoductory text on the eConsent page:"
multilang_394 = "The label for the eConsent confirmation checkbox:"
multilang_395 = "The eConsent verification notice:"
multilang_396 = "The eConsent version title:"
multilang_397 = "The eConsent type title:"
multilang_398 = "The notification that the signature will be erased:"
multilang_399 = "The 'PDF not supported in browser' notification message:"
multilang_400 = "The save changes dialog text:"
multilang_401 = "The 'End the survey?' text:"
multilang_402 = "The 'End the survey?' instructions:"
multilang_403 = "The 'Not a participant' message:"
multilang_404 = "The title of the 'partial completion' notice:"
multilang_405 = "The text of the 'partial completion' notice:"
multilang_406 = "The text of the 'start over' confirmation popup:"
multilang_407 = "The 'cannot edit' hint for email/phone fields:"
multilang_408 = "The 'survey access code' prompt:"
multilang_409 = "The 'survey access code not case sensitive' hint:"
multilang_410 = "The 'survey access code needed' alert message:"
multilang_411 = "The 'invalid survey access code' error message:"
multilang_412 = "The title of the 'save and return later' page:"
multilang_413 = "The 'save and return later' instructions:"
multilang_414 = "The 'Return Code' instructions:"
multilang_415 = "The 'survey return link' instructions:"
multilang_416 = "The notice that the 'Return Code' is not included:"
multilang_417 = "The return code label on data entry forms:"
multilang_418 = "The survey link title:"
multilang_419 = "The survey link instructions:"
multilang_420 = "The text of the 'continue now' notification:"
multilang_421 = "The 'email will not be stored' notice:"
multilang_422 = "The 'bookmark this page' instructions:"
multilang_423 = "The 'email just sent' notice:"
multilang_424 = "The 'email (without return code) just sent' notice:"
multilang_425 = "The 'return with credentials' notice:"
multilang_426 = "The 'return with return code' notice:"
multilang_427 = "The text for the alt attribute of the 'Returning?' link:"
multilang_428 = "The 'returning to survey' instructions:"
multilang_429 = "The 'survey continuation' instructions:"
multilang_430 = "The 'Return Code not case sensitive' notice:"
multilang_431 = "The 'start over' instructions:"
multilang_432 = "The 'invalid return code' error message:"
multilang_433 = "The 'Survey Access Code/Return Code mismatch' explanation:"
multilang_434 = "The message displayed when a survey has been locked:"
multilang_435 = "The message displayed when a partial survey has been locked:"
multilang_436 = "The explanation for a partial survey that has been locked:"
multilang_437 = "The 'automatically generated' notice:"
multilang_438 = "The 'thank you' message (use {0} as placeholder for the survey title):"
multilang_439 = "The 'survey progress' notice:"
multilang_440 = "The 'return code needed' notice:"
multilang_441 = "The 'contact' notice:"
multilang_442 = "The 'copy link' notice:"
multilang_443 = "The title for the confirmation email prompt:"
multilang_444 = "The confirmation email prompt:"
multilang_445 = "The 'survey results' title:"
multilang_446 = "The 'survey results' instructions:"
multilang_447 = "The 'Graphs:' title:"
multilang_448 = "The barchart explanation (use {0} and {1} as placeholders for 'blue' and 'orange', see below):"
multilang_449 = "The scatterplot explanation (use {0}, {1}, and {2} as placeholders for 'blue', 'red', and 'orange', see below):"
multilang_450 = "Translation of '{0}':"
multilang_451 = "The 'Statistics:' title:"
multilang_452 = "The descriptive statistics explanation:"
multilang_453 = "The note indicating that the survey results code will not be included in the email message:"
multilang_454 = "The 'results return' notice:"
multilang_455 = "The invalid results code error message:"
multilang_456 = "The return code notice:"
multilang_457 = "The return later notice:"
multilang_458 = "The 'Survey Queue' title:"
multilang_459 = "The '{0}' column title:"
multilang_460 = "The 'incomplete surveys' prompt:"
multilang_461 = "The 'invalid Survey Queue link' message:"
multilang_462 = "The message indicating how many surveys have been completed (use '{0}' as placeholder for the number):"
multilang_463 = "The message indicating that all surveys have been completed:"
multilang_464 = "The survey queue link explanation:"
multilang_465 = "The '– OR –' divider (dashes will be added automatically):"
multilang_466 = "The 'email sent' popup message (use {0} as placeholder for the email address):"
multilang_467 = "The 'survey queue link' email subject:"
multilang_468 = "The 'survey queue link' email body (this will be followed by the survey link):"
multilang_469 = "The survey completed status message (use {0} as placeholder for the timestamp):"
multilang_470 = "The survey completed status message (use {0} and {1} as placeholders for timestamp and identifier, respectively):"
multilang_471 = "The survey added status message (use {0} as placeholder for the timestamp):"
multilang_472 = "The survey added status message (use {0} and {1} as placeholders for timestamp and identifier, respectively):"
multilang_473 = "The secondary unique field note:"
multilang_474 = "The 'instrument locked' explanation:"
multilang_475 = "The locking info statement (use {0}, {1}, and {2} as placeholders for userid, user full name, and timestamp, respectively):"
multilang_476 = "The locking info header (use {0}, {1}, and {2} as placeholders for userid, user full name, and timestamp, respectively):"
multilang_477 = "The locking info header explanation (use {0} and {1} as placeholders for instrument name and record id, respectively):"
multilang_478 = "The locking header unlocking explanation:"
multilang_479 = "The E-Signature statement (use {0} and {1} as placeholders for the user id and the timestamp, respectively):"
multilang_480 = "PROMIS auto-scoring title:"
multilang_481 = "PROMIS auto-scoring locked message:"
multilang_482 = "PROMIS auto-scoring create record message (the placeholder {0} will contain a link to the Survey Distribution Tools page):"
multilang_483 = "PROMIS adaptive title:"
multilang_484 = "PROMIS adaptive locked message:"
multilang_485 = "PROMIS adaptive create record message (the placeholder {0} will contain a link to the Survey Distribution Tools page):"
multilang_486 = "The password disclaimer text:"
multilang_487 = "The 'invitation to be sent' tooltip (use {0} as placeholder for the timestamp):"
multilang_488 = "The 'invitation sent' tooltip (use {0} as placeholder for the timestamp):"
multilang_489 = "The 'invitation failed to send' tooltip (use {0} as placeholder for the timestamp):"
multilang_490 = "The '{0}' menu label:"
multilang_491 = "The '{0}' menu item label:"
multilang_492 = "The record renaming hint (use {0} as a placeholder for the Record Home Page link):"
multilang_493 = "The record / data access group mismatch alert (use {0} as a placeholder for the record id):"
multilang_494 = "The record / data access group mismatch explanation:"
multilang_495 = "The 'new record' hint (use {0} and {1} as placeholders for the record id and the record id label, respectively):"
multilang_496 = "The 'edit survey response' hint:"
multilang_497 = "The '{0}' subtext:"
multilang_498 = "The title of the window showing the basic data entry video:"
multilang_499 = "The 'Compact PDF' suffix:"
multilang_500 = "The 'Save & ...' tooltip:"
multilang_501 = "The 'Save & ...' popup title:"
multilang_502 = "The 'Save & ...' popup text:"
multilang_503 = "The 'deletion due to randomization field not possible' alert:"
multilang_504 = "The 'delete instrument' (longitudinal) confirmation:"
multilang_505 = "The 'delete instrument' confirmation:"
multilang_506 = "The 'reversion of survey status after deletion' notice:"
multilang_507 = "The 'deletion limited to single instance' notice:"
multilang_508 = "The 'action cannot be reversed' notice:"
multilang_509 = "The 'delete entire record' hint (use {0} as placeholder for the 'Record Home Page' link):"
multilang_510 = "The 'delete entire event' hint (use {0} as placeholder for the 'Record Home Page' link):"
multilang_511 = "The 'Editing existing record' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_512 = "The 'Adding new record' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_513 = "The 'Successfully edited record' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_514 = "The 'Successfully added record' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_515 = "The 'Successfully deleted record' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_516 = "The 'Data entry cancelled' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_517 = "The 'Successfully renamed record' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_518 = "The 'Successfully assigned record to DAG' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_519 = "The 'Successfully unassigned record from DAG' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_520 = "The 'Event successfully deleted' message (use {0} and {1} as placeholders for the record id label and record id, respectively):"
multilang_521 = "The 'Could not change record id' message (use {0}, {1}, {2}, and {3} as placeholders for the record id label, record id, instance, and record id label, respectively):"
multilang_522 = "The '{0}' default missing data code label:"
multilang_523 = "The message of the <i>number</i> validation popup:"
multilang_524 = "The message of the <i>integer</i> validation popup:"
multilang_525 = "The message of the <i>Vanderbilt MRN</i> validation popup:"
multilang_526 = "The message of the <i>date</i> validation popup:"
multilang_527 = "The message of the <i>hard range</i> validation popup:"
multilang_528 = "The message of the <i>soft range (1)</i> validation popup:"
multilang_529 = "The message of the <i>soft range (2)</i> validation popup:"
multilang_530 = "The message of the <i>time</i> validation popup:"
multilang_531 = "The message of the <i>ZIP code</i> validation popup:"
multilang_532 = "The message of the <i>phone</i> validation popup:"
multilang_533 = "The message of the <i>email</i> validation popup:"
multilang_534 = "The message of the <i>regex</i> validation popup:"
multilang_535 = "The message of the <i>general</i> validation popup:"
multilang_536 = "The message of the 'remove spaces' popup:"
multilang_537 = "The required fields notification title:"
multilang_538 = "The required fields notification text:"
multilang_539 = "The MAXCHOICE validation text:"
multilang_540 = "The MAXCHOICE affected fields prompt:"
multilang_541 = "The 'invalid values' popup text:"
multilang_542 = "The 'invalid values' prompt:"
multilang_543 = "The 'invalid values' popup title:"
multilang_544 = "The 'maximum number of choices reached' message:"
multilang_545 = "Text for the 'Submit and' prompt (followed by the 'Take survey again' button):"
multilang_546 = "Multi-Language Management is disabled for this project."
multilang_547 = "An unspecified error has occurred."
multilang_548 = "This snapshot does not exist!"
multilang_549 = "Failed to delete snapshot file from edocs."
multilang_550 = "Failed to update the snapshots table."
multilang_551 = "Failed to add the snapshot to the database."
multilang_552 = "Failed to read edocs metadata from the database."
multilang_553 = "Failed to upload the snapshot file to the edocs location."
multilang_554 = "Failed to retrieve the snapshot file from edocs."
multilang_555 = "Displayed for response 'start time' at top of data entry form (use {0} as placeholder for the timestamp):"
multilang_556 = "Displayed for response 'start time' at top of data entry form when no timestamp is available:"
multilang_557 = "Displayed for response 'total completion time' at top of data entry form (use {0} as placeholder for the duration):"
multilang_558 = "Unit for durations of time (seconds):"
multilang_559 = "Unit for durations of time (minutes):"
multilang_560 = "Unit for durations of time (hours):"
multilang_561 = "Unit for durations of time (days):"
multilang_562 = "Repeating Survey"
multilang_563 = "(Optional) For surveys, designate a field for storing a participant's language preference"
multilang_564 = "<b>ATTENTION:</b> The original values of some translated items have changed, and thus some translations might be out of date."
multilang_565 = "Review {0} changed items."
multilang_566 = "Review Changed Items"
multilang_567 = "The values of some project or user interface items have changed since translations for these were last saved. Thus, the translations might be outdated and should be reviewed."
multilang_568 = "Item"
multilang_569 = "Default text"
multilang_570 = "Accept"
multilang_571 = "Accept all translations as still valid"
multilang_572 = "Contains HTML content"
multilang_573 = "Multi-Langauage Management is currently <b>turned off</b> in this project!"
multilang_574 = "Export Language (for this instrument only)"
multilang_575 = "Translations of survey settings"
multilang_576 = "Validation Types"
multilang_577 = "{0:VisibleIndicator}Translation of the '{1:Label}' validation label:"
multilang_578 = "Survey Redirection"
multilang_579 = "Simultaneous Users Notification"
multilang_580 = "Notification title:"
multilang_581 = "Concurrent user info (use {0} and {1} as placeholders for the user name and record name, respectively):"
multilang_582 = "Explanatory text:"
multilang_583 = "Further explanatory text:"
multilang_584 = "Simultaneous users - Access to this page is denied"
multilang_585 = "Another user ({0}) is currently editing this page. Simultaneous use of the Multi-Langugage Management page is not allowed, as users might otherwise overwrite each other's changes."
multilang_586 = "If this conflict is in error, and you have confirmed that the user listed above is no longer on this page, then you will either have to wait for the logout time to expire ({0} minutes from the time of the other user's last activity on this page), or you can have that other user log back in to REDCap, which will immediately release this page and allow you to access it."
multilang_587 = "The {0} popup title:"
multilang_588 = "The duplicate value popup message (surveys; use {0} as placeholder for the value):"
multilang_589 = "The duplicate value popup message (data entry forms; use {0} and {1} as placeholders for the field name and value, respectively):"
multilang_590 = "<b>NOTICE: This instrument is an Adaptive or Auto-scoring instrument</b>, which is validated for its specific language and should never be translated. Therefore, translation has been disabled for this instrument."
multilang_591 = "<b>NOTICE: This instrument was imported from the REDCap Shared Library</b>. Please be cautious when translating a validated instrument into a different language as it may affect the instrument's validity and may not be permitted by the copyright holder. Please investigate directly with the copyright holder before taking next steps."
multilang_592 = "The '{0}' message (this will be prepended by the actual count):"
multilang_593 = "Custom Survey Submit Buttons:"
multilang_594 = "Translation of the '{0}' button label:"
multilang_595 = "Survey-specific Previous Page Button Label"
multilang_596 = "Survey-specific Next Page Button Label"
multilang_597 = "Survey-specific Submit Button Label"
multilang_598 = "Translation of the template data:"
multilang_599 = "Template data key deleted: "
multilang_600 = "DELETED"
multilang_601 = "Initial"
multilang_602 = "This setting determines which language should be displayed initially when a user visits a multi-language non-project page for the first time (i.e. when there is no information about the preferred language available from a browser cookie). This must be one of the <i>Active</i> languages."
multilang_603 = "This must be set to the language corresponding to the <i>Language.ini</i> file that is set for this REDCap instance in <i>General Configuration</i>. This language does not need to be active."
multilang_604 = "This setting determines whether a language is available for import in projects. This setting is independent of the <i>Active</i> state of a language."
multilang_605 = "This settings determines whether a language is available on multi-language pages that are not associated with a project, such as the <i>Enter Survey Access Code</i> page."
multilang_606 = "Export or import general settings"
multilang_607 = "Export General Settings"
multilang_608 = "Import General Settings"
multilang_609 = "General settings"
multilang_610 = "Use this to export and import files with general settings such as which languages are set as active, default, or fallback, which fields and survey settings are excluded, as well as the settings on the <i>Settings</i> tab."
multilang_611 = "<b>Note:</b> During an import operation, a best-effort approach is taken. Any setting that is not applicable at the time of import will be silently ignored.<br>Furthermore, this type of settings file is limited to the JSON format only."
multilang_612 = "Failed to download the export file. Please check the browser console (F12) for details."
multilang_613 = "Cannot determine file type. Use .csv/.json/.ini files only."
multilang_614 = "Invalid file type. Use .json files only."
multilang_615 = "This is not a valid MLM settings file. It must be a .json file."
multilang_616 = "Languages tab settings"
multilang_617 = "Forms/Surveys tab settings"
multilang_618 = "Alerts tab settings"
multilang_619 = "Settings tab settings"
multilang_620 = "An error occurred during processing of the file. Please check the browser console (F12) for details. The import may have succeeded only partially."
multilang_621 = "The import processes has completed."
multilang_623 = "Attempt to match initially displayed language with preferred languages set in web browsers"
multilang_624 = "https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes"
multilang_626 = "https://en.wikipedia.org/wiki/ISO_3166-1"
multilang_627 = "View list of ISO 3166-1 country codes."
multilang_628 = "The notice prepended to the subject of reminder emails:"
multilang_629 = "Require <b>admin activation</b> of multi-language support in projects"
multilang_630 = "When enabled, admins must enable multi-language support in each project. This option will not affect any projects where multi-language support is already enabled (either because it had previously been enabled explicitly by an admin or there is at least one language already set up)."
multilang_631 = "<b>Enable</b> multi-language support for this project"
multilang_632 = "Note, since there already is at least one language defined, <b>multi-language support will remain available</b> irrespective of the state of this switch. However, unless switched on, once all languages are deleted, the Multi-Language Management menu link will be hidden and users will be locked out of the Multi-Language Management page."
multilang_633 = "<b>Disable and hide</b> multi-language support for this project"
multilang_634 = "Turning on this option will hide the Multi-Language Management menu link and prevent access to Multi-Language Management for users <b>even when there are languages defined</b>."
multilang_635 = "Usage"
multilang_637 = "Failed to load usage statistics. Please check the browser console (F12) for details."
multilang_638 = "Show all projects"
multilang_639 = "Languages (Active)"
multilang_640 = "INI"
multilang_641 = "Debug mode turned on"
multilang_642 = "Deactivated by user"
multilang_643 = "Deactivated by admin"
multilang_644 = "Enabled by admin"
multilang_645 = "Legend for MLM status icons:"
multilang_646 = "Legend for status icons:"
multilang_647 = "Notice: There may be more and/or different languages available after entering the access code."
multilang_648 = "The survey access page languages note:"
multilang_649 = "Tooltip for the field-should-be-hidden indicator:"
multilang_650 = "ASI Language Source"
multilang_651 = "Internet Explorer incompatibility notice:"
multilang_652 = "Change Reason Popup"
multilang_653 = "The message of the 'Invalid value!' popup for auto-complete drop-down fields:"
multilang_654 = "The title of the 'Invalid value!' popup for auto-complete drop-down fields:"
multilang_655 = "by creating the language from scratch"
multilang_656 = "Keep this language updated automatically"
multilang_657 = "Note: This option may be locked by an administrator"
multilang_658 = "<b>Disable</b> project language initialization <b>from a file</b>"
multilang_659 = "<b>Disable</b> project language initialization <b>from scratch</b>"
multilang_660 = "<b>Force subscription</b> to system language updates"
multilang_661 = "<b>Disable UI overrides</b> in subscribed system languages"
multilang_662 = "These options control how users can add new languages to projects and whether they are allowed to make changes to user interface strings. These options can be overridden for specific projects in these projects' Multi-Language Management settings."
multilang_663 = "Override language creation, forced subscription, and UI override system settings. To <b>allow</b> these options, check the following (note, reload this page after saving to reflect any changes):"
multilang_664 = "Failed to obtain a GUID from the server. Please check the browser console (F12) for details."
multilang_665 = "Failed to load the system language from the server. Please check the browser console (F12) for details."
multilang_666 = "This is a <b>subscribed system language</b>. Therefore, user interface items cannot be edited."
multilang_667 = "Note, this is a <b>subscribed system language</b>, but you may provide select overrides of individual items."
multilang_668 = "Automatically updated UI translations"
multilang_669 = "Update this language …"
multilang_670 = "Currently editing:"
multilang_671 = "by synching with a system language"
multilang_672 = "by importing from a file (JSON, CSV, or INI)"
multilang_673 = "Update this language"
multilang_674 = "Subscription Status"
multilang_675 = "System Language:"
multilang_676 = "A unique identifier (case-insensitive) for this language. It is recommended to use the ISO code, such as '<b>en</b>' or '<b>en-US</b>' for English, or '<b>es</b>' for Spanish. <b>Use only letters and hyphen</b> (and optionally numbers at the end)."
multilang_677 = "The options above facilitate translation during project development. For <small><b>PRODUCTION</b></small> projects, it is recommended to turn off the highlight options."
multilang_678 = "When this option is enabled, REDCap will to try to match a user's/survey respondent's preferred language, as set in their web browser, to the languages available in this project. Note that for this to work, the languages' IDs <b>must</b> match a valid ISO code. Autodetection will only take effect in case the user has not actively chosen a language yet, i.e. on their first visit."
multilang_679 = "Keep existing translations"
multilang_680 = "Overwrite existing translations"
multilang_681 = "Allow blank values to overwrite existing translations"
multilang_682 = "<b>Note</b>, when creating a snapshot, it will always reflect the currently <i>saved</i> state. Thus, any unsaved changes will <b>not</b> be included in the snapshot."
multilang_683 = "Update Language"
multilang_684 = "Use the <i>Edit Language</i> dialog to change the subscription status."
multilang_685 = "Additionally, associate this language with this system language"
multilang_686 = "<b>Note</b>: Once associated with a system language, this cannot be undone."
multilang_687 = "This page gives an overview of MLM usage in projects. Click on a project link to open that project in a new browser tab. Click on a PID to get to that project's settings page. Hover over counts to see more details, and click to get to that project's MLM setup page. <i>Hint:</i> You may search for project languages or status icons by their label."
multilang_688 = "Delete Language"
multilang_689 = "This language cannot be deleted because it is subscribed to in <b>{0:Total}</b> active project(s) – {1:dev} development, {2:prod} production."
multilang_690 = "Continue"
multilang_691 = "Initialize a new language …"
multilang_692 = "The 'View PDF' in a new tab prompt:"
multilang_693 = "reCAPTCHA language code value:"
multilang_694 = "e.g., en"
multilang_695 = "Google reCAPTCHA is enabled on this REDCap system. The reCAPTCHA display language can be dynamically changed by associating a Google-supported language ({0:<a>}List of Language Codes){1:</a>} with this language."
multilang_696 = "The mark slider prompt shown on PDFs:"
multilang_697 = "Base Language"
multilang_698 = "<p>The <i>Base Language</i> should match the <b>project language</b> (i.e. the language REDCap user interface elements are displayed in). This usually is also the language used during project design, i.e. for all data dictionary items, survey settings, ASI or alert messages, missing data code labels, etc.</p> <p>If this is not the case, then a language corresponding to the project's UI language should be added and set as the <i>Base Language</i> (but it can be set as inactive if not used).</p>"
multilang_699 = "Create a base language. This is the language that corresponds to the project's language, i.e. the language of the REDCap user interface elements, such as this text, or the label of a submit button. This usually also matches the language used for field labels, survey instructions, etc., but not necessarily. Mark this language as the <i>Base Language</i>. If this language matches your data dictionary language, then you might want to mark it as the <i>Fallback</i> as well."
multilang_700 = "In case your data dictionary elements are not matching the <i>Base Language</i>, add a matching language. You probably will set this as the <i>Fallback</i> language (the ultimate fallback will always be the <i>Base Language</i> for all user interface elements, and the data dictionary elements as set up outside of Multi-Language Management will provide the ultimate fallback for those in case the <i>Fallback</i> does not provide a value)."
multilang_701 = "Add any other languages that you wish to offer."
multilang_702 = "Provide translations for the different languages by clicking the tabs above, or use the icons to the right of each language in the table shown below. Keep in mind that languages have to be <i>Active</i> and enabled for individual instruments in data entry and/or survey modes separately."
multilang_703 = "Carefully test your translations by switching back and forth between languages on the data entry forms and/or surveys that have been enabled for these languages."
multilang_704 = "Manage the available languages in this project using the table and options below."
multilang_705 = "The warning message shown when trying to print a data entry form (Saves as PDF) with unsaved changes:"
multilang_706 = "Matrix of Fields"
multilang_707 = "<b>Tip:</b> It is possible to set the <i>initially displayed language</i> of a survey by supplying the URL parameter <b>{0:ParameterName}</b>, which must be set to a valid (active) language id (case-sensitve!). Example: <code>{1:ExampleUrl}</code>. When used, this will override both a survey respondent's previous choice (stored in a browser cookie) as well as the language preference field. The <code>@LANGUAGE-FORCE</code> action tag will still take precedence, though."
multilang_708 = "Same as @LANGUAGE-SET, but the effect is limited to data entry forms (i.e., this does not affect surveys)."
multilang_709 = "Same as @LANGUAGE-SET, but the effect is limited to surveys (i.e., this does not affect data entry forms)."
multilang_710 = "The default survey offline message:"
multilang_711 = "<b>Tip:</b> Choose your \"ASI Language Source\" wisely - If ASIs have been translated in your MLM setup, it is typically recommended that you utilize the \"Language preference field\" option for determining the translation to be used for an ASI survey invitation. Choosing \"User's or survey respondent's active language\" as the ASI Language Source can have unexpected results. For example, if a participant's survey response triggers the ASI, the ASI's invitation text will be output in the correct language since it uses what the participant has chosen previously. However, if the ASI is triggered by an action of the project user, such as a data import or saving a data entry form, the ASI's text will be in the language of the project user, which may not be the language that the participant prefers."
multilang_712 = "Translation of '{0}' (insert the placeholder at the appropriate location in the translated text):"
multilang_713 = "The 'thank you' message when there is no survey title:"
multilang_714 = "Translation of the project title in the MyCap app:"
multilang_715 = "Translation of the page title:"
multilang_716 = "Translation of the page content:"
multilang_717 = "Translation of the contact page title:"
multilang_718 = "Language-specific version of the contact name:"
multilang_719 = "Language-specific version of the contact phone:"
multilang_720 = "Language-specific version of the contact email:"
multilang_721 = "Language-specific version of the contact website URL:"
multilang_722 = "Translation of the additional contact info:"
multilang_723 = "Translation of the link name:"
multilang_724 = "Translation of the link URL:"
multilang_725 = "Activities"
multilang_726 = "Profiles"
multilang_727 = "Translation for:"
multilang_728 = "Instruction Step - Title"
multilang_729 = "Instruction Step - Content"
multilang_730 = "Completion Step - Title"
multilang_731 = "Completion Step - Content"
multilang_732 = "Tasks/Fields"
multilang_733 = "There are no MyCap settings in this category that can be translated."
multilang_734 = "Select a language:"
multilang_735 = "Check to enable this language"
multilang_736 = "Check to enable translations on data entry instruments"
multilang_737 = "Check to enable translations surveys"
multilang_738 = "For single instruments, export translations, or download a translated, empty PDF"
multilang_739 = "Check to mark the task items as translated"
multilang_740 = "Task:"
multilang_741 = "Questionnaire"
multilang_743 = "Baseline Date Task"
multilang_744 = "Question whether baseline date is today"
multilang_745 = "Question to ask for past date"
multilang_746 = "Translations of MyCap settings"
multilang_747 = "How to use this file: The essential elements are all 'id', 'type', 'form', 'order', and 'translation' items and the paths leading to them, as well as the root elements 'creator' (must be left as is), 'key', 'display', and 'rtl'. All other items, including this text, are non-essential and will not be regarded during an import operation. Furthermore, subsets of this file can be created and used at will, as long as it remains valid JSON. The 'hash' items are not essential, but assist in tracking if a default value has changed since the file was created, and thus a translation may be out of date. During an import operation, a best-effort approach is taken. Any paths and/or ids that do not match the target will be silently ignored."
multilang_748 = "Note, since this instrument is a <b>MyCap Task</b>, the fields holding task-related data are hidden. You may still reveal them if you wish, but it is generally not recommended to not translate them."
multilang_749 = "Reveal Task Fields"
multilang_750 = "This field holds MyCap Task-related data."
multilang_751 = "<b>This is the default language.</b> There are no items on this tab that can be edited for the default language.<br><i>Please choose another language.</i>"
multilang_752 = "App Title & Baseline Date Task"
multilang_753 = "Messages"
multilang_754 = "About"
multilang_755 = "Contacts"
multilang_756 = "Links"
multilang_757 = "Tasks"
multilang_758 = "Active Task: General"
multilang_759 = "Active Task: 9-Hole Peg Test"
multilang_760 = "Active Task: Amsler Grid"
multilang_761 = "Active Task: Audio Recording"
multilang_762 = "Active Task: Fitness"
multilang_763 = "Active Task: Paced Serial Addition Test (PSAT)"
multilang_764 = "Active Task: Selfie Capture"
multilang_765 = "Active Task: Gait and Balance (Short Walk)"
multilang_766 = "Active Task: Spatial Memory"
multilang_767 = "Active Task: Stroop"
multilang_768 = "Active Task: Sustained Phonation"
multilang_769 = "Active Task: Timed Walk"
multilang_770 = "Active Task: Tower of Hanoi"
multilang_771 = "Active Task: Trail Making Test"
multilang_772 = "<b>Note:</b> Please ensure you are using a Language ID from the list if you wish to utilize a specific language in the MyCap app."
multilang_773 = "Show List"
multilang_774 = "Hide List"
multilang_775 = "This option determines whether a language is active for the <i>MyCap</i> app. Unlike forms and surveys, which can be enabled individually for each language, enabling a language for <i>MyCap</i> is an all-or-nothing setting. If a language is not active for MyCap, it will not appear in the <i>MyCap</i> app."
multilang_776 = "You may click on the Language ID from the list below to populate in the Language ID and Language Display Name."
multilang_777 = "Translations of survey queue items"
multilang_778 = "When this action tag is present on any field of an instrument enabled as a survey and Multi-Language Management is active with at least two active languages, the language selection menu will remain visible at all times (i.e., it will not collapse after a language button has been clicked)."
multilang_779 = "Language Notes"
multilang_780 = "Enter any notes regarding this language"
multilang_781 = "Notes may be useful to provide additional information about the language, the source of the translations, or any other information that is <b>relevant to you</b>. Notes are exported on demand only, and never imported (except when creating a new language)."
multilang_782 = "Include language notes"
multilang_783 = "Invalid column names. Expected: 'section,type,name,index,kind,text'; actual: '{0}'"
multilang_784 = "The language ID used is not supported in MyCap. Please confirm you are using the language ID for languages that MyCap supports. If you are using a language or language ID that isn't supported by MyCap, your survey questions will appear as translated, but the app's user interface (e.g., buttons, headers, tabs) will not be translated."
multilang_785 = "Translation of the popup content:"
multilang_786 = "Descriptive Popup '{0}'"
multilang_787 = "Collapse translated"
multilang_788 = "Language-specific link text:"
datatables_01 = "No data available in table"
datatables_02 = "Showing _START_ to _END_ of _TOTAL_ entries"
datatables_03 = "Showing 0 to 0 of 0 entries"
datatables_04 = "(filtered from _MAX_ total entries)"
datatables_05 = "Show _MENU_ entries"
datatables_06 = "Search:"
datatables_07 = "No matching records found"
datatables_08 = "First"
datatables_09 = "Last"
datatables_10 = "Next"
datatables_11 = "Previous"
datatables_12 = ": activate to sort column ascending"
datatables_13 = ": activate to sort column descending"
cdp_instant_adjudication_cronjob_settings_title = "Auto-adjudicate"
cdp_instant_adjudication_cronjob_settings_description = "Enable \"auto-adjudicate\" and REDCap will automatically adjudicate fetched records in a background process"
cdp_instant_adjudication_cronjob_settings_label = "Auto-adjudicate all clinical data once a day"
override_system_bundle_ca_title = "CA certificates"
override_system_bundle_ca_description = "To interact with FHIR resources, REDCap must be able to verify the identity of the EHR system using a bundle of CA (certificate authority) certificates. A digital certificate certifies the ownership of a public key by the named subject of the certificate. You can choose whether to use the bundle of CA certificates included in REDCap or use the system provided by your webserver."
override_system_bundle_ca_use_redcap = "Use the bundle of CA included in REDCap"
override_system_bundle_ca_use_system = "Use the verification provided by your webserver"
fhir_identity_provider_title = "Identity provider (optional)"
fhir_identity_provider_subtitle = "The identity provider is used in the OAuth2 authorization process to identify the server that will exchange the FHIR access token with REDCap."
fhir_identity_provider_description = "Set this parameter only if the real FHIR base URL of your EHR system is different from the one specified in this page (e.g., your EHR system is behind a proxy)."
fhir_identity_provider_description2 = "More information about the launch sequence can be <a href=\"https://build.fhir.org/ig/HL7/smart-app-launch/app-launch.html#request-4\" target=\"_blank\">found here</a>."
cdis_diff_category_1 = "Most common uses"
cdis_diff_category_2 = "Data mapping to EHR fields"
cdis_diff_category_3 = "Activation process"
cdis_diff_category_4 = "User privileges"
cdis_diff_category_5 = "Usage"
cdis_diff_ddp_1 = "Real-time data collection"
cdis_diff_ddp_2 = "Prospective clinical studies/trials"
cdis_diff_ddp_3 = "Longitudinal and/or multi-arm studies"
cdis_diff_ddp_4 = "Field mapping must be set up prior to data pull by a user with CDP Setup/Mapping privileges in the project. This is completed via the CDP mapping page (accessed via the Project Setup page)."
cdis_diff_ddp_5 = "Mapping can be adjusted at any time in a CDP project, and it can be complex when mapping EHR fields to REDCap fields (allows for one-to-many, many-to-one, or many-to-many mapping)."
cdis_diff_ddp_6 = "Temporal data (e.g., vital signs and labs) must have an accompanying date or date/time field (e.g., visit date) for determining the window of time in which to pull data (using the ± day offset). Temporal data can be mapped to fields in a classic project, to events in a longitudinal project, or to repeating instruments/events."
cdis_diff_ddp_7 = "All values for Allergies, Medications, and Problem List will be merged together for each category and each saved in its own a Notes/Paragraph field (if mapped)."
cdis_diff_ddp_8 = "The local institution may have a formal process to evaluate the users/project prior to approval (recommended) - e.g., check IRB status, check users' EHR access."
cdis_diff_ddp_9 = "REDCap administrator must enable CDP for the project on the project's Project Setup page."
cdis_diff_ddp_10 = "Project users can set up field mapping and adjudicate data from the EHR if they have project-level rights to do so. In order to adjudicate data from the EHR, users must have access to the EHR and must have launched at least one patient in the REDCap window inside the EHR user interface."
cdis_diff_ddp_11 = "REDCap administrator and team can optionally create a User Access Web Service to further control user access during adjudication (info documented on this page)."
cdis_diff_ddp_12 = "Users must launch a patient in the REDCap window inside the EHR user interface, and will be able to add the patient to any CDP-enabled REDCap project to which they have access. Once the patient is in a project, the user can manually pull data from the EHR for the patient."
cdis_diff_ddp_13 = "Data pulled from the EHR is not saved immediately in the project but is stored temporarily in a cache, in which users must first review/adjudicate all data values before being saved in the project."
cdis_diff_ddp_14 = "Once a patient has been added to a project, CDP will automatically (via a cron job) continue to look for any new data added to the EHR for up to X days, in which X is the value of the setting \"Time of inactivity after which REDCap will stop checking for new data\" (info documented on this page)."
cdis_diff_ddm_1 = "Registries"
cdis_diff_ddm_2 = "Prospective or retrospective clinical studies/trials"
cdis_diff_ddm_3 = "Searching for specific lab values or diagnosis codes for a cohort of patients over a set time period"
cdis_diff_ddm_4 = "Mapping is not required since the project structure/instruments are pre-defined when the project is created. Demographics is created as a single data collection form, and the following forms are created as repeating instruments: Vital Signs, Labs, Allergies, Medications, and Problem List. Each data value on the repeating instruments are represented as a separate repeating instance of the form."
cdis_diff_ddm_5 = "User defines the data pull configuration when creating the project - e.g., chooses specific MRNs, date range, and data fields from the EHR."
cdis_diff_ddm_6 = "Project-level settings control whether or not users in the project can 1) fetch data just one time or as often as they wish, 2) modify the data pull configuration or not and 3) if new data is pulled automatically with a cron job once a day. These settings may be changed only by a REDCap administrator."
cdis_diff_ddm_7 = "The local institution may have a formal process to evaluate the users/project prior to approval (recommended) - e.g., check IRB status, check users' EHR access."
cdis_diff_ddm_8 = "Project is first created by a user, but each revision of the data pull configuration will go through an audit process and approved by a REDCap administrator via the To-Do List (if the project-level setting has been enabled to allow configuration changes)."
cdis_diff_ddm_9 = "A user's REDCap account must be given Data Mart privileges by a REDCap administrator on the Browse Users page in the Control Center, after which the user will be able to create a Data Mart project and pull EHR data. (Note: This is not a project-level user right but a REDCap user account privilege.) Also, there is no optional User Access Web Service as there is with CDP to further control user access for pulling data."
cdis_diff_ddm_10 = "In order to pull data from the EHR, users must have access to the EHR and must have launched at least one patient in the REDCap window inside the EHR user interface."
cdis_diff_ddm_11 = "Users with Project Setup/Design rights in a Data Mart project will be able to request changes to the data pull configuration (if needed and if the project-level setting has been enabled)."
cdis_diff_ddm_12 = "Data Mart will pull data from the EHR when a user with appropriate privileges clicks the \"Fetch clinical data\" button. Also a cron job may be set from the Project-level settings control to pull any new data once a day automatically."
cdis_diff_ddm_13 = "To pull new data values in the EHR, a user must manually click the Fetch button again (assuming the project-level setting is enabled to allow more than one data pull)."
cdis_diff_ddm_14 = "Extra instruments or events may be added to the Data Mart Project, but if any of the pre-defined fields or instruments are modified, it may prevent the data pull from working successfully thereafter."
mycap_mobile_app_01 = "Participants"
mycap_mobile_app_02 = "About"
mycap_mobile_app_03 = "Contacts"
mycap_mobile_app_04 = "Links"
mycap_mobile_app_05 = "Theme"
mycap_mobile_app_06 = "The \"about\" pages are the first thing to appear after a participant scans his/her QR code. The first home page is required and CANNOT be deleted.  The logo that represents your project should be uploaded to the home page. Clicking the preview button will show you approximately how each page  will look in the mobile app. You may add as many informational pages as you like."
mycap_mobile_app_07 = "Create new about"
mycap_mobile_app_08 = "Edit About"
mycap_mobile_app_09 = "You may define the informational pages for MyCap mobile app below. After clicking the Save button at the bottom,  your page will be saved and after clicking \"Publish\", it will immediately become visible in App.  You may modify an existing page at any time."
mycap_mobile_app_10 = "STEP 1: Enter Page Information"
mycap_mobile_app_11 = "Title of this page:"
mycap_mobile_app_12 = "Page Content:"
mycap_mobile_app_13 = "STEP 2: Select Image"
mycap_mobile_app_14 = "Image Type"
mycap_mobile_app_15 = "System"
mycap_mobile_app_16 = "Custom"
mycap_mobile_app_17 = "Select System Image"
mycap_mobile_app_18 = "Custom Image"
mycap_mobile_app_19 = "Upload custom image:"
mycap_mobile_app_20 = "Preview (displaying here at max 250 pixel width):"
mycap_mobile_app_21 = "Do you wish to delete this image?"
mycap_mobile_app_22 = "Please set a title for this page."
mycap_mobile_app_23 = "Please enter page contents."
mycap_mobile_app_24 = "Image Preview"
mycap_mobile_app_25 = "Delete page?"
mycap_mobile_app_26 = "Are you sure you wish to DELETE the page named"
mycap_mobile_app_27 = "select a page"
mycap_mobile_app_28 = "[PAGE IS CURRENTLY LOCATED HERE]"
mycap_mobile_app_29 = "You may move the page listed below to any location on the current pages listing.  Choose from the drop-down below the location to which you wish to move this page."
mycap_mobile_app_30 = "Page to be moved:"
mycap_mobile_app_31 = "Move an page to another location"
mycap_mobile_app_32 = "Move the page above so that it will be located immediately *AFTER* the following page:"
mycap_mobile_app_33 = "Move page"
mycap_mobile_app_34 = "Please select a page"
mycap_mobile_app_35 = "The page was successfully moved to a new location!"
mycap_mobile_app_36 = "PLEASE NOTE that moving this page may have caused some or all of the pages to be re-numbered  automatically. They will still retain their same page title, but their page  number (#) may have changed because page numbers are generated on the fly based on the order of the pages."
mycap_mobile_app_37 = "New page created."
mycap_mobile_app_38 = "The page was updated."
mycap_mobile_app_39 = "The page was permanently deleted."
mycap_mobile_app_40 = "Remove Image"
mycap_mobile_app_41 = "This is Home page and thus CANNOT BE DELETED or MOVED. It can ONLY be edited."
mycap_mobile_app_42 = "Please upload custom image."
mycap_mobile_app_43 = "The custom image file you selected is not an image file (e.g., GIF, JPG, JPEG, BMP, PNG). Please try again."
mycap_mobile_app_44 = "Links appear in the MyCap app's menu below the \"About\" list item. A link is comprised of an icon, name, and URL.  The icon and name are displayed in the menu. Links can be configured to include your MyCap  project code and participant code."
mycap_mobile_app_45 = "Link name"
mycap_mobile_app_46 = "Link options"
mycap_mobile_app_47 = "Create New Link"
mycap_mobile_app_48 = "Icon"
mycap_mobile_app_49 = "You may define the links for MyCap mobile app below. After clicking the Save button at the bottom,  your link will be saved and after clicking \"Publish\", it will immediately become visible in App.  You may modify or remove an existing link at any time."
mycap_mobile_app_50 = "STEP 1: Enter Link Information"
mycap_mobile_app_51 = "Link Name:"
mycap_mobile_app_52 = "Link URL:"
mycap_mobile_app_53 = "STEP 2: Select Icon"
mycap_mobile_app_54 = "Edit Link"
mycap_mobile_app_55 = "Link Icon:"
mycap_mobile_app_56 = "Please set a link name."
mycap_mobile_app_57 = "Please enter link url."
mycap_mobile_app_58 = "Please select link icon."
mycap_mobile_app_59 = "Append Project Code?"
mycap_mobile_app_60 = "Should \"&projectCode=[P-EXAMPLEPROJECTCODE]\" be appended to the URL? You may want to append the project code if you are building a custom website to  display results for multiple projects using MyCap."
mycap_mobile_app_61 = "Append Participant Code?"
mycap_mobile_app_62 = "Should \"&participantCode=[U-EXAMPLEPARTICIPANTCODE]\" be appended to the URL? You may want to append the participant code if you are building a custom website to  display information specific to a participant."
mycap_mobile_app_63 = "Are you sure you wish to DELETE the link named"
mycap_mobile_app_64 = "Delete link?"
mycap_mobile_app_65 = "Link URL is not valid. Please fix it and try again."
mycap_mobile_app_66 = "Drag link up or down to move it"
mycap_mobile_app_67 = "New link created."
mycap_mobile_app_68 = "The link was updated."
mycap_mobile_app_69 = "The link was permanently deleted."
mycap_mobile_app_70 = "Additional Info"
mycap_mobile_app_71 = "Specify who a participant should contact if they have questions. Your contact(s) will be listed on the \"Get Support\" page in the MyCap mobile app. A contact could be a person or a website. You may add multiple contacts. Clicking the preview button will show you approximately how the contacts will look in the MyCap mobile app. It is recommended that you have at least one contact."
mycap_mobile_app_72 = "Create New Contact"
mycap_mobile_app_73 = "Edit Contact"
mycap_mobile_app_74 = "Please set a contact title."
mycap_mobile_app_75 = "Are you sure you wish to DELETE the contact named"
mycap_mobile_app_76 = "Delete contact?"
mycap_mobile_app_77 = "New contact created."
mycap_mobile_app_78 = "The contact was updated."
mycap_mobile_app_79 = "The contact was permanently deleted."
mycap_mobile_app_80 = "Choose a color scheme or create your own. We recommend following the <a href=\"https://material.io/color/\" target=\"_blank\">Material Design color system</a>.  <b>NOTE:</b> MyCap only updates the theme when the app loads into memory. You need to force close MyCap and then reopen to see your theme change.  Additionally, this feature is <b>not available on Android devices.</b>"
mycap_mobile_app_81 = "<b>Option 1:</b> Select a predefined color scheme."
mycap_mobile_app_82 = "<b>Option 2:</b> Create custom color schemes. (Choose your colors and click the \"Save Theme\" button.)"
mycap_mobile_app_83 = "Legend for theme letters:"
mycap_mobile_app_84 = "Primary Color"
mycap_mobile_app_85 = "Light Primary Color"
mycap_mobile_app_86 = "Accent Color"
mycap_mobile_app_87 = "Dark Primary Color"
mycap_mobile_app_88 = "Light Background Color"
mycap_mobile_app_89 = "Save Theme"
mycap_mobile_app_90 = "The Theme was updated."
mycap_mobile_app_91 = "Current version:"
mycap_mobile_app_92 = "Publish new MyCap version"
mycap_mobile_app_93 = "A new MyCap configuration version has been published successfully."
mycap_mobile_app_94 = "Are you sure you want to PUBLISH a new MyCap configuration version?"
mycap_mobile_app_95 = "Publish"
mycap_mobile_app_96 = "MyCap uses a configuration versioning system. When a participant opens their MyCap mobile app, it sends a request to the REDCap server to see if a new configuration version has been published. The mobile app updates itself as needed if a new version is found."
mycap_mobile_app_97 = "Add new About page"
mycap_mobile_app_98 = "The contact was successfully moved to a new location."
mycap_mobile_app_99 = "The link was successfully moved to a new location."
mycap_mobile_app_100 = "Enabled as MyCap task"
mycap_mobile_app_101 = "MyCap"
mycap_mobile_app_102 = "Modify the MyCap task settings"
mycap_mobile_app_103 = "Set Up MyCap Task"
mycap_mobile_app_104 = "The MyCap mobile app shows a list of tasks (instruments) that a participant needs to complete for any given date. Each task is represented by a card.   When a participant taps a card the task begins. When a task is completed a result is stored in an encrypted database on the participant's device.   If the participant has an active internet connection the result will be synchronized to REDCap. If the participant does not have an active internet   connection then the result is stored in a queue. Every time a participant completes a task all results in the queue will attempt to synchronize."
mycap_mobile_app_105 = "Collect data for this REDCap instrument?"
mycap_mobile_app_106 = "If not selected, participants will not be able see the task in App."
mycap_mobile_app_107 = "Basic Task Info:"
mycap_mobile_app_108 = "Task Title"
mycap_mobile_app_109 = "This is Card Title to be displayed to participants at the top of the task page"
mycap_mobile_app_110 = "Format"
mycap_mobile_app_111 = "Each question appears on its own screen. Recommended. Branching logic is supported."
mycap_mobile_app_112 = "It displays task progress using a circular progress indicator. <br><b>For example</b>, If your task has 20 questions and a participant completes 10 questions then the indicator would show 50% complete.   Most tasks will use this card display type."
mycap_mobile_app_113 = "It displays task results in a chart view. <br><br>Your instrument must have at least three REDCap fields:"
mycap_mobile_app_114 = "Card Display"
mycap_mobile_app_115 = "Percent Complete"
mycap_mobile_app_116 = "Chart"
mycap_mobile_app_117 = "Allow retroactive completion?"
mycap_mobile_app_118 = "Allow participant to complete tasks that were scheduled for a previous date (Not applicable for tasks with an \"Infinite\" schedule)"
mycap_mobile_app_119 = "Allow save and complete later?"
mycap_mobile_app_120 = "Should the participant complete the task all at once? or can the participant complete part of the task and finish later. Recommended for long tasks."
mycap_mobile_app_121 = "Include instruction step?"
mycap_mobile_app_122 = "You may display an instruction step that appears before the task begins"
mycap_mobile_app_123 = "Include completion step?"
mycap_mobile_app_124 = "You may display a completion step that appears after the task is completed"
mycap_mobile_app_125 = "Install Date"
mycap_mobile_app_126 = "Content"
mycap_mobile_app_127 = "Baseline Date"
mycap_mobile_app_128 = "Relative to which date task should be scheduled?"
mycap_mobile_app_129 = "All questions appear on a single screen. Participant may need to scroll if the form is long. Branching logic is not supported."
mycap_mobile_app_130 = "Card Display Example:"
mycap_mobile_app_131 = "Your MyCap Task settings were successfully saved!"
mycap_mobile_app_132 = "You may edit the MyCap task's basic information by modifying the fields below and clicking the Save Changes button."
mycap_mobile_app_133 = "Click to modify MyCap settings"
mycap_mobile_app_134 = "1. <b>Date Field</b> - Y axis. Enter the REDCap field name for a field having a format \"Text, Validation = Date (DYM, MDY, or YMD)\""
mycap_mobile_app_135 = "2. <b>Time Field</b> - Enter the REDCap field name for a field having a format \"Text, Validation = Time (HH:MM)\""
mycap_mobile_app_136 = "3. <b>Numeric Field</b> - X axis. Enter the REDCap field name for a field having a format \"Text, Validation = Integer or Number\""
mycap_mobile_app_137 = "Set the Task Schedule:"
mycap_mobile_app_138 = "Task should be scheduled relative to the date the participant scanned the QR code"
mycap_mobile_app_139 = "Task should be scheduled relative to the participant's baseline date"
mycap_mobile_app_140 = "Schedule it how many times?"
mycap_mobile_app_141 = "One Time"
mycap_mobile_app_142 = "Infinite"
mycap_mobile_app_143 = "Repeating"
mycap_mobile_app_144 = "Fixed"
mycap_mobile_app_145 = "Number of days to delay"
mycap_mobile_app_146 = "Never"
mycap_mobile_app_147 = "After it has been completed"
mycap_mobile_app_148 = "After"
mycap_mobile_app_149 = "days have elapsed"
mycap_mobile_app_150 = "At exact date: "
mycap_mobile_app_151 = "Please set a task title for this instrument."
mycap_mobile_app_152 = "If you would like to remove this page, it may be deleted at any time."
mycap_mobile_app_153 = "You may define a contact person and their info which will be provided in the MyCap mobile app for participants to view. After saving the info below and then clicking \"Publish New Version\", the info will immediately become visible to participants in their mobile app. You may modify or remove a contact at any time."
mycap_mobile_app_154 = "Click to select"
mycap_mobile_app_155 = "Material Design"
mycap_mobile_app_156 = "Information"
mycap_mobile_app_157 = "... [Full text will appear in mobile app]"
mycap_mobile_app_158 = "Website URL"
mycap_mobile_app_159 = "Chart Fields"
mycap_mobile_app_160 = "Date field:"
mycap_mobile_app_161 = "Time field:"
mycap_mobile_app_162 = "Numeric field:"
mycap_mobile_app_163 = "Please make sure this instrument have at least three REDCap fields of type - Date, Time and Number/Integer. Selection of these fields are <u>mandatory</u>.   <br>NOTE: If not you can not proceed with option \"Chart\". Alternatively, You may select \"Percent Complete\" option."
mycap_mobile_app_164 = "Instruction Steps"
mycap_mobile_app_165 = "Completion Steps"
mycap_mobile_app_166 = "Please select date field."
mycap_mobile_app_167 = "Please select time field."
mycap_mobile_app_168 = "Please select numeric field."
mycap_mobile_app_169 = "Please enter title for instruction step."
mycap_mobile_app_170 = "Please enter instruction steps."
mycap_mobile_app_171 = "Please enter title for completion step."
mycap_mobile_app_172 = "Please enter completion steps."
mycap_mobile_app_173 = "Repeating > Repeats (Weekly) > On: Please select at least one day."
mycap_mobile_app_174 = "Repeating > Repeats (Monthly) > On Day(s): Please enter comma-delimited days and day must be between 1 and 31."
mycap_mobile_app_175 = "Found invalid number:"
mycap_mobile_app_176 = "Fixed > On Day(s): Please enter comma-delimited list of days."
mycap_mobile_app_178 = "Number of days to delay:"
mycap_mobile_app_179 = "Ends (After Number of Occurrences) > When: Must be a non-zero number."
mycap_mobile_app_180 = "Ends (After Number of Days) > When: Must be a non-zero number."
mycap_mobile_app_181 = "Ends (At exact date) > When: Please select date."
mycap_mobile_app_182 = "Errors in"
mycap_mobile_app_183 = "SUCCESS! The active task was successfully created. The page will now redirected to edit this task settings."
mycap_mobile_app_184 = "NOTE: Please be aware that this instrument is created from Active task and contains pre-defined set of fields. These fields are designed for data collection from MyCap Mobile app. Please DO NOT MODIFY any field."
mycap_mobile_app_185 = "Active Tasks"
mycap_mobile_app_186 = "See <a href='http://researchkit.org/docs/docs/ActiveTasks/ActiveTasks.html' target='_blank' style='text-decoration:underline;'>ResearchKit Active Tasks</a>. Click one of the add buttons to create a predefined active task. All required REDCap fields are created automaticially.   <b>DO NOT MODIFY</b> the fields in the instrument using Online Designer.<br> Most active tasks are developed by 3rd party programmers and researchers.   MyCap developers have added these active tasks but do not have expertise in the returned results. It is up to you to ensure you understand the returned results.   MyCap developers will help as much as possible."
mycap_mobile_app_187 = "Create New Instrument"
mycap_mobile_app_188 = "To create a predefined active task "
mycap_mobile_app_189 = ", enter the name of the new instrument below."
mycap_mobile_app_190 = "Import Active Task"
mycap_mobile_app_191 = "for MyCap from a library of"
mycap_mobile_app_192 = "Get Support"
mycap_mobile_app_193 = "Intended use description"
mycap_mobile_app_194 = "A string describing the intended use of the data collected. If the value of this parameter is nil, the default localized text will be displayed."
mycap_mobile_app_195 = "Limb Option"
mycap_mobile_app_196 = "Which body part is being measured."
mycap_mobile_app_197 = "Which limb is being measured."
mycap_mobile_app_198 = "Knee"
mycap_mobile_app_199 = "Shoulder"
mycap_mobile_app_200 = "Left"
mycap_mobile_app_201 = "Right"
mycap_mobile_app_202 = "Number of steps per leg"
mycap_mobile_app_203 = "The number of steps the participant is asked to walk. If the pedometer is unavailable, a distance is suggested and a suitable count down timer is displayed for each leg of the walk."
mycap_mobile_app_204 = "Maximum span cannot be less than initial span"
mycap_mobile_app_205 = "Rest duration"
mycap_mobile_app_206 = "The duration in seconds of the rest period. When the value of this parameter is nonzero, the user is asked to stand still for the specified rest period after the turn sequence has been completed, and baseline data is collected."
mycap_mobile_app_207 = "Duration"
mycap_mobile_app_208 = "cannot be less than"
mycap_mobile_app_209 = "The length of the count down timer that runs while touch data is collected."
mycap_mobile_app_210 = "Hand Options"
mycap_mobile_app_211 = "Options for determining which hand(s) to test."
mycap_mobile_app_212 = "Walk duration"
mycap_mobile_app_213 = "The duration in seconds of the walk (the maximum is 10 minutes)."
mycap_mobile_app_214 = "Maximum span cannot be greater than"
mycap_mobile_app_215 = "The duration in seconds of the post walk rest period."
mycap_mobile_app_216 = "Distance in meters"
mycap_mobile_app_217 = "Timed walk distance must be greater than or equal to"
mycap_mobile_app_218 = "meters and less than or equal to"
mycap_mobile_app_219 = "meters"
mycap_mobile_app_220 = "The timed walk distance in meters."
mycap_mobile_app_221 = "The maximum pattern sequence length."
mycap_mobile_app_222 = "The time limit in seconds to complete the trials."
mycap_mobile_app_223 = "Inital span"
mycap_mobile_app_224 = "Play speed"
mycap_mobile_app_225 = "Initial span cannot be less than minimum span"
mycap_mobile_app_226 = "The sequence length of the initial memory pattern."
mycap_mobile_app_227 = "Minimum span"
mycap_mobile_app_228 = "The minimum pattern sequence length."
mycap_mobile_app_229 = "Maximum span"
mycap_mobile_app_230 = "Play speed cannot be longer than"
mycap_mobile_app_231 = "The time per sequence item; a smaller value means faster sequence play."
mycap_mobile_app_232 = "Max tests"
mycap_mobile_app_233 = "The maximum number of rounds to conduct."
mycap_mobile_app_234 = "Max consecutive Failures"
mycap_mobile_app_235 = "The maximum number of consecutive failures the user can make before the task is terminated."
mycap_mobile_app_236 = "Require reversal?"
mycap_mobile_app_237 = "A Boolean value that indicates whether to require the user to tap the sequence in reverse order."
mycap_mobile_app_238 = "Number of attempts"
mycap_mobile_app_239 = "Number of attempts should be greater or equal to"
mycap_mobile_app_240 = "Total number of stroop questions to include in the task."
mycap_mobile_app_241 = "Trail making instruction"
mycap_mobile_app_242 = "Instructional content describing what the user needs to do when the task begins. If the value of this parameter is nil, the default localized text is displayed."
mycap_mobile_app_243 = "Trail Type"
mycap_mobile_app_244 = "Type of trail to display."
mycap_mobile_app_245 = "A"
mycap_mobile_app_246 = "B"
mycap_mobile_app_247 = "Presentation Mode"
mycap_mobile_app_248 = "The presentation mode of the PSAT test (auditory or visual or both)."
mycap_mobile_app_249 = "Auditory and Visual"
mycap_mobile_app_250 = "Auditory only"
mycap_mobile_app_251 = "Visual only"
mycap_mobile_app_252 = "Inter stimulus interval"
mycap_mobile_app_253 = "must be greater than or equal to"
mycap_mobile_app_254 = "The time interval in seconds between two digits presented."
mycap_mobile_app_255 = "Stimulus duration"
mycap_mobile_app_256 = "The time duration in seconds the digit is shown on screen (only for visual PSAT, that is PVSAT and PAVSAT)."
mycap_mobile_app_257 = "Series length"
mycap_mobile_app_258 = "additions"
mycap_mobile_app_259 = "The number of digits that will be presented during the task."
mycap_mobile_app_260 = "Number of disks"
mycap_mobile_app_261 = "Having a large number of disks provides a poor user experience. This should be less than"
mycap_mobile_app_262 = "The number of disks in the puzzle."
mycap_mobile_app_263 = "Maximum stimulus interval"
mycap_mobile_app_264 = "Maximum stimulus interval cannot be less than minimum stimulus interval."
mycap_mobile_app_265 = "The maximum interval before the stimulus is delivered."
mycap_mobile_app_266 = "Minimum stimulus interval"
mycap_mobile_app_267 = "must be greater than"
mycap_mobile_app_268 = "The minimum interval before the stimulus is delivered."
mycap_mobile_app_269 = "Threshold acceleration"
mycap_mobile_app_270 = "The acceleration required to end a reaction time test."
mycap_mobile_app_271 = "The number of successful attempts required before the task is complete. The active step result will contain this many child results if the task is completed."
mycap_mobile_app_272 = "Timeout"
mycap_mobile_app_273 = "The interval permitted after the stimulus until the test fails, if the threshold is not reached."
mycap_mobile_app_274 = "Success sound"
mycap_mobile_app_275 = "Changing the success sound has not been fully tested. Please keep the value at 0."
mycap_mobile_app_276 = "The sound (ID) to play after a successful attempt."
mycap_mobile_app_277 = "Timeout sound"
mycap_mobile_app_278 = "Changing the timeout sound has not been fully tested. Please keep the value at 0."
mycap_mobile_app_279 = "The sound (ID) to play after an attempt that times out."
mycap_mobile_app_280 = "Failure sound"
mycap_mobile_app_281 = "Changing the failure sound has not been fully tested. Please keep the value at 0."
mycap_mobile_app_282 = "The sound (ID) to play after an unsuccessful attempt."
mycap_mobile_app_283 = "Speech instruction"
mycap_mobile_app_284 = "Instructional content describing what the user needs to do when recording begins. If the value of this parameter is nil, default localized text is used."
mycap_mobile_app_285 = "Short speech instruction"
mycap_mobile_app_286 = "Instructional content shown during audio recording. If the value of this parameter is nil, default localized text is used."
mycap_mobile_app_287 = "The length of the count down timer that runs while audio data is collected."
mycap_mobile_app_288 = "Check audio level?"
mycap_mobile_app_289 = "If YES then add navigational rules to check the background noise level."
mycap_mobile_app_290 = "Select Locale"
mycap_mobile_app_291 = "Locale to be used by speech recognition API."
mycap_mobile_app_292 = "Speech recognition text"
mycap_mobile_app_293 = "The text shown to the participant."
mycap_mobile_app_294 = "Should hide transcript?"
mycap_mobile_app_295 = "The boolean value used to show or hide the transcription from the user."
mycap_mobile_app_296 = "Allows editing transcript?"
mycap_mobile_app_297 = "The boolean value used to present step that allows editting transcription."
mycap_mobile_app_298 = "Speech instruction"
mycap_mobile_app_299 = "Instructional content describing what the user needs to do when recording begins. If the value of this parameter is nil, default localized text is used."
mycap_mobile_app_300 = "Short speech instruction"
mycap_mobile_app_301 = "Instructional content shown during audio recording. If the value of this parameter is nil, default localized text is used."
mycap_mobile_app_302 = "Tone duration"
mycap_mobile_app_303 = "The maximum length of the duration in seconds for each tone (each tone can be interrupted sooner, after the participant presses the main button)."
mycap_mobile_app_304 = "Dominant hand"
mycap_mobile_app_305 = "The participant dominant hand that will be tested first."
mycap_mobile_app_306 = "Number of pegs"
mycap_mobile_app_307 = "The number of pegs to place in the pegboard."
mycap_mobile_app_308 = "Threshold"
mycap_mobile_app_309 = "Threshold must be less than"
mycap_mobile_app_310 = "The threshold value used for the detection area."
mycap_mobile_app_311 = "Rotated?"
mycap_mobile_app_312 = "A test variant that also requires peg rotation."
mycap_mobile_app_313 = "The duration in seconds allowed to validate the peg position."
mycap_mobile_app_314 = "MyCap Task settings"
mycap_mobile_app_315 = "Cannot modify active task instrument!"
mycap_mobile_app_316 = "This instrument cannot be modified in any way because it is an active task, which means that its fields are utilized using the MyCap Mobile App. You may, however, rename or delete the instrument."
mycap_mobile_app_317 = "Active task Instrument"
mycap_mobile_app_318 = "This instrument is an active task instrument. It can only be taken from the MyCap Mobile App. As such, all fields below are permanently locked and are not editable."
mycap_mobile_app_319 = "Intro page title"
mycap_mobile_app_320 = "Intro page instructions"
mycap_mobile_app_321 = "Capture page title"
mycap_mobile_app_322 = "An optional title displayed on the audio recording screen."
mycap_mobile_app_323 = "Capture page instructions"
mycap_mobile_app_324 = "A string or paragraph to read."
mycap_mobile_app_325 = "Recording Time"
mycap_mobile_app_326 = "Maxiumum length of time in seconds to record audio."
mycap_mobile_app_327 = "An optional title displayed on the capture selfie screen."
mycap_mobile_app_328 = "A string descripting capture selfie instructions."
mycap_mobile_app_329 = "Length of time the face should be within focus in the detector view."
mycap_mobile_app_330 = "Since this instrument is enabled as a MyCap task, would you also like to change the MyCap task title to"
mycap_mobile_app_331 = "The task title is currently"
mycap_mobile_app_332 = "Also change MyCap task title?"
mycap_mobile_app_333 = "Yes, also change task title"
mycap_mobile_app_334 = "The MyCap task title has now been changed to"
mycap_mobile_app_335 = "MyCap Task title changed!"
mycap_mobile_app_336 = "Type must be knee or shoulder"
mycap_mobile_app_337 = "Limb must be left, right"
mycap_mobile_app_338 = "You must specify"
mycap_mobile_app_339 = "Received invalid hand options:"
mycap_mobile_app_340 = "Specify hand options: Both, Left, or Right"
mycap_mobile_app_341 = "Trail type must be A or B"
mycap_mobile_app_342 = "Invalid value for field: checkAudioLevel"
mycap_mobile_app_343 = "Speech recognizer locale is not valid"
mycap_mobile_app_344 = "Should hide transcript must be Yes (1) or No (0)"
mycap_mobile_app_345 = "Allows editing transcript must be Yes (1) or No (0)"
mycap_mobile_app_346 = "Dominant hand must be left or right"
mycap_mobile_app_347 = "A an optional title displayed on the capture selfie screen."
mycap_mobile_app_348 = "Length of time the face should be within focus in the detector view."
mycap_mobile_app_349 = "Detection Time"
mycap_mobile_app_350 = "Since your project contains one or more MyCap tasks, please note that although you may change the project title above   for your new project, all task settings (including the task title) for each MyCap task will be copied and remain as-is in the copied project.   If you want to change your task basic information, optional settings, or task schedule settings after copying this project, you are welcome to do so   on the Online Designer page using the Enable button or edit link in \"Enabled as MyCap Task\" column for each data collection instrument."
mycap_mobile_app_351 = "The titles of your MyCap tasks are listed below:"
mycap_mobile_app_352 = "Cannot enable for MyCap!"
mycap_mobile_app_353 = "Triggers"
mycap_mobile_app_354 = "Delete MyCap Settings"
mycap_mobile_app_355 = "Active task"
mycap_mobile_app_356 = "Invite Participant"
mycap_mobile_app_357 = "Custom Participant Label"
mycap_mobile_app_358 = "You may use the options below to set the Custom Participant Label for your MyCap Participant List. The custom label can be very useful by displaying a more recognizable identifier for each participant in the list."
mycap_mobile_app_359 = "Designate a field as the Custom Participant Label"
mycap_mobile_app_361 = "You may designate a text field to serve as the Custom Participant Label whose value will be displayed in the MyCap Participant List."
mycap_mobile_app_362 = "Pipe fields to serve as your Custom Participant Label"
mycap_mobile_app_363 = "Are you sure you wish to DELETE this participant? If so, they will no longer be able to join the project in MyCap Mobile App.   <p style=\"color: #800000;\"><b>Please note:</b> If the participant was deleted by mistake or needs to be restored for some other reason, it may be undeleted/restored.</p>"
mycap_mobile_app_364 = "The participant has now been deleted from the Participant List."
mycap_mobile_app_365 = "All participants"
mycap_mobile_app_366 = "\"Participant Display Logic\" is an advanced feature that provides a way to use conditional logic to display or hide specific records as participants. This can be used to prevent specific records from being used as participants until certain conditions have been met. Below you may define condition you want."
mycap_mobile_app_367 = "Display the participant in the list when the logic below is <i>TRUE</i>."
mycap_mobile_app_368 = "Note: Leave blank (default) to allow participant on all record insertions."
mycap_mobile_app_369 = "Delete Participant?"
mycap_mobile_app_370 = "Are you sure you wish to restore/undelete this participant? If restored, the participant can immediately gain access to your project from the MyCap Mobile App."
mycap_mobile_app_371 = "Restore/undelete participant?"
mycap_mobile_app_372 = "Undelete the participant"
mycap_mobile_app_373 = "Undelete"
mycap_mobile_app_374 = "(in ascending order by record)"
mycap_mobile_app_375 = "Invite Participants"
mycap_mobile_app_376 = "Participant Display Logic"
mycap_mobile_app_377 = "Step 4) Verify the Preview of HTML generated in Step 2:"
mycap_mobile_app_378 = "1) Choose invitation format:"
mycap_mobile_app_379 = "Example: if '[last_name], [first_name]' where entered, then for record '102' it would display value 'Doe, Jon' under \"Participant Identifier\" column."
mycap_mobile_app_380 = "2) Copy the generated invitation text:"
mycap_mobile_app_381 = "3) How to distribute the invitation text to participants:"
mycap_mobile_app_382 = "Participants can join your project on the MyCap mobile app using a QR code or hyperlink that is unique to them and their record in your REDCap project. A participant's record must already exist in the REDCap project in order for them to get a QR code or link. The methods below will provide you with template language and directions on how to onboard participants into your project. To obtain an individual participant's QR code or join link after their record has been created in the project, see the MyCap Participant Management page."
mycap_mobile_app_383 = "How to Invite Participants to Use the MyCap Mobile App"
mycap_mobile_app_384 = "QR Code"
mycap_mobile_app_385 = "Hyperlink"
mycap_mobile_app_386 = "QR Code & Hyperlink"
mycap_mobile_app_387 = "Participant QR Code and Link"
mycap_mobile_app_388 = "Get Participant URL"
mycap_mobile_app_390 = "Join by Participant URL"
mycap_mobile_app_392 = "ERROR: Something went wrong while loading QR Code. Participant code is missing."
mycap_mobile_app_393 = "Get URL template text"
mycap_mobile_app_395 = "You may scan the QR code to join the project on the MyCap mobile app."
mycap_mobile_app_396 = "Get QR code template text"
mycap_mobile_app_397 = "Print for participant"
mycap_mobile_app_398 = "The task has been successfully deleted. You will now be redirected back to the Online Designer."
mycap_mobile_app_399 = "MyCap Task successfully deleted!"
mycap_mobile_app_400 = "Your participants allow logic is saved successfully."
mycap_mobile_app_401 = "Custom Participant Label was saved successfully."
mycap_mobile_app_406 = "Scroll down to \"STEP 3: Message Settings\""
mycap_mobile_app_407 = "Click the \"Source code\" toolbar icon that looks like \"<>\". Paste the HTML that was copied to your clipboard."
mycap_mobile_app_408 = "Click the \"Source code\" toolbar icon again to toggle back to normal editing mode."
mycap_mobile_app_409 = "<b>Other ways to distribute QR codes:</b>"
mycap_mobile_app_410 = "You can also take a screenshot of the QR code and manually email it to a participant, or else print the QR code for the participant, if needed."
mycap_mobile_app_411 = "Set the alert schedule. For example,"
mycap_mobile_app_412 = "Send it Just once"
mycap_mobile_app_413 = "Select your Email From."
mycap_mobile_app_414 = "Select the email field from your instrument (you must use email validation for the field to appear here)."
mycap_mobile_app_415 = "Messages"
mycap_mobile_app_417 = "Inbox"
mycap_mobile_app_418 = "Outbox"
mycap_mobile_app_419 = "Announcements"
mycap_mobile_app_420 = "Announcements can be used to send information to <b>ALL</b> participants in your project. This is similar to the Participant > Message feature."
mycap_mobile_app_421 = "Announcement Title"
mycap_mobile_app_422 = "Create New Announcement"
mycap_mobile_app_423 = "Edit Announcement"
mycap_mobile_app_424 = "No announcements exist"
mycap_mobile_app_425 = "Announcement List"
mycap_mobile_app_426 = "Add New Announcement"
mycap_mobile_app_427 = "(in descending order by date)"
mycap_mobile_app_428 = "Please enter title."
mycap_mobile_app_429 = "Please enter message."
mycap_mobile_app_430 = "New announcement created."
mycap_mobile_app_431 = "The announcement was updated."
mycap_mobile_app_432 = "Inbox Messages"
mycap_mobile_app_433 = "No messages exist"
mycap_mobile_app_434 = "Received On"
mycap_mobile_app_435 = "From"
mycap_mobile_app_436 = "Action Needed?"
mycap_mobile_app_437 = "Announcement"
mycap_mobile_app_438 = "Are you sure you wish to send the message to the participant"
mycap_mobile_app_439 = "Please enter message body."
mycap_mobile_app_440 = "Send New Message?"
mycap_mobile_app_441 = "Sent Messages"
mycap_mobile_app_442 = "Sent On"
mycap_mobile_app_443 = "Are you sure you wish to REMOVE this announcement? If so, they will no longer be available for participants."
mycap_mobile_app_444 = "Remove Announcement"
mycap_mobile_app_445 = "The announcement was permanently deleted."
mycap_mobile_app_446 = "Editing and removing this announcement ONLY impacts future participants. Current participants will NOT be notified of any updates to this announcement."
mycap_mobile_app_447 = "<b>Please note:</b> This will publish all changes made on \"MyCap Mobile App > App Design\" pages ONLY. To publish changes made to task settings, you may use publish feature on Online Designer."
mycap_mobile_app_448 = "Please note after deleting this task setting, this instrument will no more available for data collection in MyCap Mobile App."
mycap_mobile_app_449 = "Delete this instrument's task settings?"
mycap_mobile_app_450 = "Delete MyCap Task Settings"
mycap_mobile_app_451 = "MyCap Options:"
mycap_mobile_app_452 = "After publishing a new version of the MyCap app configuration, your MyCap participants will receive these updates on their mobile device the next time they open the MyCap app."
mycap_mobile_app_453 = "Baseline Date Settings"
mycap_mobile_app_454 = "Use baseline date?"
mycap_mobile_app_455 = "A task can be scheduled relative to an Install Date or Baseline Date<br>   <b>Install Date:</b> The date a participant scans the QR code or uses a hyperlink to load your project. Automatically captured by MyCap. The Install Date is day 0 in a schedule.<br>   <b>Baseline Date:</b> Some projects schedule tasks relative to a baseline date. For example, the baseline date in a physical therapy project might indicate the date the participant began physical therapy.      A participant may install MyCap on 2017-01-01, but may begin therapy on 2017-01-20. If you want a daily diary task to appear after 2017-01-20 turn the <b>Use Baseline Date?</b> setting ON."
mycap_mobile_app_456 = "MyCap tasks can be scheduled relative to an Install Date or Baseline Date. If any tasks should be triggered based on a baseline date, check Use Baseline Date below."
mycap_mobile_app_457 = "Yes/No Question"
mycap_mobile_app_458 = "Date Question"
mycap_mobile_app_459 = "Include Instruction Step?"
mycap_mobile_app_460 = "You may include instruction steps."
mycap_mobile_app_461 = "Baseline Date Settings is saved successfully."
mycap_mobile_app_462 = "Designate a Baseline Date Field"
mycap_mobile_app_463 = "Select an existing field from your instruments to be the baseline date for the project."
mycap_mobile_app_464 = "NOTE: All of the below fields are mandatory. However,"
mycap_mobile_app_465 = "If the participant selects \"Yes\", the baseline date will automatically be set to the day they answered the question.<br>If the participant selects \"No\", they will be instructed to enter a date."
mycap_mobile_app_466 = "If participants answered \"No\" to the previous question, they are prompted to enter a date here."
mycap_mobile_app_467 = "You are not allowed to delete this data collection instruments. Since you have set baseline date field which belongs to this instrument in your project,   you may thus not delete it. If you wish to delete the instrument, then you should designate date field from another instrument as baseline date field in \"Baseline Date Settings\"."
mycap_mobile_app_468 = "WARNING: Cannot delete this instrument!"
mycap_mobile_app_469 = "You are not allowed to delete this field. Since you have set this field as baseline date field in your project,   you may thus not delete it. If you wish to delete this field, then you should designate another date field as baseline date field in \"Baseline Date Settings\"."
mycap_mobile_app_470 = "WARNING: Cannot delete this field!"
mycap_mobile_app_471 = "This instrument cannot be enabled as a MyCapt task because it contains the baseline date field for your project.       If you wish to enable this instrument for MyCap, designate a date field from another instrument as the baseline date field in \"Baseline Date Settings\"."
mycap_mobile_app_472 = "If the baseline date is entered into REDCap <b>before participants join your project</b> (e.g., via hyperlink or QR code) they will NOT complete these questions on the MyCap App."
mycap_mobile_app_473 = "Enter a Task Title:"
mycap_mobile_app_474 = "Enter a Yes/No question about whether the baseline date was \"TODAY\":"
mycap_mobile_app_475 = "Enter a question that asks for the desired date if the date was in the past:"
mycap_mobile_app_476 = "e.g., Baseline Date, Discharge Date"
mycap_mobile_app_477 = "e.g., Were you discharged from the hospital today?"
mycap_mobile_app_478 = "e.g., When were you discharged?"
mycap_mobile_app_479 = "Instruction Step:"
mycap_mobile_app_480 = "Please select Baseline date field."
mycap_mobile_app_481 = "Instruction title"
mycap_mobile_app_482 = "Instruction content"
mycap_mobile_app_483 = "Publish Task Settings"
mycap_mobile_app_484 = "* This field is set as Baseline date field for MyCap.<br>* You should NOT change variable name or Validation (other than date)."
mycap_mobile_app_485 = "-- select participant --"
mycap_mobile_app_486 = "Please select a project"
mycap_mobile_app_487 = "Please select a participant"
mycap_mobile_app_488 = "This instrument cannot be enabled as a MyCap task because this instrument is a health measure that is not currently supported by MyCap."
mycap_mobile_app_489 = "SUCCESSFUL!"
mycap_mobile_app_490 = "Binary data received. Not printing due to size. Length:"
mycap_mobile_app_491 = "Request:"
mycap_mobile_app_492 = "Response:"
mycap_mobile_app_493 = "WARNING: This action is only for testing purposes and will have no effect on the project/participant."
mycap_mobile_app_494 = "tests passed,"
mycap_mobile_app_495 = "failed"
mycap_mobile_app_496 = "Please ensure you have a a project and participant with the following codes:"
mycap_mobile_app_497 = "Endpoint:"
mycap_mobile_app_498 = "Project Code:"
mycap_mobile_app_499 = "Participant Code:"
mycap_mobile_app_500 = "[Please Click \"Save Changes\" button to enable this instrument for MyCap.]"
mycap_mobile_app_501 = "App Sync Issues"
mycap_mobile_app_502 = "An app synchronization issue is created when the Android or iOS MyCap app sends a task result to the REDCap server that is incompatible with your REDCap project for some reason.   This typically occurs when a participant completes an old version of a task/instrument. The purpose of the synchronization issue mechanism is to always capture data   that is sent from the MyCap app, ensuring no loss of data. Synchronization issues indicate a problem and should be investigated."
mycap_mobile_app_503 = "No Synchronization Issues exist"
mycap_mobile_app_504 = "Unresolved"
mycap_mobile_app_505 = "You create a task/instrument with a \"Multiple Choice - Radio Buttons (Single Answer)\" field. You specify choices   having values:<br> <code> 0, No<br>1, Yes<br>2, Sometimes<br></code>"
mycap_mobile_app_506 = "Overview"
mycap_mobile_app_507 = "Resolution for synchronization issue is saved successfully."
mycap_mobile_app_508 = "Participant"
mycap_mobile_app_509 = "Result ID"
mycap_mobile_app_510 = "Missing/Invalid Participant"
mycap_mobile_app_511 = "<b>Instructions:</b> A synchronization issue is created when the Android or iOS MyCap app sends a task result   to the REDCap server that is incompatible with your REDCap project for some reason. You must determine the   correct way to store the data in your project. This typically involves copying the MyCap data to a new REDCap   repeating instance for the appropriate record."
mycap_mobile_app_512 = "Date Recieved"
mycap_mobile_app_513 = "Error Type"
mycap_mobile_app_514 = "Resolution"
mycap_mobile_app_515 = "Problem"
mycap_mobile_app_516 = "Key"
mycap_mobile_app_517 = "Could not save to REDCap"
mycap_mobile_app_518 = "Could not find participant"
mycap_mobile_app_519 = "Could not find project"
mycap_mobile_app_520 = "You publish MyCap project configuration version 1 and a participant joins your project."
mycap_mobile_app_521 = "The participant completes the task with answer  <code>No (0)</code> and the result is sent to REDCap to be saved."
mycap_mobile_app_522 = "REDCap <strong>accepts the result</strong> because  <code>No (0)</code> is a valid choice value."
mycap_mobile_app_523 = "Later, you decide to change the values of your multiple choice field to:<br> <code>No, No<br>Yes, Yes<br>   Sometimes, Sometimes<br></code>"
mycap_mobile_app_524 = "You forget to publish a new version of the MyCap configuration."
mycap_mobile_app_525 = "The participant completes the task again with answer  <code>No (0)</code> and the result is sent to REDCap to be saved."
mycap_mobile_app_526 = "REDCap <strong>rejects the result</strong> because  <code>No (0)</code> is no longer a valid choice value. It was changed   to  <code>No (No)</code>."
mycap_mobile_app_527 = "MyCap creates a synchronization issue using the rejected REDCap response."
mycap_mobile_app_528 = "You review the synchronization issue and see that the result could not be saved due to an invalid choice value."
mycap_mobile_app_529 = "You create the appropriate REDCap entry using the provided synchroniozation issue data, and then flag the synchronization issue   as resolved."
mycap_mobile_app_530 = "You publish MyCap project configuration version 2 so participants recieve your updated multiple choice field values."
mycap_mobile_app_531 = "* Click \"Publish\" if recent changes have been made"
mycap_mobile_app_532 = "<p>Changes you make to the MyCap configuration do not automatically trigger a new version. You must explicitly   indicate that changes you have made should be published to the MyCap mobile app.</p>"
mycap_mobile_app_533 = "<p>Changes you make to REDCap instruments are not automatically pushed to <b>existing</b> participants.   You must explicitly indicate that changes you have made should be published to the MyCap mobile app. However,   <b>new</b> participants will always receive the most recent instrument fields.   </p>"
mycap_mobile_app_534 = "This data collection instrument must be a repeating instrument. After saving these settings, MyCap will turn repeatable instruments ON for"
mycap_mobile_app_535 = "(in seconds)"
mycap_mobile_app_536 = "View Task Details (all)"
mycap_mobile_app_537 = "Task Schedule"
mycap_mobile_app_538 = "Below is a list of all tasks enabled for MyCap. These tasks appear for participants in MyCap Mobile app as per schedule set for specific task.   You may enable REDCap instrument, create active task, modify or delete existing MyCap settings from Online Designer.   <br><b>NOTE:</b> Tasks displayed in green color are active tasks."
mycap_mobile_app_539 = "Total MyCap-enabled tasks:"
mycap_mobile_app_540 = "All MyCap Configuration were successfully converted into REDCap. <br>The MyCap module has now been disabled for this project, and you will be redirected to the Project Setup page."
mycap_mobile_app_541 = "Something went wrong while migrating configuration from MyCap External Module to REDCap!"
mycap_mobile_app_542 = "View/Respond"
mycap_mobile_app_543 = "<b>Note:</b> The baseline date cannot be a field on an instrument that is enabled as a MyCap task."
mycap_mobile_app_544 = "MyCap has now been enabled! Your next steps are outlined below."
mycap_mobile_app_545 = "<b>About</b> pages describing your project. These pages appear when participants join the project in MyCap, and can be referenced from the MyCap App menu at any time."
mycap_mobile_app_546 = "2) Design your instruments in the Online Designer"
mycap_mobile_app_547 = "The first instrument will be used to create the participant record and <b>CANNOT</b> be enabled as a MyCap task because a record must exist before a participant can join your project in the MyCap App.       <br>After designing your instruments in the Online Designer, you can enable them for use in MyCap. You can add new instruments and enable them for MyCap any time."
mycap_mobile_app_548 = "4) Enable your instruments for MyCap in the Online Designer"
mycap_mobile_app_549 = "All instruments in a project do not have to be enabled for MyCap. After clicking \"Enable\" for an instrument, you will be taken to the task setup page to configure the task for MyCap. These settings can be modified at any time during the course of your project.      <b>Note:</b> Instruments can be enabled as Surveys and MyCap Tasks (e.g., when not all participants are using MyCap)."
mycap_mobile_app_552 = "6) Visit MyCap Participant Management (on left-hand menu) to manage the MyCap Participant List, communications, and inviting participants to join your project:"
mycap_mobile_app_553 = "<b>MyCap is a participant-facing mobile application (on iOS and Android)</b> 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_mobile_app_554 = "The MyCap Participant List allows you invite, manage, and message participants that are using MyCap in this project. Participants will appear in this list once a record has been created in the project. Each participant may be sent a unique hyperlink or QR code to join the project. If you wish, you can limit the records that appear in the participant list by using the \"<b>Participant Display Logic</b>\" option. You may also <b>set a Custom Participant Label</b> to display a more recognizable identifier for each participant."
mycap_mobile_app_555 = "<b>NOTE:</b> Since you have been assigned to a Data Access Group, you are only able to send announcements to participants from your group."
mycap_mobile_app_556 = "This instrument cannot be enabled as a MyCap task."
mycap_mobile_app_557 = "<b>Contacts</b> display project personnel or contact information that can be used to assist participants."
mycap_mobile_app_558 = "<b>Links</b> provide constant access to important web-based resources such as videos and websites"
mycap_mobile_app_559 = "<b>Theme</b> allows you to select the color scheme of the app (<b>Note</b>: This ONLY works on iOS devices; Android devices default to the blue color scheme)."
mycap_mobile_app_560 = "<b>Participants</b> – This tab allows users to enable a Custom Participant Label, determine which records to display in the MyCap Participant List, and obtain participant access information (e.g., a record-specific QR code or dynamic link) to join the project."
mycap_mobile_app_561 = "<b>Messages</b> – This tab allows you to view messages from participants, send messages to individual participants, or make announcements to all participants. (<b>Note:</b> REDCap users do not receive an alert when participants send a message, so please check back often if you expect participants to contact you frequently.)"
mycap_mobile_app_562 = "<b>App Synchronization Issues</b> – This tab allows you to view any data that were not properly synced from the participants' mobile device to the REDCap project. Descriptive information is provided to help you understand why data were not synced. (<b>Note:</b> Synchronization issues cannot be automatically imported into your project, but the task data that would have synced properly is presented in a table that can be manually copied into a CSV, re-formatted, and manually imported into the project, if desired.)"
mycap_mobile_app_563 = "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.  MyCap is available on any iOS device (iOS v11.0+) and any Android device (Android v8.0+)."
mycap_mobile_app_564 = "All MyCap settings will exist in REDCap, eliminating the need to switch back and forth between REDCap and external module."
mycap_mobile_app_565 = "New features will only be available to those using the new MyCap Core in REDCap."
mycap_mobile_app_566 = "Only major bug fixes will be released to the External Module. "
mycap_mobile_app_567 = "Configuration settings will be transferred."
mycap_mobile_app_568 = "Participants in existing projects will not need to rejoin the project."
mycap_mobile_app_569 = "New participants will still be able to join projects via the MyCap Participant Access info (i.e., MyCap QR Code or URL)."
mycap_mobile_app_570 = "Why should I migrate my project?"
mycap_mobile_app_571 = "How will migration affect my project?"
mycap_mobile_app_572 = "The user interface for managing the MyCap settings and configuration will be new. However, these features will ensure a smooth transition: "
mycap_mobile_app_573 = "Existing MyCap Tasks"
mycap_mobile_app_574 = "Since your MyCap configuration contains total of"
mycap_mobile_app_575 = "tasks, all task settings (including the task title) for each MyCap task will be copied and remain as-is in the REDCap project. If you want to change your task information, optional settings, or task schedule settings after migrating, you are welcome to do so on the <b>Online Designer</b> using the Enable button or via the \"Edit\" link in the <b>\"Enabled as MyCap Task\"</b> column for each data collection instrument."
mycap_mobile_app_576 = "Existing Other Configuration"
mycap_mobile_app_577 = "If you want to manage your MyCap about pages information, contacts, links or theme settings after migrating, you are welcome to do so on the <b>MyCap Mobile App</b> link added in the left panel."
mycap_mobile_app_578 = "<b>NOTICE:</b> MyCap Configuration for this project is already available. Please verify the existing configuration, and begin the migration of your existing MyCap settings/data into REDCap's built-in MyCap feature."
mycap_mobile_app_579 = "After enabling MyCap on your project, follow the steps below to complete the setup:"
mycap_mobile_app_580 = "Migrate Entire MyCap Data from External Module (EM) to REDCap"
mycap_mobile_app_581 = "MyCap EM to REDCap"
mycap_mobile_app_582 = "The entire MyCap configuration can be migrated to new UI offered in REDCap to manage MyCap Configuration."
mycap_mobile_app_583 = "Note: After migrating your project from the EM to REDCap core, you and other users will no longer be able to access the      MyCap External Module. All MyCap configuration will be migrated to REDCap and there will NOT be any way to switch back to External Module user interface.<br>      Upon migration, REDCap will be converting the participant joining information (QR code, hyperlink), which was previously generated by the MyCap External Module.      This means the HTML provided to help instruct participants on joining your project has changed. During the migration, the HTML will automatically be updated      if it has been inserted into Alerts & Notifications and Survey Completion Text to ensure new participants can join the project as soon as your project is migrated.      However, if you used the External Module's \"Participant Access Info\" HTML in other places, please replace it with the HTML provided in MyCap Mobile App > Participants > \"Invite Participant (HTML)\"."
mycap_mobile_app_584 = "Please verify details below represent your MyCap EM settings, pages, tasks and participants before migrating from the EM to REDCap."
mycap_mobile_app_585 = "<b>Install Date: </b>The date a participant scanned the QR code to load your project."
mycap_mobile_app_588 = "This instrument must be a repeating instrument."
mycap_mobile_app_589 = "MyCap needs to make some changes to this instrument to fix these issues:"
mycap_mobile_app_590 = "SUCCESS! All listed MyCap issues for this instrument were successfully fixed. The page will now reload to reflect the changes."
mycap_mobile_app_591 = "Fix MyCap Issue in"
mycap_mobile_app_592 = "every"
mycap_mobile_app_593 = "Continue"
mycap_mobile_app_594 = "Continue with changes?"
mycap_mobile_app_596 = "Baseline Date Task Setup:"
mycap_mobile_app_597 = "If the baseline date <b>is not entered in REDCap when a participant joins your project</b>, they must complete these questions below and provide a baseline date before they can complete any tasks in MyCap."
mycap_mobile_app_611 = "Enable MyCap"
mycap_mobile_app_612 = "If you wish to enable MyCap in this project, a request must first be sent to a REDCap administrator for approval. Click the button below to send the request to an admin, after which you will receive an email once your request has been approved."
mycap_mobile_app_613 = "Send request to enable MyCap"
mycap_mobile_app_614 = "A user has requested that a REDCap administrator enable MyCap in this project. Click the button below to enable MyCap, after which the user will be notified via email regarding their request."
mycap_mobile_app_615 = "has requested that MyCap be enabled in the following project:"
mycap_mobile_app_616 = "Request to Enable MyCap"
mycap_mobile_app_617 = "Approve request to ENABLE MYCAP"
mycap_mobile_app_618 = "MyCap has been enabled"
mycap_mobile_app_619 = "MyCap has been enabled in your project named"
mycap_mobile_app_620 = "View important info about how to begin using MyCap in your project"
mycap_mobile_app_621 = "MyCap has been enabled, and the requester has been notified via email."
mycap_mobile_app_622 = "Modify settings for MyCap task"
mycap_mobile_app_624 = "Design the major components that participants see when they view the MyCap app on their mobile device. Use the tabs below to customize each component. To push your changes out to all participants, click the Publish button."
mycap_mobile_app_625 = "MyCap Participants"
mycap_mobile_app_626 = "MyCap Participant List"
mycap_mobile_app_627 = "<b>Baseline Date: </b>Some projects schedule tasks relative to a baseline date. For example, the baseline date in a physical therapy project might indicate the date the participant began physical therapy. See <b>Online Designer > Baseline Date Settings</b>.   From there you may turn baseline date settings <b>on/off</b> if you wish to trigger task schedules based on a specific event (e.g., discharge date, clinic visit)."
mycap_mobile_app_628 = "MyCap Participant Management"
mycap_mobile_app_629 = "Manage and invite participants to use MyCap and send/receive messages"
mycap_mobile_app_631 = "Design and Configure the MyCap App"
mycap_mobile_app_633 = "Title of Contact Page"
mycap_mobile_app_635 = "MyCap related options"
mycap_mobile_app_636 = "Survey and MyCap related options"
mycap_mobile_app_637 = "MyCap settings"
mycap_mobile_app_638 = "MyCap app configuration is out of date. Consider publishing a new version."
mycap_mobile_app_639 = "View MyCap Initial Instructions"
mycap_mobile_app_640 = "MyCap Initial Instructions"
mycap_mobile_app_641 = "1) Customize MyCap User Privileges"
mycap_mobile_app_642 = "Users with \"Project Design and Setup\" rights are able to enable and configure MyCap Tasks (Instruments) and schedules. <u>Users can also be given the \"Manage MyCap Participants\" user privilege</u> in order to invite participants, send messages to individual participants, or send announcements to all participants at once. If a user belongs to a Data Access Group, they will be able to invite and interact with only the participants assigned to their DAG."
mycap_mobile_app_643 = "NOTICE: Only REDCap administrators are allowed to perform the MyCap EM migration. Please contact your local REDCap admin if you wish to do so."
mycap_mobile_app_644 = "3) Enable the use of a baseline date, if needed."
mycap_mobile_app_645 = "all MyCap Tasks are scheduled based on the participant's install date, which is the date they join your project on their MyCap App.       <b>If you wish to trigger any or all MyCap Tasks based on another date</b>, such as a date of discharge or a clinic visit, <b>you can configure      \"Baseline Date Settings\" from the Online Designer > MyCap Options</b>.       <br>The baseline date is not a REDCap Instrument; it is only a text field with date validation. Additionally, <b>this field must be on an instrument      that is not enabled for MyCap</b> in case project users wish to enter or capture this date before the participant joins the project on their MyCap App.      Once the text field exists (e.g., in your first instrument that is not enabled in MyCap), you can select that field while configuring the baseline settings."
mycap_mobile_app_646 = "7) Publish your MyCap Tasks and Design"
mycap_mobile_app_648 = "8) Test your project on iOS and Android"
mycap_mobile_app_649 = "After publishing your tasks and designs, you are ready to test your project. We recommend testing your project on an Android (v8.0+) and iOS (v11.0+) devices prior to onboarding participants.       We also recommend testing on any device type (phones, tablets) that participants might use.       <br><b>Note:</b> if you wish to see how tasks appear to participants, you can set all MyCap Task Schedules to \"infinite\", as this allows you to complete the tasks after making and published edits.      Once the task appearance is satisfactory, setup the proper schedule and <b>Publish new MyCap version</b>."
mycap_mobile_app_650 = "9) Publish new MyCap version anytime you make changes."
mycap_mobile_app_651 = "You can make changes to your project at any time. However, any MyCap-related changes that are made must be 'published' before existing or new participants will see the update.      <br>Participants will automatically see the updated version the next time they open their MyCap App. No action is required by participants."
mycap_mobile_app_652 = "What to do after migrating my project from the MyCap External Module to the REDCap Interface:"
mycap_mobile_app_653 = "After migrating your project from the MyCap External Module to the REDCap interface, you do not have to make any changes. Existing Participants can continue to use their app to complete tasks and new participants can join your project."
mycap_mobile_app_654 = "1) **NEW FEATURE** Customize MyCap User Privileges."
mycap_mobile_app_655 = "2) Update your instruments in the Online Designer, if needed."
mycap_mobile_app_656 = "The first instrument is still used to create the participant record and <b>CANNOT</b> be enabled as a MyCap task because a record must exist before a participant can join your project in the MyCap App.       <br>You can add new instruments and enable them for MyCap any time."
mycap_mobile_app_657 = "3) Enable your instruments for MyCap in the Online Designer"
mycap_mobile_app_658 = "Task Schedules created in the External Module will not be changed after migrating. However, after migrating you can make updates or enable new instruments from the Online Designer.       As a reminder, all instruments in a project do not have to be enabled for MyCap. After clicking \"Enable\" for an instrument, you will be taken to the task setup page to configure the task for MyCap.      These settings can be modified at any time during the course of your project.       <br><b>Note:</b> Instruments can be enabled as Surveys and MyCap Tasks (e.g., when not all participants are using MyCap)."
mycap_mobile_app_659 = "4) View / edit 'Baseline Date Settings' from the Online Designer, if needed."
mycap_mobile_app_660 = "Baseline Date settings will not be changed after migrating your project. However, you can change or add a baseline date from the Online Designer. As a reminder,"
mycap_mobile_app_661 = "5) Edit the look and feel of MyCap from MyCap App Design"
mycap_mobile_app_662 = "The look and feel of your app will not change for participants after migrating. If you'd like to make updates, "
mycap_mobile_app_663 = "7) Publish new MyCap version anytime you make changes."
mycap_mobile_app_664 = "You can make changes to your project at any time. If you make any changes to instruments enabled for MyCap, task schedules, or the app design, be sure to <b>Publish new MyCap version</b> from the MyCap App Design or Online Designer pages. You only need to publish from ONE of these places.       Participants will automatically see the updated version the next time they open their MyCap App. No action is required by participants."
mycap_mobile_app_665 = "MyCap Notice:"
mycap_mobile_app_669 = "For more information about MyCap, check out the <a href=https://projectmycap.org/ target=_blank><u>MyCap website</u></a>,  <a href=https://academic.oup.com/jamiaopen/article/5/2/ooac047/6601324 target=_blank><u>publication</u></a>,  <a href=https://projectmycap.org/mycap-resources/ target=_blank><u>resources</u></a>, and a list of  <a href=https://projectmycap.org/mycap-use-cases/ target=_blank><u>MyCap use cases</u></a>."
mycap_mobile_app_670 = "Learn more about MyCap"
mycap_mobile_app_671 = "Watch some short videos on how to use MyCap in a project:"
mycap_mobile_app_672 = "Configure MyCap Tasks"
mycap_mobile_app_673 = "Take a test drive:"
mycap_mobile_app_674 = "View the MyCap app through the eyes of a participant."
mycap_mobile_app_675 = "Join a demo project using the MyCap mobile app"
mycap_mobile_app_676 = "A MyCap version has not been published yet for this project, so a participant attempting to join this project on the MyCap mobile app will fail. <u>Go to the Online Designer and click the green Publish button</u> at the top to publish your first version."
mycap_mobile_app_677 = "<b>MYCAP REMINDER:</b> Since you are using MyCap in this project, it is often important to publish a new MyCap version after making changes to your fields or instruments. Please do not forgot to do that, if needed, <u>by clicking the green Publish button</u> at the top of this page."
mycap_mobile_app_678 = "<b>MYCAP REMINDER:</b> Since you are using MyCap in this project, it is often important to publish a new MyCap version after making changes to your fields or instruments. Please do not forgot to do that, if needed, <u>by navigating to the Online Designer and clicking the green Publish button</u> at the top of the page."
mycap_mobile_app_679 = "Projects with MyCap enabled"
mycap_mobile_app_680 = "MyCap participants that have joined a project"
mycap_mobile_app_681 = "MyCap tasks created (excluding active tasks)"
mycap_mobile_app_682 = "Active tasks created"
mycap_mobile_app_683 = "Announcements and messages (sent and received)"
mycap_mobile_app_684 = "Current limitations with MyCap:"
mycap_mobile_app_685 = "Several standard REDCap features are not supported by MyCap, partially due to the fact that the MyCap app intentionally keeps very little participant data  on the mobile device at a given time. The following REDCap features are <u>not supported in the MyCap mobile app</u>:  piping, smart variables, field embedding, special functions, calculated fields, and most action tags (@HIDDEN and all @MC- prefixed action tags *are* supported).  <u>Branching logic is partially supported</u>, in which  simple, single-statement branching logic (i.e., does not contain AND, OR, or special functions), such as <code>[field]='1'</code>, is supported."
mycap_mobile_app_686 = "Prefer a detailed guide of instructions?"
mycap_mobile_app_687 = "Read the"
mycap_mobile_app_688 = "MyCap Help document"
mycap_mobile_app_689 = "If you would prefer to read detailed instructions for designing the MyCap app, see the"
mycap_mobile_app_690 = "This instrument cannot be enabled as a MyCap task because the instrument contains the randomization field."
mycap_mobile_app_691 = "Modify Project Title in App"
mycap_mobile_app_692 = "Below you may specify project title to be displayed in MyCap Mobile App."
mycap_mobile_app_693 = "Project title have been successfully modified. (The page will now reload.)"
mycap_mobile_app_694 = "If using a slider field on an instrument that is or will be enabled for MyCap, use one of the following annotations to optimize the layout on the mobile device.      <br><br><b>@MC-FIELD-SLIDER-BASIC=[MIN]:[MAX]:[STEP]:</b> This is a MyCap annotation used with slider fields. Example: <code>@MC-FIELD-SLIDER-BASIC=0:10:1</code> is scale from 0 to 10 step by increments of 1, where the slider cannot have more than 13 steps. See documentation . Note that REDCap slider does not accept values < 0 and > 100.      <br><br><b>@MC-FIELD-SLIDER-CONTINUOUS=[MIN]:[MAX]:[MAX FRACTIONAL DIGITS]:</b> This is a MyCap annotation used with slider fields. Example <code>@MC-FIELD-SLIDER-CONTINUOUS=0:100:0</code> is scale from 0 to 100 with no fractions. See documentation. A REDCap slider will default to this if no annotation is specified. Note that REDCap slider does not accept values < 0 and > 100. REDCap slider does not accept fractions, so always use 0 as the last number."
mycap_mobile_app_695 = "Learn about MyCap's Slider Action Tags"
mycap_mobile_app_696 = "By default, "
mycap_mobile_app_697 = "by default, "
mycap_mobile_app_698 = "<b>These instruments are missing the fields with required annotations:</b>"
mycap_mobile_app_699 = "These instruments must be a repeating instrument: "
mycap_mobile_app_700 = "Fix MyCap Issues"
mycap_mobile_app_701 = "MyCap needs to make some changes to the instruments to fix these issues:"
mycap_mobile_app_702 = "SUCCESS! All listed MyCap issues were successfully fixed. The page will now reload to reflect the changes."
mycap_mobile_app_703 = "MyCap requires 7 fields (with specific annotations) to be included on instruments enabled for MyCap. These fields capture details such as when tasks are scheduled, started, and completed, as well as stores supplemental data that can be helpful if errors occur while saving data from the app to the REDCap server. Note: These fields are hidden from participants."
mycap_mobile_app_704 = "<b>This instrument is missing the fields with these annotations:</b>"
mycap_mobile_app_705 = "Please note, you have enabled MyCap for this project. This will delete all MyCap data (including MyCap Participants, Messages, Sync Issues). NOTE: Task Settings, About, Contacts, Links, Theme will NOT be deleted."
mycap_mobile_app_706 = "Please note, MyCap task settings for this instrument has been stored. Once you enable MyCap for this project, task settings will be restored."
mycap_mobile_app_707 = "Please note, this will delete all MyCap data (including MyCap Participants, Messages, Sync Issues)."
mycap_mobile_app_708 = "Your project is currently in Draft Mode. You are unable to enable an instrument for MyCap while in Draft Mode if that instrument did not exist in the project prior to entering Draft Mode. Please review the changes you have made while in draft mode (by clicking the 'View detailed summary of all drafted changes link') and either click the 'Submit Changes for Review' button or click the link 'Remove all drafted changes'. After your changes have been approved (or you remove all drafted changes), the 'enable' button will be available to you and you may enable your instrument for MyCap."
mycap_mobile_app_710 = "This instrument has not yet been designated for any event(s). To fix this, (1) go to \"Designate Instruments for My Events\" and include this instrument in an event(s), and then (2) return to finalize the MyCap Task Settings in the Online Designer."
mycap_mobile_app_711 = "One or more instruments need to be non-repeating for the events listed:"
mycap_mobile_app_712 = "The instrument"
mycap_mobile_app_713 = "must be non-repeating for the event(s):"
mycap_mobile_app_714 = "NOTICE: One or more events are enabled for MyCap. You cannot remove instruments that are enabled as MyCap tasks. To remove these instruments from the event, first Delete MyCap Settings for the instrument in the Online Designer."
mycap_mobile_app_715 = "These events are enabled for MyCap. To remove these instruments from the event, first Delete MyCap Settings for the instrument in the Online Designer."
mycap_mobile_app_716 = "One or more MyCap tasks uses events from this arm. Please note, upon deletion those event(s) will no more enabled for those instruments."
mycap_mobile_app_717 = "One time with"
mycap_mobile_app_718 = "days delay"
mycap_mobile_app_719 = "This instrument must be a non-repeating for events:"
mycap_mobile_app_720 = "These events must be a non-repeating:"
mycap_mobile_app_721 = "Warnings:"
mycap_mobile_app_722 = "Fix Warnings"
mycap_mobile_app_723 = "Task Setup is not accessible!"
mycap_mobile_app_724 = "Designate which events this task should be enabled for below."
mycap_mobile_app_725 = "<b>Please note:</b> There are some issues related to MyCap task settings. All warnings will be fixed automatically upon publishing, but <b>you will need to take action to fix any errors</b>. Tasks with existing errors will NOT be published."
mycap_mobile_app_726 = "This instrument cannot be enabled as a MyCap task because this instrument is not utilizing any event."
mycap_mobile_app_727 = "This instrument cannot be enabled as a MyCap task because this instrument has no fields."
mycap_mobile_app_728 = "View MyCap Errors/Warnings"
mycap_mobile_app_729 = "Fix MyCap Warnings"
mycap_mobile_app_730 = "View MyCap Errors"
mycap_mobile_app_731 = "Fix Issues"
mycap_mobile_app_734 = "This instrument has no fields (except fields with MyCap annotation). To fix this, you may add atleast one field for this instrument."
mycap_mobile_app_735 = "One or more events need to be non-repeating:"
mycap_mobile_app_736 = "One or more events need to be non-repeating."
mycap_mobile_app_737 = "Please fix below warnings:"
mycap_mobile_app_738 = "This task will be scheduled Once,"
mycap_mobile_app_739 = "days after"
mycap_mobile_app_740 = "This instrument should be non-repeating for this event."
mycap_mobile_app_741 = "This event should be non-repeating."
mycap_mobile_app_742 = "To join the project on MyCap:"
mycap_mobile_app_744 = "App Store"
mycap_mobile_app_745 = ", Android:"
mycap_mobile_app_746 = "Play Store"
mycap_mobile_app_748 = "while on your mobile device. (If the MyCap app is not installed, it will prompt you to install MyCap.)"
mycap_mobile_app_750 = "Use one of the options below to join the project on MyCap:"
mycap_mobile_app_754 = "<b>A new MyCap app is available in the app store</b> to use for new and existing participants to support features in REDCap v13.10.0 or greater. It is only necessary to transition to the new MyCap app if your project requires it to be used for newer MyCap-related features."
mycap_mobile_app_755 = "Click to transition"
mycap_mobile_app_757 = "Transition to new MyCap app completed successfully!"
mycap_mobile_app_758 = "alerts email body were updated."
mycap_mobile_app_760 = "The project must first be in Draft Mode before you fix MyCap issues to any data collection instruments. Click the 'Enter Draft Mode' button near the top of the page to move the project into Draft Mode."
mycap_mobile_app_761 = "Can only fix MyCap issues in Draft Mode"
mycap_mobile_app_762 = "<b>Note:</b> New date field (\"Install Date\") with annotation @MC-PARTICIPANT-JOINDATE and a new text field (\"Code\") with annotation @MC-PARTICIPANT-CODE are created on first instrument which will capture participants join date when participant joins from app and code when participant is created. These fields will be hidden and can be utilized while building a report."
mycap_mobile_app_763 = "Are you sure you wish to transition to use the new MyCap app. Please note that this process is <u>irreversible</u>."
mycap_mobile_app_764 = "Yes, proceed"
mycap_mobile_app_765 = "Transition to new MyCap app?"
mycap_mobile_app_766 = "Participants can join your project on the MyCap mobile app using a QR code or hyperlink that is unique to their record in your REDCap project.      A participant's record must already exist in the REDCap project in order for them to get a QR code or hyperlink. <br><br>The methods below will provide you with template language      and directions for onboarding participants to your project. To obtain an individual participant's QR code or hyperlink after their record has been created in the project,      see the MyCap Participant Management > MyCap Participant List."
mycap_mobile_app_767 = "This project has been converted to the new MyCap app."
mycap_mobile_app_768 = "Install the MyCap app (purple background) on your mobile device (iOS:"
mycap_mobile_app_769 = "Open the MyCap app, create a profile, tap \"Join Project\", and scan the QR code below."
mycap_mobile_app_770 = "The most common methods of providing the participant with their QR code or hyperlink is via email using Alerts & Notifications or by displaying the QR code and hyperlink in the      Survey Completion Text at the end of survey. See instructions below, but note that these are not the only ways to invite a participant."
mycap_mobile_app_771 = "<b>Using an Alert:</b> Copy and paste the text above into the body of an alert that gets sent to the participant any time after their record has been created."
mycap_mobile_app_772 = "<b>Using the Survey Completion Text:</b> Copy and paste the text above into the Survey Completion Text of a survey so that the participant will see it immediately after completing the survey."
mycap_mobile_app_773 = "Open the MyCap app, create or select your profile, and tap \"Click to Join a Study from Dynamic Link \"."
mycap_mobile_app_774 = "while on your mobile device, which will prompt you to install MyCap if it's not already installed. After MyCap is open, create or select your profile, and tap \"Click to Join a Study from Dynamic Link\"."
mycap_mobile_app_775 = ", open the MyCap app, create a profile, tap \"Join Project\", and scan the QR code below."
mycap_mobile_app_776 = "To scan the QR Code below, install the MyCap app (purple background) on your mobile device (iOS:"
mycap_mobile_app_777 = "You may use"
mycap_mobile_app_778 = "For longitudinal projects, [arm-label] will display which arm the participant belongs to."
mycap_mobile_app_779 = "Scroll down to \"Set the Task Schedule\" and enable this task on at least one event."
mycap_mobile_app_780 = "or view a"
mycap_mobile_app_781 = "list of features in the MyCap app"
mycap_mobile_app_782 = "Before transitioning, read the"
mycap_mobile_app_783 = "MyCap Transition Guide"
mycap_mobile_app_784 = "when compared against the MyCap Classic app"
mycap_mobile_app_785 = "survey-related settings (survey completion text, survey confirmation email body, or ASI email body) were updated."
mycap_mobile_app_786 = "<b>Please note:</b> Tasks with existing errors are NOT published. If you wish to publish those tasks, <b>you will need to take action to fix any errors</b>."
mycap_mobile_app_787 = "The page will be reloaded to reflect this change."
mycap_mobile_app_788 = "Participants can join your project on the MyCap mobile app using one of the methods below."
mycap_mobile_app_789 = "Join by QR Code"
mycap_mobile_app_790 = "Participant Steps:"
mycap_mobile_app_791 = "Download the MyCap mobile app (purple background) from their app store."
mycap_mobile_app_792 = "Open MyCap and create a profile."
mycap_mobile_app_793 = "Press \"Join Project\""
mycap_mobile_app_794 = "Scan QR Code."
mycap_mobile_app_795 = "From a mobile device, click this link. The link will direct the participant to their app store if it is not installed."
mycap_mobile_app_796 = "Install and open the MyCap mobile app."
mycap_mobile_app_797 = "Create or select your profile."
mycap_mobile_app_798 = "Press \"Click to Join a Study from Dynamic Link\""
mycap_mobile_app_799 = "Download the MyCap Classic mobile app (black background) from their app store."
mycap_mobile_app_800 = "Open MyCap"
mycap_mobile_app_801 = "Install and open the MyCap Classic mobile app."
mycap_mobile_app_802 = "This instrument has not yet been enabled for an event. Go to MyCap task settings, scroll down to \"Set the Task Schedule\", and enable this task for at least one event."
mycap_mobile_app_803 = "Install the MyCap Classic app (black background) on your mobile device (iOS:"
mycap_mobile_app_804 = "Open the MyCap app, tap \"Join Project\", and scan the QR code below."
mycap_mobile_app_805 = "Open the MyCap app, and tap \"Join Project\". (If you have other MyCap projects, you may need to go to your Profile and click \"Join Another Project\".)"
mycap_mobile_app_806 = "while on your mobile device, which will prompt you to install MyCap if it's not already installed. After MyCap is open, tap \"Join Project\". (Note: If you have other MyCap projects, you may need to go to your Profile and click \"Join Another Project\")."
mycap_mobile_app_807 = "To scan the QR Code below, install the MyCap Classic app (black background) on your mobile device (iOS:"
mycap_mobile_app_808 = ", open the MyCap app, and tap \"Join Project\"."
mycap_mobile_app_809 = "Download the MyCap mobile app (purple background) from the app store."
mycap_mobile_app_810 = "Open MyCap and create or select an existing profile."
mycap_mobile_app_811 = "From a mobile device, click this link. The link will direct the participant to the app store if MyCap is not already installed."
mycap_mobile_app_812 = "Create or select an existing profile."
mycap_mobile_app_813 = "Open MyCap."
mycap_mobile_app_814 = "Press \"Join Project\"."
mycap_mobile_app_815 = "Download the MyCap Classic mobile app (black background) from the app store."
mycap_mobile_app_816 = "This instrument has not been designated for any events. Use the link below to include this instrument in an event(s). You will be redirected to \"Designate Instruments for My Events\" page and upon saving it will return to finalize the MyCap Task Settings."
mycap_mobile_app_817 = "Click one of the add buttons to create a predefined active task. All required REDCap fields are created automaticially.      <b>DO NOT MODIFY</b> the fields in the instrument using Online Designer.<br> Most active tasks are developed by 3rd party programmers and researchers.      MyCap developers have added these active tasks but do not have expertise in the returned results. It is up to you to ensure you understand the returned results.      MyCap developers will help as much as possible."
mycap_mobile_app_818 = "See <a href='http://researchkit.org/docs/docs/ActiveTasks/ActiveTasks.html' target='_blank' style='text-decoration:underline;'>ResearchKit Active Tasks</a>."
mycap_mobile_app_819 = "(MyCap Classic)"
mycap_mobile_app_820 = "Download detailed schedules (CSV)"
mycap_mobile_app_822 = "Time Limit"
mycap_mobile_app_823 = "Repeats"
mycap_mobile_app_824 = "On Day(s):"
mycap_mobile_app_825 = "End this"
mycap_mobile_app_826 = "task"
mycap_mobile_app_827 = "On:"
mycap_mobile_app_828 = "must be repeating for the event(s):"
mycap_mobile_app_829 = "This instrument must be a repeating for events:"
mycap_mobile_app_830 = "One or more instruments need to be repeating for the events listed:"
mycap_mobile_app_831 = "When any of the below conditions are TRUE:"
mycap_mobile_app_832 = "Modify Optional Settings, Active Task Settings and Task Schedule"
mycap_mobile_app_833 = "Modify Optional Settings and Task Schedule"
mycap_mobile_app_834 = "Set Optional Settings, Active Task Settings and Task Schedule"
mycap_mobile_app_835 = "Set Optional Settings and Task Schedule"
mycap_mobile_app_836 = "End This task > Must select at least one condition."
mycap_mobile_app_837 = "Copy below settings To:"
mycap_mobile_app_838 = "[Preview the default instructions included with this task here]"
mycap_mobile_app_839 = "Installed Date (UTC Format):"
mycap_mobile_app_840 = "Time zone:"
mycap_mobile_app_841 = "The project must first be in Draft Mode before you enable for MyCap as this includes modifications to first data collection instruments.<br><br><b>Note:</b> After enabling MyCap while in Draft Mode, be sure to submit your drafted changes afterward."
mycap_mobile_app_842 = "The project must first be in Draft Mode before you enable any data collection instruments for MyCap. Click the 'Enter Draft Mode' button near the top of the page to move the project into Draft Mode."
mycap_mobile_app_843 = "The project must first be in Draft Mode before you publish new MyCap version as there are warnings exists which will be automatically fixed upon publishing. Click the 'Enter Draft Mode' button near the top of the page to move the project into Draft Mode."
mycap_mobile_app_844 = "Cannot publish new MyCap version!"
mycap_mobile_app_845 = "These instruments are having invalid schedules:"
mycap_mobile_app_846 = "Task schedule setup for instrument(s) looks incorrect. It will set to default setting upon fixing. Alternatively, you may do it manually by visiting MyCap task setup page."
mycap_mobile_app_847 = "These events are having invalid schedules:"
mycap_mobile_app_848 = "You may use the options below to help with testing. Appending the custom Event ID or Event Label will help to identify which event upcoming tasks belong to while testing scheduling in the app. We recommend turning this option off once participants are ready to join your project. The Event ID and Event Label assigned to events can be found on the \"Define My Events\" page."
mycap_mobile_app_849 = "Select Custom Event Label:"
mycap_mobile_app_850 = "[event-id] value will be appended to task title"
mycap_mobile_app_851 = "[event-label] value will be appended to task title"
mycap_mobile_app_852 = "No Event ID or Event Lable will be appended to task title."
mycap_mobile_app_853 = "Custom Settings (App)"
mycap_mobile_app_854 = "Event display format (App-side) was saved successfully."
mycap_mobile_app_855 = "The Mobile Toolbox (MTB) is a research platform that includes a library of cognitive and other tests that can be administered remotely on a smartphone.  The MTB's measures include smartphone versions of assessments from the NIH Toolbox, the International Cognitive Ability Resource, and the Patient Reported Outcomes Measurement Information System.  The MTB also includes short versions of cognitive tests for research that uses burst design. The items listed below are the MTB tasks that are available for use in the MyCap mobile app.  <b>Note:</b> Participants using an iOS device will need to be on iOS version 13+."
mycap_mobile_app_856 = "Task Status"
mycap_mobile_app_857 = "If \"Not Active\", participants will not be able to see this task in the app."
mycap_mobile_app_858 = "Please note, the project must first be in Draft Mode to add these missing fields to selected instrument."
mycap_mobile_app_859 = "Your project is currently in Draft Mode. You are unable to fix warnings while in Draft Mode if that instrument did not exist in the project prior to entering Draft Mode. Please review the changes you have made while in draft mode and either click the 'Submit Changes for Review' button. After your changes have been approved (or you remove all drafted changes), you will be able to fix these warnings."
mycap_mobile_app_860 = "Cannot fix warnings while in draft mode"
mycap_mobile_app_861 = "(from ResearchKit only)"
mycap_mobile_app_862 = "Mobile Toolbox (MTB) tasks created"
mycap_mobile_app_863 = "MyCap tasks created from PROMIS measures"
mycap_mobile_app_864 = "You cannot enable this instrument for MyCap. You must enable the first instrument in this measure. Once the first instrument is enabled, all subsequent instruments in this measure will automatically be enabled."
mycap_mobile_app_865 = "There's no need to enable this instrument for MyCap since the first instrument in this measure has been enabled. All subsequent instruments in this measure have been automatically enabled. Participants will be able to complete all instruments included in this measure in MyCap."
mycap_mobile_app_866 = "See <a href='https://mobiletoolbox.org' target='_blank' style='text-decoration:underline;'>Mobile Toolbox</a>."
mycap_mobile_app_867 = "Notification Settings"
mycap_mobile_app_868 = "The notification settings were updated."
mycap_mobile_app_869 = "Participants receive a daily notification on days they have a MyCap task due. You can choose the time you would like participants to receive this daily notification. Participants will receive a push notification saying \"[Profile Name] has a task due today.\" at the time you choose. Unless the time is changed, the default notification time is 8:00AM in the participant's time zone."
mycap_mobile_app_870 = "Send notification at time:"
mycap_mobile_app_871 = "Please select notification time."
mycap_mobile_app_872 = "Edit Notification Settings"
mycap_mobile_app_873 = "Communicate with participants by sending a message to individual participants or an announcement to all participants. Select when participants receive daily notifications to complete tasks in the MyCap app."
mycap_mobile_app_874 = "When you send a message, the participant will receive a push notification on his or her device saying \"You have a secure message waiting.\" The participant can read the message after      opening the MyCap Mobile App and navigating to the Messages tab. If the participant does not allow push notifications, he or she will still be able to read the message, but will not see the push notification indicating a new message is available."
mycap_mobile_app_875 = "When you send an announcement to all participants, all participants will receive a push notification on their device saying \"You have a secure message waiting.\" Participants can read the announcement after opening the MyCap Mobile App and navigating to the Messages tab."
mycap_mobile_app_876 = "App Settings"
mycap_mobile_app_877 = "MyCap App Settings"
mycap_mobile_app_878 = "Design the major components and user interface that your participants will see when they view the MyCap app on their mobile device. Create an About page containing a list of Links and Contacts, define a color scheme to theme the look of the MyCap mobile app, and customize when participants should receive a MyCap notification on days tasks are due."
mycap_mobile_app_879 = "<b>You will need to publish a new configuration when changes are made to any App Settings.</b>"
mycap_mobile_app_880 = "5) Design the look and feel of MyCap from MyCap App Settings"
mycap_mobile_app_881 = "You may access the \"MyCap App Settings\" page from either the Online Designer or via the MyCap step on the Project Setup page.      MyCap App Settings will allow you to configure the following:"
mycap_mobile_app_882 = "After configuring all tasks, schedules, and the App Settings, use <b>Publish new MyCap version</b> from the MyCap App Settings or Online Designer pages. You only need to publish from ONE of these places."
mycap_mobile_app_883 = "Select an existing field from your instruments to be the baseline date for each arm. Please select a field for at least one arm. The baseline date setting option in the task setup will be visible once a baseline date field is selected for the arm."
mycap_mobile_app_884 = "Please select Baseline Date field for at least one arm."
mycap_mobile_app_885 = "ResearchKit Active Tasks"
mycap_mobile_app_886 = "Importing instrument..."
mycap_mobile_app_887 = "You may select a form completion status of"
mycap_mobile_app_888 = "When submitted through the MyCap app, tasks will be stored with the selected status for the instrument's Form Status Complete field as seen on the Record Status Dashboard and Record Home Page."
mycap_mobile_app_889 = "Baseline settings have changed. <br>To save these changes, press Save.<br><br>Next, be sure to Publish new MyCap Version."
mycap_mobile_app_890 = "You cannot message this participant because they have not yet joined your project in the MyCap App."
mycap_mobile_app_891 = "A MyCap version has not been published yet for this project so participants will not be able to join the project on MyCap. To publish your first version, <u>go to the Online Designer and click the green Publish button</u> at the top."
sql_help_001 = "REDCap's \"sql\" field type for dynamically querying data"
cdis_custom_mapping_title = "Clinical Data Interoperability Services - Custom Mappings"
cdis_custom_mapping_description = "Custom mappings provide the flexibility to tailor mappings to the specific needs of your institution. Once defined, these custom mappings are available across all CDIS projects (CDP and CDM). To ensure that your custom mapping file is preserved during REDCap updates, it will be securely stored in the edocs folder. It is important to note that custom mappings take precedence over the default mappings provided by REDCap. This means that any custom mappings you define will override the existing mappings, ensuring your tailored configurations are always used."
cdis_custom_mapping_note_title = "Please note:"
cdis_custom_mapping_note_description = "When adding a new LOINC code, please visit LOINC.org to cross-reference the label and description. LOINC.org offers an accurate and up-to-date database of codes, ensuring consistent medical coding. Consulting this trusted resource helps maintain high standards and provide reliable information to your users."
cdis_custom_mapping_note_1 = "Custom entries will not overwite existing entries provided by REDCap"
cdis_custom_mapping_note_2 = "Only two categories are supported: \"Laboratory\" and \"Vital Signs\""
cdis_custom_mapping_note_3 = "The \"field\" column should contain the LOINC code"
cdis_custom_mapping_note_4 = "The \"temporal\" column should always be set to 1"
cdis_custom_mapping_note_5 = "The file must contain at least one line with the headers AND one entry"
cdis_custom_auth_params_01 = "Custom authentication parameters"
cdis_custom_auth_params_02 = "The \"Custom authentication parameters\" setting allows users to define and include their own parameters during the Smart on FHIR authentication process. These custom parameters provide flexibility and customization options, facilitating integration with external systems and enabling the exchange of context-specific information."
cdis_custom_auth_params_03 = "Custom parameters"
cdis_custom_auth_params_04 = "To add custom parameters, click on the \"Add Custom Parameter\" button, then enter a key and a value, finally specify the context where the parameter must be used. Use the delete icon to remove a parameter if needed."
cdis_custom_auth_params_05 = "Add Custom Parameter"
cdis_custom_auth_params_06 = "key"
cdis_custom_auth_params_07 = "value"
cdis_custom_auth_params_08 = "context"
cdis_custom_auth_params_09 = "always"
cdis_custom_auth_params_10 = "ehr launch"
cdis_custom_auth_params_11 = "standalone launch"
project_setting_fhir_system_title = "CDIS: Connected FHIR system"
project_setting_fhir_system_description = "You can choose a specific FHIR (Fast Healthcare Interoperability Resources) system for your project. This selection determines the source of the healthcare data your project will access and use. If 'Default' is selected, then the first FHIR system in the list will be used. You can create FHIR system configurations using the CDIS settings page."
project_setting_fhir_01 = "Please note that this option is currently managed at system level in the CDIS settings page"
project_setting_fhir_02 = "CDIS settings"
econsent_01 = "Participant"
econsent_02 = "Active?"
econsent_03 = "Selected instruments"
econsent_04 = "All instruments"
econsent_05 = "The REDCap e-Consent Framework provides standardized tools to obtain consent and store consent documentation with a certification screen and a storage function which automatically  generates a \"hard-copy\" PDF of the signed form. The e-Consent Framework offers many options to allow customization to your specific needs. The e-Consent Framework can be enabled for any survey in this project.  You may optionally provide consent forms as either an inline PDF or rich text that will be displayed on the consent survey itself. The consent forms can be context-specific if you are using MLM languages and/or  Data Access Groups so that it displays the correct consent form for a participant with a specific language set and/or assigned to a specific DAG. See the \"Add consent form\" link for more details after  enabling e-Consent for a survey."
econsent_06 = "No e-Consent items to display"
econsent_07 = "Back to Online Designer"
econsent_08 = "Hide inactive"
econsent_09 = "Save snapshot when..."
econsent_10 = "Custom tag/category"
econsent_11 = "Consent survey:"
econsent_12 = "PDF consent form displayed below {0} for"
econsent_13 = "Complete survey"
econsent_14 = "PDF consent form displayed below {0}"
econsent_15 = "Location(s) to save the signed consent snapshot"
econsent_16 = "Location(s) to save the snapshot"
econsent_17 = "Logic becomes true:"
econsent_18 = "Save signed consent when:"
econsent_19 = "STEP 2: Scope of the snapshot"
econsent_20 = "Specified field:"
econsent_21 = "Governed<br>by e-Consent"
econsent_22 = "MLM Language"
econsent_23 = "A consent form represented as either rich text or an inline PDF as defined on the e-Consents & PDF Snapshots page. This smart variable will be replaced with the proper consent form considering the current context  for a Participant consent item defined for a given survey on the e-Consents & PDF Snapshots page, including Data Access Group and MLM language (when applicable)."
econsent_24 = "Custom consent form text displayed below {0}"
econsent_25 = "Custom consent form text displayed below {0} for"
econsent_28 = "Type of e-Consent:"
econsent_29 = "e-Consent Framework"
econsent_30 = "PDF Snapshots of Records"
econsent_31 = "Single survey response"
econsent_32 = "Add new trigger"
econsent_33 = "Survey completion"
econsent_34 = "{0} e-Consent and {1} PDF Snapshots"
econsent_35 = "Settings for e-Consent & PDF Snapshots"
econsent_36 = "This page can be used to set up triggers for capturing PDF Snapshots of records. A PDF Snapshot is a REDCap-generated PDF file of a single instrument/survey, multiple instruments, or all the instruments of a given record. PDF Snapshots can be triggered when 1) a survey is completed, or 2) when specified conditional logic evaluates as True. When triggered, snapshots can be stored in the PDF Snapshot Archive folder in the File Repository and/or stored in a specified File Upload field. You may create as many triggers as you wish for capturing snapshots."
econsent_37 = "e-Consent active?"
econsent_38 = "Triggers for PDF Snapshots"
econsent_39 = "e-Consent Framework Settings"
econsent_40 = "e-Consent cannot be used because no surveys exist in the project yet. e-Consent can only be used for surveys."
econsent_41 = "Logic-based"
econsent_42 = "Type of trigger"
econsent_43 = "Edit settings"
econsent_44 = "Enable the e-Consent Framework for a survey"
econsent_45 = "Add consent form"
econsent_46 = "Modify e-Consent Settings"
econsent_47 = "Enable e-Consent for a Survey"
econsent_48 = "All surveys in the project have e-Consent enabled. If you wish to modify the e-Consent settings of a survey, you may do so using the table on this page."
econsent_49 = "You may enable the e-Consent Framework for any survey in the project. First, choose the survey below for which you want to enable e-Consent, and then you will be prompted to specify all the e-Consent settings for that survey afterward."
econsent_50 = "Enable e-Consent"
econsent_51 = "e-Consent settings for survey"
econsent_52 = "You may use this dialog to provide your static consent form (or consent form text) that will be displayed on the survey page to the participant.  Below you may add a consent form or replace an existing one with a new version. If you have a simple project, you may choose to add your consent form to a Descriptive field via the Online Designer.  But if you have a more complex project that utilizes multiple Data Access Groups and/or multiple MLM languages, each of which might require their own unique consent form,  then providing your consent forms in this interface might be a more manageable option."
econsent_53 = "Choose a Descriptive field on the survey that will serve as the location of the consent form. The consent form will be displayed immediately below this field on the survey page.  Note: The Descriptive field selected must be the same for all consent forms specified for this survey. If the field is changed, it will be changed for all consent forms for this survey."
econsent_54 = "No languages defined on MLM page"
econsent_55 = "When participant has no language selected"
econsent_56 = "Only display this consent form when viewing the survey in the selected language."
econsent_57 = "No data access groups exist"
econsent_58 = "When record is not assigned to a DAG (default)"
econsent_59 = "Only display this consent form when the record is assigned to the selected data access group. Note: The default option will be used if no DAG-specific consent forms exist."
econsent_60 = "Save settings"
econsent_61 = "E-Consent was successfully enabled for survey \"{0}\"."
econsent_62 = "E-Consent settings were successfully modified for survey \"{0}\"."
econsent_63 = "Consent form version:"
econsent_64 = "The version of the consent form being used by e-Consent for the current context (current record, event, survey, data access group, MLM language, etc.).  This can be used to capture the consent form version when a survey participant is providing their informed consent.  NOTE: This action tag only adds a new value to the field when its field value is blank and only when the instrument is being completed as a survey."
econsent_65 = "Consent Form (Rich Text)"
econsent_66 = "Consent Form (Inline PDF)"
econsent_67 = "Placement of consent form:"
econsent_68 = "Display for specific language:"
econsent_69 = "Display for specific DAG:"
econsent_70 = "Add new consent form"
econsent_71 = "No PDF Snapshot triggers to display"
econsent_72 = "Consent form"
econsent_75 = "Save PDF Snapshot to the following locations:"
econsent_76 = "-- select a File Upload field --"
econsent_77 = "It is required to version each consent form (e.g., \"<code>1.1</code>\", \"<code>2.3.1 2024-06-01</code>\") so that you may manage any future changes and differentiate all versions of the consent form.  It is recommended that you do not begin the version number with the letter \"v\"."
econsent_78 = "ERROR: Make sure you have entered a Version number and have selected a Location for the Consent Form."
econsent_79 = "The consent form was successfully added!"
econsent_80 = "View image of new location"
econsent_81 = "<b>Optional notes:</b> You may add any custom notes here for reference and documentation purposes."
econsent_82 = "ERROR: Only PDF files are allowed to be uploaded. Please try again."
econsent_83 = "ERROR: You must add a version (e.g., <code>1</code> or <code>3.2</code>)."
econsent_84 = "ERROR: You must select a location for the consent form. Choose a Descriptive field from the drop-down list."
econsent_85 = "ERROR: You must change the consent form version when replacing an existing consent form. Try incrementing the version number, and resubmit it."
econsent_86 = "Replace existing consent form"
econsent_88 = "Provide your consent form as a block of styled text that will be displayed directly below the field selected for 'Location of consent form' on the instrument/survey."
econsent_89 = "Provide your consent form as a PDF file that will be displayed inline on the page directly below the field selected for 'Location of consent form' on the instrument/survey."
econsent_90 = "Current consent form:"
econsent_91 = "Upload your PDF consent form:"
econsent_92 = "ERROR: You have provided a consent form in the form of rich text *and also* as a PDF file. You cannot have both. Please remove the PDF or erase the contents of the rich text editor, and try again."
econsent_93 = "ERROR: You must provide your consent form as a block of styled text or as an uploaded PDF file. Please add a consent form in either of these two forms, and try again."
econsent_94 = "The consent form was successfully replaced!"
econsent_96 = "Set as inactive"
econsent_97 = "e-Consent has been successfully re-enabled for survey \"{0}\""
econsent_98 = "e-Consent has been successfully disabled for survey \"{0}\""
econsent_99 = "Add/Edit Trigger for PDF Snapshot"
econsent_100 = "Are you sure you wish to disable e-Consent for this survey?"
econsent_101 = "Use the options below to create a trigger for capturing a PDF Snapshot of a record. The snapshot can be triggered by a survey being completed *or* when specified conditional logic becomes true (but not by both).  You may provide the scope of the snapshot, which is simply which instruments/events you wish to include in the snapshot (one instrument, multiple instruments, or all instruments).  When triggered, snapshots can be saved to the File Repository and/or a single File Upload field. Additionally, you may specify a custom prefix for the snapshot's file name when it is saved.  You may create as many triggers as you wish, and you can deactivate/reactivate them at any time."
econsent_102 = "Click the pencil in the text box below to select specific instruments/events to be included in the PDF."
econsent_103 = "Save to File Repository"
econsent_104 = "Save to specified field:"
econsent_105 = "Trigger for PDF Snapshot was successfully created!"
econsent_106 = "Trigger for PDF Snapshot was successfully modified!"
econsent_107 = "TIP: Leave blank to include all instruments/events (i.e., the entire record's data)."
econsent_108 = "ERROR: Please choose a location to save the snapshot."
econsent_109 = "ERROR: Please choose a trigger for the snaphot: either when a survey is completed or when some conditional logic becomes true."
econsent_110 = "NOTICE: The \"Save a PDF of completed survey response to a File Upload field\" feature has been moved to the \"e-Consent and PDF Snapshots\" page in the Online Designer."
econsent_111 = "NOTICE: The e-Consent Framework and PDF Auto-Archiver features have been moved to the \"e-Consent and PDF Snapshots\" page in the Online Designer."
econsent_112 = "Save as Compact PDF (includes only fields with saved data)"
econsent_113 = "When the following logic becomes true (only once per record):"
econsent_114 = "Every time the following survey is completed:"
econsent_115 = "PDF Snapshot Archive"
econsent_116 = "{1} PDF Snapshots"
econsent_117 = "View all versions"
econsent_118 = "Custom label for PDF header:"
econsent_119 = "Disable?"
econsent_120 = "e-Consent and PDF Snapshot settings"
econsent_121 = "Snapshot file name"
econsent_122 = "Use static text or piping to customize the prefix of the snapshot file's name when it gets stored. Note: The file name will always be appended with the date/time when the snapshot was saved."
econsent_123 = "(option will be located in the Online Designer)"
econsent_124 = "The e-Consent Framework includes end-of-survey certification and archival of the PDF consent form. It is recommended to hide this option only if you will not be using e-Consent in any projects on this REDCap installation."
econsent_126 = "Save PDF Snapshot"
econsent_127 = "PDF Snapshot Trigger has been successfully re-enabled"
econsent_128 = "PDF Snapshot Trigger has been successfully disabled"
econsent_129 = "Are you sure you wish to disable this PDF Snapshot Trigger?"
econsent_130 = "Set consent form as inactive"
econsent_131 = "Are you sure you wish to make the current saved consent form inactive, thus removing the consent form and its settings so that it can no longer be used? NOTE: This will not have any effect on any participants have already consented using this consent form, but will only prevent this consent form from being used in the future."
econsent_132 = "Consent form has been successfully removed"
econsent_133 = "View all consent forms and versions"
econsent_134 = "The table below lists all the consent forms and their versions that have been added for the survey"
econsent_135 = "View more"
econsent_136 = "Displaying consent form content"
econsent_137 = "Time added"
econsent_138 = "Consent form text or file"
econsent_139 = "Number of records consented"
econsent_140 = "STEP 1: Trigger conditions"
econsent_141 = "- Define when the snapshot will be triggered."
econsent_142 = "Scope of the snapshot"
econsent_143 = "STEP 3:"
econsent_144 = "STEP 4:"
econsent_145 = "[All instruments]"
econsent_146 = "Use the settings below for setting up the e-Consent Framework for this survey. e-Consent often requires obtaining the consenting participant's name (and sometimes their date of birth) on the final consent form as documentation of their identity.  Below you may select fields used to capture that info, in which the values for those fields will be automatically inserted into the footer of the PDF consent form that the participant will review at the end the survey.  And then afterwards, that PDF \"hard-copy\" will be archived in the File Repository (with the additional option to also store the PDF in a File Upload field).  Other e-Consent related options can be set below, such as setting a custom tag/category, custom label for the PDF header,  location(s) to save the signed e-Consent snapshot, and the file name format of the snapshots being stored."
econsent_147 = "Primary settings"
econsent_148 = "Additional settings"
econsent_149 = "Manually trigger or re-trigger PDF Snapshots"
econsent_150 = "Snapshot ID"
econsent_151 = "Trigger"
econsent_152 = "Already triggered?"
econsent_153 = "Trigger it?"
econsent_154 = "It is sometimes necessary to manually trigger or re-trigger a PDF snapshot. You may manually trigger or re-trigger the active PDF snapshot triggers listed below by clicking the green trigger button(s). If any buttons are grayed out, then they are not able to be triggered because of the current context or due to your user privileges being limited. <u>Survey completion triggers cannot be initially triggered but can only be re-triggered after the survey has been completed.</u> In order to re-trigger survey completion triggers, you must have Edit privileges for that survey instrument. Additionally, survey completion triggers can only be re-triggered when viewing that specific survey instrument in a data entry form context. Regarding logic-based PDF snapshots, please be aware that logic-based triggers can be triggered <u>even if its conditional logic does not currently evaluate to True</u>. NOTE: If a PDF snapshot was initially triggered by a participant and stored in a specific MLM language, re-triggering the snapshot might not store the new snapshot in the same language as before because the snapshot will always have the current user's/participant's language at the time of the triggering."
econsent_155 = "Re-trigger"
econsent_156 = "Trigger PDF Snapshots"
econsent_157 = "PDF Snapshot was successfully triggered!"
econsent_158 = "Trigger it"
econsent_159 = "Are you sure you wish to trigger Snapshot ID"
econsent_160 = "I certify that I am re-triggering this e-Consent survey, which will electronically regenerate and store a PDF Snapshot that is the equivalent of a physical document."
econsent_161 = "By clicking the submit button below, I am agreeing to the following text:"
econsent_162 = "The e-Consent Framework adds two things to the typical survey-taking process. 1) Before a participant completes the survey, an extra certification page is added to end of the survey that displays an in-line PDF copy of their survey responses in which they will be asked to confirm that all information in the document is correct. Once they confirm all is correct, the survey will then be marked as complete. The survey will not be considered complete until they fulfill the certification step. 2) Upon completion of the survey, a static copy of their responses in the form of a consent-specific PDF will be stored in the project's File Repository. The consent-specific PDF will have the values of the e-Consent Framework Options inserted at the bottom of each page in the PDF. These values (i.e., name, date of birth, etc.) are added to the PDF as extra documentation of the identity of the person who is consenting."
econsent_163 = "What is e-Consent version and the custom tag/category?"
econsent_164 = "e-Consent version and custom tag/category are both free-form text fields whose value will be inserted at the footer of each page in the PDF.  Versioning of a consent form is a concept whereby you may give it a number or alpha-numeric designation to represent the current version or state of the consent form.  So if the consent form is modified AFTER data collection begins, then it is recommended that a new version be applied. For example, the first version might simply be '1',  and after collecting the consent of a few participants, a question is modified or added, which represents a new version of the form, so you might increment the version to '2' (and so forth).  Using consent forms is an optional feature. Once e-Consent is enabled for a survey, you may add one or more consent forms (if needed), in which each consent form must be given a version.  The e-Consent 'custom tag/category' is another optional setting that is a free-form text field that is just a text label that you might want to display in the PDF footer to signify the type of e-Consent that  this survey represents (e.g., pediatric). The tag/category is often used to distinguish between multiple e-Consent forms within a project."
econsent_165 = "Custom tag/category for PDF footer"
econsent_166 = "Consent forms added here will be displayed dynamically on the survey based on the current context.    For example, if you have a DAG-specific consent form, you can specify that the consent form only be displayed for participants in that DAG, while participants in other DAGs will see a different consent form.    The consent forms provided here will be displayed immediately below a specific Descriptive field (specified below) on the survey.    <b>NOTICE: After clicking the \"Add new consent form\" submit, the consent form will GO LIVE IMMEDIATELY on the e-Consent survey.</b>"
econsent_167 = "WARNING: Triggering this PDF snapshot will overwrite any file already stored in the File Upload field where the snapshot will be saved."
econsent_168 = "Note: Piping may be utilized, including the use of Smart Variables."
econsent_169 = "Copy trigger"
econsent_170 = "Do you wish to copy this PDF Snapshot Trigger?"
econsent_171 = "The PDF Snapshot Trigger was successfully copied!"
econsent_172 = "Edit trigger"
econsent_173 = "Name of trigger:"
econsent_174 = "add optional title"
econsent_175 = "WARNING: No Descriptive fields exist on this survey. Please create one."
econsent_176 = "ERROR: Version number already used! The version number you submitted has already been used. Please enter a different version number."
econsent_177 = "ERROR: Version number already used! The version number you submitted has already been used by the current DAG and MLM language selected. Please enter a different version number."
econsent_178 = "ERROR: You may set only a logic-based trigger condition OR a survey completion trigger condition but not both. In Step 1, please either remove the conditional logic from the text box, or else de-select the currently selected option in the survey list drop-down."
econsent_179 = "Inline Image:"
econsent_180 = "Note: This should be static text only."
econsent_181 = "PDF utilized e-Consent Framework"
econsent_182 = "(and additionally save to an External Storage server managed by your institution)"
econsent_183 = "* If the PDF Snapshot contains a completed e-Consent survey response, the snapshot will additionally be saved to an External Storage server managed by your institution."
econsent_184 = "e-Consent Framework and PDF Snapshots"
econsent_185 = "Additional text to display at the bottom of the Modify e-Consent Settings dialog on the e-Consent Framework setup page of *every* project.  This may be utilized to inform your users of specific information surrounding the use of the e-Consent Framework at your institution, for example."
econsent_186 = "NOTE: <u>Piping and field embedding are not allowed</u> in the consent form text below and thus cannot be used there."
econsent_187 = "PDF Snapshots"
econsent_188 = "e-Consent"
econsent_189 = "Additionally, images added via the rich text editor will not be rendered in PDF exports or stored PDF snapshots that include the consent form text below."
top_usage_report_01 = "Top Usage Report"
top_usage_report_02 = "Identifier"
top_usage_report_03 = "CPU Time (hours)"
top_usage_report_04 = "Percent of Total CPU Time"
top_usage_report_05 = "Call Count"
top_usage_report_06 = "Percent of Total Calls"
top_usage_report_07 = "Average Seconds Per Call"
top_usage_report_08 = "Module Page"
top_usage_report_09 = "Include incomplete HTTP requests"
top_usage_report_10 = "This includes both requests that are still running AND requests that completed but did not store a script_execution_time (skewing results). We might be able to store script_execution_time in more scenarios in order to accurately measure HTTP requests that are still running. Currently-running cron jobs are always included regardless of this setting."
top_usage_report_11 = "CPU time percentage minimum threshold:"
top_usage_report_12 = "Display only calls using at least this percentage of total CPU time. CPU time is often a reasonable proxy for database load. The only known significant exceptions are processes that perform a lot of sleep calls (e.g. Flight Tracker crons)."
top_usage_report_13 = "This page displays the most active projects, users, pages, specific URLs, External Modules, cron jobs, etc. within a given period of time. It can be used to quickly identify where server resources are being spent under periods of high load. Here are a few things to keep in mind when interpreting these stats:"
top_usage_report_14 = "This page tracks many, but not all, HTTP requests. See your web server's logs for ALL requests."
top_usage_report_15 = "Hours and percentages represent an accurate portion of the totals tracked, but are duplicated between 'Types' (may add up to more than 100%). For example, if a user makes API requests on a single project totaling 70% of the server's CPU usage, seperate lines for the user AND project will be included (both showing 70%). Aggregating stats like this is important when usage within a single 'Type' becomes excessive (e.g. one user across many projects, or many users on one project)."
top_usage_report_16 = "are not currently included in these stats"
top_usage_report_17 = "No calls were found over the minimum threshold specified."
top_usage_report_18 = "The begin time is outside the range of available data."
top_usage_report_19 = "<b>NOTICE:</b> The Vanderbilt REDCap Team will not be able to help you interpret this report or discuss performance concerns specific to your institution. Understanding these stats can be challenging, and may require in-depth and system-specific historical knowledge. If you have any questions about this report, it is recommended that you ask them to the community at large on <a target='_blank' href='https://redcap.vumc.org/community/'>REDCap Community</a>. For questions relating to a specific External Module, please address those to that module's author (listed in the Control Center)."
top_usage_report_20 = "data is available starting"
top_usage_report_21 = "Unless you're experiencing issues due to server load (slow response times, crash messages, etc), these stats likely do NOT indicate a problem, even if they show very high utilization by certain projects/URLs/users/modules/etc."
cdp_dashboard_label_cdp = "CDP Dashboard"
cdp_dashboard_label_ddp = "DDP Dashboard"
cdp_dashboard_index_bg_processes_description = "<h6>Background processes</h6><p>This dashboard provides a comprehensive view of the data fetching process in CDP and DDP projects, making it easier to follow and monitor.These projects must meet certain prerequisites to be evaluated, such as having real-time web service enabled, being active, not deleted, and not completed.</p><p>There are two cron jobs involved in this process:</p><ol><li><strong>Queueing:</strong> The first cron job checks if records in enabled CDP and DDP projects meet the criteria for fetching their mapped data from the EHR system. If the criteria are met, the records are queued for fetching.<br>This process runs every five minutes.</li><li><strong>Fetching:</strong> The second cron job fetches data for the queued records and stores it in a caching table, where users can review and adjudicate it, moving it from the cache to the data table.<br>This process runs every minute.</li></ol></p><p>The queueing process operates based on specific criteria:</p><ul><li><strong>Future Dates:</strong> Records with mappings that have future dates.</li><li><strong>Recent Data Collection:</strong> Records where data from the EHR system was collected recently, determined by the <code>updated_at</code> field in <code>redcap_ddp_records</code> being within a specified range.</li><li><strong>Lack of Recent Updates:</strong> Records that have not been updated recently, as indicated by the event log.</li></ul><p>The dashboard is designed for providing a clear view of this background process.It allows users to manually queue records for fetching when needed, such as in long-running projects or when mappings are updated,ensuring your projects have the most current and accurate data possible.</p>"
cdp_dashboard_index_cached_values_description = "<h6>Cached values</h6><p>To provide a comprehensive overview of the data fetching process, the dashboard includes a page for cached values. This page allows users to view the cached data for each record and field of their project, providing detailed information such as field names in REDCap, the mapped EHR resources, and the data timestamps. This view is particularly important for temporal data, enabling users to track when data was last updated. The cached data are encrypted for privacy,but users can decrypt the data for debugging or verification purposes.</p>"
cdp_dashboard_not_queueable_description = "<p>This page displays a table of records that have been identified as non-queuable based on specific criteria. For each record, one or more reasons are provided to explain why the inclusion criteria were not met. These records are not automatically queued for data fetching due to the following factors:</p><ul><li><strong>Future Dates:</strong> Records with mappings that have future dates.</li><li><strong>Recent Data Collection:</strong> Records where data from the EHR system was collected recently, determined by the <code>updated_at</code> field in <code>redcap_ddp_records</code> being within a specified range.</li><li><strong>Lack of Recent Updates:</strong> Records that have not been updated recently, as indicated by the event log.</li></ul><p>Additionally, the project must meet certain prerequisites to evaluate the records, such as having real-time web service enabled, being active, not deleted, and not completed.</p><p>Here, you have the ability to manually mark some or all of the records in the project as QUEUED. By doing so, you will force their data to be fetched during the next data fetching cycle.</p>"
cdp_dashboard_queued_description = "<p>This page displays a table of records that have been marked as QUEUED for data fetching.<br>These records are scheduled to have their data fetched during the next data fetching cycle.</p>"
cdp_dashboard_cached_description = "<p>This page displays the cached data for each record and field of your project.<br>Here, you can view detailed information such as the name of the field in REDCap, the EHR resource that was mapped, and the timestamp of the data, which is particularly important for temporal data like Observations.</p><p>The values of the cached data are encrypted for privacy.<br>If you need to view the actual values for debugging or verification purposes, you can click the Decrypt button.<br>After a confirmation, the data will be decrypted and displayed.</p>"
cdp_dashboard_cached_alert = "Please note that decrypting the data is a sensitive action and should only be performed when absolutely necessary."
cdp_dashboard_no_records = "no records"
cdp_dashboard_table_header_select_all = "Select All"
cdp_dashboard_table_header_record = "Record"
cdp_dashboard_table_header_reasons = "Reasons"
cdp_dashboard_queue_selected = "Queue Selected"
cdp_dashboard_queue_all = "Queue All"
cdp_dashboard_encrypt = "Encrypt"
cdp_dashboard_decrypt = "Decrypt"
cdp_dashboard_confirm_decrypt = "Are you sure you want to decrypt the cached values? Decrypted data will be visible in the 'Cached Value' column"
cdp_dashboard_confirm_queue_queue_selected = "Are you sure you want to queue the selected records?"
cdp_dashboard_confirm_queue_queue_all = "Are you sure you want to queue the all records?"
cdp_dashboard_alert_success = "Success"
mycapui_general_001 = "Mobilizing the Participant Voice"
mycapui_general_002 = "Ok"
mycapui_general_003 = "Done"
mycapui_general_004 = "Participate"
mycapui_general_005 = "MyCap is a mobile app used by research participants to enter data for research projects. To start, select and edit \"primary Profile\" or create a new profile. To join a project a research team will provide a hyperlink (URL) or QR code."
mycapui_general_006 = "Powered by [Vanderbilt University Medical Center]"
mycapui_general_007 = "Create Profile"
mycapui_general_008 = "Username"
mycapui_general_009 = "Passcode (6 Digits)"
mycapui_general_010 = "Save"
mycapui_general_011 = "Login with Passcode"
mycapui_general_012 = "Enter 6-digit Passcode"
mycapui_general_013 = "wrong passcode"
mycapui_general_014 = "remaining "
mycapui_general_015 = "Select a study or join a new one"
mycapui_general_016 = "Currently not enrolled in any studies."
mycapui_general_017 = "JOIN PROJECT"
mycapui_general_018 = "Currently enrolled in"
mycapui_general_019 = "Study Initialization Error"
mycapui_general_020 = "Could not proceed. Another profile is already enrolled in this study using same participant credentials."
mycapui_general_021 = "Retry"
mycapui_general_022 = "Cancel"
mycapui_general_023 = "Join Project"
mycapui_general_024 = "Example"
mycapui_general_025 = "Scan the QR code you were given and MyCap will load the appropriate project. Your QR code will look similar to the example shown above. "
mycapui_general_026 = "Scan QR Code"
mycapui_general_027 = "App Info"
mycapui_general_028 = "Privacy Policy"
mycapui_general_029 = "For Participants"
mycapui_general_030 = "Ownership"
mycapui_general_031 = "You, the user, are entering data into a mobile device. While the data resides on the mobile device, you own all data that you have created or modified. Your data is sent to the project's server. When data is sent to the server, the project administrator owns the data. Any non-user data retrieved from the server, such as configuration information, is owned by the project administrator."
mycapui_general_032 = "Privacy"
mycapui_general_033 = "Your data is treated as private. All attempts are made to secure the data from outside interception. Data is sent via a SSL connection to the MyCap server from which the project originated."
mycapui_general_034 = "Storage"
mycapui_general_035 = "The project configuration and (optionally) some user data are downloaded from a MyCap server via a SSL connection. The configuration and any data are stored in one or more encrypted databases on the mobile device. If a user is participating in multiple projects then there will be multiple encrypted databases. Each project has a siloed database."
mycapui_general_036 = "Allocation of Software and Data"
mycapui_general_037 = "The parent MyCap server hosts the project and the final copy of the data. This resides at the host institution/organization that is running the MyCap REDCap module."
mycapui_general_038 = "The mobile device hosts the project configuration and any temporary study data. The data does not become authoritative until sent to the MyCap server."
mycapui_general_039 = "End-User License Terms for MyCap"
mycapui_general_040 = "End Users, by downloading and/or using MyCap hereby agree to the following terms and conditions in addition to the Licensed Application End User License Agreement supplied by Apple, Inc."
mycapui_general_041 = "Definitions"
mycapui_general_042 = "HIPAA: shall mean the United States statute known as the Health Insurance Portability and Accountability Act of 1996, as codified at 42 U.S.C. §1320d, and further in the Health Information Technology Act of 2009, as codified at 42 U.S.C.A. prec. § 17901 (\"HITECH Act\")"
mycapui_general_043 = "Protected Personal Information: shall mean personal, private, or health information protected against disclosure by laws such as HIPAA, the European Data Privacy Directive, and/or any other applicable laws, rules, and regulations of any jurisdiction governing such health information to which the downloading and/or use of MyCap may be subject."
mycapui_general_044 = "Additional Terms of Use"
mycapui_general_045 = "You, as an End User, agree that any information stored on any device using MyCap may be Protected Personal Information and hereby warrant that you will not disclose such information to any person except as may be permitted or required under the applicable laws, rules, and regulations of the jurisdiction governing such information to which your downloading and/or use of MyCap may be subject. In no event, however, shall the privacy of any such information be maintained with a lessor standard of care than would be necessary to comply with HIPAA. You agree to seek legal advice from a licensed legal counselor to inform yourself about all such applicable laws, statutes, or regulations that apply to your use of MyCap."
mycapui_general_046 = "You, as an End User, shall indemnify, defend and hold harmless Vanderbilt University and its directors, officers, employees, and students (the \"Indemnitees\") against any liability, obligation, damage, loss, adverse impact or expense (including reasonable attorney's fees and expenses of litigation) incurred by or imposed upon the Indemnitees or any one of them arising out of or related to your use of MyCap, including, but not limited to, any claims arising under HIPAA or any other applicable laws, rules, and regulations of any jurisdiction governing such personal information to which your downloading and/or use of MyCap may be subject."
mycapui_general_047 = "By downloading and/or using MyCap, you, as an End User hereby: (a) irrevocably submit to the exclusive jurisdiction of the United States District Court for the Middle District of Tennessee or a local court sitting in Davidson County, Tennessee (collectively, the \"Courts\") for purposes of any action, suit or other proceeding relating to or arising out of this Agreement and (b) agree not to raise any objection at any time to the laying or maintaining of the venue of any such action, suit or proceeding in any of the Courts, irrevocably waives any claim that such action, suit or other proceeding has been brought in an inconvenient forum and further irrevocably waives the right to object, with respect to such action, suit or other proceeding, that such Court does not have any jurisdiction over such Party."
mycapui_general_048 = "Should the terms of this Notice of Permitted Use and Additional End-User License Terms for Users Downloading MyCap (the \"MyCap Agreement\") conflict with any terms in the Licensed Application End User License Agreement supplied by Apple, Inc, the terms of this MyCap Agreement shall control."
mycapui_general_049 = "Experiencing an issue? Tap here to"
mycapui_general_050 = "Settings"
mycapui_general_051 = "App Settings"
mycapui_general_052 = "Report a Bug"
mycapui_general_053 = "Exit"
mycapui_general_054 = "Cancel"
mycapui_general_055 = "Report a Bug."
mycapui_profiles_001 = "Primary Profile"
mycapui_profiles_002 = "CREATE PROFILE"
mycapui_profiles_003 = "My Projects"
mycapui_profiles_004 = "Pending study to join"
mycapui_profiles_005 = "Select Profile or Create New Profile to Join a Study from the dynamic link"
mycapui_profiles_006 = "Select a study or Join a new one"
mycapui_profiles_007 = "Click to Join a Study from Dynamic Link"
mycapui_profiles_008 = "Welcome!"
mycapui_profiles_009 = "Thank you for participating in this project."
mycapui_profiles_010 = "Notifications"
mycapui_profiles_011 = "Allowing notifications enables the app to show you reminders."
mycapui_profiles_012 = "If allowed, notifications will come through that say [Profile name] has a task due today."
mycapui_profiles_013 = "Not now"
mycapui_profiles_014 = "Allow"
mycapui_profiles_015 = "Receiving notifications is NOT allowed"
mycapui_profiles_016 = "Receiving notifications is allowed"
mycapui_profiles_018 = "Checking updates..."
mycapui_profiles_019 = "Retrieving Studies..."
mycapui_profiles_020 = "Profile Image"
mycapui_profiles_021 = "Gallery"
mycapui_profiles_022 = "Edit Profile"
mycapui_profiles_023 = "Disabled"
mycapui_profiles_024 = "Enabled"
mycapui_profiles_025 = "Delete Profile"
mycapui_profiles_026 = "Save Changes"
mycapui_profiles_027 = "The '___________' Profile is deleted."
mycapui_profiles_028 = "Confirm"
mycapui_profiles_029 = "Would you like to continue and delete '________' profile?"
mycapui_profiles_030 = "Good!"
mycapui_profiles_031 = "You will be asked for permissions to access device features."
mycapui_profiles_032 = "Complete"
mycapui_profiles_033 = "Could not proceed. You are already enrolled in this study."
mycapui_profiles_034 = "Joining project via dynamic link..."
mycapui_profiles_035 = "Delete Study"
mycapui_profiles_036 = "Would you like to proceed and delete the study"
mycapui_profiles_037 = "from this profile?"
mycapui_profiles_038 = "Reload Complete"
mycapui_profiles_039 = "Project"
mycapui_profiles_040 = "successfully reloaded!"
mycapui_profiles_041 = "Updating Project Configuration"
mycapui_profiles_042 = "Reload"
mycapui_profiles_043 = "Alert"
mycapui_profiles_044 = "Please confirm to reset task notification for"
mycapui_profiles_045 = "Passcode"
mycapui_profiles_046 = "Create a 6-digit passcode to identify yourself to the app and protect access to information you have entered."
mycapui_profiles_047 = "Enter your Passcode"
mycapui_profiles_048 = "Profile"
mycapui_profiles_049 = "Delete"
mycapui_profiles_050 = "Continue"
mycapui_profiles_051 = "Sending Task Result"
mycapui_profiles_052 = "Transferring data... Please keep the app open."
mycapui_profiles_053 = "Syncing tasks in progress, that takes up to 60 seconds"
mycapui_profiles_055 = "Failed to Connect"
mycapui_profiles_056 = "Error with retrieving saved tasks"
mycapui_profiles_057 = "This project supports the following languages. Please choose the language you wish to use and tap \"Next\" to proceed."
mycapui_profiles_058 = "Success"
mycapui_profiles_059 = "Please select a destination from the options below"
mycapui_activities_001 = "HOME"
mycapui_activities_002 = "HISTORY"
mycapui_activities_003 = "CHART"
mycapui_activities_004 = "TASKS"
mycapui_activities_005 = "TASK"
mycapui_activities_006 = "UPCOMING"
mycapui_activities_007 = "Activities"
mycapui_activities_008 = "Completed Tasks"
mycapui_activities_009 = "Date"
mycapui_activities_010 = "No completed chart tasks yet"
mycapui_activities_011 = "Select Language"
mycapui_activities_012 = "OVERDUE"
mycapui_activities_013 = "English"
mycapui_activities_014 = "Simplified Chinese"
mycapui_activities_015 = "Hindi"
mycapui_activities_016 = "Standard Arabic"
mycapui_activities_017 = "French"
mycapui_activities_018 = "Bengali"
mycapui_activities_019 = "Brazilian Portuguese"
mycapui_activities_020 = "Urdu"
mycapui_activities_021 = "Japanese"
mycapui_activities_022 = "Lahnda (Western Punjabi)"
mycapui_activities_023 = "German"
mycapui_activities_024 = "Korean"
mycapui_activities_025 = "Italian"
mycapui_activities_026 = "Tagalog"
mycapui_activities_027 = "Vietnamese"
mycapui_activities_028 = "Haitian Creole"
mycapui_activities_030 = "Ukranian"
mycapui_activities_031 = "Add more translations"
mycapui_activities_032 = "Confirm Selection"
mycapui_activities_033 = "Localization Menu"
mycapui_activities_034 = "Close"
mycapui_activities_035 = "Chart Tasks"
mycapui_activities_036 = "1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17...100 %"
mycapui_activities_037 = "Show by Time"
mycapui_activities_038 = "Show by Date"
mycapui_activities_039 = "Calendar"
mycapui_activities_040 = "Alert:"
mycapui_activities_041 = "This is a future task. Please come back later to complete it!"
mycapui_activities_042 = "January"
mycapui_activities_043 = "February"
mycapui_activities_044 = "March"
mycapui_activities_045 = "April"
mycapui_activities_046 = "May"
mycapui_activities_047 = "June"
mycapui_activities_048 = "July"
mycapui_activities_049 = "August"
mycapui_activities_050 = "September"
mycapui_activities_051 = "October"
mycapui_activities_052 = "November"
mycapui_activities_053 = "December"
mycapui_activities_054 = "Monday"
mycapui_activities_055 = "Tuesday"
mycapui_activities_056 = "Wednesday"
mycapui_activities_057 = "Thursday"
mycapui_activities_058 = "Friday"
mycapui_activities_060 = "Saturday"
mycapui_activities_061 = "Sunday"
mycapui_messages_01 = "Refresh"
mycapui_messages_02 = "Type your message here"
mycapui_messages_03 = "Send"
mycapui_messages_04 = "Messages"
mycapui_messages_05 = "[Profile name] has a task due today."
mycapui_messages_06 = "You have a secure message waiting."
mycapui_about_01 = "About"
mycapui_contacts_01 = "Name"
mycapui_contacts_02 = "Phone"
mycapui_contacts_03 = "Email"
mycapui_contacts_04 = "Web"
mycapui_contacts_05 = "Note"
mycapui_contacts_06 = "Contacts"
mycapui_links_01 = "Links"
mycapui_tasks_001 = "Exit Task"
mycapui_tasks_002 = "Confirm to Exit"
mycapui_tasks_003 = "CANCEL"
mycapui_tasks_004 = "DISCARD RESULTS"
mycapui_tasks_005 = "SAVE FOR LATER"
mycapui_tasks_006 = "Switch Study Successful"
mycapui_tasks_007 = "Switch Study"
mycapui_tasks_008 = "Successful"
mycapui_tasks_009 = "Due on"
mycapui_tasks_010 = "Finished Task!"
mycapui_tasks_011 = "Send Your Answer?"
mycapui_tasks_012 = "Back"
mycapui_tasks_013 = "Time"
mycapui_tasks_014 = "Specified field validation not supported yet"
mycapui_tasks_015 = "Required Field"
mycapui_tasks_016 = "Please enter a value"
mycapui_tasks_017 = "Invalid phone number format"
mycapui_tasks_018 = "Please enter a valid phone number"
mycapui_tasks_019 = "Invalid email format"
mycapui_tasks_020 = "Please enter a valid email address"
mycapui_tasks_021 = "Invalid zip code format"
mycapui_tasks_022 = "Please enter a valid zip code"
mycapui_tasks_023 = "Invalid input value"
mycapui_tasks_024 = "Please enter a number smaller than"
mycapui_tasks_025 = "Please enter a number greater than"
mycapui_atgeneral_01 = "Activity Complete"
mycapui_atgeneral_02 = "Next"
mycapui_atgeneral_03 = "Finished"
mycapui_atgeneral_04 = "Thank you for taking the tests"
mycapui_atgeneral_05 = "Discard results and quit?"
mycapui_atgeneral_06 = "No"
mycapui_atgeneral_07 = "Yes"
mycapui_holepeg_01 = "Hole Peg Test"
mycapui_holepeg_02 = "This activity measures your upper extremity function by asking you to place a peg in a hole. You will be asked to do this"
mycapui_holepeg_03 = "times."
mycapui_holepeg_04 = "[x] - Hole Peg Test"
mycapui_holepeg_05 = "Both your right and left hands will be tested. You must pick up the peg as quickly as possible, put it in the hole, and once done"
mycapui_holepeg_06 = "remove it again"
mycapui_holepeg_07 = "Get Started"
mycapui_holepeg_08 = "Tap Get Started to begin."
mycapui_holepeg_09 = "Put the peg in the hole using your left hand. Pick up the peg using two fingers."
mycapui_holepeg_10 = "Put the peg in the hole using your left hand. Lift fingers to drop the peg."
mycapui_holepeg_11 = "Put the peg in the hole using your right hand. Pick up the peg using two fingers."
mycapui_holepeg_12 = "Put the peg in the hole using your right hand. Lift fingers to drop the peg."
mycapui_amsler_01 = "This activity helps in detecting problems in the user's vision."
mycapui_amsler_02 = "Hold the device 12 inches from your face and at eye level through out the test."
mycapui_amsler_03 = "Close your LEFT Eye and stare at the dot in the center of the square grid. Using your finger or stylus, mark any distortions you see such as blurred or wavey lines."
mycapui_amsler_04 = "When you are done, swipe left anywhere outside the grid."
mycapui_audio_01 = "Audio"
mycapui_audio_02 = "You will record your audio on the next screen."
mycapui_audio_03 = "Press \"Start Recording\" to record your audio."
mycapui_audio_04 = "Start Recording"
mycapui_audio_05 = "Play"
mycapui_audio_06 = "Reset"
mycapui_fitness_01 = "Fitness"
mycapui_fitness_02 = "\"MyCap\" Would like to Access Your Motion & Fitness Activity Access to motion sensors is required to register participants steps."
mycapui_fitness_03 = "Don't Allow"
mycapui_fitness_04 = "Walk outdoors at your fastest possible pace for"
mycapui_fitness_05 = "seconds."
mycapui_fitness_06 = "When you're done, sit and rest comfortably for"
mycapui_fitness_07 = "To begin, tap Next."
mycapui_fitness_08 = "Starting activity in"
mycapui_fitness_09 = "Walk as fast as you can for"
mycapui_fitness_10 = "Sit comfortably for"
mycapui_psat_01 = "The Paced Auditory and Visual Serial Addition Test measures your auditory and visual information processing speed and calculation ability."
mycapui_psat_02 = "Single digits are presented every"
mycapui_psat_03 = "You must add each new digit to the one immediately prior to it."
mycapui_psat_04 = "Attention, you must calculate a running total, but only the sum of the last two numbers."
mycapui_psat_05 = "Add the new digit to the previous one."
mycapui_selfie_01 = "Selfie Capture"
mycapui_selfie_02 = "You will take your selfie on the next screen."
mycapui_selfie_03 = "Press \"Start Preview\" to take your selfie."
mycapui_selfie_04 = "Start Preview"
mycapui_selfie_05 = "Searching For Faces..."
mycapui_selfie_06 = "Please keep your face in front of the camera"
mycapui_swalk_01 = "Gait and Balance"
mycapui_swalk_02 = "This activity measures your gait and balance as you walk and stand still. Do not continue if you cannot safely walk unassisted."
mycapui_swalk_03 = "Find a place where you can safely walk unassisted for about 20 steps in a straight line."
mycapui_swalk_04 = "Put your phone in a pocket or bag and follow the audio instructions."
mycapui_swalk_05 = "Walk up to 20 steps in a straight line."
mycapui_swalk_06 = "Turn around and walk back to where you started."
mycapui_swalk_07 = "Stand still for 20 seconds."
mycapui_spatial_01 = "Spatial Memory"
mycapui_spatial_02 = "This activity measures your short-term spatial memory by asking you to repeat the order in which flowers light up."
mycapui_spatial_03 = "Some of the flowers will light up one at a time. Tap those flowers in the same order they lit up. To begin, tap Get Started, then watch closely."
mycapui_spatial_04 = "Watch the flowers light up"
mycapui_spatial_05 = "Try Again"
mycapui_spatial_06 = "You didn't quite make it through that time. Tap Next to continue."
mycapui_spatial_07 = "Tap the flowers in the order they lit up."
mycapui_spatial_08 = "Sequence Complete"
mycapui_spatial_09 = "To continue, tap Next"
mycapui_stroop_01 = "Every time a word appears, select the first letter of the name of the COLOR that is shown. "
mycapui_stroop_02 = "Next"
mycapui_stroop_03 = "When you are ready to begin the Stroop activity tap Get Started."
mycapui_stroop_04 = "Select the first letter of the name of the COLOR that is shown."
mycapui_stroop_05 = "BLUE"
mycapui_stroop_06 = "GREEN"
mycapui_stroop_07 = "RED"
mycapui_stroop_08 = "YELLOW"
mycapui_phonation_01 = "Voice"
mycapui_phonation_02 = "This activity evaluates your voice by recording it with the microphone at the bottom of your phone."
mycapui_phonation_03 = "Your more specific voice instructions goes here. For example, say 'Aaah'"
mycapui_phonation_04 = "Tap Next to begin."
mycapui_phonation_05 = "Please wait while we check the background noise level."
mycapui_twalk_01 = "Tone Audiometry"
mycapui_twalk_02 = "This activity measures your lower extremity function."
mycapui_twalk_03 = "Assistive device"
mycapui_twalk_04 = "Use the same assistive device for each test."
mycapui_twalk_05 = "Do you war an ankle foot orthosis?"
mycapui_twalk_06 = "Do you use assistive device?"
mycapui_twalk_07 = "Tap here to select an asnwer."
mycapui_twalk_08 = "None"
mycapui_twalk_09 = "Unilateral Cane"
mycapui_twalk_10 = "Unilateral Crutch"
mycapui_twalk_11 = "Bilateral Cane"
mycapui_twalk_12 = "Bilateral Crutch"
mycapui_twalk_13 = "Walker/Rollator"
mycapui_twalk_14 = "Find a place, preferably outside, where you can walk for about 100 meters in a straight line as quickly as possible, but safely. Do not slow down until after you've passed the finish line."
mycapui_twalk_15 = "4"
mycapui_twalk_16 = "3"
mycapui_twalk_17 = "2"
mycapui_twalk_18 = "1"
mycapui_twalk_19 = "Walk up to 100 m in a straight line. Tap Next when complete."
mycapui_twalk_20 = "Turn around"
mycapui_twalk_21 = "Tap Next when complete."
mycapui_twalk_22 = "Walk up to where you started."
mycapui_tone_02 = "This activity measures your ability to hear different sounds."
mycapui_tone_03 = "Tap any button when you are ready to begin."
mycapui_tone_04 = "Tap"
mycapui_tone_05 = "Left Ear"
mycapui_tone_06 = "Right Ear"
mycapui_tone_07 = "Every time you start hearing a sound, tap the left or right button to indicate which ear you hear the sound in."
mycapui_hanoi_01 = "Tower of Hanoi"
mycapui_hanoi_02 = "This activity evaluates your puzzle solving skills."
mycapui_hanoi_03 = "Move the entire stack to the highlighted platform in as few moves as possible."
mycapui_hanoi_04 = "Get Started"
mycapui_hanoi_05 = "Solve the Puzzle"
mycapui_hanoi_06 = "Number of moves"
mycapui_trail_01 = "Trail Making Test"
mycapui_trail_02 = "Test visual attention and task switching."
mycapui_trail_03 = "This activity evaluates your visual attention and task switching by recording the time required to tap a series of dots in order. "
mycapui_trail_04 = "After the countdown, tap the numbered dots in order. Begin by tapping the first number '1' followed by the numbers '2' - '3' - '4'...until you reach the last number."
mycapui_trail_05 = "Do this as quickly as you can without making mistakes."
mycapui_trail_06 = "Tap Get Started to begin "
mycapui_trail_07 = "Starting activity in "
mycapui_trail_08 = "5"
mycapui_trail_09 = "6"
mycapui_trail_10 = "7"
mycapui_trail_11 = "8"
mycapui_trail_12 = "9"
mycapui_trail_13 = "10"
a11y_01 = "Skip to main content"
cdis_info_auto_login_active = "Auto-login is enabled in the <code>Launch from EHR</code> context."
cdis_info_auto_login_inactive = "Auto-login can be enabled after a successful <code>Launch from EHR</code>."
cdis_info_auto_login_title = "Auto-login Information"
cdis_info_auto_login_what_is_summary = "What is Auto-login?"
cdis_info_auto_login_what_is_description = "Auto-login is a feature used during the <code>Launch from EHR</code> process. Once a user successfully logs in for the first time, REDCap links the user’s REDCap and EHR accounts. This link allows for automatic recognition in future interactions between REDCap and the EHR, reducing the need for repeated logins."
cdis_info_auto_login_how_to_enable_summary = "How to enable Auto-login?"
cdis_info_auto_login_how_to_enable_description = "Auto-login is automatically set up after a successful <code>Launch from EHR</code>. Once linked, future REDCap interactions through the EHR interface will no longer require the user to input credentials. This process enhances the user experience and makes it easier to retrieve and manage EHR data."
cdis_info_auto_login_1 = "Auto-login is a feature used during the <code>Launch from EHR</code> process. The first time a user successfully authenticates, REDCap creates a link between their REDCap account and their EHR account. This connection allows REDCap to automatically recognize the user in future sessions when using the CDIS feature within the EHR system."
cdis_info_auto_login_2 = "With auto-login enabled, users don’t need to repeatedly enter their REDCap credentials every time they interact with REDCap from the EHR interface, streamlining the authentication process."
cdis_info_ehr_access_info_title = "EHR Access Information"
cdis_info_ehr_access_active = "The user has active EHR access and can pull data from the EHR system using the CDIS feature."
cdis_info_ehr_access_inactive = "The user should obtain EHR access before they can pull data from the EHR system."
cdis_info_ehr_access_inactive_02 = "The user should connect to the EHR system before they can pull data."
cdis_info_ehr_access_info_summary = "Info about EHR Access..."
cdis_info_ehr_access_info_description = "When a user connects to the EHR system, REDCap generates an <code>EHR access token</code> that temporarily allows the user to access and retrieve patient data from the EHR. This token is like a digital pass that grants permission to securely pull data from the EHR system. If the token is active, the user has EHR access; if it expires, the user must reconnect to get a new token."
cdis_info_ehr_access_get_access_summary = "How to get access..."
cdis_info_ehr_access_get_access_summary_02 = "How to connect to the EHR system..."
cdis_info_ehr_access_get_access_description = "EHR access can be obtained in two ways:"
cdis_info_ehr_access_get_access_method_1 = "<strong>Standalone Launch</strong>: Directly connect to the EHR system from within REDCap."
cdis_info_ehr_access_get_access_method_2 = "<strong>Launch from EHR</strong>: Access is initiated from the EHR system, which will grant the user EHR access and allow interaction with REDCap from within the EHR interface."
cdis_info_ehr_access_get_access_note = "Users must have valid EHR system credentials to access the system."
cdis_info_ehr_access_usage_summary = "How your access is used..."
cdis_info_ehr_access_usage_description_1 = "Once EHR access is granted, it allows real-time data retrieval through REDCap's CDIS feature and also enables background processes (e.g., cron jobs) to access data."
cdis_info_ehr_access_usage_description_2 = "<strong>For background processes:</strong>"
cdis_info_ehr_access_usage_criteria_1 = "REDCap selects the most suitable EHR access as follows:"
cdis_info_ehr_access_usage_criteria_2 = "Only tokens from users assigned to the current project are considered."
cdis_info_ehr_access_usage_criteria_3 = "Tokens specific to a patient (obtained via <strong>Launch from EHR</strong>) are prioritized."
cdis_info_ehr_access_usage_criteria_4 = "If multiple tokens are available, the most recently issued one is used."
draft_preview_01 = "Draft Preview Mode"
draft_preview_02 = "Draft Preview Mode allows you to <b>preview your data entry forms with your current drafted changes <u>as if they were live</u></b>. This allows you to fully test the changes you have made in Draft Mode, including all branching logic, calculations, action tags, and embedded fields, before submitting your drafted changes for approval."
draft_preview_03 = "Turn on Draft Preview Mode"
draft_preview_04 = "<b>DRAFT PREVIEW MODE</b> is currently enabled. <b>Any data entered will be transient and not saved permanently. Several features are currently inactive.</b> To turn off Draft Preview Mode, go to the {0:LinkStart}Online Designer{1:LinkEnd} or click the DRAFT PREVIEW indicator on the left-hand menu."
draft_preview_05 = "DRAFT PREVIEW"
draft_preview_06 = "{0:RecordID-Label} <b>{1:RecordID}</b> {2:Instance} has been saved to a <b>temporary location</b> for testing during DRAFT PREVIEW only."
draft_preview_07 = "While <b>DRAFT PREVIEW</b> is enabled, access to the Randomization module is <b>disabled</b>.<br>To turn off DRAFT PREVIEW mode, go to the {0:LinkStart}Online Designer{1:LinkEnd} or click the DRAFT PREVIEW indicator on the left-hand menu."
draft_preview_08 = "Disabled while in DRAFT PREVIEW mode"
draft_preview_09 = "While <b>DRAFT PREVIEW</b> is enabled, creation of new records is <b>disabled</b>.<br>To turn off DRAFT PREVIEW mode, go to the {0:LinkStart}Online Designer{1:LinkEnd} or click the DRAFT PREVIEW indicator on the left-hand menu."
draft_preview_10 = "<b>DRAFT PREVIEW MODE</b> is currently enabled. New records cannot be created while in Draft Preview Mode."
draft_preview_11 = "Disabled while DRAFT PREVIEW MODE is active"
draft_preview_12 = "A new instance was not created. The creation of new records or instances <b>is disabled</b> while <b>Draft Preview Mode</b> is enabled."
draft_preview_13 = "Record-level delete operations <b>are disabled</b> while <b>Draft Preview Mode</b> is enabled."
draft_preview_14 = "You are currently in <b>Draft Preview Mode</b>. To cancel this mode, click here.<br><small>(Note: The page will reload automatically.)</small>"
draft_preview_15 = "Please note that any changes made to a record in <b>Draft Preview Mode</b> will not be reflected in any reports or data exports. To turn off DRAFT PREVIEW mode, go to the {0:LinkStart}Online Designer{1:LinkEnd} or click the DRAFT PREVIEW indicator on the left-hand menu."
draft_preview_16 = "Please note that <b>Draft Preview Mode</b> does not support nor affect data imports using the Data Import Tool or the API. This means that even though DRAFT PREVIEW is currently enabled, any imports <b>will permanently affect the data stored in this project</b> and any reference to drafted data dictionary changes will result in an error. To turn off DRAFT PREVIEW mode, go to the {0:LinkStart}Online Designer{1:LinkEnd} or click the DRAFT PREVIEW indicator on the left-hand menu."
draft_preview_17 = "DRAFT PREVIEW cannot be used on this REDCap instance because the <code>session.serialize_handler</code> is not supported as currently set. It must be <code>php</code> or <code>php_binaray</code>. Please talk to your REDCap administrator to have this fixed."
draft_preview_18 = "Note that Draft Preview Mode is <u>active only for you</u>. It will remain active until turned off or until your current REDCap session ends."
draft_preview_19 = "<b>DRAFT PREVIEW MODE</b> is currently enabled. Any data entered will be transient and not saved permanently."
draft_preview_20 = "Additionally, Draft Preview Mode will <b><u>simulate</u> live data entry on data entry forms</b>, thus allowing you to enter *ephemeral data* that is stored only in your session; however, <b>no data will actually be saved to the project</b>. Once you leave Draft Preview Mode, all ephemeral data that has been entered will vanish.<br><br> <b>LIMITATIONS</b>: While in Draft Preview Mode, the following limitations exist...<ul> <li>No new records can be created</li> <li>No data can be changed or stored in the project (all data changes are transient and are bound to your login session)</li> <li>Only changes to <u>already existing forms</u> can be previewed</li> <li>Delete operations (deleting whole records or deleting data for forms/events) are disabled</li> <li>Record locking and form-level locking/unlocking are disabled</li> <li>Randomization of a record and access to the Randomization module are disabled</li> <li>Field Comments/Data Resolution Workflow and the Data History Popup are disabled</li> <li>No Alerts, ASIs, or Data Entry Triggers will be triggered</li> <li>Form Display Logic is disabled</li> <li>Note: Draft Preview Mode only operates on data entry pages, the Record Status Dashboard, and the Record Home Page. It does not impact any other pages, and it currently <b>does not work on survey pages.</b></li></ul>"
draft_preview_21 = "<b>Draft Preview Mode has been enabled.</b> You may begin testing your drafted changes on data entry forms for existing records."
em_config_1 = "<b>Enable module on all projects by default:</b><br>Unchecked (default) = Module must be enabled in each project individually"
em_config_2 = "<b>Make module discoverable by users:</b><br>Display info on External Modules page in all projects"
em_config_3 = "<b>Module configuration permissions in projects:</b><br>By default, users with Project Setup/Design privileges can modify this module's project-level configuration settings. Alternatively, project users can be given explicit module-level permission (via User Rights page) in order to do so"
em_config_3_1 = "Require Project Setup/Design privilege"
em_config_3_2 = "Require module-specific user privilege"
em_config_4 = "<b>Language file:</b><br>Language file to use for this module. This setting can be overridden in the project configuration of this module"
em_config_5 = "<b>Language file:</b><br>Language file to use for this module in this project (leave blank for system setting to apply)"
em_config_6 = "--- None ---"
em_config_8 = "<b>Allow non-admins to enable this module on projects:</b><br>When this and the discoverable setting above are both checked, users with Project Setup/Design privileges will have the ability to enable this module on projects without administrator approval"
em_config_9 = "<b>Hide this module from non-admins in the list of enabled modules on each project</b>"
em_config_10 = "Hide this module from non-admins in the list of enabled modules on this project"
em_errors_1 = "Requests directly to module version directories are disallowed. Please use the getUrl() method to build urls to your module pages instead."
em_errors_2 = "The current user is a super user, so this module will be automatically disabled."
em_errors_3 = "A fatal error occurred while loading the {0} external module.<br>Disabling that module..."
em_errors_4 = "The {0} external module was automatically disabled in order to allow REDCap to function properly. The REDCap administrator has been notified. Please save a copy of the above error and fix it before re-enabling the module."
em_errors_5 = "An error occurred while disabling the {0} module:"
em_errors_6 = "The '{0}' setting key is reserved for internal use. Please use a different setting key in your module."
em_errors_7 = "This module's main class does not extend AbstractExternalModule!"
em_errors_8 = "This module cannot be enabled because a different version of the module is already enabled under the following prefix: {0}"
em_errors_9 = "One or more cron jobs for this module failed to be created."
em_errors_10 = "Some cron job attributes in the module's config file are not correct or are missing."
em_errors_11 = "Cron job 'name' must be no more than 100 characters."
em_errors_12 = "Cron job 'name' can only have lower-case letters, numbers, and underscores (i.e., no spaces, dashes, dots, or special characters)."
em_errors_13 = "Cron job attributes 'cron_frequency' and 'cron_max_run_time' must be numeric and greater than zero --OR-- attributes 'cron_hour' and 'cron_minute' must be numeric and valid."
em_errors_14 = "The external module '{0}_{1}' has a cron job named '{2}' that is trying to call a method '{3}', which does not exist in the module class."
em_errors_15 = "The '{0}' module was automatically disabled because of the following error:"
em_errors_16 = "REDCap External Module Automatically Disabled - {0}"
em_errors_17 = "Lock acquisition timed out while setting a setting for module {0} and project {1}. This should not happen under normal circumstances. However, the following query may be used to manually release the lock if necessary: {2}"
em_errors_18 = "You may want to use the disableUserBasedSettingPermissions() method to disable this check and leave permissions up the the module's code."
em_errors_19 = "You don't have permission to save system settings! {0}"
em_errors_20 = "You don't have permission to save project settings! {0}"
em_errors_21 = "Cannot save the setting for prefix '{0}' and key '{1}' because the key is longer than the {2} byte limit."
em_errors_22 = "Cannot save the setting for prefix '{0}' and key '{1}' because the value is larger than the {2} byte limit."
em_errors_23 = "Unexpected number of affected rows ({0}) on External Module setting query: {1}"
em_errors_24 = "One or more module prefixes must be specified!"
em_errors_25 = "Unable to set the type of '{0}' to '{1}'! This should never happen, as it means unexpected/inconsistent values exist in the database."
em_errors_26 = "The setting key cannot be empty!"
em_errors_27 = "More than one ({0}) External Module setting exists for prefix '{1}', project ID '{2}', and key '{3}'! This should never happen!"
em_errors_28 = "The Project Id cannot be null!"
em_errors_29 = "An error occurred while running an External Module query: "
em_errors_30 = "See the server error log for more details."
em_errors_32 = "The '{0}' module threw the following exception when calling the hook method '{1}':"
em_errors_33 = "REDCap External Module Hook Exception - {0}"
em_errors_34 = "REDCap External Modules threw the following exception:"
em_errors_35 = "REDCap External Module Exception"
em_errors_36 = "<p>{0} return values were generated from hook {1} by the following external modules:</p>"
em_errors_37 = "<p>Only the last result from <b><u>{0}</u></b> will be used by REDCap. Consider disabling or refactoring the other external modules so this does not occur.</p>"
em_errors_38 = "REDCap External Module Results Warning"
em_errors_39 = "This module's maximum compatible PHP version is {0}, but you are currently running PHP {1}."
em_errors_41 = "This module's maximum compatible REDCap version is {0}, but you are currently running REDCap {1}."
em_errors_42 = "This module's minimum required REDCap version is {0}, but you are currently running REDCap {1}."
em_errors_43 = "COMPATIBILITY ERROR: This version of the module '{0}' is not compatible with your current version of PHP and/or REDCap, so cannot be installed on your REDCap server at this time. Details:"
em_errors_44 = "Cannot create module instance, since the module with the following prefix is not enabled: {0}"
em_errors_45 = "The '{0}' module MUST specify a 'namespace' in it's config.json file."
em_errors_46 = "Could not find the module class file '{0}' for the module with prefix '{1}'."
em_errors_47 = "The file '{0}.php' must define the '{1}' class for the '{2}' module."
em_errors_48 = "Unexpected key: {0}"
em_errors_49 = "Unsupported resource added: {0}"
em_errors_50 = "You must specify a prefix!"
em_errors_51 = "An error occurred while parsing a configuration file! The following file is likely not valid JSON: {0}"
em_errors_52 = "The EDoc ID specified is not valid: {0}"
em_errors_54 = "You must specify a module to delete!"
em_errors_55 = "Cron job '{0}' failed for External Module '{1}'."
em_errors_56 = "External Module Exception in Cron Job"
em_errors_57 = "The following action has been throttled because it is only allowed to happen {0} times within {1} seconds, but it happened {2} times: {3}"
em_errors_58 = "The framework version must be specified as an integer (not a string) for the {0} module."
em_errors_60 = "An integer was required but the following value was specified instead: {0}"
em_errors_61 = "The '{0}' module defines the '{1}' setting multiple times!"
em_errors_62 = "The '{0}' module has a setting named '{1}' that contains invalid characters. Only lowercase characters, numbers, and dashes are allowed."
em_errors_65 = "You must supply the following either as a GET parameter or as the last argument to this method: {0}"
em_errors_69 = "The following method does not exist: {0}"
em_errors_70 = "Initializing the framework requires a module instance."
em_errors_71 = "A username was not specified and could not be automatically detected."
em_errors_72 = "You don't have permission to manage external modules on this project."
em_errors_73 = "Our apologies, but your web browser is not compatible with the External Modules Manager page. We recommend using another browser (e.g., Chrome, Firefox) or else upgrade your current browser to a more recent version. Thanks!"
em_errors_74 = "ERROR: Web browser not compatible"
em_errors_75 = "An error occurred while converting the configurations to JSON: {0}"
em_errors_76 = "An error occurred while converting the versions to JSON: {0}"
em_errors_77 = "An exception was thrown when generating links"
em_errors_79 = "EDoc {0} was not found on project {1}!"
em_errors_80 = "You do not have permission to save system settings!"
em_errors_81 = "You must specify a module to disable"
em_errors_82 = "The module named '{0}' is missing a description. Fill in the config.json to ENABLE it."
em_errors_83 = "The module named '{0}' is missing its authors. Fill in the config.json to ENABLE it."
em_errors_84 = "The module named '{0}' needs at least one email inside the authors portion of the configuration. Please fill an email for at least one author in the config.json."
em_errors_85 = "The module named '{0}' is missing an institution for at least one of it's authors in the config.json file."
em_errors_86 = "Exception while enabling module: {0}"
em_errors_87 = "You do not have permission to save the following project setting: {0}."
em_errors_88 = "You could not save a file properly."
em_errors_89 = "You could not find a file."
em_errors_90 = "Unable to parse module settings!"
em_errors_91 = "The email address entered for the following field is not valid:"
em_errors_92 = "Dates must be specified in MM/DD/YYYY format. The following value is not a valid date:"
em_errors_93 = "An error occurred while loading the project list!"
em_errors_94 = "The file was not able to be deleted."
em_errors_95 = "One or more of the files could not be saved."
em_errors_96 = "An error occurred while saving settings:"
em_errors_97 = "Error cleaning {0}"
em_errors_98 = "You do not have permission to get or set rich text files."
em_errors_99 = "Cron job attributes 'cron_frequency' and 'cron_max_run_time' must be numeric and greater than zero --OR-- attributes 'cron_hour' and 'cron_minute' must be numeric and valid."
em_errors_100 = "External Module Long-Running Cron"
em_errors_101 = "The '{0}' cron job is being skipped for the '{1}' module because a previous cron for this module did not complete. Please make sure this module's configuration is correct for every project, and that it should not cause crons to run past their next start time. The previous process id was {2}. If that process is no longer running, it was likely killed, and can be manually marked as complete by running the following URL:<br><br><a href='{3}'>{4}</a><br><br>In addition, if several crons run at the same time, please consider rescheduling some of them via the <a href='{5}'>{6}</a>."
em_errors_102 = "Some cron job attributes in the module's config file are not correct or are missing (cron_frequency/cron_max_run_time or hour/minute)."
em_errors_103 = "The specified root ({0}) does not exist as either an absolute path or a relative path to the module directory."
em_errors_104 = "The parent directory ({0}) does not exist. Please create it before calling getSafePath() since the realpath() function only works on directories that exist."
em_errors_105 = "You referenced a path ({0}) that is outside of your allowed parent directory ({1})."
em_errors_107 = "REDCap External Module Deadlocked Query"
em_errors_108 = "Query execution failed"
em_errors_109 = "The following query parameter type is not supported:"
em_errors_110 = "Binding query parameters failed"
em_errors_112 = "Your external module activation request has been sent to a REDCap administrator for review. You will hear back from them via email once the module has been enabled for this project."
em_errors_114 = "The error from the database was: "
em_errors_115 = "The following log parameter name is not valid (see the documentation for allowed characters): {0}"
em_errors_116 = "Empty log parameter names are not allowed."
em_errors_117 = "An array of parameters is required as the second argument to the query method to encourage use of prepared statements. If no parameters are needed, an empty array must be specified to show that the use of a parameters was considered."
em_errors_118 = "Could not find module ID for prefix '{0}'!"
em_errors_119 = "Cannot find directory prefix!"
em_errors_120 = "You must be a REDCap SuperUser to execute this command!"
em_errors_121 = "Direct access to this file is not allowed!"
em_errors_122 = "This feature is not allowed in your module's framework version."
em_errors_123 = "A module prefix must be specified as a query parameter!"
em_errors_124 = "The module with prefix '{0}' is currently disabled systemwide."
em_errors_125 = "The NOAUTH parameter is not allowed on this page."
em_errors_126 = "The '{0}' module is not currently enabled on project {1}."
em_errors_127 = "The specified page does not exist for this module."
em_errors_128 = "You do not have permission to access this page."
em_errors_129 = "You do not have permission to select project {0} for the '{1}' setting because you do not have design rights on that project."
em_errors_130 = "External Module Framework version {0} does not exist in your REDCap version. You must upgrade REDCap before using this version of this module."
em_errors_131 = "Invalid value for project id!"
em_errors_132 = "You must specify at least one key field name to uniquely identify instances."
em_errors_133 = "The specified key fields must all be on the same repeating form!"
em_errors_134 = "Every instance must specify a value for the '{0}' field."
em_errors_135 = "Multiple instances of the '{0}' form exist with the same key fields as the following instance: "
em_errors_136 = "The instance data should be an array containing sub-arrays for each instance, but a non-array child value was found."
em_errors_137 = "Expected all 'redcap_repeat_instrument' values to be blank or set to '{0}', but a value of '{1}' was found."
em_errors_138 = "The specified instances cannot be saved because more than one of them has the same key fields as the following instance: "
em_errors_139 = "The specfied key field '{0}' was not found on the project."
em_errors_140 = "WARNING: The 'key' for the above link was ignored. Please modify it in 'config.json' to only contain valid characters ([-A-Za-z0-9])."
em_errors_141 = "Link keys must be unique. The key '{0}' has already been used."
em_errors_142 = "The '{0}' field type is not yet supported for the '{1}' field."
em_errors_143 = "The following query spans multiple repeating instruments, which is not a valid use case of REDCap::getData(). The queryData() method could potentially support this, but was initially written to be fully compatible with REDCap::getData(): {0}"
em_errors_144 = "The '{0}' field does not exist on project '{1}'."
em_errors_145 = "SQL clause not allowed: {0}"
em_errors_146 = "Invalid LIMIT clause value: {0}"
em_errors_147 = "Only the 'json' return format is currently supported."
em_errors_148 = "The list of fields to return must be explicitly specified."
em_errors_149 = "Only a value of '{0}' is supported for the '{1}' argument."
em_errors_150 = "The record ID field was used in filter logic. The REDCap::getData() and $module->getData() implementations behave differently in this case, so it is not allowed. Pass in the record IDs using the $records parameter, or use REDCap::getData() or $module->queryData() instead."
em_errors_151 = "Queries must start with a 'select' statement:"
em_errors_152 = "SQL expression type '{0}' not allowed for the following expression: {1}"
em_errors_153 = "Only lowercase letters, numbers, and underscores are allowed in field names. The following field name contains invalid characters: {0}"
em_errors_154 = "The '{0}' module has been automatically disabled because its enabled version ('{1}', Repo ID '{2}') could not be automatically downloaded. This version may have been disabled in the Repo. See the following Exception for details: "
em_errors_155 = "The directory for version '{0}' of the '{1}' module could not be found."
em_errors_156 = "The 'redcap_csrf_token' parameter is required for all POST requests to pages defined by the module framework itself (as opposed to pages defined by modules)."
em_errors_158 = "The 'redcap_csrf_token' parameter specified does not match the expected value."
em_errors_159 = "The log message supplied is longer than the {0} byte limit."
em_errors_160 = "The log param name supplied is longer than the {0} byte limit."
em_errors_161 = "The log param value supplied is longer than the {0} byte limit."
em_errors_162 = "A project ID could not automatically be detected. You must manually include the 'project_id' column in the where clause to ensure that logs are not unintentionally removed for all projects."
em_errors_163 = "Temp file/dir creation is not allowed during shutdown."
em_errors_164 = "The module mentioned in the error below is preventing REDCap from working properly. It is recommended to disable this module until it can be updated to avoid this error"
em_errors_165 = "The request to retrieve the name for module {0} from the repo failed. This error is typically caused by a firewall preventing your server from accessing https://redcap.vumc.org. Please ensure that URL is accessible from your REDCap server, and returns the login page. On Linux, this can be tested via the 'curl' command. On Windows, this can be tested by accessing that URL in your browser. If more specific errors were returned, they will be shown here: {1}"
em_errors_166 = "Configuration item '{0}' in section '{1}' must be of type string in configuration file '{2}'."
em_errors_167 = "Configuration item '{0}' in section '{1}' is reserved. Please use a different name in configuration file '{2}'."
em_errors_168 = "Configuration section '{0}' must be an array in configuration file '{1}'."
em_errors_169 = "Module construction failed for '{0}' (version {1}). In case a custom constructor is used, it must include a call to the parent constructor ('parent::__construct();')."
em_errors_170 = "The '{0}' module contains an invalid character in its namespace in config.json."
em_errors_171 = "This action could not be completed because you are not currently logged in. Please make a copy of any unsaved changes, refresh the page, then try again."
em_errors_172 = "The following module's config.json should NOT contain a 'permissions' section for the specified 'framework-version': {0}"
em_errors_173 = "This module's minimum required config.json and/or composer platform PHP version is {0}, but you are currently running PHP {1}."
em_errors_174 = "The 'redcap_csrf_token' parameter is required for all browser initiated POSTs to module pages in this module's framework version. See the documentation for Framework Version 8 for more information, including how to handle custom API requests."
em_errors_175 = "The following query failed due to deadlock after multiple tries with a delay between each. To prevent future deadlocks, please consider refactoring any long running INSERT, UPDATE, or DELETE queries on this table. For example, using LIMIT to run DELETEs in smaller batches of 1000 or 100 can help significantly:"
em_errors_176 = "Action tag information could not be obtained from the server for unknown reasons. Please try again and/or reload the page."
em_errors_177 = "You do not have permission to list hooks."
em_errors_178 = "The {0} external module rejected this request with the following error: {1}"
em_errors_179 = "The specified URL is not an Amazon S3 URL: {0}."
em_errors_180 = "Both records and fields need to be specified in arrays."
em_errors_181 = "REDCap External Module Error"
em_errors_182 = "An error occurred in the '{0}' external module. Please view <a target='_blank' href='{1}'>the Recent Errors page</a> for details. Error emails will be disabled for this module for the next hour. Please review that page again one hour after this email was sent and consider any additional errors that occurred during that time for this module."
em_manage_1 = "External Module has updates available for download from the REDCap Repo."
em_manage_2 = "External Modules have updates available for download from the REDCap Repo."
em_manage_3 = "View Updates"
em_manage_4 = "Updates are available for the modules listed below. You may click the button(s) to upgrade them all at once or individually."
em_manage_5 = "Update All"
em_manage_6 = "The module was successfully downloaded to the REDCap server, and can now be enabled."
em_manage_7 = "The module and its corresponding directory were successfully deleted from the REDCap server."
em_manage_8 = "External Modules - Project Module Manager"
em_manage_9 = "Configure Module:"
em_manage_10 = "Settings"
em_manage_11 = "Values"
em_manage_12 = "Cancel"
em_manage_13 = "Save"
em_manage_14 = "External Modules - Module Manager"
em_manage_15 = "Set custom text for Project Module Manager page"
em_manage_16 = "You may optionally provide custom text in the text box below that will appear to users on the External Modules 'Project Module Manager' page in each project. It may be useful to provide some custom text to users for any of the following reasons: 1) To make users aware of institutional policies or procedures required before an administrator can enable a module, 2) To display guidelines (or a link to an external page with guidelines) regarding the usage of particular modules at your institution, or 3) To bring to the user's attention anything that might be helpful regarding particular modules or External Modules in general."
em_manage_17 = "<b>Custom text displayed on Project Module Manager page:</b>"
em_manage_18 = "NOTE: HTML may be used in order to adjust the style of the text or to display links, images, etc."
em_manage_19 = "Enable Module:"
em_manage_21 = "System Settings for All Projects"
em_manage_22 = "Enabled for All Projects"
em_manage_23 = "Discoverable"
em_manage_24 = "View Documentation"
em_manage_25 = "Set custom text for Project Module Manager (optional)"
em_manage_26 = "The custom text was successfully saved!"
em_manage_27 = "SUCCESS"
em_manage_28 = "Download external module?"
em_manage_29 = "Download"
em_manage_30 = "ERROR"
em_manage_35 = "Do you wish to download the External Module named <b>{0}</b>? This will create a new directory folder for the module on the REDCap web server."
em_manage_36 = "Disable module?"
em_manage_37 = "Are you sure you wish to disable this module ({0})?"
em_manage_38 = "Are you sure you wish to disable this module ({0}) for the current project?"
em_manage_39 = "Disable module"
em_manage_40 = "Search available modules"
em_manage_41 = "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 at the system level or project level."
em_manage_42 = "As a REDCap administrator, you may enable any module that has been installed in REDCap for this project. Some configuration settings might be required to be set, in which administrators or users in this project with Project Setup/Design privileges can modify the configuration of any module at any time after the module has first been enabled by an administrator. Note: Normal project users will not be able to enable or disable modules."
em_manage_44 = "You may click the 'View modules' button below to navigate to the REDCap Repo (Repository of External Modules), which is a centralized catalog of curated modules that have been submitted by various REDCap partner institutions. If you find a module in the repository that you wish to download, you will be able to install it, enable it, and then set any configuration settings (if applicable). If you choose not to enable the module in all REDCap projects by default, then you will need to navigate to the External Modules page on the left-hand menu of a given project to enable it there for that project. Some project-level configuration settings, depending on the module, may also need to set on the project page."
em_manage_45 = "<b>DISCLAIMER:</b> Please be aware that External Modules are not part of the REDCap software but instead are add-on packages that, in most cases, have been created by software developers at other REDCap institutions. Be aware that the entire risk as to the quality and performance of the module as it is used in your REDCap project is borne by you and your local REDCap administator. If you experience any issues with a module, your REDCap administrator should contact the author of that particular module."
em_manage_46 = "<b>NOTICE:</b> It has been detected that you have a development version of the External Module Framework installed at <code>{0}</code>. As such, please note that REDCap will use that version of the framework rather than the one bundled in this REDCap version."
em_manage_48 = "Enable a module"
em_manage_49 = "View available modules"
em_manage_50 = "View modules available in the REDCap Repo"
em_manage_51 = "Currently Enabled Modules"
em_manage_52 = "Modules Currently Available on this System"
em_manage_53 = "Search enabled modules"
em_manage_54 = "Configure"
em_manage_55 = "Disable"
em_manage_56 = "View Usage"
em_manage_58 = "Change Version"
em_manage_59 = "Enable"
em_manage_60 = "None ('name' is not specified in config.json for {0})"
em_manage_61 = "(Current version: {0})"
em_manage_62 = "(Not enabled)"
em_manage_64 = "Do you wish to delete the module {0} ({1})? Doing so will permanently remove the module's directory from the REDCap server."
em_manage_66 = "An error occurred because the External Module directory could not be found on the REDCap web server."
em_manage_67 = "An error occurred because the External Module directory could not be deleted from the REDCap web server."
em_manage_68 = "Close"
em_manage_69 = "An error occurred while enabling the module:"
em_manage_70 = "None"
em_manage_71 = "Enabling..."
em_manage_72 = "* must provide value"
em_manage_73 = "Delete File"
em_manage_74 = "Save and Upload"
em_manage_75 = "Error"
em_manage_76 = "SOME SETTINGS REQUIRE A VALUE! It appears that some settings are required but are missing a value. If you wish to go back and enter more values, click CANCEL. If you wish to save the current settings, click OK."
em_manage_77 = "None"
em_manage_78 = "Project Usage:"
em_tinymce_language = "en_US"
em_manage_79 = "The module was successfully updated and enabled."
em_manage_80 = "All {0} modules were successfully updated and enabled."
em_manage_81 = "SUCCESS + ERRORS"
em_manage_82 = "{0} modules were successfully updated and enabled, but {1} were not able to be updated for unknown reasons."
em_manage_83 = "Upload a file"
em_manage_84 = "Delete"
em_manage_85 = "Are you sure you want to permanently delete this file?"
em_manage_86 = "Configure Cron Start Times"
em_manage_87 = "Manager for Timed Crons"
em_manage_88 = "<b>Project:</b> {0}"
em_manage_89 = "An error occurred while requesting module activation:"
em_manage_90 = "An error occurred while activating the external module."
em_manage_91 = "Reset Cron Now (must be REDCap superuser)"
em_manage_92 = "Successfully reset the cron job."
em_manage_93 = "As a user with Project Setup/Design privileges in this project, you can modify the configuration (if applicable) of any enabled module. Note: Only REDCap administrators are able to enable or disable modules."
em_manage_94 = "Export"
em_manage_95 = "Please select the modules whose settings you would like to export. The export will include settings displayed in the <b>Configure</b> dialog, as well as settings used behind the scenes by the module (the same as the behavior when copying projects)."
em_manage_96 = "Exporting module settings..."
em_manage_97 = "You must select at least one module to export."
em_manage_98 = "Module Settings"
em_manage_99 = "Import"
em_manage_100 = "You must specify a file!"
em_manage_101 = "Settings were imported for the following modules:"
em_manage_102 = "Settings were not imported for the following modules because they are not currently enabled on this project:"
em_manage_103 = "The import reported the following warnings:"
em_manage_104 = "The following project dropdown settings were not imported for security reasons. They will need to be configured manually to ensure the correct values for this system/project:"
em_manage_105 = "The following settings were not imported because they may have security implications. A REDCap system administrator will need to manually configure them to ensure appropriate values for this system/project:"
em_manage_106 = "Settings were exported for the following modules:"
em_manage_107 = "The export reported the following warnings:"
em_manage_108 = "The following settings were not included in the export because they may have security implications:"
em_manage_109 = "I confirm that I intend to replace <b>ALL settings</b> on this project for modules included in the supplied export. I understand that for modules in the supplied export, any settings not also present in the export will be <b>removed permanently, including hidden settings</b> used behind the scene by each module. I understand that prior to clicking <b>Import</b> below, it is highly recommended to perform a settings export for all modules on this project, and save it as a backup. After the import completes, I agree to review the settings for and fully test affected modules to ensure that they are behaving as expected."
em_manage_110 = "Choose a module settings export zip file to import:"
em_manage_111 = "Importing module settings..."
em_manage_112 = "View Logs"
em_manage_113 = "External Module Logs"
em_manage_114 = "Manage"
em_manage_115 = "This page is primarily intended for External Module developers and advanced users. External Modules have a generic logging feature that can be used for anything a module author can imagine. Many modules benefit from a way to allow users to view these logs for troubleshooting purposes. This page is provided by REDCap so that separate log viewing pages don't have to be implemented in each individual module that uses logs."
em_manage_116 = "Delete Version"
em_manage_117 = "An error occurred while attempting to download the External Module:"
em_manage_118 = "Module Security Scanning"
em_manage_119 = "Developer Tools"
em_manage_120 = "This module uses the following hooks. See <a href='{0}' target='_blank'>REDCap's Developer Documentation</a> for details:"
em_manage_121 = "(this setting can be overridden on each project)"
em_manage_122 = "Start Date"
em_manage_123 = "End Date"
em_manage_124 = "Message Length Limit"
em_manage_125 = "Module(s)"
em_manage_126 = "Date/Time"
em_manage_127 = "Module"
em_manage_128 = "Project"
em_manage_129 = "Message"
em_manage_130 = "Available Modules"
em_manage_131 = "View action tags provided by external modules:"
em_manage_132 = "This module directory was removed from the filesystem without first disabling the module. If this module is still desired, the directory will need to be restored in order for it to function. If it is not desired, please disable it."
em_manage_133 = "Parameter Length Limit"
em_manage_134 = "Actions"
em_manage_135 = "Validate & Format JSON"
em_manage_136 = "Delete Versions"
em_manage_137 = "Select the versions of the module {0} that you wish to delete. Note that doing so will permanently remove the module's directories from the REDCap server. {1}"
em_manage_138 = "You must select at least one version to delete."
em_manage_139 = "The following versions of the module have been deleted successfully: {0}"
em_manage_140 = "The following versions of the module could not be found on the REDCap web server: {0}"
em_manage_141 = "The following versions of the module could not be deleted from the REDCap web server: {0}"
em_manage_142 = "Select all versions"
em_manage_143 = "An unexpected error occurred."
em_manage_144 = "For details, see the console via your browser's Developer Tools."
em_manage_145 = "Here are the details:"
em_manage_146 = "Too many results were found. Please try a smaller date/time range."
em_manage_147 = "Record"
em_manage_148 = "UserName"
— OR —

2.) Select an existing language file to update for this version of REDCap

REDCap streamlines the process of updating your language files by automatically merging them with the newest English text and rendering them out for you in merged fashion. Simply click the buttons below to have your existing translated text merged with the newest English text for any given language file. Then you will simply need to translate only the English portion of the file and replace that language file on your web server.

No language files were found!