IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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



Add a new idea Subscribe
Status Needs more information
Workspace Data Lineage by Manta
Created by Guest
Created on Dec 4, 2024

RELATED IDEAS

Support for Complex File Formats in Manta Lineage

So the idea here is to augment the Filesystem flow model and introduce the notion of file section by adding the notion of file section but make it optional. This means that a given customer could choose to model file with sections or a file without the notion of sections, when, for instance, producing OpenManta Extensions. See examples below:

Proposed new Filesystem flow model:

Type | Description

Server | The file Server

Directory | Directory containing files and directories

File | File in the filesystem

section | (optional) Section name within the file

Column | Column in a file

Proposed new flow model rules:

Rule 1 - A File can contain zero or more child Sections

Rule 2 - A Section can contain zero or more child Sections

Rule 3 - A Column can have as a parent node either a Section or a File.

Needed By Not sure -- Just thought it was cool
  • Guest
    Nov 17, 2025

    Well the YAML part in OpenMantaDesigner is definitely necessary, but it is also necessary to make sure Manta is capable of representing such new concept in the Flow server UI/Neo4J. 

    Regarding role in exports, yes it will have impact, but keeping the notion of Section optional will assure retro-compatibility with existing projects that are exporting Filesystem to a given catalog. Ultimately we would need to rollout this new concept to any and all exports that export Filesystem lineage to a given catalog. I can imagine that this might entail a lot of work, but I would be surprised if existing catalogs not already allow the modelling of complex file structures. Nonetheless, they should be able to accommodate this change.

    Cheers,

    Luís

     

     

    Reply
  • Guest
    Nov 17, 2025

    Well the YAML part in OpenMantaDesigner is definitely necessary, but it is also necessary to make sure Manta is capable of representing such new concept in the Flow server UI/Neo4J. 

    Regarding role in exports, yes it will have impact, but keeping the notion of Section optional will assure retro-compatibility with existing projects that are exporting Filesystem to a given catalog. Ultimately we would need to rollout this new concept to any and all exports that export Filesystem lineage to a given catalog. I can imagine that this might entail a lot of work, but I would be surprised if existing catalogs not already allow the modelling of complex file structures. Nonetheless, they should be able to accommodate this change.

    Cheers,

    Luís

     

     

    Reply
  • Admin
    Eli Carter
    Oct 7, 2025

    Hello Luis, would you be able to give a example of this in practice?

    2 replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.