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,
Post an idea
Upvote ideas that matter most to you
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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io
The end consumer of a data module is a business author.
The trusted badge needs to be at an object level, not at the DM level.
As a business author I would like to know the heritage of the objects within a data module I am using. Then if someone shares a DM with me, i know which bits are 'central objects', and which bits have been added by other users.
It feels more like you need different badges for different objects within the module.
Then as a business author i could say "only show me objects with the central IT badge", "show me objects from central IT and my team".
The idea of not breaking links is good - but this requires a lot more things to be links! As joins, standalone calcs, nav paths (to name a few) arent links, then just having a trusted table isnt of value. If its a star schema i need to be able to trust the fact table, any dimensions, and the join! currently only the tables are links.
On the bigger picture, the whole reusing bits of a data module in other data modules isn't really a good scalable solution though. The idea floated here is data modules managed by central IT teams. These data modules are typically going to be large complex for data warehouses. Why would a user want to bring bits of this large DM this into their own data module? Who is likely to have the biggest, most complicated DM, the central IT team, or the end user?
What is the end user wanting to do, add a new calc? add a new bit of data - maybe an excel file?
So the end user has to create a new DM, bring in all this stuff from the main IT held corporate DM, then add a new calc. And then repoint any reports, dashboards they may already have to their new DM to use that calc!
Now imagine the central IT team has updated the central DM, maybe added some new calcs, some new tables, dimensions etc and the business user want to use those too. They have to open up their DM, bring in all the new stuff and then they can use it. And they are forever stuck in this pattern.