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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
In Match 360 there should be an easier way to remove attributes from published model
In current version of Match 360 as soon as data model is published, there is no way to remove a single attribute even if no data is mapped to it and it is not used in matching. The only way to solve it is to run unpublished reset model APIs which ...
Flexibility to Make Attributes Searchable After Creation in Match360
Currently, in the Match360 data model, an attribute can only be designated as searchable during its initial creation. Once the attribute is created and published, it cannot be altered as a searchable attribute. This lack of flexibility restricts t...
Match360: Create UI to parameterize feature weightings (and any other code based configurations)
Match algorithm tuning and configuration requires code adjustments to adjust feature weightings that affect the customer record match scoring. Match tuning and configuration had been set as a business activity. The business users should not be goi...
Loading incremental sources will require full extract from Match360 to consuming systems
For our customer, sources will be loaded into Match 360 gradually. First 5 sources will go thru initial load and then ongoing inbound process will be turned on to apply updates thru ongoing_sync APIs. Match 360 itself is not a point of data consum...
Publishing events functionality is missing reprocessing logic in case of Kafka unavailability
In the new events publishing functionality ( version 4.7) where update/insert/delete events are published into Kafka queue, in case if Kafka queue is unavailable and updates still happen to Match 360, all events are lost and will not be sent into ...
Ongoing sync API for Match 360 update should have an option not to update record if nothing change and not to trigger match/entity composition
In our process we do not know what values changed in the customer record during ongoing inbound process. As there are multiple record types generated from a single customer record, all record types get updated, person record type gets updated , ma...
We are planning for an upgrade to MDM v12, later in 2023. We as a business are moving to cloud based infrastructure and as part of that journey we are guided by corporate principles for deployment. IBM provided containers for MDM do not meet our c...
ACM (Advanced Catalog Management) currently supports only FTP. Unfortunately, our customer is disabling FTP protocol organization-wide and pushing all apps to migrate to SFTP. Request to enhance ACM to support SFTP.
Match 360 - Creating matches across different entity types
Match 360 needs to be able to create matches across different entities. Currently, matches are only performed within an entity type only. Not across entity types. Example is matching algorithm will match within Person Type and Org Type independent...
Do not place IBM confidential, company confidential, or personal information into any field.