Option to update/replace Project data asset when add it from Catalog to avoid duplicate data asset

See this idea on ideas.ibm.com

When we add a data asset from Catalog to Project brand new are added to project as many times we add it from Catalog. The idea here is to have an option to update/replace the data asset when add it in the Project that the data asset has already been added, avoiding the duplication of it.

We are using Catalog to business users consume the data asset and Project to process Data Quality rules, these DQ results are published back to the Catalog to maintain the data asset updated, but when any update are made in Catalog data asset by data steward it cannot be updated to the data asset in Project, so when the DQ rules are processed and the results are republished, we lost the updated information in the Catalog.

Now, the only way we have to use the new information available in Catalog is adding the data asset again in Project and rebuild the DQ rules to process this new data asset.

If we can update/replace the data asset in Project with the new information of the data asset in Catalog, we can avoid this behavior.

Image 1asset.png shows only one data asset in Project, by adding same data asset from Catalog to Project (image 2adding_fromCatalog_toProject.png) we have 2 same data assets in Project (image 2assets.png). If we repeat the process once more (3adding_fromCatalog_toProject.png) the Project have 3 data assets, the same one, as shown in image 3assets.png

1asset.png

2adding_fromCat...

2assets.png

3adding_fromCat...

3assets.png

Needed By

Yesterday (Let's go already!)

Post comment

Guest

Apr 7, 2025

Thanks for the update Susanna, this improvement will really help us.

Reply
Hide replies

Admin
Susanna Tai

Apr 3, 2025
Hi Diogo, thank you for submitting the Aha idea. I've added this to our roadmap for future consideration.

Having said that, in CPD5.2, we will be introducing new handling of Data assets that address duplicate assets in the platform, which will help with the user flow described this aha idea. At a high level, if 2 (or more) Data assets are "identical" (meaning they represent the same physical asset in a data source) in different catalogs and projects, there will be a set of common and shared properties that will be referenced by these identical data assets. The implication is that, from different projects or catalogs, the assets can reference the same set of shared properties, which will eliminate the need for the user to add asset from catalog to project, re-do the DQ rules and then re-publish the asset, just to preserve the updates made to the catalog assets.

So the user flow to re-run DQ in CPD5.2 can be as follows:
1. User runs DQ rules on asset in project and publishes the asset to catalog for the first time.
2. After publish, the project asset and the catalog asset now share the same common properties.
3. User updates shared properties in the catalog asset. These changes are immediately visible to the project asset (as long as the project asset is not being updated).
4. User re-runs DQ rules on the same project asset from step 1, which is now in "Draft".
5. User publishes the project asset to the catalog, and the new DQ scores are updated on the catalog asset. The updates in step 3 are still there, since the project asset is referencing the shared properties before re-running DQ rules in step 4.
These changes in CPD5.2 on managing identical data assets are designed to ensure users in different workspaces are viewing (and sharing) the same metadata if the data assets are "identical".
Hope that helps.

Regards,
Susanna Tai, Product Management
Reply
Hide replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Option to update/replace Project data asset when add it from Catalog to avoid duplicate data asset