In

Data Quality

, an asset is an object that defines part or all of a data quality operation.

In

Data Integration

, assets are mappings, taskflows, and tasks such as

mapping

tasks,

synchronization

tasks, and

replication

tasks.

Data Integration

assets also include components such as business services, mapplets, and hierarchical schemas.

You can create the following assets in

Data Quality

: cleanse, deduplicate, parse, labeler, rule specification, and verifier. Add the assets to a Cleanse transformation, Deduplicate transformation, Parse transformation, Labeler transformation, Rule Specification transformation, and Verifier transformation respectively when you design a mapping in

Data Integration

. You can add each transformation to a non-elastic mapping. You can add a Cleanse transformation, Parse transformation, Rule Specification transformation, and Verifier transformation to an elastic mapping.

You can also create dictionaries in

Data Quality

that other data quality assets can use. A dictionary is a table of reference data that a mapping can read to evaluate the accuracy or usefulness of source data.

Create assets to satisfy your data objectives. Templates are available for certain asset types. You can use a template as-is, or you can use it as a head start and customize it to meet your needs.

You can use assets in multiple projects. All assets must be part of at least one project. If you create an asset without specifying a project, the asset is created in the default project.