[Vis Builder] Vis Builder meta issue

[ashwin-pc]

Parent issue to track the different task for the Drag and Drop experience.

• Feedback: [Feedback] Visualization Builder - Experimental Release #2280

Tasklist:

Framework

• Drag and drop entrypoint [D&D] Add Icon to the "Create new visualization" popup #959
• State management [D&D] Add state management for the Drag & Drop plugin #947
• Visualization service [D&D] Add Visualization service #952
  • Contributions [D&D] Viz Service: Contributions #1274
  • Remove contributions [D&D] Remove contributions #1705
  • Expressions [D&D] Visualization type pipeline #1275
  • Agg service/viz class research [D&D] Aggregation service and Viz class research spike #1699
• Save and embed
  • Save visualization [Vis Builder] Save Visualization #1620
  • Add to Dashboard via saved object [D&D] Add to Dashboard via saved object #1703
  • Add to Dashboard directly from dashboard [D&D] Add to Dashboard directly from editor #960
  • Add to Dashboard directly from visualization [VisBuilder] When creating wizard from visualization page, provide additional options to add to new/existing dashboard, or add to library #2534
• Localization [Vis Builder] Add Localization  #958
• Testing
  • Initial unit tests [D&D] Add unit test coverage #1704
  • Integration and E2E tests [D&D] Functional Tests for the Drag and Drop experience #961
  • Increase test coverage [VizBuilder] Increase test coverage #2380
• Drag and drop [Vis Builder] Add drag and drop to main canvas #956
• Initial visualizations [Vis Builder] Add visualization types #957
  • Metric [D&D] Add Metric Visualization #1614
  • Datatable [D&D] Datatable visualization #1615
  • Bar [D&D] Bar Chart #1616
  • Line [D&D] Line Chart #1617
  • Area [D&D] Area chart #1618
  • Pie [VisBuilder] Add Pie Chart visualization type #1619

UI

• Add Topnav [D&D] TopNav Index pattern #949
  • Persistance [Vis Builder] Persist the global query parameters including global filters, time range and time filters #1913
• Add Index pattern selector [D&D] [UI] Update index pattern selector #948
• Add breadcrumbs [D&D] Add breadcrumbs #1621
• Empty workspace polish [D&D] empty workspace polish #1684
• Field summary view [D&D] Add Field summary view #950
• Field search [D&D] Field Search in Data panel #951
• Viz style [D&D] Add Visualization styling tab #953
• Viz toolbar [Vis Builder] Add Visualization controls #955
• Viz type selector [D&D] Visualization type selector #954

Meta

• Documentation [Vis Builder] Drag and drop experience documentation #962
• Replace "wizard" with real name [D&D] Replace wizard naming convention #1706
• Plan to release as beta/preview feature [D&D] Add support for release as beta/preview feature #1708

---

• Original Design: [Design] Drag & Drop Visualization CX #896
• Proposal: [Proposal] VisBuilder - Drag & Drop Visualization CX #883

[seanneumann]

For reference the RFC: #896

[seanneumann]

I'd like to make sure we start talking about two requirements:

• Supporting PPL
• Supporting multiple data sources.

We don’t need to implement them in the initial release, but should include them in the design so they will be incrementally added.

[ashwin-pc]

I'm currently working on the design for #1275 which will cover these two topics. But just to highlight the general approach, we will be using the expressions language already built into OpenSearch Dashboards to create a pipeline that a visualization will use to render given the various user inputs. Current visualizations also use the same flow.

A sample pipeline:

 opensearchDashboards                                                   // Retrieves global information for the dashboards query and filters
 | opensearch_dashboards_context query='QUERY' filters='[]'             // Retrieves Visualization specific information such as datasource and filters
 | opensearchaggs index='INDEX_ID'  aggConfigs='AGGREGATION_CONFIG'     // Performs aggregation
 | opensearch_dashboards_pie visConfig='VISUALIZATION_CONFIG'           // Renders visualization

The implementation details for each function in the pipeline is separate from the function calling it. This way we can swap out any section of the pipeline with a different datasource and/or different query engine to render the same visualization as long as the inputs and outputs to the other functions in the chain remain unchanged.

[kavilla]

[Groom]:
We should update this issue with our 2.2 planned deliverables.

@ahopp @opensearch-project/opensearch-ux the current 2.2 planned deliverables aren't feature complete and should be indicated as such. So that it should be configurable to toggle this on and off.

[seanneumann]

Hey team, I'd like to propose a new name for this functionality. While drag and drop is a part of the story, we should give it a name that is more encompassing. Here are some thoughts:

1. Vis Builder
2. Vis Wizard
3. Vis Designer
4. Vis Maker
5. Data Explorer

Let's discuss.

cc: @elfisher @ashwin-pc @ahopp

[kgcreative]

I'm partial to:

1. Vis builder
2. Data explorer

[xeniatup]

1. Viz builder - because it explains what it does really clearly
2. Data Wizard - hints on ease of use and emphasizes the underlying data

[btzeng]

Vis Builder

[abbyhu2000]

Vis builder or vis maker make the most sense for me:)