Give context on the use case / what you’re trying to achieve
For several use cases I have modeled ontology data models with hierarchical links and I would like to give the ability to the user to view and navigate the data structure in simple way in a Workshop.
Example mock data structure for a Asana/Jira like use case:
Objects:
- Project
- Epic, linked many to one Project
- Feature, linked many to one Epic
- User Story, linked many to one Feature
Instantiation example
└── Project: TIME-MACHINE
├── Epic: Develop Time Travel Core
│ ├── Feature: Quantum Stabilizer
│ │ ├── User Story: Research Quantum Mechanics for Stabilization
│ │ ├── User Story: Implement Quantum Stabilizer Prototype
│ ├── Feature: Temporal Calibration System
│ ├── User Story: Design Temporal Calibration Interface
│ ├── User Story: Integrate Calibration with Time Travel Core
├── Epic: Safety Protocols for Time Travel
├── Feature: Multi-dimensional Awareness
├── User Story: Develop Awareness Module for Multiverse Detection
└── Project: FTL-DRIVE
├── Epic: Build Faster-Than-Light Engine
│ ├── Feature: Hyper-Space Entry Mechanism
│ │ ├── User Story: Research Hyper-Space Physics
│ │ ├── User Story: Build Hyper-Space Entry Mechanism
├── Epic: Navigation System for FTL
├── Feature: Cosmic Navigation AI
│ ├── User Story: Design AI Algorithm for Navigating Star Systems
├── Feature: Multi-dimensional Maps
├── User Story: Generate 4D Maps for Hyper-Space Navigation
I would like to provide a dynamic vizualisation to users in a Workshop, where they can expand/collapse levels and vizualize different informations at each level, with several options.
-
One like the “Links” part of an Object View, but configurable on which links to show or not,
-
One Table structure, combining expand/collapse controls (and indentation) with the columns of tabular data
Why you can’t do it today / work-arounds
Current non satisfactory workarounds:
- Vertex template to view the data structure. It works to visualise it, but it quickly becomes unreadable and overwhelming for the user when there are a lot of object instances. It is also impossible for the user to expand/collapse links.
- Encapsulated loop components to view and expand the data structure, by configuring a loop component for each level, and encapsulating sub loops in loop components. It works but it takes times to set up, and the visual result is a bit bulky.
Why will this make a huge difference for you or your business?
The result products would be much more user friendly, driving more adoption and more value !