Template-Based Use Case Planning and Development

Overview:
The goal is to develop a feature for template-based use case planning and development. This feature would combine elements of a solution designer, data lineage, marketplace, and use cases [beta]. The ambition is to provide a unified platform that simplifies and streamlines the development process, bringing together various scattered functionalities into one cohesive tool.

Example:
Imagine having a set of patient symptoms and corresponding diseases stored in S3 buckets. You are developing a workshop application where the end user enters symptoms in order, and the tool provides the corresponding disease. Since keyword-based searches for symptoms aren’t effective, this process involves semantic search.

Proposed Workflow:

  1. User Login:
    Users log into the platform.
  2. Access the Template Planner:
    Users navigate to the Template Planner and are prompted to provide a name and description for the use case.
    Ex:- Disease predictor
  3. Design the Workflow:
    Users drag and drop design nodes such as data connections, transformations, ontology objects, and workshop widgets into the planner.
    Ex:- S3 Connection, Basic pipeline transformations, Ontology objects like symptoms and diseases, Workshop with basic widgets
  4. Node Creation:
    During node creation in step 3, users are prompted to specify sample table names, columns, and other relevant details.
  5. Application Setup:
    Upon saving the draft, the user is prompted to create the corresponding applications under a project folder. If the user chooses to proceed, the system automatically sets up an S3-connected sandbox environment, pipelines with one or two transformations, corresponding ontology objects, and a workshop app with those objects.
  6. Customization:
    Users can then go into each individual component and make changes as needed to suit their specific requirements.

Conclusion: This approach is akin to installing from a marketplace and then customizing the setup. However, it goes a step further by providing users with a platform to create their own flow from scratch. While some of these capabilities might already exist, they are currently scattered across different tools. This feature aims to unify these functionalities into a single, user-friendly interface.

1 Like

I like this idea. I’ve thought it would be convenient to import Build with AIP modules using a transform node within Pipeline Builder.

1 Like