DQ-DIC integration improvements

Dear Collibra DQ Team,

We appreciate the great work you did regarding brand new DQ -> DIC integration and new UI (a link for reference - https://productresources.collibra.com/docs/collibra/latest/Content/DataQuality/Collibra%20DIC%20Integration/co_about-integrations.htm ). It is far better than we had before (via edge integration and countless workarounds for scheduling, rule lifecycle, etc.). However, there are a few suggestions how we can make this integration even better:

Ability to select/deselect OOTB adaptive rules/shapes etc. in the syncronization
Community (tenant) mapping is not working properly (124247)
Support views in database mappings (currently only tables are detected) (124213)
Some times the passing fraction is not updated properly (124217)
Business unit assignment moves all the jobs from “Unassigned DQ Job” community to new business unit community (122948)
Bring column level relation for user defined rules (122946)
Fix DIC aggregation path - the config does not take into consideration data quality dimensions (122949)
Add link to DIC from DQ UI

I hope that these features/bug fixes will be considered. Thank you in advance!

Current DQ version: 2023.08-ABDGCSHILM-3292

Responses

K

Kestutis_Daugela

7 Messages

9 months ago

Once again, we were truly impressed by the exceptional performance of this integration, especially its seamless synchronization with Collibra DQ findings. This is not a criticism, but rather an opportunity for further enhancement.

0

C

carlsoto

4 Messages

8 months ago

Have you submitted an ideation? https://productresources.collibra.com/ideation-platform

1

0

K

Kestutis_Daugela

7 Messages

We talked to the product team and it appears that this setting is not working. Moreover, it is supposed to be working only for multi-tenant environment. Currently all DQ -> DIC ingestions end up in centralised community (you can afterwards move/rename it, so it is not much of a deal). On the other hand, this feature won’t provide much value anyway, because at this point you can add one integration per DIC environment and you can not map datasets to particular communities (there is one possibility, however - using Business Unit tag in DQ. this way DQ DIC integration will create a sub communities underneath the pre-defined one).

Regarding the ideation platform and URL https://productresources.collibra.com/ideation-platform - seems to be redirecting back to https://productresources.collibra.com/ (at least recently). Maybe the end of ideations?

Like

Reply

8 months ago

0

Community

Kestutis_Daugela

DQ-DIC integration improvements

Kestutis_Daugela

carlsoto

Kestutis_Daugela

Related Tags

Related Conversations

Was this helpful?