Difference between revisions of "5th TCom Meeting: 27th March 2013 Discussions and Notes"

From D4Science Wiki
Jump to: navigation, search
(Data Confidentiality)
(Geospatial cluster discussion)
Line 6: Line 6:
 
* the layer need to be then republished.
 
* the layer need to be then republished.
 
* Since the Geonetowrk was based on teh concept of workspaces, everything is under design to remove the workspaces.
 
* Since the Geonetowrk was based on teh concept of workspaces, everything is under design to remove the workspaces.
 +
 +
keywords in metadata?
  
 
Also WPS processes will be published on GeoNetowork ( also Statistical Manager algortithm)
 
Also WPS processes will be published on GeoNetowork ( also Statistical Manager algortithm)

Revision as of 16:09, 27 March 2013

Geospatial cluster discussion

Integration of the new library Geopublisher

  • actvitiy of integration is ongoing
  • the layer need to be then republished.
  • Since the Geonetowrk was based on teh concept of workspaces, everything is under design to remove the workspaces.

keywords in metadata?

Also WPS processes will be published on GeoNetowork ( also Statistical Manager algortithm)

publication part:

  • Aquamaps ( upgrade metadata with a script)
  • Timeseries
  • SPD.


Data Confidentiality

How to give access to the public to our layers ? seadanet is harvesting one on our Goeserver.

We should prioritize teh activity on publishing.

Geoserver is public while geonetowork is private.

What we should provide is to add accounting to Georserver/Geonetowor and the same for SPD.

VME-DB how can we give access to users of geonetowork according to the VREVirtual Research Environment.. maybe shibolett?

We can see another solution usign portal roles mapped to genetowork users.

Requirements to be discussed with Emmanuel.

Lino proposed then to have private and public maps ( an option given to the users)

Comparison tools with Aquamaps also to be implemented ( it's a requirement also from Nicholas) based on Statistical. ( Statistical should also be extended to take as inout a WFSWeb Feature Service).


first version would not be so integrated.