If you have defined business rules and specified permanent keys, dependencies, and joins for a data source, you may want to copy the data source's metadata and standards to apply them to another load of data that matches the data source structure.
| Change type | Description |
|---|---|
| Introduced in version 17.3 | Capability to copy data source's metadata.to a new data source and add data to an empty data source. |
- Example scenario:
-
Assume that your enterprise has several locations that rely on the same application to place and fulfill product orders. The data is locally stored at each location, but transmitted to the home office on a monthly basis for financial auditing purposes.
The home office can apply the same data compliance checks across the various site locations to assess data quality. This requires copying data compliance checks across data sources with identical structures.
The following outlines the steps needed to complete this process:
- Create a data source and load the data into the repository.
- Apply all compliance checks.
- Copy metadata to a new data source (consider this a template since no data is copied).
- Load data into the new data source.
- Review the resulting compliance.