|Status:||Released||Start date:||Nov 04, 2016|
|Priority:||Normal||Due date:||Nov 11, 2016|
|Assignee:||Massimiliano Assante||% Done:|
VRE Full Name: Strategic Investment analysis and Scientific Planning/Alerting VRE
VRE name: SIASPA (to be used also as the site/scope name)
VRE abstract: Strategic Investment analysis and Scientific Planning/Alerting VRE offers a geospatial multi-factor optimization and alerting platform for intelligent identification of locations of interest for investors and stakeholders seeking optimization of intended investments and scientists seeking areas that are becoming of environmental importance
**VRE logo: attached to the ticket
Membership policy: restricted
VRE expected datasets: Datasets will be imported using the VRE's deployment tools (https://support.d4science.org/issues/5438)
VRE expected functionalities:
- Users Management facilities
- Geoanalytics portlet
- Geoanalytics Administration portlet (restricted to VRE managers)
- PostGIS (9.1+)
- zookepper (3.4.6+)
- Geoserver (2.9.1)
- Geoanalytics service deployed in apache tomcat 8 running with java 8
- Geonetowrk to be also available in this scope.
This VRE will be evolved in 2 stages. In stage 1 (after the gCube 4.1 release) it will be used as a demo VRE where limited functionality will be available. In stage 2 the full planned functionality will be made available.
- Stage 1: geospatial data ingestion and project management facilities will be available
- Stage 2: intelligent identification of locations of interest of intended investments and optimization techniques will be made available
#3 Updated by Leonardo Candela almost 4 years ago
- % Done changed from 80 to 10
I'm lowering the percentage because I miss the specification.
The specification should include the information described here https://support.d4science.org/projects/bluebridge/wiki/VREs_Deployment_and_Operation
#9 Updated by George Kakaletris over 3 years ago
- Invite_Policy set to VRE_Manager
- VRE_Policy set to Restricted
- Subject changed from Strategic Investment analysis and Scientific Planning/Alerting VRE (Blue Economy VRE#2) to Blue Economy VRE 2.1 - Strategic Investment analysis and Scientific Planning/Alerting VRE
#22 Updated by Leonardo Candela about 3 years ago
Not clear to me what is the semantic of declaring this VRE 100% done, AFAIK we are not here yet, e.g. we lack some portlets aren't we?
Moreover, why the link with #5438 was dropped? Is not mandatory to have these dataset in the infrastructure before actually being in the position of releasing this VRE?
#23 Updated by Panagiota Koltsida about 3 years ago
- % Done changed from 100 to 60
- Due date changed from Nov 04, 2016 to Nov 11, 2016
Dear @email@example.com ,
thank you for your comments.
It seems I had the wrong impression that this ticket was covering the "creation" part of the VRE (scope creation, site in liferay and the deployment of the core portlets) and this is why I thought it should be moved to 100%.
If this ticket covers also the datasets that will be imported by using the geoanalytics tools etc it should not be in 100%
The reason that I removed the subtask was in order to be able to add a due date, and I was thinking of adding it as related instead of a 'sub' task, for the reasons I explained above
Finally, I tried to deploy the geoanalytics portlets into this VRE, but it seems they are not available on the portal. @firstname.lastname@example.org , could you please deploy them?
#24 Updated by Leonardo Candela about 3 years ago
Tickets having tracker = VRE should be used to capture the entire set of tasks leading to the deployment and release of a VRE.
As a consequence, we should add any sub-ticket representing an activity that is mandatory for having the VRE in place.
It will be great if we can capture by sub-tickets the deployment and configuration of the back-end technology falling outside the standard gCube stuffs, e.g. Geoanalytics service.
Re GeoNetwork and the rest of gCube SDI facilities, namely THREDDS and GeoServer cluster ... they are already added to the VRE scope. Is this VRE planning to use them or it needs dedicated instances?
@email@example.com could you please add any sub-ticket worth having?