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
When developing Data Science models, data source and targets can be both data assets in files or in databases. Especially in large environment, when data is stored in Data Warehouses, data should not have to leave the database from beeing used in data science. As such, connections exist in CP4D and are usable in most tools, like Watson Studio, SPSS and WML. Still, when building a model in Watson Studio, deploying this into WML, creating a Batch Deployment Job and run this, it is still possible (in some point of time, it would be great, if the actual chosen data source in WML will be used and not the asset that has been saved in SPSS!). However, when creating a pipeline with several jobs to do, this is NOT possible, which makes it very difficult to e.g. first run a DataStage Job to prepare data in a database and then use WML to score it: the node "Run Batchjob" does not allow to chose connections, just data assets.
Do not place IBM confidential, company confidential, or personal information into any field.