1 Message
•
200 Points
Custom relation between data attribute and Table
Hello,
One of our business team is requesting to create a custom relation between Logical data asset: 'Data attribute' and Physical data asset: 'Table'.
What are the pros and cons of creating the requested relation? Generally, Collibra recommends having a relation between Data attribute and Column only.
The use-case is that the Data entity and its attributes can represents many tables and columns.
Our Business Steward would want an easy means to display the relation between Data attribute and Table, Column in a hierarchical view of the data asset domain. Our operating model has already a relation between the Data attribute & Column.
Regards,
Kiranmai Nukala.
grantrollerson1
102 Messages
•
6.9K Points
2 months ago
Not a great idea, since a table is just a physical construct... which datapoints (row/column) could be built in a variety of ways, eg name-value-pair or denormalised grid etc. That being said Collibra DQ uses the r/ship Data Asset represents / represented by Data Asset to go from DQ Job to Table. Go Figure.
So, you can use Resource Id 00000000-0000-0000-0000-090000010026 for this Data Asset represents / represented by Data Asset, and if needed put a Filter in the assets' characteristic data model definition.
0