Introduction to Mapper
Mapper is one of elluminate’s options for transforming imported data into new tables / domains and delivering it to a target data store. Mapper provides a graphical interface where users can perform complex transformations in a low-code environment, while the platform generates T-SQL.
Why Use Mapper:
- Assists with transforming imported data to CDISC standards (e.g., SDTM or ADaM), custom standards, or listings, ensuring downstream reports and analytics.
- Links to Standards / Specifications, offering auto-complete field names, labels, and code lists to reduce errors.
- Reuses work across studies by exporting or promoting mapped domains to the Global Library for import elsewhere in elluminate.
-
Tracks versions, execution history, and data dependencies so transformations remain transparent and reproducible.
Mapper provides a Domain Editor that displays source tables, transformation layers, and previews of data or SQL. There are property panels for domain and variable settings as well as management tools for importing, exporting, migrating, and scheduling mappings.
Key Features Include:
- Dynamic Unions: Combine multiple tables that follow a naming pattern into a single domain without requiring manual unions.
- SQL Tokens: Replace hard-coded schema prefixes to make code portable across studies and environments.
- Skip Missing / Cascade Changes: This option allows mappings to run even when variables or domains are absent and propagates edits through parent layers when desired.
- Global Library Integration: Promotes mapped domains to the Global Library for cross-study reuse governed by user privileges.
Access Mapper
- From the Platform Menu, select Mapper from Data Mapping & Computing.
-
From the right side of the Platform menu, select the study. The Mapper window opens.
Note: If using Global Data Stores for your mapping, select it from the center of the Platform menu, choose the study, and then select Mapper from the product drop-down, which defaults to Details.
The top half of the screen displays any existing mappings. A mapping is a set of domains or tables that are created based on the source domains / data that have been imported into the study.
The bottom half of the screen lists the corresponding domains after you have selected a mapping from the top half.
Domain Transformation Options
| OPTION | DESCRIPTION | |
|---|---|---|
| Variable Rules | General | Define exclusions, renaming, converting types, or deriving variables |
| Filtering | Set filter rules to specify what data gets mapped | |
| Sorting | Set a sort order for mapped data | |
| Pivot / Unpivot | Choose rows and columns to create a pivot table | |
| Aggregate / Rank | Create summary information fields. Add First, Last, Previous or Next value to a record. | |
| Domain Rules | Join | Define a join to map data from multiple tables. Creates a new table with columns from both the original tables. |
| Union | Merge data from two tables. Will only work if the number and structure of the tables is the same. | |
| Dynamic Union | Merge fields from multiple tables in a single transformation based on criteria you specify. | |
| Intersect | Merge the data from two tables with the same basic structure. Results will only include records that existed in BOTH tables. | |
| Subtract | Compare the data in two tables, shows records that are in the second table, but not in the first. This could be used if comparing all data to reviewed data. The result will be only unreviewed data. | |
Tip: Mapping rules can be exported so that they can be re-used in other studies, as long as the data structures match.