Warning Jobserver and all related Jobserver integrations are end of life starting October, 2024, with the exception of Public Sector customers using GovCloud or on-prem environments.
For information on registering a data source via Edge, go to Registering and synchronizing a data source via Edge.

Registering a data source via Jobserver

By registering a data source via Jobserver, you connect a data source to Collibra. With this, you can make metadata of the data source available in Collibra.

During the data source registration process, you create a Schema asset. Via this asset, you can refresh the metadata of the data source.

Tip You can also register a data source via Edge.

Data source ingestion steps

The following table shows the steps required for data source ingestion.

Step	What?	Description
1	Register a data source	Registering a data source creates a connection between your data source and Collibra. It makes metadata of the data source available in Collibra. Note You can register a data source using a Collibra-provided driver or your own driver.
2	Ingestion	After registering a data source, Collibra creates a Physical Data Dictionary domain and new assets of the type Schema, Table and Column, corresponding to the data in your data source. Note Once you used a connection to successfully register a data source via Jobserver, you cannot change the connection properties. See Error when managing connection properties of a driver for Jobserver.
3	Refresh a data source	Refreshing the schema of a registered data source updates the metadata of the data source in Collibra. You typically do this when the data in a registered data source has been updated. Tip You can do this manually or automatically at fixed intervals.

Profiling data options

When you register your data source, you can choose profiling options for the registered data.

Option	Description
Store Data Profile	Option to perform data profiling on the registered data.
Detect advanced data types	Option to detect advanced data types in the data source.
Store Sample Data	Option to extract sample data from the registered data.
Tables excluded from registration	Database tables that will not be ingested. Note  If required, you can exclude multiple tables. To do this, press Enter after typing a value and then type the next. You can use an asterisk (*) as wildcard to select multiple tables. For example, if you want to exclude the tables that all start with act_, you can enter act_*. The table names are case sensitive. You can add or remove tables from this list by refreshing the schema. The Table assets that are created after ingestion have an attribute type called Table Type that defines the type of table that is declared in the data source. For example, TABLE, VIEW,...

After registering a data source

When the registration is complete:

• A message at the top right tells you that data source registration is complete. A domain and Schema asset are immediately created and an ingestion job is started.
• You can immediately add the registered data source to a data set by clicking the corresponding link in the confirmation message.
• The ingestion job creates assets that represent the metadata of the data source.

  Note Table assets that are created after ingestion have an attribute type called Table Type that defines the type of table that is declared in the data source. For example, TABLE, VIEW,...

• A workflow to assign a technical steward to the new domain is started. This is a simple packaged workflow that you can edit to fit your organization's needs. When you have assigned a technical steward, that technical steward has to set the security classification and indicate whether the data elements contain personally identifiable information (PII).