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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Created by Guest
Created on Oct 23, 2020

Auto-update "Contained Relationships" of Physical Data model / Schema Relationships

In Metadata Asset Manager (IMAM), relationships can be defined between Physical Data Models (PDMs) and Implemented Data Resource (IDR) schemas. These relationships can have "Contained Relationships" which associate design tables with IDR tables within the PDM and schema.

Once the contained relationships are set, they are static. If the PDM and schema are updated with new tables, no new relationships are defined without manually reviewing the relationship and using a matching criteria to identify new contained relationships.

We are looking for a way to automatically scan existing PDM / schema relationships and identify new design table / IDR table relationships based on pre-defined criteria (e.g. "Exact names (case-sensitive)" or "Exact names (non case-sensitive").

We are looking for this feature to be able to be triggered either through the interface manually for all existing relationships, or programatically via an API interface so that we can script and schedule this update.

  • Guest
    Oct 25, 2020

    Thanks for your idea.

    Currently, we are not looking to expand the current capabilities to detect and set the implementation relationship between Data Models and Implemented Data Sources. These relationships are inferred by the Data Model upon import, and often require the data modeller or other individual to augment those inferred relationsihps.

    Within Watson Knowledge Catalog, the next generation Data Quality, Data Governance and Catalog solution and offering, we are reviewing the total process for importing of Data Models and how such implementation relationships are either inferred or augmented.