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

Drop-down of saved scenarios in import/export section can be improved #1280

Open
mabijkerk opened this issue Oct 18, 2022 · 5 comments
Open
Labels
Enhancement Pinned Will never be marked as stale or auto-closed.

Comments

@mabijkerk
Copy link
Member

When I go to the Flexibility -> Import/Export section, I can select price curves from saved scenarios.

image

When I try to select a saved scenario there are however two issues:

  1. There does not seem to be a logical ordering of scenario titles
  2. The list of saved scenarios is not exhaustive i.e., some of my saved scenarios are missing

image

@antw would you be able to have a look at this please, to see if the drop-down can be improved?

@antw
Copy link
Contributor

antw commented Oct 18, 2022

Here's how it works today:

  1. No saved scenarios for the current area code are shown. If your current scenario is nl2019 no saved scenarios for nl2019 will be included in the list.
  2. At the top of the list are scenarios with the same end year as your current scenario, ordered with the most recently updated first.
  3. Below those are the rest of your saved scenarios ordered by end year and then by most recently updated.

I think 2) and 3) are somewhat confusing.

@mabijkerk What do you think would be a more sensible ordering of scenarios? By title? Most recently updated first (regardless of end year)? Something else?

@mabijkerk
Copy link
Member Author

Thanks for the explanation, it makes sense now. It does seem a bit too advanced to be easily navigated by users.

Option 1: in my opinion the most simple would be:

  • Sort first on end year (regardless of date modified)
  • Then sort alphabetically on title

Option 2: another option would be to include a header between scenario groups:

  • Show first the scenarios with the same end year as your current scenario, sorted alphabetically on title
  • Then show the scenarios with another end year, sorted first on end year and then alphabetically on title

The dropdown with the two headers would then look something like the dropdown in the current modifiable curves section:
image

Discussion
To be honest my preference would go to option 1. @AlexanderWirtz I'm interested in your opinion on this. Do you have a preference for either sorting options or do you feel like something else would be clearer?

@AlexanderWirtz
Copy link
Contributor

Thx for the explanation, @antw .

I prefer option 1. Most of all, I would like a search function too, but I assume that is a bit more time consuming.

Here's my current bind: I have a recent German scenario whose curve I want to use for a Dutch scenario. I know it exists in 'My scenarios', but cannot find it in the endless list of scenarios I get now. Even now that I know and understand the current sorting logic.

I hope the new sorting method will fix this inability to find a scenario, but I am not sure. Hence the hope that we might implement a search function.

@mabijkerk
Copy link
Member Author

mabijkerk commented Oct 19, 2022

Right, I forgot about areas. Taking areas into account my sorting preference would be: area > end year > scenario title (alphabetically). I think this feels most intuitive because creating a new saved scenario works the same way: first you select the area, then the end year and finally you save it under a certain title.

@github-actions
Copy link

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

@github-actions github-actions bot added the Stale Issue had no activity for 60 days and will be, or has been, closed. label Dec 19, 2022
@mabijkerk mabijkerk added Pinned Will never be marked as stale or auto-closed. and removed Stale Issue had no activity for 60 days and will be, or has been, closed. labels Dec 19, 2022
@antw antw removed their assignment Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Pinned Will never be marked as stale or auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants