 |
Page History
...
| Use Data Validation | Always start with a fresh Template with Data Validation to help avoid uncaught errors due to invalid manually entered data. We have added a lot more error handling in this release, but it's not perfect yet, in particular when invalid or retired concepts are used. |
|---|---|
| Required Columns | All templates require a BATCH USER, BATCH NAME, and SEQ ID on each row. |
| Delete/Purge | When reimporting, it is safest to select all the rows and "Delete", then select "Purge", then select all rows and “Purge Records". For Forms, select "Delete Hierarchies", then select "Purge", then select the rows and "Purge Hierarchies". |
| Unique Column Names | You may add additional columns to the template for taking/keeping notes after the last template column, but the column names must be unique. |
| Invalid or Retired Concepts | Invalid VM Concepts on import are not saved in the system and can create a GAP in the concept drop down. If the invalid or missing concepts are found, the system will display and error. Curators should fix all Concept Errors reported on Import BEFORE Validating. |
| Concept Formatting | Concept String should not contain commas, tabs, or or other hidden characters. Always "Paste Values" in order to avoid issues. |
| CSV Files!! | Template must be saved as CSV for importing. Other file types will cause an error. |
| Seq ID Rules | Seq ID must be an a unique integer. |
| Import Exceptions | Missing Batch User, Batch Name, or Seq ID will cause Exception. |
| Selecting the "Import" Command | For imports and matching, select the type of import/match item from the "Favorites" list, then select the "Import" command. For most imports there will be a dropdown with either one or two of the following choices: "Conceptual Object Import" and "Data Object Import". For most imports choose the first choice in the list. For VM Match both choices are presented, choose the second one, "Data Object Import". |
| Exception on SEQ/Except Row Number | Multiple missing required fields may not report the correct row number in the Exception Message. Inspect the template for empty cells. |
| Save / Revalidate | If making changes through front-end, Save and Revalidate. This will refresh the messages. |
...
| Column Order | VM Match is designed to find matching concepts and insert the Concept Name and Code into the grid. You can use Delivery Options to export the results and cut and past the contents of these columns into the PV/VM Import to simplify creating the list of PV/VMs to import into a Value Domain. |
|---|
Tips for Form Imports
| Import from REDCap Data Dictionary Format | Form import uses a csv file format which is one row per Question. The template contains an Excel Macro so when opening the template to paste your content into, select "Enable Macros". |
| Running the Macro | Choose "Shift" + "CMD" + "t" |
| Filling the template with form data | The 1st row of headings are the REDCap DD headings. The 2nd row of headings match caDSR headings. Enter a short name in the Variable / Field Name, this can be used for matching to an existing CDE. In future release it will be added as a Question Short Name. |
| Form Context | REDCap does not have a column for Context. In Sprint 41 Context for the form is selected after importing the template into caDSR. |
Tips for Designation Imports
...
