Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Frozen" state of the landing page for kedro viz (for easier navigation) #1673

Closed
ElenaMironovaQB opened this issue Dec 6, 2023 · 4 comments

Comments

@ElenaMironovaQB
Copy link

ElenaMironovaQB commented Dec 6, 2023

Description

Is your feature request related to a problem? A clear and concise description of what the problem is: "I'm always frustrated when ..."

a helpful feature would be to be able to fix the state of the landing page - e.g. we have huge pipelines, we've collapsed some things and hid some outputs - can this state be "frozen", so that every time you open kedro viz, you land at this "prepared" view? Right now we don't let colleagues from outside of our product team handle our kedro viz, cause they'd just get lost directly on the landing page

@ElenaMironovaQB ElenaMironovaQB changed the title <Title> "Frozen" state of the landing page for kedro viz (for easier navigation) "Frozen" state of the landing page for kedro viz (for easier navigation) Dec 6, 2023
@rashidakanchwala rashidakanchwala moved this to Inbox in Kedro-Viz Jan 15, 2024
@rashidakanchwala rashidakanchwala moved this from Inbox to Backlog in Kedro-Viz Jan 15, 2024
@NeroOkwa
Copy link
Contributor

NeroOkwa commented Jan 22, 2024

Thanks @ElenaMironovaQB for this.

Context

Users who have large pipelines have collapsed some nodes/ filtered out some parameters or datasets. When they share this with other stakeholders, this configuration or 'prepared view' is lost, and the new user has to go through a checklist of steps in other to arrive at the chosen state. To currently solve this @ElenaMironovaQB has to share a short video walkthrough of their pipeline instead, which loses the value and interactivity of Kedro-Viz.

Solving this means that users with large pipelines are able to prepare their pipelines (with configured settings) and share it with another stakeholder (e.g. business) and that stakeholder can see the same 'prepared view' state as the initial user. The benefit of seeing the same view is greater collaboration, debugging, on the project.

This would also complement #1116.

Possible Implementation

Kedro-Viz flowchart is stateful, but can be improved (to solve this pain point) by adding hiding/filtering features. This can be implemented through the URL or some settings config file.

Acceptance Criteria

A user is able to easily share a 'prepared state' or landing page of their Kedro-Viz visualisation to another user by

  • Configuring the required settings (collapsed nodes, filtered parameters, or datasets) on their pipeline flowchart view
  • The state is saved (or unique url is created)
  • Using the shareable Viz feature they share that visualisation with another stakeholder, who is able to see the exact same page as the initial user
  • Together they can discuss and collaborate on the pipeline, making decisions on the next step of the project.

@astrojuanlu
Copy link
Member

@ElenaMironovaQB Stateful URLs hopefully addresses this issue by now. There's no documentation for them though 🥲

For showing/hiding datasets you could use tags.

Does this solve your problem? If there are no further comments we will close this issue in a few days.

@astrojuanlu astrojuanlu moved this from Backlog to Done in Kedro-Viz Jul 11, 2024
@ElenaMironovaQB
Copy link
Author

Thanks a lot, team! We are yet to explore using stateful URLs in our product, but based on demos looks like they should solve it :) looking forward to the docs!

@astrojuanlu
Copy link
Member

Thank you! Closing this for now, we'll deal with the docs separately. If there's any further requests let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

7 participants