Edit Sources
This section explains how to modify metadata and temporality parameters for each source, and how to add scripts and schedules for processing the source data.
On the Sources page, click on the icon on the source that you want to configure.
The Edit Source dialog that opens contains a number of tabs that allow you to modify different parameters for the source and to add scripts and schedules. To save the changes, click on Save. To close the dialog without saving, click on Cancel.
Source Tab
The Source tab has two sections: Metadata and Load type.
Metadata
The Metadata section allows you to configure the source name in Yotilla (Name) and the associated name of the source table (Location) in the source system schema on the target system.
Load type
In the Load type section you define whether the source data is provided via a full load or a delta load.
If the source provides flags that identify deleted records you must define these flags in the Delete Detection Tab tab.
Temporality Tab
In the Temporality tab you can configure how different timelines are processed. For more details about timelines, see Temporality.
Inscription time
In the Inscription time section you can set the source attribute that defines the inscription time in the source. If there is no inscription time in the source, leave this option at None.
The datatype of the inscription time source attribute must be a timestamp.
External stage load time
The External stage load time section is relevant when the source can contain more than one extract by the time the loading process starts. This is needed to identify each extract and to process them in the right order. If the source will not contain more than one extract at any given time, leave this option at None.
The datatype of the external stage load time must be a timestamp.
Initial load
The Initial load section covers the configuration when loading data for the first time.
The option Use external stage load time as load time will use the external stage load time as the technical load time of the data warehouse, but only for the initial load. This source data might come from a persistent staging area of an existing data warehouse that contains multiple extracts. Enabling this option allows you to reuse the technical load time to keep the technical temporal reference. This is relevant if the technical load timeline is the main temporal reference for analysis.
The Initial load option requires that an external stage load time is set.
The options Use custom value for the first load time slice and Use custom value for the first inscription time slice allow you to set a defined timestamp for the first time slices of the first load. This is useful in case the timelines of your business objects start in different points in time, resulting in gaps at beginning when joining the timelines of the sources. A common and unified starting point across the timelines of the sources would ensure that there are no gaps and that data can be combined.
Delete Detection Tab
The Delete Detection tab is an additional configuration for the delta load type in the Source Tab tab.
With the Delete Flag option you can select a boolean attribute in the source table that indicates a deleted record in your delta load. This ensures that deletions detected in the source are represented correctly in the data warehouse.
Scripts Tab
The Scripts tab allows you to define SQL scripts that are run before Yotilla loads data from the source on the target system (pre scripts), and/or after the load process has finished (post scripts). Each script section can contain one or more SQL statements.
A pre script could for example include an import statement to load data from an external source system to the target database or prepare data for ingestion, while a post script could cover the clean up steps of said data preparation.
Schedule Tab
The Schedule tab allows you to configure when and how often the source will be loaded into the data warehouse. Each schedule can be enabled or disabled separately. You can define different schedules for the Development and Production environments. Schedules are defined using cron syntax.
For an explanation of the cron syntax, see cron (Wikipedia article).