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

Generate full link for sections #474

Open
mabijkerk opened this issue May 17, 2023 · 4 comments
Open

Generate full link for sections #474

mabijkerk opened this issue May 17, 2023 · 4 comments
Assignees
Labels

Comments

@mabijkerk
Copy link
Member

In some cases it is useful to be able to direct clients to specific parts of the Dataset Manager. For example to refer to the Electricity own use in Denmark, which is located in the Energy production > Energy demand section.

Screenshot 2023-05-17 at 14 47 14

When visiting this section, the link remains unchanged: https://data.energytransitionmodel.com/datasets/DK

An idea would be to generate the full link for sections, like we do in the ETM frontend. So something like: https://data.energytransitionmodel.com/datasets/DK/energy-production/energy-demand

@noracato are there any practical considerations not to implement this?
@Charlottevm what do you think of this idea?

@Charlottevm
Copy link
Contributor

Yes good idea! I am definitely in favor of referring people to the datasetmanager as much as possible, lets make use of all the information that is there.

Would it be possible to easily drop a link in ETModel which then 'changes' based on the dataset you open? So if we insert a link in ETModel referring to the electricity own use, it shows this if you open a scenario for Denmark but shows Amsterdam if you were to open a scenario for Amsterdam? @noracato

@noracato
Copy link
Member

Very possible and not too hard. The url's in ETLocal would take less than a day.

Would it be possible to easily drop a link in ETModel which then 'changes' based on the dataset you open?

We already do this in 'sources', so yes, that would be very easy 🙂

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 label Jul 18, 2024
@mabijkerk mabijkerk added Pinned and removed Stale labels Jul 18, 2024
@mabijkerk
Copy link
Member Author

@noracato is this something @louispt1 would be able to pick up at some point?

@louispt1 louispt1 assigned louispt1 and unassigned noracato Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants