Skip to content
  • There are no suggestions because the search field is empty.

Working with Sources and Targets

Source and Targets are how Zengines organizes the schemas (and their data) in migration projects. For data to be migrated it must belong to a Source and have a schema defined for it.

Defining Sources and Targets

  • Sources and Targets contain the schema, related meta data, and associated data, they are defined by either:
    • Creating using a schema definition file which can contain multiple tables and should contain column data type definitions, as well and other constraints and metadata.
    • Using a data file that represents a single table, data types and other metadata is inferred in this case and should be reviewed before use.
  • Sources and targets can be duplicated
  • Source and Target must have unique and SQL compliant names.
  • Sources and Target can be deleted depending on the user's role and specific project restrictions.
  • Source and Target schema can be edited:
    • Tables and fields can be modified .
    • Tables and fields can be added.
    • Tables can be duplicated.
    • Tables and fields can be deleted depending on the user's role and specific project restrictions.
    • Batch updates can be made (excluding delete actions).
  • Sources and Targets have 2 statuses: Draft and Ready,
    • In Draft status, they will not be used in Zengines matching processes (although they can be manually set in Mapping).
    • In Draft status, a Target schema will not be available to use in a Conversion Job.
    • In Ready status they will be included in matching processes and conversion jobs.

Associating Data with a Source or Target

  • Data files can be associated with a table, as long as the Data file headers (column names) match the table field names.
    • Files paired with a table can optionally be set as example data to display on in the schema/table definition. Example data is a random sample of 10 values extracted from the Data file.
  • Associated data files can have their use restricted, so that no part of their content is sent to LLMs.
  • Associated data files can be profiled and a report generated (statistics for value per field).
  • Associated data files can be validated for conformity against the schema (data types, constraints).
  • Associated data files appear as the default selectable items for data sources in Conversion jobs.
  • A table can have many associated data files.
  • A data file can only be associated with 1 table.