Managing multiple datasources

Data merges can be completed by different methods when a study has multiple attached datasources. Standard Oracle Site Select columns have predefined data merging while customer datasource managers define data merging for custom columns. Additionally, when a study has multiple datasources, datasource managers can define datasource priority.

Merging data

Oracle Site Select provides the ability to define how data is merged when multiple customer datasources are attached to a study. For standard Oracle Site Select data columns, Oracle defines how each column will handle data merges. For custom data columns, customer datasource managers will define the method by which data is merged for a particular column. Available merge methods for custom columns are:

concatenate data (string array)
highest priority datasource wins (all data types)
sum data (integer, real)
average (integer, real)

Note:

Please contact your Oracle Project Manager to coordinate custom column merging methods prior to data load.

Custom column example

A custom column “Equipment list” is defined at the site level in two customer datasources as a string array. In datasource 1, it includes “fMRI” and “portable X-ray.” In datasource 2, it includes only “portable infusion pump” for the same site record. When both datasources are attached to a single study, and the column is defined to concatenate array values, the resulting site record will include “fMRI, portable X-ray, and portable infusion pump” for the data column “Equipment list.”

Datasource priority

Datasource managers can adjust the priority of the study's site profile datasource. The datasource itself corresponds to the account or study level site profile datasource attached to the study.

On the Choose data sources for <study name> page, a Datasource manager can move the site profile datasource up or down in priority against other chosen study datasources. Priority (i.e., higher or lower in the list of the study's attached datasources) determines the data displayed in the site grid. For example, study site "Joshua Johnston" (no "e") exists in the Site Profile datasource, and "Joshua Johnstone" (with "e") exists in another datasource titled Preferred Sites. The site grid displays the name "Joshua Johnston" (no "e) when the Site Profile datasource is prioritized above the Preferred Sites datasource. If the Site Profile datasource is reprioritized lower than the Preferred Sites datasource, the site grid displays "Joshua Johnstone" (with "e").

After the Datasource manager saves the updated priority order, the site grid updates immediately to show the appropriate data. Site grid exports and Oracle Site Select reporting views also reflect the data displayed in the site grid after the priority order update.

Please note: When the study's attached Site Profile datasource has a lower priority than other attached datasources, the site profile could display information that does not match the site grid (e.g., the site name could be different). This is expected behavior.

Parent topic: Import and Manage Data