 |
Page History
Some of the features in caDSR II allow you to process content from a CSV file for bulk/batch importing to create new content. To view or use these features, log in as described in Logging In. These features need specially formatted templates that are attached to this wiki page.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
|
...
| 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 Context, DEC Public ID and Version are required for an Update. Any other columns that are populated will be treated as a change to teh the 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 |
Tips for VD Imports
None at this time.
Tips for PV VM Imports
| Import into Existing VD | The PV VM import is designed to import an enumeration into an existing Value Domain. PV/VMs can be created using existing VMs, or you can specify a new VM either with or without concept codes. |
|---|---|
| Specified VM Definition | Optional Specified VM Definition is only used if the VM Type is "TEXT". The system will not throw an error but it won't be added to the VM. |
| Possible Timeout | Validate/Create will timeout if more than 5 minutes. Try batches of 100 until we can redesign the code. Watch. |
| VM Reuse | In a Text VM is specified and an existing VM with the exact name is found, it will be reused, even if it has concepts. The Validation message will indicate that existing VM is being used (need to fix spacing). |
Tips for VM Match
| . Retired DECs cannot be updated. DEC WFS will be set to "DRAFT NEW". | |
| Known Issue | In release 1.53.4, if a duplicate DEC exists in another Context, you cannot bulk update the DEC. This will be fixed in future release. |
|---|
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 |
Tips for VD Imports
None at this time.
Tips for PV VM Imports
| Import into Existing VD | The PV VM import is designed to import an enumeration into an existing Value Domain. PV/VMs can be created using existing VMs, or you can specify a new VM either with or without concept codes. |
|---|---|
| Specified VM Definition | Optional Specified VM Definition is only used if the VM Type is "TEXT". The system will not throw an error but it won't be added to the VM. |
| Possible Timeout | Validate/Create will timeout if more than 5 minutes. Try batches of 100 until we can redesign the code. Watch. |
| VM Reuse | In a Text VM is specified and an existing VM with the exact name is found, it will be reused, even if it has concepts. The Validation message will indicate that existing VM is being used (need to fix spacing). |
Tips for VM and Concept Match
| After Importing | The results after importing are displayed one row per entry in the template. All 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" or select "VM Match" again and filter for your batch name, then click "Apply Filter" to see just your results. To see the details of each row of matches, select "Edit" and select "VM Matched Results". |
|---|---|
| Use Cases | This feature can be used to match text strings entered into the template to:
By selecting the appropriate command, end user can control the breadth of the matching algorithm. Terms can be the Permissible Value if the value is text, or the name a variable. |
| "User Tips" Column | 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. |
| Matched Results | 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. |
| 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" VM Header 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 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". |
"Run Match - VM Only" VM Header Command | 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. |
"Run VM - Match Unrestricted" VM Header Command | 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. |
"Run Match - Concepts Only" VM Header Command | This match searches only for Concepts by name and synonyms. |
"Run Match Concepts Only - Unrestricted" VM Header Command | This match searches only for Concepts by name and synonyms |
| 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. |
"Run Match - Terminology" | This matches allows the user to select a specific terminology to search for Concepts by name, synonyms or Concept Code. |
| "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. |
...
