Task #4913

Project WP #654: WP6 - Supporting Blue Economy: VREs Development [Months: 1-30]

Project Task #656: T6.2 Strategic Investment analysis and Scientific Planning/Alerting VRE [Months: 1-30]

Publish Geopolis imported data to geonetwork

Added by Panagiota Koltsida over 3 years ago. Updated about 3 years ago.

Status:ClosedStart date:Nov 07, 2016
Priority:NormalDue date:
Assignee:Panagiota Koltsida% Done:

100%

Category:Default
Sprint:WP06
Infrastructure:
Milestones:
Duration:

Description

Data that will be imported using the geopolis tool should be automatically published to the geonetwork.


Subtasks

Task #5660: Resolve conflicts in geoanalytics components between 'geo...ClosedEfthymios Theodorakopoulos


Related issues

Related to BlueBRIDGE - Task #1996: Integrate Geopolis with gCube Infrastructure Resource Man... Closed Dec 15, 2015

History

#1 Updated by Panagiota Koltsida over 3 years ago

As discussed during the last TCom meeting CNR can provide a library to achieve this task.
@fabio.sinibaldi@isti.cnr.it , could you please provide us with all the necessary information regarding this?

#2 Updated by Fabio Sinibaldi over 3 years ago

Hi,
the gcube library used to generate and publish GIS metadata is documented here https://wiki.gcube-system.org/gcube/GeoNetwork_library.
If you also need to publish your data onto GeoServer, you might want to use this other library instead (which uses Geonetwork_library to publish metadata) https://wiki.gcube-system.org/gcube/GIS_Interface.
Let me know if you need any clarification.

#3 Updated by Panagiota Koltsida over 3 years ago

Hi @fabio.sinibaldi@isti.cnr.it , it seems that the Geonetwork library is what we need.
Can you give me some more info or point me to a code snippet regarding the metadata publishment and how to login?

#4 Updated by Fabio Sinibaldi over 3 years ago

Hi,
these information are already available in the page https://wiki.gcube-system.org/gcube/GeoNetwork_library
Login mechanism is explained here https://wiki.gcube-system.org/gcube/GeoNetwork_library#Login_2 (basically you just use "public void login(LoginLevel level)" declared by "GeoNetworkReader" interface).
To easily generate metadata I suggest to use the GcubeIsoMetadataClass explained here (https://wiki.gcube-system.org/gcube/GeoNetwork_library#GcubeISOMetadata_class). Obviously it is possible to extend its behavior for specific needs.
Common usage snippets (such as publishing and querying) are provided in the last section https://wiki.gcube-system.org/gcube/GeoNetwork_library#Example_Code.

These should meet your needs, let me know if you have more questions.

#5 Updated by Panagiota Koltsida about 3 years ago

  • % Done changed from 0 to 40
  • Status changed from New to In Progress

Thanks @fabio.sinibaldi@isti.cnr.it for the information.
We are performing several tests on "devVRE" by providing some dummy metadata. Using the publisher we can retrieve the metadata back by using the ID, but if we go directly to geonetwork's page we cannot find them.
Is this normal?

#6 Updated by Fabio Sinibaldi about 3 years ago

Well,
when publishing in a certain scope, you use both dedicated user and group. This feature is used to map a scope oriented visibility on metadata.
(More information here : https://wiki.gcube-system.org/gcube/GeoNetwork_Configuration#Security_in_gcube_4.X)
If you try to search on geonetwork for the same metadata you need to login using a user which have read rights in the group the metadata has been published into.
A faster way to check the metadata existence in a scope is to use the geoexplorer portlet on the same scope, which (by using the geonetwork library) performs query using the current scope's user.

#7 Updated by George Kakaletris about 3 years ago

  • Related to Task #1996: Integrate Geopolis with gCube Infrastructure Resource Management added

#8 Updated by Panagiota Koltsida about 3 years ago

  • % Done changed from 40 to 90

The use of geonetwork library resulted to conflicts between the "geotoolkit" library used by the Geonetowrk library and the "geotools" library used by the geoanalytics components.
To resolve these issues all affected classes should be replaced by custom code which will use the "geotools" library.

#9 Updated by Panagiota Koltsida about 3 years ago

  • Status changed from In Progress to Closed

Also available in: Atom PDF