Bridge Tables
Bridge tables are used when a multi-multi relationship exists. An example of such a relationship is the Task Owner field. In Digital.ai Agility, a Task can be owned by several owners (Members) and any one Member can own several Tasks. In the VersionOne datamart, all Bridge tables are in a database namespace (schema) known as "Bridge".
Multi-Multi Relationship Bridge Tables
Bridge.EpicOwner
Members can own multiple Epics and any Epic can be owned by multiple members. This relationship changes over time.
Table Description
| Column Name | Description | Datatype | Foreign Key To |
|---|---|---|---|
| DateKey | Identifies the date this record is valid | int | Dim.Date |
| EpicKey | Identifies the Epic owned by a member | int | Dim.Epic |
| MemberKey | Identifies the Member owning the Epic | int | Dim.Member |
Bridge.EpicStrategicTheme
Portfolio Item (Epics) can be related to multiple Strategic Themes.
Table Description
| Column Name | Description | Datatype | Foreign Key To |
|---|---|---|---|
| EpicKey | Identifies the Epic | int | Dim.Epic |
| StrategicThemeKey | Identifies a Strategic Theme associated with the Epic | int | Dim.StrategicTheme |
Bridge.MemberGroup
Members can be a part of many Member Groups.
Table Description
| Column Name | Description | Data Type | Foreign Key To |
|---|---|---|---|
| MemberKey | Identifies the Member in a Member Group | int | Dim.Member |
| MemberGroupKey | Identifies the Member Group | int | Dim.MemberGroup |
Bridge.PrimaryWorkitemRequest
Stories and Defects (PrimaryWorkitems) can be related to many Request.