Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Functionality already exists
Workspace Knowledge Catalog
Created by Guest
Created on Sep 23, 2021

UAT Custom Asset API allows duplicate asset in Catalog

The create custom asset api does not throw error if asset with same name is created in a given catalog. 

Expected Result: API should not create duplicate asset in the catalog

Steps to reproduce :

# Create a catalog in ICP4D

# execute the Create Asset Type API ( use following end point and request)

## end point - <ICP4D Hostname>/v2/asset_types?catalog_id=<Catalog ID>

## Request Json -

                    \{{    "name": "system",    "description": "System asset type",    "fields": [        {                    "key": "abc",            "type": "number"        }    ]}

 

       3. Now use the Create Asset API and submit request using following steps

                 1. end point - <ICP4D Hostname>/v2/assets?catalog_id=<Catalog ID>

                 2. request JSON - 

                   {

"metadata": {

"name": "Telecom System ",

"description": "Test System asset",

"asset_type": "asset",

"origin_country": "us"

}

}

       4. Repeat step 4 again and you would see "Telecom System" asset getting created as duplicate within the catalog

Needed By Month
  • Admin
    Susanna Tai
    Reply
    |
    Aug 23, 2024

    This requirement should be addressed now with option in the catalog settings page for the admin to specify how "duplicate" assets are to be handled. For example, if you don't want duplicate assets to be created, select one of:

    • Update original assets

    • Overwrite original assets

    • Preserve original assets and reject duplicates

    You should be aware that asset name alone does not determine whether an asset is a duplicate or not. Oftentimes, customers have tables with the same name that come from different sources. These are not duplicate assets, and indeed the assets can have the same name within the catalog.

    Here's the documentation on the topic: https://www.ibm.com/docs/en/cloud-paks/cp-data/5.0.x?topic=catalog-duplicate-asset-handling

    Please reach out if you have further questions.

    Regards,

    Susanna Tai


  • Admin
    Susanna Tai
    Reply
    |
    Oct 1, 2021

    Hi Sudha, it's on our roadmap to address handling of duplicate assets in catalogs in Q4 2021 and into 1H 2022.

    in Q4 2021, we will have updated publish to catalog API to determine how to handle duplicates - allow, reject, merge or overwrite.

    We also plan to have a catalog setting where the default behaviour for handling duplicates can be set.