[record_id] < 1020" . "Values for this property should use the standard REDCap syntax for logic. This value" . " is passed to REDCap, and REDCap-ETL relies on REDCap to check this value for errors." - . " Unfortunately, error checking for filter logic in REDCap is extremenly limited, and" + . " Unfortunately, error checking for filter logic in REDCap is extremely limited, and" . " in most cases where there is an error, REDCap will not generate an error message" . " and simply return no records." . "" @@ -223,17 +223,18 @@ class Help . " (e.g., value 0 for label \"no\")." . " Originally, REDCap-ETL stored only the multiple choice values in the" . " database tables it generated." - . " Corresponding views were also created that contained" - . " the labels for the multile choice questions." + . " Corresponding views are also created that contain" + . " the labels for the multiple choice questions." . " The name of the view is the same as the" - . " name of the table with \"label view suffix\" appended to it." + . " name of its corresponding table with the \"label view suffix\" appended to it." . "" . "
" - . " Now, both value and label fields are generated for tables created by REDCap-ETL." + . " Now, both value and label fields are generated for database tables created by REDCap-ETL." . " The value is stored in the field name specified by the user, and the label is" . " stored in the same field name with the \"label field suffix\" appended to it." + . " If the \"label field suffix\" is left blank, no label fields will be generated." . " The label views have been deprecated and turned off by default for new projects," - . " and the plan is to remove them in the future." + . " and the plan is to remove label views in the future." . "
" . "" . "This page allows you to run an ETL configuration or ETL workflow" - . " that you have previsouly created." + . " that you have previously created." . "
" . "" . "Steps:"