Skip to main content
added 2 characters in body
Source Link
ulrich
  • 1.2k
  • 9
  • 24

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

My goal is to incorporate search results from the remote node and the local node into one single response.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.searchxml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

My goal is to incorporate search results from the remote node and the local node into one single response.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

My goal is to incorporate search results from the remote node and the local node into one single response.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

edited body
Source Link
ulrich
  • 1.2k
  • 9
  • 24

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

My goal is to incorporate search results from the remote node and the local node into one single response.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

My goal is to incorporate search results from the remote node and the local node into one single response.

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

My goal is to incorporate search results from the remote node and the local node into one single response.

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

My goal is to incorporate search results from the remote node and the local node into one single response.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

added 108 characters in body
Source Link
ulrich
  • 1.2k
  • 9
  • 24

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

My goal is to incorporate search results from the remote node and the local node into one single response.

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

On a GeoNetwork 3.0 node, I would like to search directly on another remote GeoNetwork node rather then harvest its data.

I can search on a local catalogue using the q-search service from the API.

In the docs from version 2.10 I found the hint, that there is an option remote, which should be used for searching on remote GeoNetwork catalogues when using the xml.search service.

I wonder, if this can be applied for the q-search service in the 3.x version. Is there any example how to achieve this or has anyone done something similar before?

My goal is to incorporate search results from the remote node and the local node into one single response.

Source Link
ulrich
  • 1.2k
  • 9
  • 24
Loading