[Draft][Design]Transition of Legacy Visualization to VisBuilder

[SheyGao]

Problem Statement

// users utilize visbuilder instead of re-creating from saved objects? several options: 1. migrate saved objects into visbuilder, migration function is one of them

Objective

1. Create a migration function to load legacy visualizations in VisBuilder with proper aggregations.
2. When save the migrated visualization, VisBuilder can save the current migrated visualization to the new VisBuilder format.
3. Ensure the new saved VisBuilder format visualizations can be embedded into dashboards, maintaining a consistent user experience.

Out of Scope

// paragraph

Proposed Design

// paragraph

The User Flow

• flow chart

Architecture

Workflow
Step 1: mapping & bridging

• flow chart

Step 2: saved objects in visualization - change URL -> visbuilder

• migration function
• testing
• flow chart

Step 3: UX update

• https://quip-amazon.com/Hr2bAmzjaPSJ/UX-Update

Saved Object & Embeddable

• saved object structure https://github.com/opensearch-project/OpenSearch-Dashboards/issues/7053
• how objects are fetched and saved in VisBuilder https://github.com/opensearch-project/OpenSearch-Dashboards/issues/7055
• embeddable

Future Scope

Open Questions