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,
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
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
Hi Ravikumar,
The approach we are taking for #2 for the considerable future is to leverage refinery, DataStage aaS or other ETL tools to combine the data before loading into MDM.
Thank You
Hi Ravikumar,
Thank you for your reply.
The goal of the mapping to is map (or not map) a column in dataset to an attribute in the MDM data model. So for each column, you should have both options available, correct? One option is to exclude from mapping, i.e. not map it and the other option is to select an attribute in the data model, i.e. map it.
Currently, you would need to use refinery services or other ETL tools to combine the data into 1 file first before performing mapping and matching. But this is a great requirement we would consider for future.
Thanks
Here, I have mentioned one possible defect(#1) and second one as an Idea.
In Mapping tab for the dataset columns, it was allowing me to select "Exclude from mapping" and also allowing me to select the column to be mapped. I think this not correct.
Currently I can do the mapping and loading from Single file. But we might have data in different files and there should be way to add data from multiple files (data sets - Address file and Phone file) to single entity(Person) before I go for matching set up.
Thank you for the Idea, Ravikumar. I think we have two separate requests here, can you confirm or are these items related?
For both of them could you add a little detail here as to what you are trying to accomplish with these requests as I'm not quite following the objective.
If I understand #2 correctly, you are asking to match multiple source files with the same entity. This is in fact possible. But again more clarity on what you're trying to accomplish would help us better understand the requirement.