Automatically Generate Transformations Based on a Table Name Pattern Using Dynamic Mapping Templates

This article is currently being updated. Please come back later for updates.

Objective: Automatically merge all data tables that begin with the name "LAB", e.g. LAB_CHEM, LAB_HEME, LAB_PG, LAB_UM, LAB_COAG, etc. as new data are imported across the entire clinical trial portfolio using Dynamic Mapping Templates.

Important: This tutorial assumes the user is already familiar with Mapper, how to create mappings and mapping domains, and the general functionality of Mapper.

Permissions: Requires the Mapper and Advanced Mapper privileges.

Instructions

  1. To begin, open the Platform menu and under Data Mapping & Computing select Dynamic Mapping Templates.
  2. To create a new Dynamic Mapping Template, click the plus icon in the Master Header.
  3. When the Create Dynamic Mapping Template window opens, enter the following details (items in parentheses are the use case entries and selections): 
    • Template Name (required) - name of the template. [LBUnion]
    • Template Description - description of what the template is designed to do. [Builds a union of all lab datasets]
    • Transformation (required) - the type of transformation. [Union]
    • Source Table(s) (required) - the source table being renamed or source tables being merged. This field is case insensitive. [LAB*]

      Tip: Unions support wildcards * any characters, ? specific character.

    • Target Mapping (required for Auto Create) - name of the mapping the domain should be created within, will be created if Auto Create is checked. [DMTLB]
    • Target Datastore (required for Auto Create) - name of the datastore that should be used if the mapping doesn't exist and Auto Create is checked. [Reporting]
    • Auto Create - check if the template should create the mapping and domain if it doesn't already exist. [checked]
    • Target Domain (required) - the name of the domain being created. [LB_ALL]
    • Target Domain Label - the label for the domain being created. [All lab datasets]
    • Active - check if the template should automatically execute when data are ingested that match the selected scope. [checked]

      Note: Alternatively, Dynamic Mapping Templates can be executed manually from within Mapper if desired.

    • Domain Tags - any tags that should be associated with the domain. [n/a]
    • Exclude Variables - any variables that should not be included in the domain created by the template. [blank]
    • Always Add Variables - any variables that should always be added to the domain created by the template, null values will be added to any variables where data do not exist. [blank]
    • Check one of the following, (required for Union):
      • Include All Variables - include any variables even if they are not in all the sources being merged. [checked]
      • Include Matching Variables - only include variables that are present in all the sources being merged. [unchecked]
    • Append Source Identifier - adds a FORMOID source column. [unchecked]
    • Scope: (required)
      • Choose the TA, Programs, Compounds, Studies, and/or Global Data Stores for which the Dynamic Mapping Template should apply. [All Studies]
      • Choose the Input Data Stores that should trigger the model for the selected scope. [Clinical]
  4.  To finalize the template, click Save.
  5. The Dynamic Mapping Template will be triggered and create the target domain upon a data import that matches the selected scope.

    Note: Domains created by the Dynamic Mapping Template will be indicated with a lightning bolt symbol to the right of the name in Mapper.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request