You may choose to set up your own projects, or your administrator may set up projects for you, especially if the project will be used by more than one person in your company. Projects can be configured for specific profiling tasks, and assist in preventing duplicate efforts by different business teams.
The following table provides a list of common project grouping ideas:
|
Purpose |
Group |
|---|---|
|
Data Source Quality Analysis |
Group entities together allowing you to perform data quality analysis activities on the entity group, as opposed to each separately. For example, you may want to group all entities that contain customer data, regardless of their original data source. |
|
Target Mapping Analysis |
Group entities mapped to a single target entity as part of a data integration activity. |
|
Source Database Definition |
Group all entities that are sourced as part of a single database or database system, such as Relational Database Management System (RDBMS) or Content Management System (CMS). |
|
Subject Area Definition |
Group all entities that are a discrete part of a source database or database system, such as RDBMS. For example, a grouping might reference relational subject areas or an IMS sub-schema. |
|
Project Management Work Allocation |
Group individual user-managed data analysis activities. These activities might be defined in an external project plan document. |
|
Compliance Standards |
|
|
Data Tracking Requirements |
Group entities that contain data with the same data tracking requirements, allowing you to perform your compliance and profiling activities on the entity group, instead of individual entities. |