-
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
Twins prototype requirements #55
Comments
@patrickkaleta : Thanky, looks good. I think we do not need more at the moment. |
ok, I will implement this in the CSIS |
I implemented the entity type and the view and configured the GL-step and its view to display the twins. For now, I also deactivated the Twins-tabs for all other steps except the first step (Hazard Characterization), since they are not yet defined and not even the mock-ups exist for those twins. |
@patrickkaleta : I sent you the Key via e-mail, please check, if it is working. |
@Itsman-AT: the key works. I've added it to the CSIS site. |
Here is the updated Twins data model (already implemented in CSIS Drupal): Marketplace-Entities.svg @Itsman-AT Please discuss the Hazard Twins with @DenoBeno. I seems that the Hazard Twins idea has been abandoned. |
I would appreciate a fast decision on this matter, since I'm currently working on a function to include these Twins (or whatever it's going to be in the end) into the final report (similar to the recently implemented Report image functionality) Locally, I already managed to establish a working prototype, which displays the available Twins below the Twins-Map and separates them into those who are already included (always shown on top) and the ones who are available (and could be included in the report). |
Some improvements that should be implemented before ECCA 2019: Filter is applied on map onlyThe (Hazard) and type filter are applied on the map only, but not on the table Twin Maps for additional EU-GL StepsWe should add Twin Maps for the other EU-GL Steps and show Twin and Showcase Entities that are assigned to the respective step. For Twin and Showcase Entities related to Elements at Risk (EE Step) and [Adaptation Options] (IAO Step)), we can show Elements at Risk and Adaptation Options filters, too. Avoid i18n duplicates |
Filters are applied to the map and the table showing "Available Twins/Showcases". For the "Included in Study report" table I deactivated the filters on purpose, since IMO users would get confused if those filters would "remove" already selected Elements from their study again. But it's not a problem to change that and make the filters affect this table as well.
That's the way it was intended. I've hidden the Twins-Tab on all others steps, because currently all existing Twins/Showcases are assigned to the "Characterize Hazard" Step, so the Twins-Tab would be completely empty on all other steps. I'll have a look at it tomorrow to see if some of the Twins/Showcases would better fit into another step. Regarding the shown select filters I talked to Denis and he wants (for now) to only show the "select hazard" option to keep it simple and not confuse the users. I therefore deactivated the "Select Type" option.
Done, as mentioned in this comment. |
You are right, it seems to work - but not very reliably. If you filter by "heat" and then by "flood" both tables disappear:
You're right, the filter should be applied to the second table only. |
Strange, the tables disappear after the second time filter are applied (no matter which filters are used). Those filters are not custom-made but the ones provided by default by the Drupal Views. So probably it's just some misconfiguration, I'll check that. |
Grouping Twins/Showcases into the EU-GL StepsI had a look at the currently available Twins/Showcases (10+1) and grouped them by the most relevant EU-GL step. For the Studis we now have Twins-Maps shown for the following 4 EU-GL Steps: Hazard characterization:
Hazard characterization - Local effects:
Exposure Evaluation:
Adapt. Opt. Identification:
@Itsman-AT could you please have a look and decide if this is reasonable or if you would change some of them? Also I prefixed some of the Twins with "!!!" - those have little to no description, so it would be great if this could be fixed. |
This bug is fixed now and tables stay visible after applying filters multiple times. Apparently Drupal's Contextual filters can run into problems when using Exposed filters and AJAX. Changing the Contextual filter's parameters was the solution. |
@patrickkaleta Now it seems that showcases are missing on map and in table. |
@p-a-s-c-a-l after having a look at all twins/showcases I moved some of them into different tabs (by setting the The second showcase cids GUP-MV is shown on the Exposure tab in the map and in the table (at least for me thats the case). |
at https://csis.myclimateservice.eu/node/1287 @Itsman-AT Can you please check what's going on? Quota exceeded, wrong key? |
|
First find: Quota does not seem to be exceeded:
|
I am investigating on the 100% error value. |
Works in _Chrome. Probably a firefox issue. They added a lot of tracking protection functionality lately.
O.K. And what happens on day 58? :-) |
AIT DRC would have to pay the bill :-) - not a good solution ;-) |
IMHO this is revolved and can be closed? |
@p-a-s-c-a-l : Yes, please close the issue. We will handle this AIT internally. |
@DenoBeno : Did you already create a DSS Google Maps Billing Account for Clarity? The Key expired now which is unfortunate. Can I be of any help? |
Last week, I started implementing a first prototype for the Twins in my local environtment using the Geofield_map and Geofield module.
So far, I have a new content type called "Twin" with the following fields:
@Itsman-AT Do we need anything else for now?
On the Twins-tab in the study this could then look something like this:
![prototype-for-twins](https://user-images.githubusercontent.com/42167036/54109032-cf85da00-43dd-11e9-8c77-1ff4c87c969f.png)
@Itsman-AT as discussed last week, we need a Google Maps API key, so that we can fully use the Geofield_map module. Let me know, once you have one.
The text was updated successfully, but these errors were encountered: