-
Notifications
You must be signed in to change notification settings - Fork 0
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
Data Package Views #47
Comments
I added further fields now. But I have troubles to map the three Scenario lines to fields of the Data Package content type or content types referenced by it (like data set, analysis context and so on). |
Any further progress here? The Data Tabs are quite important, they show the content of the Data Package relevant for the current GL-Step (e.g. for HC-LE) . This is also where we reuse most of our Taxonomies, so its quite important for v1. @DanielRodera perhaps you could have a look at this? :o) |
sure I will |
The data package view looks really terrible with the new theme. E.g. no indication that the list of resources are clickable links, but underlined link are not clickable, no clear separation between fields, important fields are missing (references, path, ...), etc. Any change to improve this? |
Hi, @p-a-s-c-a-l, Thank you for the feedback. I will inform Alejandro about the issue and we will propose a solution for this. |
Any news on that? See also the related issue: clarity-h2020/clarity-theme#7 |
I am working on it. |
And that's probably not even the worst title in our system. Looking at the page for Study 1, I doubt that this page can be improved with CSS only, so we need to do something with those names.
The Drupal-default title is was can be seen on the page now. I see two possibilities:
|
As a quick suggestion, one could modify the periods from:
One could also change:
|
Thanks @RobAndGo , seems good to me. I would've guessed the meaning of "std" and "mean", but from what I saw it's also always described in the resource description. Probably another great help (for @bullz and all the users) would be to use spaces instead of underscores. @maesbri would that be possible or would this be in violation of the specifications? |
No problem with that as in drupal we are not using the "name" property anymore (if I recall correctly), only the "title", which is text free. |
@bullz yes, this looks now much better than before!
Sure, the tabs are generated by two views (one responsible for the tabs of the Study group and one responsible for the tabs in all the individual GL-steps) as a custom text field FYI: The tabs in the GL-steps don't always have to be there (if there is no content for the tab, that tab is not displayed), but the order of the tabs is always the same ("Data" is after "Introduction", "Maps" after "Table" etc.) |
I have uploaded to the clarity theme a new version. the content of the display field now should be:
|
Great, I will update the View and test this tomorrow in my local instance and deploy it afterwards to the CSIS server (I'm guessing this hasn't been done yet?). |
Changes made by @bullz are now on the CSIS server, but it doesn't look quite like shown in your screenshot. I will continue the discussion for this specific view here: clarity-h2020/clarity-theme#7 |
Well, we are trying to replace tons of resources with one using variables. This will take some time, but see clarity-h2020/data-package#47. This will make the names shorter too. |
Main issue resolved. |
Please update the Data Package Views (Data Tabs in Study, HC, EE, ....) so that they they properly show the contents of the Data Package.
Views should follow the Mock-Ups. E.g. in the Study View (https://csis.myclimateservice.eu/study/1/view/data) is is probably sufficient to show the general meta-data of the whole data package, possibly with the link to all actual Data Resources. In The Data Tabs of the Module Steps, only the relevant Data Resources (e.g. only Hazard Resources in Hazard Tab) should be shown (Example).
Mock-Up: Data Package Content for EE Step
The text was updated successfully, but these errors were encountered: