Governance Actions

A governance action is a single task that is assigned to a data steward. The action generally states what the problem is and what it is associated to (e.g. a Data Store, Data Schema, Transformation, etc.). A typical governance action may look like this:

../../_images/governance_action.png

For all governance actions there are two ways to complete it:

  1. Mark the action as dismissed - this may be useful if governance action created is not actually an issue

  2. Mark the action as confirmed - this may be useful if the action has been looked into but the update is not reflected within Tree Schema

Tip

For certain types of governance actions you can simply correct the item that Tree Schema has brought to your attention and it will automatically be marked as completed. For example, if a governance action is created because your Data Schema does not have a description then updating the associated schema will automatically mark it as completed.


List of Governance Actions

The following is a list of all Governance Actions within Tree Schema, the column Auto Complete specifies whether or not the action will automatically be completed if you take the appropriate action within Tree Schema:

Governance Action

Description

Auto Complete

Data Store created without description

A new data store is created without a description

To auto complete, add a description to the Data Store

Yes

Data Schema created without description

A new data schema is created without a description

To auto complete, add a description to the Data Schema

Yes

Data Field created without description

A new data field is created without a description

To auto complete, add a description to the Data Field

Yes

Transformation Created Without description

A new transformation is created without a description

To auto complete, add a description to the Transformation

Yes

Field data type change

An update is made to a Field and the value for the data type changed (e.g. from Number to boolean)

No

Field multiple data types

When you automatically create your fields from a connected Data Store and the underlying data has more than 1 data type in the same field (this will only ever happen for fields that come from a sample file or data stores that do not always enforce a schema, such as MongoDB)

No

Transformation Link incompatible data types

A transformation is created that links to fields which do not share the same data type (e.g. boolean field to number or string field to list

No