All templates require a BATCH USER, BATCH NAME, and SEQ ID on each row.

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".

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".

New concepts are automatically loaded once a month when EVS publishes the monthly NCI Thesaurus file on their FTP site. If new concepts have been created for your content before they are published in the NCI Thesaurus, please contact the NCI Registration Authority at caDSR.RA@mail.nih.gov for assistance. The NCI Curation Team can import concepts directly into caDSR for their use before they are published in the NCI Thesaurus.

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. The QA process tests only on a Windows PC platform, not Mac laptops, however team testing using Mac laptops have not reported issues.

1. Paste your form content into the template starting on Row 3, column E. At a minimum you must run the Macro "Standardize", see instructions below.
2. If importing a PhenX REDCap Data Dictionary, you must run "Standardize", then "PhenxStandarize".
3. "CombineZip" is optional, it automates copying form content into the template from one or more REDCap dictionary csv files. See instructions below. 
4. Enter a Batch User, Batch Name and ensure that each row has a unique "Seq Id"
5. Save the Form Template file as csv.
6. Run Form Import from Manage>>Manage Data (or your bookmarked Favorites)
7. Select "Import" from the toolbar, then "Conceptual Data Object" from the drop-down
8. Select the checkbox next to "Form Import RedCAP v1" and select "Import" option from the toolbar (Between "Add New Mapping" and "Go To Data Manager")
9. Select the "Choose File" and select the Form Import Template from our desktop that you have prepared for loading
10. Change the last row in the table "Start at Row" from 2 → 3
11. Select "Import" at the bottom of the Table
12. After "Success" message, Select "Go to Data Manager" or Manage>>Manage Data>> Form Import (or from your bookmarked Favorites)
13. Use the filter to search for your form, Click "Apply Filter"
14. Select "Edit" for your form
15. Select a "Context" from the dropdown
16. Save
17. Select "Parse Form"
18. If successful, select "Validate Form"
19. Review the results
20. After successful Validate, Select "Create Form"
21. Copy the Public Id and choose "Forms" from Manage>>Manage Data (or your bookmarked Favorites) to view the newly created form in caDSR

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". 

You can update the following attributes for Administered Items Value Meaning, Data Element Concept, Data Element, and Value Domain via the Definitions Import template:

• Preferred Definitions
• Alternate Definitions

TBD

TBD

TBD

CDE Match transforms the Source input into one row per column, permissible value and optionally permissible value meaning depending on the format of the data on the Source tab and which Excel Macro is used. There are 3 Excel Macros for 3 different input formats: TransformInput (shortcut: "opt"+"cmd"+"t"), TransformInput_REDCap (shortcut: "opt"+"cmd"+"r"), and WordDocumentFormat. 

To access the macros from the Excel tool bar select "Tools>>Macro>>Macros". Make sure the "Macros In" option is set to "This Workbook". Select the Macro that matches the format pasted into the Source tab. 

To access examples of the three source formats download the "CDE Match_Source Input Examples" spreadsheet attached to this page.

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

The results after importing templates are stored in one table for all imported files. After the "success message" select "Go to Data Manager", or if on the main page select "VM/Concept Match" again. The system will display a filter where users can enter their batch user name and/or batch name, then click "Apply Filter" to see just your results. 

To see the details for the matches for each row in the input template, select "Edit" next to the rows and then select "VM Matched Results".

There are several commands available because the feature can be used to match text strings entered into the template to:

1. Existing caDSR Value Meanings (VM). caDSR VMs are already associated with Concepts
2. EVS Concepts from NCI Thesaurus or selected external terminologies

By selecting the appropriate command, the user can control the breadth of the matching algorithm.

Terms in the input template can be any text, the Permissible Value, the Permissible Value label, or the name of a variable/data element. 

The User Tips column is used by the system instead of the user supplied name. Sometimes the string 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 imported name. User Tips can be entered through the front end or entered into the Template for each row and imported. 

The system indicates how many matches were found, why each row was considered a match, and the type of match that was run. Once a match is selected, it is displayed in the table of summary results by row.

Punctuation and spaces are removed. The "Rule Description" explains why each match was selected. The algorithm does not currently account for spelling errors.

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 caDSR Value Meaning (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".

This match searches only for existing VM names that are good matches to either the name of synonyms. It includes exact matches to the name or alternate VM names.

This match does not stop after finding exact matches. It extends the search to emphasize matches on the longest term in addition to "like" matches. 

This match searches only for Concepts by name and synonyms.

This match searches only for Concepts by name and synonyms the longest term in addition to more extensive matches. 

This matches allows the user to select a specific terminology to search for Concepts by name, synonyms or Concept Code.

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. 

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. 

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.