Page History
...
Run Transform | CDE Match transforms the Source input into one row per column and permissible value. The command to transform the Source input details is "opt"+"cmd"+"t". |
---|---|
See Instructions | Please see the CDE Match Instructions document attached to this page. |
Special Features | CDE Match has a command "Run DEC Match". This will run the match algorithm on the imported files using just the CDE names, ignoring the permissible values. Click the "Matched DEC" node to see results. |
Tips for DEC
...
Import and Update
Validating Lots of Rows | Sometimes, the system throws an error when attempting to validate more than 4 rows at a time. If that happens, try validating a few rows at a time. |
---|---|
DEC Import Required Fields | DEC Context, OC Concepts, Property Concepts and DEC CD Name/ID are required. |
DEC Update Required Fields | The DEC Public ID and Version are required for an Update. Any other columns that are populated will be treated as a change to teh existing DEC, such as DEC CD, OC Concepts, Property Concepts and Context. |
Tips for DEC Match
Description | DEC match will run matching algorithms on the names in the template and display results in the "Matched DEC" node. You can select one of the DECs as "Preferred" and then download the results using the Delivery Options feature. |
---|---|
Context Column | In the Context column, you can enter one or more contexts to search for matching DECs. Separate each DEC with a comma. Do not use spaces between DECs. For example: XXX,CTEP,CCR |
...
After Importing | The results after importing are displayed one row per Value Meaning. All VM Match user results are kept in one database table, and without filtering results, they are all displayed in the same grid. So, after selecting "Go to Data Manager" enter your batch name and click "Apply Filter" to see just your results. |
---|---|
"User Tips" Column | The User Tips column is used by the system instead of the VM Name. Sometimes the VM Name from your form or data is not very representative of the its meaning, or consists of too many terms. If a "User Tip" is entered it is used instead of the VM Name. User Tips can be entered through the front end, or starting in Sprint 47, can be entered into the Template for each row and imported. |
Algorithm | Punctuation and spaces are removed. The "Rule Description" explains why each match was selected. The algorithm does not currently account for spelling errors. |
"Run Match" Command | Select the rows to run the match algorithm against and select the "RUN MATCH" Command. Punctuation and spaces are removed. This command will try to find Exact or Like Matches using the VM preferred name for existing VMs, Concept Preferred name and Synonyms. Click "VM Matched Results" to review recommended matches. If you do not find a desired match, select "Run VM Match Unrestricted". |
"Run VM Match Unrestricted" Command | This match searches on the longest term in addition to more extensive matches. |
"VM Matched Results " | If there is only one exact match, the system will automatically associate the matched result with the imported VM Name. If there are multiple matches the user can select a row from "VM Matched Results" and select the "Set Preferred" command. Multiple Concepts can be selected one at a time to post coordinate concepts. The system will appended the concept to the preferred concept string and generate the resulting name in the order the concepts are selected. This can be viewed by selecting the Node with the Concept Name to view the selected items. The concepts and be reordered manually, but be sure to reorder the concept names, or clear the results, "Save" and then select concepts again from the matched results. |
Advancing through the imported VMs | When on the "VM Match Header" you can advance to the next VM in your imported file by using the "Rows x of xxx" arrows. |
Column Order | The main column in VM Match is the VM Name. The processing is designed to find matching concepts based on the name and insert the Concept Name and Concept Code into the table next to the VM NAME unless "User Tips" are entered. This order of the columns makes it easier to populate the PV/VM Template using cut and paste. |
Exporting results | Use the "Delivery Options" command to export the VM Match results into and Excel file. This simplifies creating the list of PV/VMs for PV/VM Import to populate and existing Value Domain. |
Tips for Form Imports
Import from REDCap Data Dictionary Format | The Form Import Template is an xslm filetype and contains several Excel Macros, so please be sure to select "Enable Macros" when opening the template. This has been tested for use only on a Windows PC platform, not Mac laptops.
| ||||||||||||
Running the Macros | There are 3 macros in the Excel Template. The Macro run key sequence can be viewed by selecting "Tools" from the Excel menu bar, then "Macro".
| ||||||||||||
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. Paste content into the template starting in the 3rd row. Please see the template for the mappings between the REDCap Data Dictionary column names and the caDSR form column names. | ||||||||||||
Form Context | REDCap does not have a column for Context. Context for all the forms in the templates is selected after importing the template into caDSR. |
...