Data Governance Datasets Joines

The name of the dataset implies the granularity.  That said @DataMaven  has seen that not all DomoGovernance datasets have the expected cardinality.  

If I were using a DG dataset, I would enforce a GROUP BY clause to the data BEFORE JOINing it to another table to guarantee granularity.

For Cards and Pages, I would

1) GROUP BY the respective ID columns

2) Remove any columns that violate 3NF (https://www.google.com/search?q=3nf&rlz=1C1CHBF_en-GBGB896GB896&sxsrf=ALeKk03VjLpKmne8NdduxuFJHUrQdI_eSA:1593595988080&tbm=isch&source=iu&ictx=1&fir=hkPjDYPQfqeZOM%252CdmBtnH4lW3c_rM%252C%252Fm%252F01cs9w&vet=1&usg=AI4_-kSf2mDdYZOQm9EJ2xSN-KoB3jnq4Q&sa=X&ved=2ahUKEwjqv6PW36vqAhVu-ioKHWy0C4YQ_B0wIHoECAgQAw&biw=1536&bih=731#imgrc=hkPjDYPQfqeZOM) -- remove columns that are not attributes of the ID column.

3) use FIRST or MAX aggregates to get the text values (like Title or Creation Date).

For Bridge tables (Pages and Cards and Pages and Users)

1) I would GROUP BY the key columns, 

2) remove any descriptive columns, like Title or Description, because those attributes will come from dimensional tables

3) Only keep measures like Share Date.