Open han-f opened 1 month ago
I saw a missing space on the current OEP release in the text and I would really argue for having a word of caution as suggested above, as we cannot check any possible combination if it yields the correct results : This visualisation is still in beta stage and may contain errors.
I will fix the missing space.
As for the word of caution, I didn't delete it, I just moved it directly to the ‘Submit’ button that generated the result. At the moment it only becomes visible when you click on the very small blue ‘+’ symbol below the text. I can move it to the text that is always visible, or keep both and change the text a bit so it doesn't look like a duplicate?
Ah that is fine for me. I wasn't able to check the visualisation. I hope I will find some time today to test, but I may not be able to do so...
Ah I see, I've already spoken to adel -> we want to change this today so that the dropdowns and the sbumit button are visible as soon as the user accesses the page.
Off topic though: I've realised that I need to look through the bundles a bit more carefully, as not all of them have the datasets needed for the comparison. I've only looked at it for a few minutes so far and thought this bundle was good for demonstration.
Description of the issue
@jh-RLI and I discussed that we will include a disclaimer excerpt on top of the projection visualisation to show the nature of it being a "demonstration" only. Text suggestion below.
Note - do we need to say which tables can be selected only? Or will only these tables show in the drop-down anyhow?
Ideas of solution
This scenario projection comparison below is early access and serves illustration purposes: It shows for selected case study tables how projection data can in principle be automatically compared on the Open Energy Platform. It is a proof of concept. The Open Energy Knowledge Graph enables this comparison, based on the ontological annotation of the OE Metadata of the associated tables. This visualisation is still in beta stage and may contain errors.
Workflow checklist
cc @stap-m @wingechr @l-emele @christian-rli